Kakemonstre Posted May 14, 2012 Report post Posted May 14, 2012 Hi ,i'm trying to install the client on the site server ,the client installs ,but it can't locate its MP(MP is on another server). I have 2 other server in the same subnet where Push install works fine(Boundery is OK) ,Firewalls are disabled. This CM12 site does not publish to AD. This seems to be a problem only on the site server. This is from the location.log: Processing pending site assignment. Assigning to site 'C01' LSIsSiteCompatible : Verifying Site Compatibility for <C01> Retrieved lookup MP [MP.FQDN.COM] from Registry Attempting to retrieve lookup MP(s) from AD No lookup MP(s) from AD Attempting to retrieve lookup MP(s) from DNS Using default DNS suffix FQDN.COM Attempting to retrieve default management points from DNS Found DNS record of MP.FQDN.COM port 443 Lookup Management Points from DNS: Name: 'MP.FQDN.COM' HTTPS: 'Y' ForestTrust: 'N' Retrieved lookup MP(s) from DNS LSGetSiteVersionFromAD : Failed to retrieve version for the site 'C01' (0x80004005) Retrieved lookup MP [MP.FQDN.COM] from Registry Attempting to retrieve lookup MP(s) from AD No lookup MP(s) from AD Attempting to retrieve lookup MP(s) from DNS Using default DNS suffix FQDN.COM Attempting to retrieve default management points from DNS Found DNS record of MP.FQDN.COM port 443 Lookup Management Points from DNS: Name: 'MP.FQDN.COM' HTTPS: 'Y' ForestTrust: 'N' Retrieved lookup MP(s) from DNS LSIsSiteCompatible : Failed to get Site Version from all directories Won't send a client assignment fallback status point message because the last assignment error matches this one. Any idea? Quote Share this post Link to post Share on other sites More sharing options...
Eswar Koneti Posted May 15, 2012 Report post Posted May 15, 2012 did you check if the site attributes are published to AD ? did you extend schema ? what does hman.log says ? also check site published to AD forest is selected or not ? also ensure to provide full permission to system management container .... Quote Share this post Link to post Share on other sites More sharing options...
Kakemonstre Posted May 15, 2012 Report post Posted May 15, 2012 This site does not currently publish to AD in fear of interfering with my CM2007 site. I push the client with the SMSSITECODE= FSP= AND SMSMP= parameters. hmman.log looks fine ,no errors or warnings. Quote Share this post Link to post Share on other sites More sharing options...
Eswar Koneti Posted May 16, 2012 Report post Posted May 16, 2012 try publishing the Attributes to AD since it wont cause any effects unless you have common boundaries and try it out. Quote Share this post Link to post Share on other sites More sharing options...
Kakemonstre Posted May 16, 2012 Report post Posted May 16, 2012 It works when i publish to AD. had 2 more servers showing the same problem as the site server ,so i ended up publishing to AD. Just think it's strange that some servers manage to install the client just fine ,while other servers on the same vLan require site info to be published to AD. Quote Share this post Link to post Share on other sites More sharing options...