Side by Side Client Migration
Hello All, I am doing a Side by Side SCCM migration to new hardware in my test lab. The goal is to upgrade my current SCCM Server running on Windows 2003 to X64 server, and SQL 2008 r2. i will list my steps followed by my question regarding moving client to the new system. I prefer thsi method over a system restore to new hardware. Here are the steps I followed. I will get this another dry run next week to get the step in order before moving to production. Please let me know if I miss or did something wrong or asking for problems. 1. Install SCCM 2007 r3 on Windows 2008, with SQL 2008 R2. 2. Attach new server to my current W2k3 SCCM site as a child site with no boundaries. 3. Let objects replicate, packages, advertisements showed up with locks on my new system. The new site also appeared in my W2k3 console. 4. Removed boundaries from my original W2k3 site server, and added the boundaries to my new W2k8 Site server. 5. On my original site server under site management properties. I uncheck publish this site in AD 6. Also deleted the old server site code from the system container then I removed the parent child communication on both site servers. The new cite server is a central site the old server is still running but not publishing anything in AD. 7. On my new site server the locks removed after I rebooted the server. I saw a few docs on how to remove the locks and was prepared to do that but a reboot removed them. 8. I used a script to update the site code on one client to test my script. The client appeared in my console on the new server long before the othe clients did. 9. The other client appeared unassigned in the console on my new site server. I'm not sure if these are the correct in order steps but my new site server site status is health and my question is why do the client show with the site code by not assigned. My concern is that I would have to redeploy the client installation to 1k in my production environment again? Thanks ConfigAdmin
January 20th, 2011 4:04pm

Why would you do a side by side just to upgrade the OS? Just install and restore from your SCCM backup. That's way easier. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|
Free Windows Admin Tool Kit Click here and download it now
January 20th, 2011 4:24pm

I need to change the name of the SCCM server to fit with our new server naming convention. Also I thought this would be a easy approach. Since I need to upgrade the database from SQL 2005 to SQL 2008 R2 which we plan to host in a cluster. I'm still wondering why all client show up unassign when they show up in the new server.
January 20th, 2011 5:25pm

you can change SQL versions in a restore but not server names. Personally I'd rather save client history etc than to deal with a side-by-side. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|
Free Windows Admin Tool Kit Click here and download it now
January 20th, 2011 10:48pm

That is good to know that I can change the SQL version during a restore. The only thing that concerns me about a side by side migration. Let say if I had 10,000clients to migrate using GPO to re-install the client could be a major problem. You know bandwith and the fact that I have no control if all client logon at the same time. I only have 1000 clients and reinstalling the client is not so bad the client installation is not to big.
January 20th, 2011 11:19pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics