I found that if you just reassign a client from the control panel applet then it is ok, but when you do it remotely it would fail. Even though the AD is correct.
However if you reassign the SMSSLP entry on the client first, then you can remotely reassign no problem. The SMSSLP is no longer used in 2012, the role is merged with the MP, but the entry in the registry remains. It may be that I had the SMSSLP parameter in the initial install command line for the POC site -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Dienstag, 15. Oktober 2013 15:57 To: [email protected] Subject: RE: [mssms] Reassigning CM 12 clients In 2012, client can get the trusted root key from AD so assuming that they have AD forest extended and you publish your site info in their forest, then you just need to send out a script to reassign them. J -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Brian McDonald Sent: Tuesday, October 15, 2013 7:33 AM To: [email protected] Subject: [mssms] Reassigning CM 12 clients Good morning, We recently acquired a new company Who has deployed as SCCM 2012 already into their environment. They have one primary site managing all clients. That would be the best approach to reassign these clients to our corporate HQ primary site? Thank you, Brian Sent from my iPhone
