Re: Clients from previous SMS installs associated with wrong site

Thanks but, not really what I am asking. My apologies if
I wasn't clear.

Let me restate, these sites are 'not' attached, so there
is no hierarchy ATM. Since we have only one WINS
environment and since you can add only one SLP to WINS we
made the future Central primary site server as the SLP to
WINS. The question remains since the sites are not
connected as parent - child yet, does the SLP from one
site have the ability to locate MP's from other sites, or
must they be connected first.

Thanks.


>-----Original Message-----
>The SLP role is seperate from the MP role. Defining it
at the higest site in
>the hierarchy is best practice and this will not impact
where you have MP's
>at that site or other sites. Someone might have also
added the MP role to
>this system however there is no dependency on this.
>
>
>--
>Richard Threlkeld
>Microsoft MVP - SMS
>http://myitforum.techtarget.com/blog/rthrelkeld/
>
>
>"uhprentins" <uhprentins@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message
>news:BDCEF853-78D5-43BF-89AC-
70ABF31EE8E4@xxxxxxxxxxxxxxxx
>>I have a question about client site issues in an
inherited SMS setup I am
>> trying to work with.
>>
>> Basically there are three separate primary sites ATM.
They are all
>> detached.
>> One SMS server per site with all roles. What is
intended to become the
>> Central site has client records for machines that
should exist only in one
>> of
>> the other sites. The boudary IP range (this is an NT
domain ATM, no AD
>> sites
>> to use...yet, but that will change soon) is set to the
correct subnet
>> however
>> machines are listed from subnets from the other two
sies.
>>
>> I am strugling to figure out firstly, some SMS
behaviors that I am not
>> clear
>> on which would probably explain what is happening.
>>
>> For example, the central site has itslef as the SLP
but like I said the
>> sites are detached, so therefore, would I be correct
in assuming that
>> although the SLP from the (planned to be )Central site
and all three MP
>> records are registered correctly in WINS and clients
seem to be locating
>> the
>> SLP, they can only get the MP for the central site
until the other sites
>> become attached (children) to the primary? That would
explain some things.
>> Additionally, the installation properties for the
Advanced Client from the
>> Central site have the smssitecode specified instead of
AUTO. Two
>> possibilities have struck me that either A.) the admin
had originally set
>> client push and set subnets on the central site so
that clients were
>> discovered from other sites and then redisabled those
subnets in network
>> discovery or B.) Same as above except that in a
previous installation of
>> SMS
>> 2003 (of which I understand there were 2-3 previous
installs and
>> reinstalls)
>> where clients possibly had the same site code setup
that exists now for
>> the
>> Central site.
>>
>> I had wanted to reinstall the client from the focus of
one of the other
>> (soon to be) child primary sites to attemot to see if
it would chenge its
>> site code to the correct site but I could not, the
client failed install
>> becasue the child primary wasn't running SP1 like the
Central and the
>> newer
>> client was already installed from the Central. CCM.log
shows them stopping
>> install even when the force upgrade is checked.
>>
>> Unfortunately I have no one to get any firsthand info
from the client's
>> engineers, the SMS admin is not available and will not
be for some time.
>> Any
>> insight or confirmation / correction about the above
would be appreciated.
>> My
>> primary concern is cleaning up as much as possible
without connecting the
>> children to the parent site, unless the benefits of
connecting them (like
>> auto discovery working from the SLP for example)
outweigh any concern.
>>
>> Thanks ahead of time.
>>
>>
>
>
>.
>
.

Relevant Pages

  • Re: site boundry problem
    ... This newsgroup handles SMS Installer related questions. ... > domainAdmin and have defined it in client push installation account,the ... > client cannot be installed from SMS in domain A to desktops in domain B. ... > SLP 194.225.13.253 specified on the command line, ...
    (microsoft.public.sms.installer)
  • Re: Client not assigned to site
    ... what is an SLP in Wins, I know Wins but I could find nothing about assigning ... an SLP in there in the documentation. ... If you change the Installation ... > Properties in the Advanced Client tab of the Client Push Installation ...
    (microsoft.public.sms.admin)
  • Re: Client not assigned to site
    ... Do you have an SLP configured and registered in WINS? ... If you change the Installation ... Properties in the Advanced Client tab of the Client Push Installation ... > workstation it has the correct information in the SMS Admin console under ...
    (microsoft.public.sms.admin)
  • Clients from previous SMS installs associated with wrong site
    ... I have a question about client site issues in an inherited SMS setup I am ... One SMS server per site with all roles. ... the central site has itslef as the SLP but like I said the ... Same as above except that in a previous installation of SMS ...
    (microsoft.public.sms.admin)
  • Re: SLP needed?
    ... You only needs an slp if your client installation method needs it (Login ... > We run SMS2003 with only Advanced Clients, which we install through Client Push. ...
    (microsoft.public.sms.setup)