I have two domains from two different forest i,e domain 1 domain 2 . Both domains has two way trust relationship. Issue : Now the clients in domain 2 are not able to communicate to SCCM server ( not able to find out the MP ) even after SCCM client is installed. Receiving many errors from the log : Locationservics.log : " LSVerifySiteVersion: Failed to get Site Version from AD and SLP " Please suggest. Regards, Suman Vaddiparthi.

You must treat clients in alternate forest as workgroup clients: http://technet.microsoft.com/en-us/library/bb694003.aspx This has nothing to do with trusts because its not about security, its about server location. Thus you should add an SLP to the hierarchy and configure the client to use it at installation time.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

Thans Janson... To my understanding.... first we have to install the client on the machine and next add manually the Server Locator Point Information to WINS right? Once after we do the above steps can we manage the clients henceforth from SCCM console? Thank You in advance. Regards, Suman Vaddiparthi.

Order doesn't explicity matter although if the SLP doesn't exists before you install the client, there is no way for the client find it because it doesn't exist yet. Also, most folks don't use WINS anymore so the only option is to specify the SMSSLP public property on the command-line when installating the client. http://technet.microsoft.com/en-us/library/bb632435.aspx Although not explicitly listed in that article, SLPs are also used to verify that the client version matches that of the MP.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

Suman, You have a few steps out of order - but are on the right track. In the console of your primary site (or central site if you have a tiered site), install the Server Locator Point role. It is a "Role" that you will find under the site and server in the admin console. Once you install it - clients will be able to translate Site Codes and assignment by that role rather than AD or DNS publishing. The technical explanation is that it's a web page on the site server that the client communicates to and gets determines "Site code" assignment by passing in a few values like Subnet, or sitecode which return the servername.Install the clients in the remote domain. You should use the commandline like this: ccmsetup.exe SMSSLP=<Server> SMSSITECODE=AUTO. If you don't know the boundaries or arn't sure, you can also specify the sitecode manually: ccmsetup.exe SMSSLP=<server> SMSSITECODE=<sitecode>.If you have already installed the client, then you can simply go to the registry and manually enter the SLP. Do this by browsing in the registry to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM. Then edit (or create) the registry key SMSSLP. Type the Name or FQDN of the server you installed the SLP on. Then open the Configuration Manager applet in the control panel, then enter the sitecode or press discover. Then click OK.Lastly - if there are any firewalls in the other domain, make sure that the client's can communicate back to the server on the required ports. After this - you should be able to manage the clients! If the trust isn't in place properly - you may have to "approve" the clients in the console. This is easy, and after the client is installed - you will see it in the console as "Not Approved." Simply right click on the client and select Approve. Hope this helps!

Hello, I have followed the given steps mentions above. In my primary site the SLP role is already defined. And After installing the client with the above method, I can able to view the SLP server in the registry settings i.e HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM. However, when I am trying to discover the site code again it is giving the error msg 'LSVerifySiteVersion: Failed to get Site Version from AD and SLP" LSGetSiteVersionFromAD : Failed to retrieve version for the site 'xxxxxx' (0x80004005) Note : just for FYI... My primary DNS IP address is able to ping and the alternative DNS Server is showing Request time out. Is there any issue from this point.. Kinldy help me if I can try any other steps to resolve. I have some sever clients in domain 2 and my requirement is to manage those servers through SCCM server which is reside in the domain 1. Thank You in advance. Regards, Suman Vaddiparthi.

Suman, Just an FYI - if the client's are windows 7 64-bit, you will want to put the SLP key in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\CCM. I forgot to mention that in my previous post. Once you put the value in the key, you will need to restart the SMS Agent Host service. Then try the discover task again. If that still doesn't work, verify your clients can get to the SMS SLP website. On the client, open a web browser and browse to: http://<Servername>/sms_slp/slp.dll?site&ip=<Client Subnet> Ensure you enter the servername and the client subnet. You should get a website that comes up with an XML that tells site information. I found a quick UK technet blog which shows pictures and some examples of the SLP website for troubleshooting: http://blogs.technet.com/b/manageabilityguys/archive/2011/06/30/testing-slp-availability.aspx Hope this helps you more!

Side note: directly modifying the registry value for the SLP is unsupported. To my knowledge it works, but is not something Microsoft will recommend that you do.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

Thanks for keeping an eye on the details for me Jason! I think Microsoft officially supports the key now - it's been added to the technet documentation over the past few years (at least for imaging with computers in workgroup). http://technet.microsoft.com/en-us/library/bb693951.aspx I agree - if you are having issues though, it's always better to install or reinstall the client with the command line switches to ensure everything is working correctly!

Interesting. Guess it is supported :-) Not sure if I was just wrong (wouldn't be the first time) or if that got added recently.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

Suman, I believe I am understanding you now. You have 2 domains, with a Configmgr site installed. This means that you will NOT be able to use the "auto" discovery feature, since the client in domain 2 will ALWAYS find his assignment from AD first, and therefore not point to your Configmgr in Domain 1. SO - my recommendation is this. ON the client you want to reassign, uninstall the client and reinstall using this command line: ccmsetup.exe SMSSLP=<SLP in Domain 1> SMSSITECODE=<sitecode in Domain 1>. This should force the client to assign itself to the Domain 1 site even though his "auto" assignment would drive him to Domain 2's server. Hope this helps! We frequently have this situation in our test domain since we have a Configmgr test environment, but other application servers are there and we want the to go back to the production environment for patching. It does work - just remember auto assignment will assign it incorrectly since it pulls from AD. Hope this helps!

Huh? You totally lost us/me. You don't point a client at a console -- you can assign clients to primary sites but without knowing a lot more about what your hierarchy looks like and your end goal, not much can be said.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

It is a new requirement however, I came to know after getting into the logs and even I have tried installing the client using the ccmsetup.exe SMSSLP=<SLP in Domain 1> SMSSITECODE=<sitecode in Domain 1> However, it is still not able to resolve the primary site code. Please guide me if I am missing any point to notice or follow. Thank You.Regards, Suman Vaddiparthi.