Hi guys, From here: Determine If You Need a Server Locator Point for Configuration Manager Clients Server locator points are used in a Configuration Manager 2007 hierarchy to complete client site assignment on the intranet and help clients find management points when they cannot find that information through Active Directory Domain Services. ... Install a server locator point if either of the following conditions applies: You have not extended the Active Directory schema for Configuration Manager 2007 or not all sites in the hierarchy are published to Active Directory Domain Services. You have workgroup clients or clients from another forest. Does this mean that for a workgroup-based server, if you specify a Management Point (SMSMP parameter) and site code (SMSSITECODE parameter), you don't really need an SLP? What purpose does the SLP serve if this is already specified on the command line at installation time? I think we feel a little uncomfortable allowing unauthenticated port 80 from the DMZ back into the intranet. Cheers.

No, if you are statically assigning the site code and MP, then you don't need an SLP.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Perfect -- just the answer I was hoping for :)

You will likely need an SLP if you intend to use the OSD feature though. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |

I went back and reviewed the documentation and consulted an insider (after being prompted by Torsten); the answer I gave above is wrong, sorry. Here is the answer I got back from the insider (Carol Bailey): "A server locator point is always required on the intranet if the client can’t access site information published to Active Directory – even if manually assigned."Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Thankyou, Jason! This was driving me nuts some weeks ago. I specified the MP and sitecode, and even added the SMSLP parameter, but still no joy. There were still log entries that the client was trying to validate the MP (and was only trying AD and WINS). Not good for clients without NetBT enabled. Even with SMSLP on the command line, it still wanted WINS to find the SLP. (Sorry, I'll have to try to dig out the logs or replicate the issue to be able to give you an exact quote from LocationServices.log. Yes, we are in mixed mode, not native.) And all the time I was thinking, "I shouldn't even need the SLP ... I've told it where the MP is." So you've solved one part of my mystery. (I should post separately about the other issue, that SMSLP parameter seemed to be ignored. And what's the point of publishing the MP to DNS, if the SLP is required and DNS can't be used for the SLP also?) Did Carol indicate whether they'll be updating the documentation? Darren

P.S. can we find out from some insiders why an SLP is required? Darren

It's needed because the client has to determine the version of the site before it can be assigned. That can be done by querying AD (well, not for workgroup clients of course) or using the SLP.

It is actually (kind of) documented: http://technet.microsoft.com/en-us/library/bb681005.aspx (under the Completing Site Assignment by Checking Site Compatibility section). I think that paragraph is a little "flaky" at best, but it is there.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys