SCCM 2007 - new Sitecode, update clients
Hello,
i would like to know what steps i have to do when i replace my single sccm server with another sccm server. I want to do this, because sccm2007 on 2008r2 with sql2008r2 seems to raise problems if i think of the reporting services or wds. Now i replaced the
server with a 2003 standard server, sccm 2007 and sql2005 sp4. Everything seems to be fine, but now i would like to know how the clients get the new sitecode? When i start a push-installation of the client for the whole domain, does this update the clients
with the new sitecode?
Many thanks
Olaf
July 23rd, 2011 11:15am
ConfigMgr works fine on server 2008 and SQL 2008 (see
http://technet.microsoft.com/en-us/library/ee344146.aspx for the exact requirements). I would not install OS and SQL versions that are not the current ones.
Reassigning clients to other hierarchies might cause problems with the trusted root key. A push with RESETKEYINFORMATION=TRUE takes care of that. Also make sure that the system management container is cleaned up.Torsten Meringer | http://www.mssccmfaq.de
Free Windows Admin Tool Kit Click here and download it now
July 23rd, 2011 11:56am
ConfigMgr 2007 SP2 also works fine on Server 2008 R2 and SQL 2008 R2. The false error message that is sometimes encountered on the SSRS Reporting Point is fixed by installing the latest SQL Server CU.
Installing an almost 10 year old OS is not a very idea IMO.
Here's an article about reassigning clients:
http://blogs.technet.com/b/configmgrteam/archive/2009/04/09/reassigning-a-configuration-manager-client-across-hierarchies.aspx.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
July 23rd, 2011 9:02pm
Thanks for your answers. Can you tell me, how I can initiate a push with RESETKEYINFORMATION=TRUE? So a Push-Installation of the sccm-client for all clients does not update the key information, right? I also think that a ten
year old os is not the best solution, but the rest of our infrastructure consists of only 2003 servers, also the DC. We want to migrate the whole infrastructure til the end of the year and then use 2008R2 servers. So i thought i can "freeze" the 2008 sccm
(vm) and start it again when the migration process is finished
Free Windows Admin Tool Kit Click here and download it now
July 24th, 2011 4:07am
Just enter that parameter here:
http://technet.microsoft.com/en-us/library/bb633205.aspxTorsten Meringer | http://www.mssccmfaq.de
July 24th, 2011 5:29am
i face this issue before i changed sitecode only and the client detected the new sidecode
may be some client hang and not detected the new one so you can do it manual from control panel in client
configuration manager - Advanced - Configure Settings - DiscoverMohamed Abd Elhamid Abd Elaziz Microsoft System Administrator Abdul Samad Al Qurashi Co.
Free Windows Admin Tool Kit Click here and download it now
July 24th, 2011 6:41am


