SCCM-Upgrading 2012R2SP1CU2 to 1511

Rate this post

Hi All,

today I upgraded my lab that was running SCCM 2012 R2 SP1 CU2 to 1511 build. these are my “notes from the field”

1- Download and Install KB3095113 (https://support.microsoft.com/en-us/kb/3095113) on all your WSUS/SUP Servers to add support for W10 via SUP
2- Download ADK for Windows 10 TH1 (http://download.microsoft.com/download/8/1/9/8197FEB9-FABE-48FD-A537-7D8709586715/adk/adksetup.exe). Make sure you download the TH1 version and not TH2 (for Windows 10 1511, and here is the why: http://blogs.technet.com/b/configmgrteam/archive/2015/11/20/issue-with-the-windows-adk-for-windows-10-version-1511.aspx)
3- Backup your USMT Windows 8.1 Folder
4- Backup your Boot Images
5- Uninstall ADK for Windows 8.1
6- Install ADK for Windows 10 (you only need to select Deployment Tools, Windows preinstallation Environment (Windows PE), Imagining And Configuration Designer (ICD), User State Migration Tool (USMT))
7- Reboot server
8- If you have console installed on the site server, remove any 3rd party extensions (you should not have it anyway)
9- Download SCCM Build 1511 (it is available via MSDN, Volume License, and Microsoft Evaluation Center)
10- Create a backup of your database via SQL
11- restore your backup on another SQL Server that meets the SQL requirement for SCCM
12- Use the testdbupgrade to see if you can upgrade the database without any problems (setup.exe /testdbupgrade ). if it fail, do not upgrade 🙂
13- Download SCCM Prerequirements (use setupdl.exe)
14- Start Build 1511 installation, the only difference is the Service Connection Point Setup. I installed it on the site server itself and the upgrade took just over 30min.
15- Some tasks may happen after the upgrade is completed, just be patient
16- open console and confirm that the console has been upgrade to version 1511 (console version should be 5.0.8325.1000)
17- go to monitoring->system status->component status and check the status (and just be patient, this may take a while to update from unknown to the correct status)
18- go to administration->site configuration->servers and site system roles and confirm the new role (service connection point) is there
19- on the console menu (same where you open powershell), select Usage Data and select the appropriate usage data you want to send to Microsoft. the default is Enhanced
20- go to administration->cloud services and confirm you see Updates and Servicing and a child node called Features
21- go to software library, you should see a new node called Windows 10 Servicing with All Windows 10 Updates and Servicing Plans
22- Import old boot images (the ones you have exported before the adk migration).
23- You may need to import new boot images (Windows 10 boot images). on my lab I had already created the Windows 10 images, so I assume the update will do it for you
24- go to administration->site configuration->sites. Select your site and click Properties. Confirm the site has been upgraded to version 5.00.8325.1000
25- go to administration->site configuration->sites. Select your site and click Hierarchy Settings and click Client Upgrade, to automatically upgrade clients and confirm that the version has been increased to 5.00.8325.1000
26- go to monitoring and confirm the new node Site Servicing Status
27- go to administration->site configuration->sites. Select your site and click Configure Site Components->Software Update Point. under classification, you should have the Upgrades available and under supersedence rules, you should have Run WSUS Cleanup Wizard (I would recommend you to find more info about this). you may need to sync your sup before the upgrades classification appear
28- go to administration->site configuration->client settings. open default client settings and see if Windows PE Peer Cache option exist
29- go to assets and compliance, you’ll see few new nodes that, like compliance settings->Windows 10 Edition Upgrade, compliance settings->Terms and Conditions, compliance settings->Conditional Access
30- reinstall any console extension that you may had (I’m against that, but people may have)
31- on every remote console, remove the extensions, update the console and re-install the extension. this is just to avoid any problem that may cause the console to crash
32- upgrade your clients. if the automatic client upgrade is checked, SCCM will do for you, otherwise you can create a package/program to do that, like old times…

now is where the fun starts…you need start testing your deployments, mainly your task sequences, to be sure that it is still work. you may need to change/update your TS to use the new boot images you imported before upgrading the ADK

Tags:

Recent Posts

Comments are closed.
%d bloggers like this: