Re: Client not assigned to site

From: Steve K. (this)
Date: 07/22/04


Date: Thu, 22 Jul 2004 22:56:33 +0200

Thanks Mike,

what is an SLP in Wins, I know Wins but I could find nothing about assigning
an SLP in there in the documentation. If this is all it takes then it easy.

So, what is SLP?

And, thanks for your help,

Steve K.

"Mike Church [MSFT]" <mchurch@online.microsoft.com> wrote in message
news:eQ8gGcAcEHA.1656@TK2MSFTNGP09.phx.gbl...
> Do you have an SLP configured and registered in WINS? If you left the
> installation command line to SITECODE=Auto then it will try to find an SLP
> to get a site name to install into, if there is no SLP then it will
install
> the client but not assign it to a site. If you change the Installation
> Properties in the Advanced Client tab of the Client Push Installation
> properties wizard to SMSSITECODE=<your site code> and run the push it will
> auto assign the client to the site you specify. The help on that tab
gives
> some more examples of command line paramiters that you can use on that
tab.
>
> --
> "This posting is provided AS IS with no warranties and confers no rights."
>
>
>
> "Steve K." <steve[remove this]@kitley.com> wrote in message
> news:e5ETsr8bEHA.2940@TK2MSFTNGP10.phx.gbl...
> > Hello,
> >
> > I installed a client through the client push installation wizard. It
> > installed just fine but I noticed the client did not have a site code
> > under
> > control panel - systems management. So, I added the site code for the
> > client.
> >
> > Now, in the SMS Admin console, under collections, Win2003 Servers, I
> > notice
> > that this client (Win 2003 Server) does not show up in the list as an
SMS
> > client. Furthermore, the client does not show up as being assigned to
the
> > site. This is strange. Where I have manually installed the client on
an
> > XP
> > workstation it has the correct information in the SMS Admin console
under
> > collections - XP as an SMS client and as being assigned to the site. I
am
> > wondering if whether I might have some type of communication problem or
> > misconfiguration here.
> >
> > Any help here would be greatly appreciated.
> >
> > Thanks in advance,
> >
> > Steve K.
> >
> >
> >
> >
> >
>
>



Relevant Pages

  • Re: Clients from previous SMS installs associated with wrong site
    ... environment and since you can add only one SLP to WINS we ... >> Central site has client records for machines that ... the central site has itslef as the SLP ... the installation properties for the ...
    (microsoft.public.sms.admin)
  • 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
    ... 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)
  • 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)
  • Re: Client push question - the plot thickens
    ... for clients within the site boundaries of a secondary site are disseminated ... If Client Push is enabled at that site then the ... SMS 2003 and Advanced Client push installation behavior. ... secondary site unless the secondary site has both initiated discovery of the ...
    (microsoft.public.sms.admin)