Microsoft has recently released 1710 version of SCCM. Keep in mind this is an In-console update, not a baseline version. You can upgrade to 1710 only from SCCM version 1610,1702,1706. If you have to do a fresh setup of SCCM. Then first you need to install SCCM using Baseline version 1702, once installed – 1710 can be installed as In-Console update.
You must install the In-console update on Central site, once completed, Primary sites will automatically upgrade to 1710 as well. For Secondary sites, you need to do it manually through Console.
For fresh installation of SCCM, you require baseline version
If you are installing a new SCCM server, you cannot directly install 1710 version. You need to first install SCCM Current Branch through Baseline Version ( SCCM 1511 or 1606 or 1702, as 1511 or 1606 is already End of life, so only option remaining is 1702). Baseline version means complete setup of SCCM source in the form of ISO which can be downloaded from your enterprise Volume Licensing Service Center (VLSC) or MSDN Subscription. Once installed, you can upgrade to 1710 through In-console update.
New features included in SCCM 1710
- Peer Cache – This is no longer a pre-release feature, which means you can now use this feature without any doubt.
- Cloud distribution point support for Azure Government Cloud
- Improvements for Run Scripts
- New mobile application management policy settings
- Add child task sequences to a task sequence
- Software Center customization
- Surface driver updates – This is no longer a pre-release feature.
Checklist for SCCM 1710
- ADK (Windows Assessment and Deployment Kit) – You must have ADK 1703 or later (ie ADK 1709 as a latest). You must uninstall the old ADK version and install the latest version. If you don’t do this, your existing boot image will lose the ability to add the drivers as drivers node will be missing under boot image property. Installing latest ADK will install update the latest version of WinPE. For your reference sharing the screenshot of old & new boot image for your reference:
Boot Image 15063 was installed as part of ADK 1703 while Boot Image 16299 was installed as part of ADK 1709. Now with new feature of SCCM starting with 1706, you can update your old WinPE boot image to the latest one by right click “update distribution Point” and selecting option “Reload this boot image with the current Windows PE version from the Windows ADK”
This will update your existing Boot Image version from 15063 to latest version 16299.
For more details you can visit: https://docs.microsoft.com/en-us/sccm/core/plan-design/configs/support-for-windows-10#windows-10-adk
- Ensure your all sites run a version of SCCM that supports update to 1710.
- Review the site and hierarchy status and verify that there are no unresolved issues
- Review file and data replication between sites
- Install all applicable critical updates for operating systems on computers that host the site, the site database server, and remote site system roles
- Disable database replicas for management points at primary sites
- Set SQL Server AlwaysOn availability groups to manual failover
- Disable all site maintenance tasks at each site for the duration of the update installation on that site:
- Backup Site Server
- Delete Aged Client Operations
- Delete Aged Discovery Data
For more details go to:
Support for Windows 10
Following Windows 10 versions are supported for various SCCM versions:
Open SCCM Console, click on Administration Tab, go to Overview > Updates and Servicing. On right Pane you will see “Configuration Manager 1710”.
Right click it and download the update. Update will be download as cab file under following location and can be verified using log file dmpdownload.log
Once downloaded it will extract the content with same name folder as cab file.
Run Prerequisite Check
Once update is downloaded, right click “configuration Manager 1710” on console and select “Run Prerequisite Check”. Check the log file c:\ConfigMgrPrereq.log for success / failure.
Right click “Configuration manager 1710” and click on install.
Select next, select the options you want to select or leave it as default.
As SCCM version upgrades the SCCM client version as well, this will give 2 options, selecting option 1 will upgrade SCCM client in production, this is what I selected, but in enterprise we must select option 2 so that we can validate the new version before moving it to production.
Select next and specify your Software Assurance expiration date.
Click next to complete.
You can monitor the installation through CMUpdate.log.
Once installation is done, and you try to open the SCCM console, this will ask you to update your console.
Once completed you can verify the site version and control version.