Re: SMS Site Code - Clients discovery
- From: "Heejae Lee [MSFT]" <heejael@xxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 17 Jan 2007 15:21:08 -0800
Also please check your other site FFD and the new site ABC have the
overrapping site boundaries.
Thanks,
Heejae Lee [MSFT/SMS Extreme Team]
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Kim Oppalfens <MVP>" <Kim dot Oppalfens@google mail.com> wrote in message
news:648DA9F5-3019-4FD2-A120-630F105344F3@xxxxxxxxxxxxxxxx
Restricting discovery to your ou can easily be configured in the discovery
methods.
As for clients auto-assiging to the wrong site, this means you have
overlapping site boundaries configured between your site, and the other
sms site. Overlapping boundaries is not supported.
In other words talk to the ffd* admin, and tell him to set his boundaries
correctly.
--
"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System SMS - MVP
"ALAL" <ALAL@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:386B9132-1D38-4A6E-BF76-050F2404EC4B@xxxxxxxxxxxxxxxx
Hi Kim,
indeed there is a machine named FFD* in another AD tree with SMS
installed.
I didn't knew.
Is there any way that I can restrict the SMS discovery only to my OU in
the
AD tree that my OU is? Discovery method in the SMS server is only to my
OU
but the clients search for the SMS code in the entire AD forest and they
discover the other site (in diferent tree)!
Like I said in my first post, even if I force my site code in the clients
they try to comunicate with the other SMS server!
Many thanks.
ALAL
"Kim Oppalfens <MVP>" wrote:
Has the ffd* machine existed in the past? Could it be that some
leftovers
are available in ad or wins?
--
"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System SMS - MVP
"ALAL" <ALAL@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9230F6C4-9E55-4000-816F-B9D1668CB592@xxxxxxxxxxxxxxxx
Hello.
I'm having a strange problem when configuring the clients.
After the setup of SMS server named LISSSMS01 (SMS version 2003 with
SP2)
and the SMS Admin configuration I run the network discovery. Please
note
that
I've not extended my AD schema and extending the AD is not an option.
I detect all the PCs from my OU in the AD. I deploy the Install Client
(Advanced Client). Then a strange thing happens. All the installed PCs
with
the Advanced Client discover a site with the code FFD and not the code
that
I've specified in the SMS setup (ABC). Even if I force my site code
(ABC)
another strange thing happens at the client. Checking for the logs in
the
client I see in CcmExec.log the following:
<![LOG[HTTP ERROR: URL=http://FFDSSMS01/ccm_system/request, Port=80,
Code=12007,
Text=ERROR_WINHTTP_NAME_NOT_RESOLVED]LOG]!><time="10:32:01.375+000"
date="11-02-2006" component="CcmExec" context="" type="1" thread="888"
file="ccmhttperror.cpp:121">
It atempts to check for the following server name FFDSSMS01 and not my
server LISSSMS01. Sounds like it is replacing the 3 first characters
LIS
to
FFD!
The machine FFDSSMS01 does not exists in the entire network!
Any ideias why this is happening?
I've run out of ideias.
Many thanks.
ALAL
.
- Prev by Date: Re: OK, I've switched to Advanced Security now what?
- Next by Date: Re: Delta distribution to clients when package was already downloaded
- Previous by thread: OK, I've switched to Advanced Security now what?
- Next by thread: Accidentally selected "Delete special"
- Index(es):
Relevant Pages
|
