Remember to remove WSUS before upgrading OS’s. 2008 had an older version of WSUS that has changed in 2012.
Microsoft said at one time that if you don’t you will have to start over. Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 From: Patton, Uriah Allen<mailto:urpat...@iu.edu> Sent: Thursday, May 4, 2017 3:16 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] RE: SCCM 2012 to CB upgrade Yeah, I followed the online info I found. I’m just hesitant about doing two full OS upgrades. Thanks, Uriah Patton IT Support "It gives patience, to listen to error without anger.” -Gandalf From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Kent, Mark Sent: Thursday, May 4, 2017 2:15 PM To: mssms@lists.myitforum.com Subject: [mssms] RE: SCCM 2012 to CB upgrade Did close to just that. Upgraded from Server 2012 to 2012R2. Upgraded SCCM from 2012 to CB 1610. This was done in December. And just yesterday upgraded SQL from 2012 to 2016. There is good guidance online for everything. Mark Kent Manager, Client Systems Engineering Technology Support Services Resources for Information, Technology and Education (RITE) http://rite.buffalostate.edu<http://rite.buffalostate.edu/> From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Patton, Uriah Allen Sent: Thursday, May 4, 2017 1:27 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com>; Patch Management Mailing List <patchmanagem...@listserv.patchmanagement.org<mailto:patchmanagem...@listserv.patchmanagement.org>> Subject: [mssms] SCCM 2012 to CB upgrade I’m currently in the process of upgrading my SCCM 2012 R2 sp1 install to SCCM CB. Thus far I’ve upgraded to 1610 with little problem. However I cannot upgrade to 1702 because I am running Server 2008 R2 with SQL 2008. My question is; What are everyone’s thoughts on upgrading the server operating system and the SQL install for the purpose of bring my SCCM up to 1702? I have created a process that works using my test environment (an almost perfect mirror of production) and my test environment seems to be running ok for about a week now. I would rather not bring up a new server and completely re-create my SCCM environment if I can help it. Below is essentially the process I used in my test environment. 1. Upgrade server OS to Server 2012 (it sucks that I cannot upgrade to server 2016 from server 2008) 2. Upgrade SQL to 2016 (worked surprisingly well) 3. Upgrade server OS to Server 2016 4. Upgrade SCCM to 1702 Obviously there are a few things in between but that’s the heart of it. What are everyone’s thoughts on the full upgrade process? Has anyone done this kind of upgrade before? Thanks, Uriah Patton Systems Administrator IU School of Medicine Department of Pediatrics "It gives patience, to listen to error without anger.” -Gandalf
