I have Central site in one Forest and Primary site Servers in multiple forests. There is no trust between the forests. The site is running in MIXED mode. Here is the link about Serve Locator Point. http://technet.microsoft.com/en-us/library/bb693467.aspx You need only one server locator point for the Configuration Manager 2007 hierarchy, even if you have multiple sites. In a multi-site hierarchy, install the server locator point in the central site. If you install a server locator point in the middle of the hierarchy, it will have no knowledge of sites above it in the hierarchy. 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. Question Does this hold good - only single SLP needed even if there is no trust between the forests. I have following problem When I use in the client properties ccmsteup SMSSLP= <Central Site Name> (in Forest A) SMSMP=<Primary Site Server> site code DBA (in Forest B) the clients are not getting the site assignment. I see the following error in the Location Services log of the client Sending Fallback Status Point message, STATEID='500'. LocationServices 4/7/2011 3:15:41 PM 2680 (0x0A78) Failed to send status 500 to the FSP (8004027E) LocationServices 4/7/2011 3:15:41 PM 2680 (0x0A78) Processing pending site assignment. LocationServices 4/7/2011 3:15:41 PM 2680 (0x0A78) Assigning to site 'DBA' LocationServices 4/7/2011 3:15:41 PM 2680 (0x0A78) LSVerifySiteVersion : Verifying Site Version for <DBA> LocationServices 4/7/2011 3:15:41 PM 2680 (0x0A78) Retrieved SLP [Central SITE FQDN] from Registry LocationServices 4/7/2011 3:15:41 PM 2680 (0x0A78) Failed to resolve 'SMS_SLP' to IP address from WINS LocationServices 4/7/2011 3:15:46 PM 2680 (0x0A78) LSGetSLP : Failed to resolve SLP from WINS, is it published LocationServices 4/7/2011 3:15:46 PM 2680 (0x0A78) LSGetSLP: Successfully discovered SLP(s) for Lookup LocationServices 4/7/2011 3:15:46 PM 2680 (0x0A78) [CCMHTTP] HTTP ERROR: URL=http://<Central SITE FQDN>/sms_slp/slp.dll?site&sc=DBA, Port=80, Protocol=http, SSLOptions=0, Code=0, Text=CCM_E_BAD_HTTP_STATUS_CODE LocationServices 4/7/2011 3:15:46 PM 2680 (0x0A78) Raising event: instance of CCM_CcmHttp_Status { DateTime = "20110407191546.342000+000"; HostName = "Central SITE FQDN"; HRESULT = "0x8004027e"; ProcessID = 428; StatusCode = 401; ThreadID = 2680; }; LocationServices 4/7/2011 3:15:46 PM 2680 (0x0A78) LSGetSiteVersionFromSLP : No site version returned from SLP for site <DBA> LocationServices 4/7/2011 3:15:46 PM 2680 (0x0A78) LSVerifySiteVersion: Failed to get Site Version from AD and SLP LocationServices 4/7/2011 3:15:46 PM 2680 (0x0A78) Sending Fallback Status Point message, STATEID='608'. LocationServices 4/7/2011 3:15:46 PM 2680 (0x0A78) On the Central Site IIS logs I have the following error 2011-04-08 20:55:53 x.x.x.x GET /sms_slp/slp.dll site&sc=DBA 80 - x.x.x.x SMS+CCM 401 3 5 187 Note : - If I install the SLP on the Child Primary Site in Forest B client assignment completes successfully and works fine. But Per documentation I need only one SLP in the hierarchy.

[CCMHTTP] HTTP ERROR: URL=http://<Central SITE FQDN>/sms_slp/slp.dll?site&sc=DBA, Port=80, Protocol=http, SSLOptions=0, Code=0, Text=CCM_E_BAD_HTTP_STATUS_CODE The SLP is not working, that's why site assignment does not work.Torsten Meringer | http://www.mssccmfaq.de

1. You can install the server locator point in either forest. 2. Make sure that you have name resolution between the two forests - so that client can resolve the name i.e. SLP. 3. If there is no trust between the client domain and the site server's domain, you will need a network access account for these clients to access distribution points. See How to Configure the Network Access Account. 4. When you install these clients, they require a server locator point to complete site assignment. Make sure that the server locator point is installed and that these clients can access it - and the easiest way to do this is to use the SMSSLP property when you install the client. For more information, see How to Create a Server Locator Point in Configuration Manager and How to Specify the Server Locator Point for Configuration Manager Client Computers. For more information Click here -- Thanks, Vinayak-- Vinayak Sharma

