Here are the steps that worked for me and my coworker Kevin:
- Shutdown all SMS services and set them to disabled. (Don't want to restart machine and make changes to SCCM)
- Upgrade SQL 2005 to SQL 2008 R2 on old machine.
- Shutdown all SQL services and set them to disabled.
- Backup up SCCM 2007 databases *.mdf and *.ldf files for SMS_001 (Check for file locations by right-clicking on SMS_001 in SQL Management Studio and clicking on file)
- Change computer name of the old computer to something like SCCM2 instead of SCCM
- Turn off old computer.
- Build Windows 2008 R2 64-bit on the new machine. Name computer name SCCM but keep in mind that all permissions that were set are now set for SCCM2 based on the SID.
- Install SQL 2008 R2.
- Install SCCM 2007 SP1. Reuse same Site ID and Site Name (as long as services are off on the old computer this should not have problems)
- Upgrade to SCCM 2007 R2 (match the version level of the old machine)
- Verify that everything installed correctly by logging into the Config Manger console.
- Shutdown all SCCM services temporarily.
- In SQL Management Studio change the name of the SMS_SiteCode database to something like SMS_SiteCode_new.
- Right-Click and attach the old database files that are in the same location as on the old SCCM computer
- We had permission problems on our c:\SQL_logs folder where the folder was set for read-only.
- If the new database looks attached correctly as SMS_SiteCode, then go ahead and start up all SCCM services
- You should be able to log into Config Manager now and see some errors about Active Directory permissions under SMS_Site_Component_Manager.
- Go to Active Directory Computers and Users
- Select "Advanced Features" under the View Menu
- Expand "System" object
- Right-click on "System Management" and choose Properties
- Note that the old SCCM computer will have full control permissions using the new computer name.
- Add the new SCCM computer which is called "SCCM" in my example and give it full control
- Right-click on "SMS-MP-SiteCode-SiteComputerName" and choose Properties
- Add the new SCCM computer which is called "SCCM" in my example and give it full control.
- Restart "SMS_SITE_COMPONENT_MANAGER" Windows Service.
We had a little bit of problems that had to be ironed out by running the Site Recovery and Repair tool. I also needed to copy the permissions for the local computer group onto the new server (i.e. SMS Admins)
We ran into a problem trying to change the computer name after installing Reporting Services but were able to fix it following this link.