Re: Unable to update site assingment

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

"Alan" <Alan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:31725400-79E7-4FA0-ACC4-9F9921B90C24@xxxxxxxxxxxxxxxx
> Thanks Steve, that is a good read! However I have some more question after
> reading the guide. My environment has AD but there are some workstations
that
> do not login to the domain but as a local administrator.
>
> 1. The SMS server do not extend the AD schema and does not reside on a AD
> server. No accounts have domain admin rights, does that mean that it
cannot
> register with an AD site?

It means that you will not be able to take advantage of the AD integration
that SMS 2003 offers.

> 2. The site boundaries are configured with IP subnets and not AD. I
assumed
> it is using WINS to resolve the IP of the management point. Given a site
code
> AHA, nblookup can't resolve AHA, although there is no error when changing
the
> site code in control panel. Now I want the problematic client to locate
the
> MP, do I add an entry of AHA to LMHOST file?

nblookup? you probably mean nslookup -- you'd want to enable a Server
Locator Point for your site. Register the SLP and the MP in WINS. Search the
Books online for SLP and WINS and you'll see how to do this (you'll use
netsh).

> "In a Windows Internet Name Service (WINS) environment, without Active
> Directory, the client must query the management point of the assigned
site.
> The client locates the IP address of a management point by doing a WINS
> lookup that is based on the site code. "

Exactly correct, although I'd add for safety and reliability, add the SLP to
WINS as well.

Steve


.

Relevant Pages

  • Re: Site Discovery
    ... says that in a WINS environment the client "could be presented with an XML ... SLP puts together the XML file, ...
    (microsoft.public.sms.admin)
  • Re: Push client no MP?
    ... >> entry and slp is enabled on the server. ... >> not find that directory on the client? ... >>> What do the client side logs indicate? ... >>> Steve ...
    (microsoft.public.sms.admin)
  • Re: MVPs and Terminal Services
    ... but the Printer group is in the Windows Client ... Keep in mind that Windows Server 2003 is almost three years old, ... a TS environment is widely frowned upon). ... Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • Re: MVPs and Terminal Services
    ... Printer group is in the Windows Client org not in the Windows Server org ... Keep in mind that Windows Server 2003 is almost three years old, ... a TS environment is widely frowned upon). ... Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • Re: Disaster Recovery Planning
    ... each requiring telephone activation which admittedly doesn't ... take long), after removing Dell '3rd party rubbish', updated the system ... matched to a corporate environment. ... as server and client OS probably need ...
    (microsoft.public.windows.server.sbs)