1. You can install the server locator point in either forest. 2. Make sure that you have name resolution between the two forests - so that client can resolve the name i.e. SLP. 3. If there is no trust between the client domain and the site server's domain, you will need a network access account for these clients to access distribution points. See How to Configure the Network Access Account. 4. When you install these clients, they require a server locator point to complete site assignment. Make sure that the server locator point is installed and that these clients can access it - and the easiest way to do this is to use the SMSSLP property when you install the client. For more information, see How to Create a Server Locator Point in Configuration Manager and How to Specify the Server Locator Point for Configuration Manager Client Computers. For more information Click here -- Thanks, Vinayak-- Vinayak Sharma

Thanks Torsten. How can I find the SLP is working. After installation I checked the smsslpsetup.log. Found that the installation completed sucessfully. Service has started successfully. The sitecomp.log SLP Configuration for <Central Site> is correct. SMS_SITE_COMPONENT_MANAGER 4/8/2011 6:12:30 PM 2544 (0x09F0) Installing Security settings on site system ... SMS_SITE_COMPONENT_MANAGER 4/8/2011 6:12:30 PM 2544 (0x09F0) Security settings are up to date for <Central Site>. SMS_SITE_COMPONENT_MANAGER 4/8/2011 6:12:30 PM 2544 (0x09F0) Publishing <Central Site> as an SLP into Active Directory. SMS_SITE_COMPONENT_MANAGER 4/8/2011 6:12:30 PM 2544 (0x09F0) SLP Class SMS-SLP-CEN-<Central Site>doesn't exists. Creating SMS_SITE_COMPONENT_MANAGER 4/8/2011 6:12:31 PM 2544 (0x09F0) SMS-SLP-CEN--<Central Site> could not be created, Win32 error = 5. In the Central Site component status SMS_SERVER_LOCATOR_POINT is green. I am still working with AD team to provide access to the system container for the <Central Site>computer account to publish the information. Is this the reason for the client request access being denied and site assignment is failed? Thanks for your help. Sri

Thanks Vinayak for the reply. If I install the SLP on the Child Primary Site in Forest B client assignment completes successfully and works fine. But Per documentation I need only one SLP in the hierarchy. I would like to add to this that I need to install SLP in every forest. Then only the clients in that forest are able to complete the site assignment. If I do it on Central and initiate the installation in other forest the site assignment fails. I do have 3 forests. I instaledl the SLP in all these forests on the child Primary. But per documentation I need only one. Per documentation I would like to install SLP on Central. Need some help on this. Is something is missing here? 2. Make sure that you have name resolution between the two forests - so that client can resolve the name i.e. SLP. I am able to resolve the SLP name with FQDN in the Central Site where SLP is installed from the client. Sri

Hi, Did you point the client to the SLP when you did the installation? You can use a command like this for that: Ccmsetup.exe /MP:FQDN_ManagementPoint /retry:1 SMSSLP=FQDN_ServerLocatorPoint SMSSITECODE=AAA DNSSUFFIX=contoso.local SMSDIRECTORYLOOKUP=WINSPROMISCUOUS CCMLOGLEVEL=0 If you don't want to specify the command you need WINS.Follow me through my blog and Twitter!

Thanks for the reply James In the commnad line I provided the SMSMP=<FQDN_Managementpoint>. Here is the command line which has been used for install CCMSETUP.EXEC /noservice SMSSLP=<FQDN_CentralSiteName> FSP=<FQDN_PrimarySiteServer> SMSMP=<FQDN_ManagementPoint> SMSSITECODE=DBA (PrimarySiteServer in Forest B). 2011-04-08 20:55:53 x.x.x.x GET /sms_slp/slp.dll site&sc=DBA 80 - x.x.x.x SMS+CCM 401 3 5 187 This is from the IIS log of SLP in the Central Site which is in different Forest (Forest A). When I open the page from the client http://<Central SITE FQDN>/sms_slp/slp.dll - I get access denied error. Is this any security issue? Thanks. Sri

I always use the commandline as specified. Please try it with that one.Follow me through my blog and Twitter!