We are in the same process and the steps we do are.
1. Install SQL server 2012 SP1 CU on a new SQL server (we are moving from standalone to a cluster, so you need to do the SQL cluster process). 2. If you have reporting the one of the SQL server will be used to install the reporting role. 3. Install a new server with server 2012 for site server with wsus 2012, do not do any IIS or wsus config, do it only after the rename. 4. First we migrated SQL Steps given below 5. Then we moved for the site server migration (very important -WSUS registry setting you need to get this restored or after WSUS sync the content version will change to 0) *Steps for Central SQL Migration:-* 1. Stop all configuration Manager services. 2. Take a SQL backup for all sites. 3. Take a backup of CAS SMS registry key. (this is require if we have any issues with WSUS content version) 4. Restore CAS SQL backup on the SQL cluster. 5. Stop all configuration Manager services. 6. Start the site reset and point the SQL to new CAS SQL cluster. Check the Configuration manager setup.log from c:\ 7. Once the reset is successful then CAS will be in maintenance mode monitor SQL replication and rcmctrl.log till the site becomes active. *Steps for Central Site server Migration:-* 1. Copy the content from old server to new server SCCMContentLib and SMSPKGSIG 2. Take a SQL backup for all sites after replication active. 3. Take a backup of CAS SMS registry key and SCCMContentLib and SMSPKGSIG from CAS. 4. Start the CM backup for CAS. 5. Rename the old server 6. Rename the new build windows server 2012 server to same server (Install ADK, SQL 2012 client tools, WUS 2012). If you have WSUS on a remote server then only WSUS console. 7. Copy the content again to do any delta 8. Start the Setup from the Installation CD and do the site recovery using the CM backup. (using skip database restore option and re-install Site server). 9. Once the recovery is successful. You will need to remove and re-add the Site server name from SQL DB if not site comp will fail. Once all the components are installed we need to stop the WSUS Sync thread and restore registry value for HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\COMPONENTS\SMS_WSUS_SYNC_MANAGER from the backup to the new CAS server. 10. We need to stop the replication manager thread and restore registry value HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\COMPONENTS\SMS_REPLICATION_MANAGER from the backup to the new CAS server. 11. Once the Site is active and replication is green then we need to start the WSUS sync and monitor the WSUS content version across all sites. Hope this helps. Regards, / On Wed, Jan 29, 2014 at 9:59 AM, Andrew Berges <[email protected]>wrote: > Greetings All, (and apologies for the hugely long email) > > I plan to begin an upgrade to SP1 and R2 and plan on moving the primary > site (currently Windows Server 2008 R2) to new hardware (Windows Server > 2012). The primary site holds pretty much all the server roles (DP, MP, > SUP, FSP, Reporting Services), is the sole primary, and runs a local SQL > 2008 R2 SP2 instance. We have no secondary sites and no CAS, just remote > DP's with WDS enabled for PXE. In the process of this upgrade, I would > also like to upgrade SQL to 2012 SP1. > > I'm thinking the best way to accomplish this is to upgrade to SP1 on the > existing server, then backup the new SP1 instance, shutting down the old > server, renaming the new server, restoring the backup to the new server, > uninstalling SQL 2008 R2 on the new server, installing SQL 2012 SP1 on the > new server, and then applying CM 2012 R2. > > Here's the process I've got worked out in my head so far... if there's > someone that can think of any steps I've missed or details I might have > overlooked, I'd greatly appreciate any feedback. > > OLD SERVER: > > * Uninstall Windows AIK > * Install Windows 8 ADK > * Install WMF 3.0 > * Disable "Delete Aged Client Operations" site maintenance task > * Run prerequisite checker > * Create site backup > * Test DB upgrade > (would install KB2734608 here, but it's already installed) > * Remove boot images from DP's > * Disable Antivirus > * Upgrade Configuration Manager 2012 to SP1 > * Assuming successful upgrade: > * Create new OSD boot media > * Re-enable "Delete Aged Client Operations" and perform site backup > * Copy backup, application/package source location, and ReportServer DB > to new server > * Shutdown server > > NEW SERVER: > > * Rename server to same hostname as old server > * Add Roles: > * Background Intelligent Transfer Services > * Windows Server Update Services > * Add Features: > * .NET Framework 3.5 > * .NET Framework 4.5 > * IIS 6 Metabase Compatibility > * IIS 6 WMI Compatibility > * ISAPI Extensions > * Remote Differential Compression > * Windows Authentication > * Install SQL 2012 SP1 > * Install Windows 8 ADK > * Install Microsoft Deployment Toolkit 2012 Update 1 > * Run prerequisite checker > * Disable Antivirus > * Install Configuration Manager 2012 SP1 > * Restore site backup > * Restore ReportServer DB > * Raise compatiblity level of restored SQL databases to SQL 2012 > * Integrate Microsoft Deployment Toolkit 2012 Update 1 with Configuration > Manager > * Assuming successful server migration: > * Uninstall Windows 8 ADK > * Install Windows 8.1 ADK > * Install Microsoft Deployment Toolkit 2013 > * Integrate Microsoft Deployment Toolkit 2013 with Configuration Manager > * Disable Antivirus > * Upgrade Configuration Manager 2012 to R2 > * Create new OSD boot media > * Install KB 2905002 on server > * Install KB 2907591 on server > > Does this seem like a proper aproach to take? Am I missing any steps? > Anything else I should be considering? > > Thanks in advance, > > Andrew > >
