Consulting ServicesNeed help with your SCCM infrastructure ? Consult our fixed price consulting plans to see our rates or contact us for a custom quote.
A new upgrade for SCCM Current Branch is now available. This post is a complete step-by-step SCCM 1702 installation guide. If you’re looking for a complete SCCM installation guide, see our blog series which covers it all. You can’t install this upgrade if you are running SCCM 2012. You need to be at least at SCCM 1511.
Installing SCCM upgrades is very important to your infrastructure. It adds new features and fixes lots of issues, which some of them are important.
New Update and Servicing Model
If you’re not familiar with the new SCCM servicing model, read our New Update and Servicing section of the 1602 upgrade post which explain it all.
Similar to SCCM 1610, if you need to make a new SCCM installation, you can’t install SCCM 1702 directly. You need to install SCCM 1606 first and then apply SCCM 1702 from the console. SCCM 1606 is the baseline version if you’re starting from scratch.
*If you are running SCCM 1511, 1602,1606 or 1610, the latest updates will be replaced by SCCM 1702 in the SCCM Console after installation. If you are on SCCM 1511, you won’t be able to install 1602, 1606 or 1610 after 1702. You can skip all previous versions and install SCCM 1702 directly which contains all 1602, 1606 and 1610 fixes and features.
SCCM 1702 New Features and Fixes
If you’ve been installing SCCM Technical Preview in your lab, SCCM 1702 contain most features included in the latest Technical Previews. Refer to the chart in the Capabilities delivered in technical previews section.
1702 includes lots of new features and enhancements in Operating system deployment, Software Updates, application management and Mobile device deployment.
Consult the What’s new in version 1702 of System Center Configuration Manager Technet article for a full list of changes. 1702 also applies the latest KB/fixes to fix known bugs, including KB3209501, KB3214042, KB4010155
Here’s our list of favorite features:
- Close executable files at the deadline when they would block application installation – If executable files are listed on the Install Behavior tab for a deployment type and the application is deployed to a collection as required, then a more intrusive notification experience is provided to inform the user, and the specified executable files will be closed automatically at the deadline
- Support for Windows 10 Creators Update – This version of Configuration Manager now supports the release of upcoming Windows 10 Creators Update
- Express files support for Windows 10 Cumulative Update – Configuration Manager now supports Windows 10 Cumulative Update using Express files
- Customize high-risk deployment warning – You can now customize the Software Center warning when running a high-risk deployment, such as a task sequence to install a new operating system
Version 1702 drops support for the following products:
- SQL Server 2008 R2, for site database servers. This version of SQL Server remains supported when you use a Configuration Manager version prior to version 1702.
- Windows Server 2008 R2, for site system servers and most site system roles. This version of Windows remains supported when you use a Configuration Manager version prior to version 1702.
- Windows Server 2008, for site system servers and most site system roles.
- Windows XP Embedded, as a client operating system. This version of Windows remains supported when you use a Configuration Manager version prior to version 1702.
Support for SCCM Current Branch Versions
Ensure to apply this update before you fall in an unsupported SCCM version. Read about the support end date of prior version on the following Technet article.
Before you begin
Downloading and installing this update is done entirely from the console. There’s no download link, the update will appear in your console once the Service Connection Point is synchronized.
If you’re running a multi-tier hierarchy, start at the top-level site in the hierarchy. After the top-level site upgrades, you can begin the upgrade of each child site. Complete the upgrade of each site before you begin to upgrade the next site. Until all sites in your hierarchy are upgraded, your hierarchy operates in a mixed version mode.
Before applying this update, we strongly recommend that you go through the upgrade checklist provided on Technet. Most importantly, initiate a site backup before your upgrade.
In this post, we’ll be updating a standalone Primary Site Server, consoles and clients.
Before installing, check if your site is ready for the update:
- Open the SCCM console
- Go to Administration \ Cloud Services \ Updates and Servicing
- In the State column, ensure that the update is Available
- If it’s not available, right-click Updates and Servicing and select Check for Updates
- The update state will change to Downloading
- You can follow the download in Dmpdownloader.log or by going to Monitoring / Site Servicing Status, right-click your Update Name and select Show Status
- The process will first download a .CAB file and will then extract the file in the EasyPayload folder in your SCCM Installation directory. (GUID : 2dc025b9-af2f-4f22-a477-33f19c16c14c) It can take up to 15 minutes to extract all files.
SCCM 1702 Installation guide
Step 1 | SCCM 1702 Prerequisite check
Before launching the update, we recommend to launch the prerequisite check :
- Open the SCCM console
- Go to Administration \ Cloud Services \ Updates and Servicing
- Right-click the Configuration Manager 1702 update and select Run prerequisite check
- Nothing will happen, the prerequisite check runs in the background. All menu options will be grayed out during the check
- One way to see progress is by viewing C:\ConfigMgrPrereq.log
- You can also monitor prerequisite check by going to Monitoring / Site Servicing Status, right-click your Update Name and select Show Status
- When completed the State column will show Prerequisite check passed
Step 2 | Launching the SCCM 1702 update
We are now ready to launch the SCCM 1702 update. At this point, plan about 45 minutes for the update installation.
- Right click the Configuration Manager 1702 update and select Install Update Pack
- On the General tab, click Next
- On the Features tab, select the features you want to update
- If you don’t select one of the features now and want to enable it later, you’ll be able to so by using the console in Administration \ Cloud Services \ Updates and Servicing \ Features
- In the Client Update Options, select the desired option for your client update
- This new feature allows updating only clients member of a specific collection. Refer to our pre-production client deployment post for more details
- On the License Terms tab, accept the license terms and click Next
- On the Summary tab, review your choices and click Next
- On the Completion tab, close the wizard. The whole process took a minute but the installation is not over, it has been initiated
- During installation, the State column changes to Installing
- You can monitor installation by going to Monitoring / Site Servicing Status, right-click your Update Name and select Show Status
- … or you can follow detailed installation progress in SCCM Installation Directory\Logs\CMUpdate.log
[su_box title=”Warning” style=”glass” title_color=”#F0F0F0″]We’ve done numerous SCCM upgrades. Some installation start a couple of minutes after you complete the wizard but we’ve seen some installation starts after a 10 minutes delay. Do not reboot or restart any services during this period or your update could be stuck in “Prerequisite check passed” status and all other options grayed out. There’s actually no officially documented methods by Microsoft to fix that. Patience is the key ![/su_box]
- When completed, you’ll notice the message There are no pending update package to be processed in the log file
- Monitoring / Site Servicing Status, right-click your Update Name and select Show Status, the last step will be Installation Succeeded
- Refresh the Updates and Servicing node, the State column will be Installed
Updating the consoles
As a previous Cumulative update, the console has an auto-update feature. At console opening, if you are not running the latest version, you will receive a warning and the update will start automatically.
- Since all updates operations were initiated from the console, we didn’t close it during the process. We received a warning message when clicking certain objects. You will have the same message when opening a new console
- Click OK, console update will start automatically
- Wait for the process to complete. You can follow the progress in C:\ConfigMgrAdminUISetup.log and C:\ConfigMgrAdminUISetupVerbose.log. Once completed, the console will open and you’ll be running the latest version
After setup is completed, verify the build number of the console. If the console upgrade was successful, the build number will be 5.0.8498.1500. You can also notice that Version 1702 is stated.
- Go to Administration \ Site Configuration \ Sites
- Right-click your site and select Properties
- Verify the Version and Build number
The client version will be updated to 5.00.8498.1007 (after updating, see section below)
SCCM 1702 Client Package distribution
You’ll see that the 2 client packages are updated:
- Navigate to Software Library \ Application Management \ Packages
- Check if both packages were updated, if not, select both packages and initiate a Distribute Content to your distribution points
Boot images are automatically updated during setup. See our post on upgrade consideration in a large environment to avoid this if you have multiple distribution points.
- Go to Software Library / Operating Systems / Boot Images
- Select your boot image and check the last Content Status date. It should match your setup date
Updating the Clients
Our preferred way to update our clients is by using the Client Upgrade feature: (You can refer to our complete post documenting this feature)
- Open the SCCM Console
- Go to Administration / Site Configuration / Sites
- Click the Hierarchy Settings in the top ribbon
- Select Client Upgrade tab
- The Upgrade client automatically when the new client update are available checkbox has been enabled
- Review your time frame and adjust it to your needs
Monitor SCCM Client Version Number
SCCM Reports Client Version
You can see our SCCM Client version reports to give detailed information about every client version in your environment. It’s the easiest way to track your client updates.
You can also create a collection that targets clients without the latest client version. I use it to monitor which client haven’t been updated yet.
Here’s the query to achieve this: (You can also refer to our Set of Operational Collection Powershell Script which contains this collection)[pastacode lang=”sql” manual=”select%20SMS_R_SYSTEM.ResourceID%2CSMS_R_SYSTEM.ResourceType%2CSMS_R_SYSTEM.Name%2CSMS_R_SYSTEM.SMSUniqueIdentifier%2CSMS_R_SYSTEM.ResourceDomainORWorkgroup%2CSMS_R_SYSTEM.Client%20from%20SMS_R_System%20where%20SMS_R_System.ClientVersion%20!%3D%20’5.00.8498.1007′” message=”” highlight=”” provider=”manual”/]
Happy updating ! 🙂
Could you provide a trusted post that guide or at last telling the steps should I take to go
Windows Server 2008r2 SP1 ====> Windows Server 2016
SQL 2012 SP1 ====> SQL 2016 SP1
SCCM 2012 R2 SP1 ====> SCCM 1702
Anyone have issue setting up new DPs after this upgrade? Since the upgrade to 1702 when we go to setup remote DPs the content looks like it has uploaded but the DP config status shows that 0 packages have been uploaded. We just ran the KB update for 1702, but it still looks to be an issue.
Maybe a bug in 1702.
It is a bug in 1702, MS gave us this workaround, this will not be fixed until the 1706 upgrade.
Hopes this help anyone with the issue.
The workaround is to execute the below stored procedure on the site database
exec spRebuildContentDistribution 1
Does anyone know supported versions of ADK? Does 1511 ADK still work fine with 1702?
We got this covered right here : https://systemcenterdudes.com/how-to-update-windows-adk-on-a-sccm-server/
We are currently running SCCM 1610 but need to be able to specify flags for ccmsetup under the client installation properties. We can’t do that in SCCM 1610. Can we specify ccmsetup properties in the console with version 1702?
not sure what you try to achieve. You can specify many flags for the installer within the client push configuration.
Can you be more specific on the need and which flag?
We are at SCCM 2012 SP2 and finally got approval from management to upgrade to SCCM 1702. I see at the top of this page it says “You can’t install this upgrade if you are running SCCM 2012. You need to be at least at SCCM 1511.” I also see at https://docs.microsoft.com/en-us/sccm/core/plan-design/changes/whats-new-in-version-1702 that it says regarding SCCM 1702 “It is also available as a baseline version you can use when installing a new deployment.” Does this mean I can now upgrade directly to SCCM 1702? I there a step-by-step guide somewhere that will walk me through upgrading from SCCM 2012 to SCCM 1702?
you are right about 1702 being a Baseline release. You can in-place upgrade your SCCM 2012 SP2 straight to 1702.
Take a look at our guide for SCCM 1511 which is still a valide method of upgrading SCCM 2012 to Current Branch.
We are running SCCM 2012 R2 on Windows Server 2008 R2 and SQL Server 2008 R2.
We intend to upgrade to SCCM 1702, but obviously the above Operating System and SQL Server versions are not supported with 1702. So an In-place upgrade of the Operating System and SQL Server is inevitable here.
My question is mainly on the sequence of steps to be followed.
Do we first perform an in-place upgrade of the Operating System and SQL Server to Windows Server 2012 R2 and SQL Server 2014, and then touch the SCCM part?? That way I guess we would qualify for a direct upgrade to 1702 Baseline.
Also how do we handle the upgrade of the Secondary Sites and Remote Distribution Points? Do they automatically get updated once the Upgrade is applied on the CAS / PRIMARY Sites?
We are upgrading our Sccm infra from CB 1610 to 1702. Primary Site got upgraded successfully.
But we are facing issue while upgrading our secondary sites. Some secondary sites got upgraded successfully but some are failing to upgrade. Following are the errors which we are getting:
1. The collation of the site database does not match the collation of the parent site’s database. All sites in a hierarchy must use the same database collation.
2. Current SUM configuration uses virtual locations for some of the active SUPs. Please remove any virtual locations from the existing SUM configuration.
3. Either the user account running Configuration Manager Setup does not have sysadmin SQL Server role permissions on the SQL Server instance selected for site database installation, or the SQL Server instance could not be contacted to verify permissions. Setup cannot continue
And it is not our first upgrade. We upgraded from 1511 –> 1602 –> 1606 –> 1610 smoothly.
Dont know why this time while upgrading from 1610 –> 1702, we are getting above errors.
I’m currently on 1511 and am planning the upgrade to 1702. Based on what updates appear in the console, it looks like I have to first upgrade to 1610 and then 1702 will be available. This is my first time upgrading SCCM in my current environment, so I’m new to the upgrade process. We have one Primary Site, 50 remote DPs (no Secondary Sites), and about 1500 clients. Can I upgrade from 1511->1610->1702 in one sitting? Do I have to wait for all my remote DPs and Clients to update to 1610 first? I’m not sure if I need to do this over the span of a few weeks – i.e. upgrade to 1610 first and then wait for everything to settle until going to 1702, or if it could be done in a few hours over a weekend?
Microsoft has stated that 1702 is a new baseline. Last night, per Microsoft’s confirmation, I upgraded directly from SCCM 2012 R2 SP1 to 1702; worked without an issue.
Mark (or anyone if Mark is no longer following this thread) can you please recommend documentation to perform the upgrade from 2012 R2 to 1702? I need to do the same procedure. I’ve found this https://docs.microsoft.com/en-us/sccm/core/servers/deploy/install/upgrade-to-configuration-manager, but I like to have some guidance from a third-party, too. Will the steps here https://systemcenterdudes.com/sccm-1511-upgrade/ also work for upgrading to 1702?
My question was whether you can upgrade from 1511 to 1702 using the ISO media. Based on what I am finding online, this is not possible and I must upgrade to 1610 first and then to 1702. It sounds like you CAN upgrade from 2012 SP1, SP2, or 2012 R2 but not from anything higher. I think I confirmed this fact by mounting the 1702 ISO and the only thing that is available is “Uninstall this Config Mgr site”.
According to support from Microsoft, they stated I do NOT have to upgrade to 1511 from SCCM 2012 R2 before going to 1702. Your guide contradicts that. Which source should I follow?
Specifically, I am running SCCM 2012 R2 SP1 (5.00.8239.1000).
More info about 1702 being a baseline upgrade found here: https://twitter.com/djammmer/status/854110273854095360
we have a lab for test environment and there is no internet connection, in that case how to update from sccm 1606 to sccm 1702
I am trying to build a new server from scratch. Can I install 1702 as fresh install? Or I need to install 1606 and then upgrade to 1702?
I did just that as the bits for 1702 have not shown up on our VL site yet. If you have the install bits for 1702 just go ahead and install it that way to save yourself some time.
1702 is a baseline version, so you can create a new deployment/site with this. No need to setup 1602 first surely?
“The first release of System Center Configuration Manager current branch was version 1511, which was a baseline version. More recent baseline versions include version 1606, and 1702:+
Use the latest baseline version when you install a new site in a new hierarchy.”
I think the above is a little out of date…
Just followed this guide as first Current Branch upgrade. Worked a treat. Great work. 🙂
Followed this by latest ADK / MDT as main interest of upgrading was Windows 10 1703.
Wish List for Microsoft – Provide some form of BootImage creator / migration for ADK upgrades. We have so many different HW types, that recreating doesnt become practical and we end up using DISM.
Hey Guys.. Thanks for the infor.. nice guide.
Just a quick question, I am looking at doing a new build from 2007 to SCCM 170x. I understand the instalation process but before I begin I need to know a few things. I is there a migration tool to assist me in moving the the packages, collections and advertisments, and the second question is does SCCM 170x suppot Windows 7 clients?
I sugguest you take a look at our post on Side-By-Side Migration https://systemcenterdudes.com/sccm-1511-migration/
Step are pretty much the same for latest Current branch.
I am currently running 2012 R2 and have stood up its replacement with Server 2016, SQL 2016 and 1702. I will say that the migration tools leave a lot to be desired as you still have to rely on 3rd party tools for certain things unless you want to do some manual work.
I had issues with migrating packages and some Task Sequences. The biggest pain was changing all the package source locations for everything that was imported from my 2012 SCCM.
Hi, not sure it is the update or what, but this is new to me, the recent deployed and upgraded secondary site giving me problem. When deploy a required OSD task sequence (with or without re-run) using PXE Boot, client able to boot into WinPE every time. (I got the network adapter at first boot priority for zero touch OSD) But, it ended with an endless boot loop like, Boot to WinPE -> Download WIM -> Apply WIM -> Configure the rest -> Reboot -> Boot to WinPE -> Repeat… Why? Isnt the PXE Service Point should be *remember* that the client has booted to required PXE?
I’m quite sure that i got the same PXE settings for both primary and secondary site, but my primary site doesnt have this issue at all. Can anyone point a light please? 🙁
2 of my Secondary Sites are stuck in “Upgrade” state for the past 8 days. I have attempted to reboot them, reboot my primary server and that does nothing to fix it.
Since they are stuck in “Upgrade” I cannot click on “Recover Secondary site”. I’d prefer not to delete the site and have to start all over again. What can be done to manually kick off the upgrade or fix this situation.
Hi Sal, you’re not alone. I got 1 of my secondary site stuck in Upgrade state too. The installation status shows Prerequisite Check Complete and it never continue. It’s been 2 days so far without rebooting or restarting services. Please keep me updated if you found any solution. Thanks
Update: I got mine upgraded without doing anything. It started after distributing content and all went OK.
Thanks for the update. My Distribution points are on VSAT.. so they take daysssssss to push content then..
You’re most welcome 😉
My secondary site is stuck in upgrade as well, what exactly did you do to get past this?
Glad to see am not alone on this!
The update didnt finish. it got stuck on the post installation section…any advice to get it to finish?
additionally the update is no longer showing up under updates and servicing.
So I am using SQL 2008 R2 SP3 in my SCCM 1610 + 2 hotfixes in my lab. The Prepreq Check says it fails. After checking the prereq log it indicates the OS version will be outdated soon and the SQL version needs to be upgraded before setup will run for 1702. So we should upgrade the SQL portion to get 1702 installed and that is all? Can I upgrade to server 2016 eval? Is there a stepbystep for upgrading the SQL piece?
Pingback: Step-by-Step SCCM 1702 Installation Guide |
Pingback: How to enable Android for Work in SCCM and Intune |
Benoit does mention “we strongly recommend that you go through the upgrade checklist provided on TechNet”
but I would just like to remind everyone that RUNNING THE DATABASE UPGRADE TEST is one of the most important things you can do besides taking a backup of the site database before you run the Install Update Pack.
Pingback: Configure High-Impact Task Sequence Settings in SCCM 1702 |
Do you need to update any additional site serves, or is this now automatic?
Pingback: Enable and Configure SCCM Install Behavior for Applications |
Can Server 2008 R2 be used for the Site Database server, so long as SQL Server 2012 is in use ?
I’d say no. The only site system role supported on Windows Server 2008R2 are Distribution Point and StateMigration Point.
Here’s Microsoft statement about Windows server 2008 R2 :
Beginning with version 1702, this operating system is not supported for site servers or most site system roles, however versions prior to 1702 continue to support its use. This operating system does remain supported for the state migration point and distribution point site system role (including pull-distribution points, and for PXE and multicast) until deprecation of this support is announced, or this operating system’s extended support period expires. Beginning with version 1602, you can upgrade in-place the operating system of a site server from Windows Server 2008 R2 to Windows Server 2012 R2.
WE are running SCCM 1610 on Windows Server 2012 not R2 and after running the prereq it gives me a warning that Windows Server 2008 r2 is no longer supported. But Server is not 2008 it is 2012. Any ideas is we can go ahead with the update to 1702?
Is your SCCM install on one server only? including site database(SQL)?
Wondering if you could have remote sites like Distribution or secondary site, still running 2008R2
Hello — I am having a similar issue as Jason.
I am running SCCM on Windows Server 2012 R2 and with latest critical updates. I have the DB running on a separate server, also running on Windows Server 2012 R2 with latest critical updates.
I am receiving these messages (Warning):
[Completed with warning]:Starting with version 1702, Configuration Manager does not support Windows Server 2008 R2 operating system. https://go.microsoft.com/fwlink/?linkid=841654. This check verifies that the site server operating system meets the minimum requirement of Windows Server 2012 for site server installation.
[Failed]:Verifies that the site server operating system meets the minimum requirement of Windows Server 2008 SP2 for site server installation.
My task sequences no longer show up during OSD, any suggestions. I’m running 1702 and ADK 10.
Can you provide more details please?
Where does it no longer show up? In the console? at PXE boot? in WinPE? In Software Center?
What are you trying to achieve?
Hi Jonathan, I get into the OSD, I can log in but immediately after I login into the OSD the system stops and says no TS available for this computer. Since upgrading I have create new boot.wim files for both architectures and I have created new TS to see was it a corruption during upgrade but same results.
The deployments to Unknown Computer groups just doesnt seem to be working.
I have cleare Pxe deployements on my groups and also on the individual device im testing the Upgrade on.
Any help would be great
I would be surprised about any kind of corruption.
Might be an issue with duplicate MAC address.
Take a look in the SMSPXE.log located on your SCCM PXE server. D:\Program Files\Microsoft Configuration Manager\Logs\SMSPXE.log
I suggest to test OSD with an available deployment, instead of mandatory(with deadline).
Hi Jonathan, DO you know of any issues in 1702 at recognizing Unknown Computers, I can see the system recognizing the system as Unknown but the collections font seem to be updating with the new unknown systems hence the Task Sequences aren’t being presented to those devices to OSD.
We are also experiencing issues with unknown systems not being recognized after this update. No amount of troubleshooting fixes the issue. Just called MSFT and they admit the issue as well stating there should be a fix coming soon. So I wouldn’t recommend the upgrade unless you wan to import MAC address for your bare metal builds in order to make it a known system.
This also seems to be effecting post first wave deployments of 1702 which already includes this hotfix.
see the most recent post here regarding deployments to unknown computers no longer working in sccm 1702
Did you resolve this issue?
I see there is a new ADK, do we need to install it along with SCCM 1702 for Windows 10 Creators Update support? Seems to be some info saying yes but I’ve seen nothing regarding installing it as part of the 1610-to-1702 upgrade? Also, I saw something about having the new ADK installed before upgrading to 1702 to get the newest boot WIM’s, a tad confused…
Yes there’s a new ADK, for the new Windows 10. It is NOT mandatory to install it to deploy Windows 10(even creator update).
SCCM Upgrade do not include ADK updates as they will not always match.
As for the boot images, no need to install the ADK before upgrading. ADK can be updated at a later time, then boot images updated after this.
For now I would suggest to hold the update to new ADK, as it seem to have some bugs.
We are working on a post about the ADK to clarify all this.
We are running SCCM 1606 (no hotfix), can we install 1702 and skip 1610 ?
The 1702 update not visible in console, even after I clicked on “Check for Updates”.
Have you ever had to run EnableFastUpdateRing1702.ps1 to make it available ?
We just ran the upgrade now, and it failed at ‘Upgrade ConfigMgr database’.
*** [Microsoft][SQL Server Native Client 11.0][SQL Server]ERROR 547, Level 16, State 0, Procedure sp_SetupSettingsAndRules, Line 177, Message: The MERGE statement conflicted with the REFERENCE constraint “CI_CurrentRuleDetail_SettingID_FK”. The conflict occurred in database “CM_V01”, table “dbo.CI_CurrentRuleDetail”, column ‘SettingID’. : spRethrowError CONFIGURATION_MANAGER_UPDATE 2017-04-04 14:59:30 41488 (0xA210)
ERROR: Failed to execute SQL Server command; CCISource::InsertObject returned -1 CONFIGURATION_MANAGER_UPDATE 2017-04-04 14:59:30 41488 (0xA210)
ERROR: Failed to install default configuration items (FinalSqlOperations). CONFIGURATION_MANAGER_UPDATE 2017-04-04 14:59:30 41488 (0xA210)
Failed to update database. CONFIGURATION_MANAGER_UPDATE 2017-04-04 14:59:30 41488 (0xA210)
Failed to apply update changes 0x87d20b15 CONFIGURATION_MANAGER_UPDATE 2017-04-04 14:59:59 41488 (0xA210)
We are retrying the upgrade right now, hoping it was just a glitch…
But if anyone has any input, it would be very much appreciated.
No luck after trying the upgrade again. Same error.
Follow-up: There was an error in the database, and we had to contact Microsoft to get it fixed.
Thanks for the update Par, can you provide any more detail on what Microsoft did?
On my instance i am currently running 1610.
There are two additional Hotfixes available, KB4010155 and KB4016483 BUT not 1702 update available.
There dont seem to be any errors in the dmpdownloader.log or hman.log
Restarted the SMS_DMP_DOWNLOADER component.
The update is rolling out progressivelly. It’s normal if you’re not seeing it right away. It should appear in the following weeks. A script can be run to have it faster :
(At the bottom)
Note: As the update is rolled out globally in the coming weeks, it will be automatically downloaded and you will be notified when it is ready to install from the “Updates and Servicing” node in your Configuration Manager console. If you can’t wait to try these new features, this PowerShell script can be used to ensure that you are in the first wave of customers getting the update. By running this script, you will see the update available in your console right away.
Why is there no mention of updating SQL to 2012 ? Is it required?
As Benoit great info… Don’t foget if they want to add features later. Updates and Servicing is its own node now and not under Cloud Services any more.
can i still use 2008R2 Servers as Distribution Points or do i need to upgrade them, too?
You can still 2008 R2 Sp1 as a DP or a State Migration Point