Hi, We are in the process of rolling out an SCCM 2007 SP1 mixed-mode environment containing 1 primary site and several secondary sites. The AD schema has been extended and all SCCM sites are publishing to AD. All SCCM clients and servers are in the same W2K3 domain. SCCM clients are being deployed via an OSD task sequence using the SMSSITECODE=AUTO switch. Automatic site assignment is working OK in all sites except one secondary. Checking the LocationServices log for clients in this site, it appears that the clients are unable to get the info they need from AD: LSGetSiteVersionFromAD : Failed to retrieve version for the site 'CXD' (0x80004005) All of our SCCM sites are using AD DNS except two; one of these two is the site that is failing. These two sites, I believe, use some version of Linux DNS, but Im still trying to get more information on this. I dont have access to these so cant check logs etc. Ive found that the problem can be resolved by changing the DNS server address on the SCCM client from the Linux DNS to an AD DNS. The client can then access the SCCM info in AD that it needs and joins the site OK.Can anyone advise exactly what the SCCM client is querying DNS for when it tries to access the SCCM info in AD, or suggest what it is about the Linux DNS that might be causing the problem? Everything else on the client appears to be working fine - AD authentication, name resolution etc. Ive verified that the Linux DNS is successfully returning SRV records and records with underscores, but am not really sure what else to ask the DNS admin guys. Any suggestions would be much appreciated.Pierre

Were you able to figure out why is was happening? I am having the same issue...

Hi, To enableclients on the intranet to resolve the computer names of site systems to IP addresses, they can use either WINS or DNS. DNS is recommended because it provides better security, and it provides a robust distributed service.If you are using FQDNs for your site systems, DNS must be used to resolve the FQDN server names to IP addresses. In addition to name resolution, DNS might be required for clients to find their default Management Point if Configuration Manager is configured to publish to DNS.Allclients on the intranet need to locate the Management Points when they are first installed and on a regular basis. Intranet clients use Active Directory Domain Services as their primary method of service location. Regards, Jannes Alink | Please mark posts as Answered if appropriate.

Mlaxy said: Can anyone advise exactly what the SCCM client is querying DNS for when it tries to access the SCCM ...This should answer your question:http://technet.microsoft.com/en-us/library/bb632936.aspx

Torsten, I have a similar problem but to SetAssignedSite. It works if I execute locally inmy machine. But it fails (0x80004005) if I indicate another machine to change the site code. I'm using the script below: WMIC.EXE /node:@Machines.txt /namespace:\\root\ccm path sms_client CALL SetAssignedSite "L04" /NOINTERACTIVE Where Machines.txt is a simples text file with the name of a machines. It works if the machines is my onw one, but not for another one. Please, if you can help, please contact me at pierre.satiro@hsbc.com.br. Any idea?