Re: subnet inclusion in the AD site boundary is not being seen by

Tech-Archive recommends: Speed Up your PC by fixing your registry

As Kim said, if they are not in AD they have no AD site...
"Phillip McIntosh" <PhillipMcIntosh@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:EB9645FB-07F2-416B-8475-7CE8DAD44A06@xxxxxxxxxxxxxxxx
SMS client is on a server that is not in AD.
We have NT4 standalone servers, Win2k standalone servers, W2k servers in
Win2k AD Forest (seperate to 2003 AD Forest), Win2003 standalone servers and
Win2003 serevrs in 2003 AD Forest.

We are trying to manage all of these from a single SMS 2003 infrastructure.

The SMS DB, MP, DP servers etc. are all Win2003 servers in the 2003 AD Forest.

The configuration is working well so far except for two instances where
standalone Win2k servers can't find their SMS site until we add their IP
subnet to the SMS site boundaries - even though their subnet is already part
of the SMS site boundaries due to the fact that it is define in the AD site
boundary that is far of the SMS site boundary.

I originally thought that it may be an issue due to the SMS client being a
Win2k standalone server and hence it not knowing anything about AD let alone
a subnet defined in the AD Site definition. However, there are 50+ other
servers in the same situation and they all function correctly.

Bizarre!!




"Todd Hemsell" wrote:

> Not sure if you have done it or not but lets verify the machine hosting the sms client is in the correct ad site
> If you look in the reg key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ Netlogon\Parameters youo will see the current AD site for the server.
> Need to make surethe client thinks he is in the correct site. Now that I think of it you should see the AD site in the locationservices.log in the client logs directory..
>
> Have a look at that logfile and see if there are any errors and verify the client thinks he is on the same AD site you think he is on.
> "Phillip McIntosh" <PhillipMcIntosh@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:6F7817C7-9E00-418A-8F77-B970C93617A1@xxxxxxxxxxxxxxxx
> Sorry, may not be using the correct SMS terminology. Let's try again.
>
> The servers have had the SMS Advanced Client manually installed on them but
> they do not appear in any of the collections on the SMS Console.
> On the client itself, when you click the "Discover" button (Advanced Tab) it
> cannot find the SMS site hence doesn't return any SMS site code.
>
> As soon as we manually add the explicit subnet to the SMS site boundaries
> (as opposed to having it included via it being part of the AD site
> definition) then the SMS site is discovered and the sever then appears in the
> collections.
>
> Hope that makes it clearer.
>
> Phil
>
> "Todd Hemsell" wrote:
>
> > Phillip,
> >
> > what discovery mechanism are you using? I would guess netowrk discovery.
> >
> > You say that the machines are not DISCOVERED until you add in the subnet? does that also mean that if you manually installed the client then these machines could not get a site code? or does it mean exactly what you said, that they are not discovered.
> >
> > Not sure about being discovered but they should certainly function based on AD site alone..
> >
> > This is very interesting..
> >
> > Todd
> >
> >
> > "Phillip McIntosh" <PhillipMcIntosh@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:855EB7FD-8613-45CC-B1AB-FA8304AEA763@xxxxxxxxxxxxxxxx
> > SMS2003 SP2
> > Advanced SMS Clients on Win2k server SP4, 2003 SE SP1 & R2 , 2003 EE SP1.
> >
> > Twice now we have had servers (not in AD) that weren't discoverable to SMS.
> >
> > They were located on subnets which weren't specifically defined in the SMS
> > Site Boundaries however the subnet was defined in the AD site which IS
> > defined in the SMS Site Boundaries
> >
> > When we explicitly defined the subnet in the SMS site boundary the servers
> > were discoevred by SMS straight away.
> >
> > Any idea why the subnet inclusion in the AD site boundary is not being seen
> > by some non AD Advanced SMS Clients?
> >
Quantcast