Hi there, I was wondering if anyone has any solutions to a problem I'm facing. We are trying to get a side-by-side upgrade of Server 2003 running SCCM 2007 R1 to Server 2008 R1 Running SCCM 2007 SP2 R2. After implementing this side-by-side upgrade the old client machines are not receiving the new client installation from the new SCCM 2007 R2 system. These are the general steps that I did to implement the upgrade: Installed a new Primary SCCM 2007 R2 on a new Server 2008 box Created address relationship between the new server (SHI) and old server (NEI) Created a child-parent relationship between the new and old primary sites (SHI is a child of NEI) Replicated all distribution points to the new site (SHI) and allowed for the collections to propagate from the parent to the child Promoted the child site to a central site, and then made the old server a child of the new site (NEI is not a child of SHI) Added the site boundaries to the new system SHI, and removed the site boundaries from the old site NEI On the all systems collection ran a Install Client action Note: both sites are running in mixed mode Now problem I am facing is the old primary site (NEI) has the 4.00.5931.0001 client installer and the new site (SHI) has the new client 4.00.6487.2000 installer. When I try and propagate the update to the client machines they are installing from the old site (NEI) and not the new one (SHI). Is there something I am missing to change the pointer of the MP and installer? Here are a few additional things to note: We do not utilize the ADM template for SCCM Client Pushes, nor have we implemented any for WSUS. The site codes appears changed in the ConfigMgr console on the new SHI system but when I perform a wmic /namespace:\\root\ccm Path SMS_LocalMP command the MasterSiteCode and SiteCodes are blank on the client machine. What we want to accomplish is: Updating the SCCM servers to the latest version and have all the managing systems run on Windows 2008 and not 2003 (hence why I chose to do a side-by-side upgrade and not an in-place upgrade) Move clients to new site code (SHI) De-commissioning the old site without losing any of the collections and packages to allow new server to function as the Primary site server.

Couple things here.... If I remember correctly (I don't have an SP1 site to look at) 4.00.5931.0001 is SP1 client and 4.00.6487.2000 is SP2 client. So while you are using the terms R2 and R3 as what you think changes the client version I think it's actually the SP level that's not the same. My site is 4.00.6487.2000 and I do not have R3 installed. Two simple approaches to fix this: 1. Upgrade the lower level site to the current SP and R revisions. 2. Use software distribution instead of client push to upgrade the clients. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|