Hi, These are the steps I did when we upgraded central server from OS win2003 to OS win2008r2 Except I did not know about Step 18 and 21 or 22 which caused the network access account to not work anymore or something like that http://support.microsoft.com/en-au/kb/2509330 basically what this article describes happened to us...
1. Build a new server with OS 2008 R2 Called <NewServerName>, with the same drive letters as the current server.(ensuring that it is as similar as it can be) 2. Ensure that all requirements for SCCM installation has been done (SQL, IIS settings, webdav and such) 3. Copy All the Packages source to the new server 4. Initiate a SMS back up of <CurrentSCCMServerName> server 5. Check that the backup was successful. 6. Copy back up to <NewServerName> 7. Back up Site Control file (preinst.exe /dump XXX) (XXX is our Primary site name) 8. Copy the Backed up site control file to the new server. 9. Disable SMS services on the <CurrentSCCMServerName> server 10. Rename <CurrentSCCMServerName> to <CurrentSCCMServerName>OLD 11. Shut server down 12. Rename <NewServerName> to <CurrentSCCMServerName> 13. Reboot server after rename 14. Make sure that System account has been added to the AD group that gives the other site servers admin rights to this one, and this to others 15. Restart the server to ensure that its has all the credentials. 16. Install SCCM to the same location as it was on the old server (G:\SMS) 17. Bring SCCM back up to the same Patch level as it was on the old server (SP2, R3, Same SCCM Patches) 18. SRVACCT backup for restoring after Recovery Wizard. 19. Add the AD group to the local groups that give other site servers admin rights to this one and other way around. (the AD group has all the SCCM site server's computer accounts as members) 20. Run the recovery Wizard pointing it to the Backup from the old server 21. Copy SRVACCT back to its normal spot from back up 22. Perform a site Reset ________________________________ MAGNUS TVETEN SERVER SUPPORT ENGINEER CO CITRIX/SERVER Insurance Australia Group Limited Lvl 1, 23 Lakeside Drive, Burwood Burwood East VIC 3151 Australia T +61 3 8804 3226 M +61 411 010 460 E [email protected] www.iag.com.au PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL. ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of ccollins9 Sent: Thursday, 9 April 2015 2:42 AM To: mssms Subject: Re: [mssms] RE: SCCM 2007 Migrate to new Hardware - I agree that migrating it to another server is a waste of time and you should go to SCCM 2012. But clearly that isn't your decision, so that advice is moot. Here are some answers to your question: Some of my questions surround the following: * In what order should the upgrade take place ? Primary Parent site first? I would use the backup/restore features of SCCM to move it to a new server. The server needs to have the same computer name. https://social.technet.microsoft.com/Forums/systemcenter/en-US/f7e88c60-1e7d-4a52-a7f4-3afaa7efa74f/moving-sccm-2007-to-a-new-server?forum=configmgrbackup https://technet.microsoft.com/en-us/library/bb632545.aspx https://kobile.wordpress.com/2010/10/10/moving-sccm-server-to-new-hardware/ * Can I go from X86 server OS to X64 server OS. YES * Physical to Virtual supported YES * Sql Server versions, do they need to be the same (2005) You can use a higher version of SQL, but you might need to run the database in the "mode" of the previous version of SQL. Standard and Enterprise support this. If you are using local SQL express on the SCCM server, just install the same version on the new server. * Drive configuration (Raid levels etc..) Just use what you normally use, SCCM doesn't have a requirement here, it's up to the admin. If you're going to a virtual server, then the backend storage is typically a SAN and should already be setup for RAID, etc. As far as drive specifics, just use the same setup on the old server, for example if SCCM is installed on C drive, then install it on C drive of new server. Personally, I follow the "old ways" and often install enterprise apps on a data drive other than C. * Are there any gotchas that I should be looking at? Server name needs to be the same. So, you would need to disjoin the old server from the domain, reset the AD computer account, then join the new server under that name, which could get you into trouble if for some reason the migration doesn't go well. But theoretically you should be able to just rejoin the old server as a rollback. I haven't done this tho, I'm sure some other people on this list can weigh in on that. On Wed, Apr 8, 2015 at 12:24 PM, Juelich, Adam <[email protected]<mailto:[email protected]>> wrote: I'd move to the newest of everything if you can. No point in going to 2008R2 being that it is nearing 7 years old. Server 2012 R2 ConfigMgr 2012 R2 SQL 2014 or 2012 R2 (Don't remember if there are any ConfigMgr snaffus with this....) ----------------------------------------------- Adam Juelich Pulaski Community School District<http://www.pulaskischools.org> Client Management Specialist 920-822-6075<tel:920-822-6075> On Wed, Apr 8, 2015 at 10:53 AM, Michael Mott <[email protected]<mailto:[email protected]>> wrote: Unless your limited by politics, I would go to a parallel scenario with one beef virtual server and get to CM12 ASAP. From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Enley, Carl Sent: Wednesday, April 08, 2015 11:43 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] SCCM 2007 Migrate to new Hardware - I have been approached with a project to migrate our existing SCCM 2007 R2 environment to new Server hardware. We are currently running on Server 2003 and need to get to 2008R2 before EOL in June\July. I suppose a in place upgrade is not supported? I have suggested time and time again that we should put our efforts into SCCM 2012 but Mgt has not made a decision and time is running out. We have 2 primary sites with about 5000 clients and I am looking for a brief outline of the steps required to perform this upgrade with no loss of data \ production services - patching, software distribution, reporting etc... Some of my questions surround the following: * In what order should the upgrade take place ? Primary Parent site first? * Can I go from X86 server OS to X64 server OS. * Physical to Virtual supported * Sql Server versions, do they need to be the same (2005) * Drive configuration (Raid levels etc..) * Are there any gotchas that I should be looking at? If anyone has performed this task before and you are willing to share some tips or outline the steps that you have taken I would greatly appreciate it. Thanks ________________________________ Legal Notice: This email is intended only for the person(s) to whom it is addressed. If you are not an intended recipient and have received this message in error, please notify the sender immediately by replying to this email or calling +44(0) 2083269015<tel:%2B44%280%29%202083269015> (UK) or +1 866 592 4214<tel:%2B1%20866%20592%204214> (USA). This email and any attachments may be privileged and/or confidential. The unauthorized use, disclosure, copying or printing of any information it contains is strictly prohibited. The opinions expressed in this email are those of the author and do not necessarily represent the views of 1E Ltd. Nothing in this email will operate to bind 1E to any order or other contract. _______________________________________________________________________________________ The information transmitted in this message and its attachments (if any) is intended only for the person or entity to which it is addressed. The message may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information, by persons or entities other than the intended recipient is prohibited. If you have received this in error, please contact the sender and delete this e-mail and associated material from any computer. The intended recipient of this e-mail may only use, reproduce, disclose or distribute the information contained in this e-mail and any attached files, with the permission of the sender. This message has been scanned for viruses. _______________________________________________________________________________________
