Hello All, I have installed another primary site server in another location where clients already report to the only primary site server before the introduction of this new primary site server. Now, I need existing clients to report to the new primary site server. I tried manually putting the new primary site code to the clients but they it is failing. Am I missing anything? 1- What are the requirements to assign existing clients to the new site? What are the options? 2- What would be the impact of this reassignment of clients to the new primary site server? Thanks in advance.

That's covered in detail here: http://blogs.technet.com/b/configmgrteam/archive/2009/04/09/reassigning-a-configuration-manager-client-across-hierarchies.aspxJason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Thanks for the reply. Just confirming. 1- If we change the site code manually, it fails. But, when it is done through registry it changes. Is this normal behavior? 2- If we change the site code manually, shoud it change other than giving certificate error? 3- If we push the client to those machines on which we want to change site code, would it do the job? thanks in advance.

#1: No #2: the client should be reassigned to the new site then, but it's not able to talk to the MP because of the TRK #3: just try it (but if you can't wait to do that one minute task on your own: yes, it will work)Torsten Meringer | http://www.mssccmfaq.de

#1: No #2: the client should be reassigned to the new site then, but it's not able to talk to the MP because of the TRK #3: just try it (but if you can't wait to do that one minute task on your own: yes, it will work)Torsten Meringer | http://www.mssccmfaq.de

Thanks for the reply. If the client is giving error upon manual site assignment through client agent on the client machine then what would be causing it as I have only been able to solve it through push installation of the clients where I wanted to change the site code.

Examine the relevant logfiles in both scenarios and you'll get an idea for the reason why it's failing in one case.Torsten Meringer | http://www.mssccmfaq.de

Examine the relevant logfiles in both scenarios and you'll get an idea for the reason why it's failing in one case.Torsten Meringer | http://www.mssccmfaq.de