The third upgrade for SCCM Current Branch is now available. This post is a complete step-by-step SCCM 1610 upgrade 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 feature 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 1606, if you need to make a new SCCM installation, you can’t install SCCM 1610 directly. You need to install SCCM 1511 (or 1606) first and then apply SCCM 1610 from the console. SCCM 1606 is the baseline version if you’re starting from scratch.

*If you are running SCCM 1511, 1602 or 1606, the latest updates will be replaced by SCCM 1610 in the SCCM Console after installation. If you are on SCCM 1511, you won’t be able to install 1602 or 1606 after 1610. You can skip all previous versions and install SCCM 1610 directly which contains all 1602 and 1606 fixes and features.

SCCM 1610 New Features and Fixes

If you’ve been installing SCCM Technical Preview in your lab, SCCM 1606 contain most features included in the latest Technical Previews (1605 and up).

1610 includes lots of new features and enhancements in Windows 10 and Office 365 management, application management, end user experience, client management and also includes new functionality for customers using Configuration Manager in hybrid mode with Microsoft Intune.

Consult the Summary of changes in System Center Configuration Manager version 1610 article for a full list of changes.

Consult this Technet article for a full features list. 1606 also applies the latest KB/fixes to fix known bugs, including KB3202796, KB3192616, KB3186654 and KB3180992

Here’s our list of favorite features :

  • Office 365 Servicing Dashboard and app deployment to clients features help you to deploy Office 365 apps to clients as well as track Office 365 usage and update deployments.
  • Software Updates Compliance Dashboard allows you to view the current compliance status of devices in your organization and quickly analyze the data to see which devices are at risk.
  • Cloud Management Gateway provides a simpler way to manage Configuration Manager clients on the Internet. You can use the SCCM console to deploy the service in Microsoft Azure and configure the supported roles to allow cloud management gateway traffic.
  • Client Peer Cache is a new built-in solution in Configuration Manager that allows clients to share content with other clients directly from their local cache with monitoring and troubleshooting capabilities.
  • Enhancements in Software Center including customizable branding in more dialogs, notifications of new software, improvements to the notification experience for high-impact task sequence deployments, and ability for users to request applications and view request history directly in Software Center.

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 check list 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

SCCM 1610 upgrade guide

  • If it’s not available, right-click Updates and Servicing and select Check for Updates

SCCM 1610 upgrade guide

  • The update state will change to Downloading

SCCM 1610 upgrade guide

  • 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

SCCM 1610 upgrade guide

SCCM 1610 upgrade guide

  • The process will first download a .CAB file and will then extract the file in the EasyPayload folder in your SCCM Installation directory. It can take up to 15 minutes to extract all files.

SCCM 1610 upgrade guide

SCCM 1610 Upgrade guide

Step 1 | SCCM 1610 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 1610 update and select Run prerequisite check

SCCM 1610 upgrade guide

  • Nothing will happen, the prerequisite check runs in the background. All menu options will be grayed out during the check

SCCM 1610 upgrade guide

  • One way to see progress is by viewing C:\ConfigMgrPrereq.log

SCCM 1610 upgrade guide

  • You can also monitor prerequisite check by going to Monitoring / Site Servicing Status, right-click your Update Name and select Show Status

SCCM 1610 upgrade guide

  • When completed the State column will show Prerequisite check passed

SCCM 1610 upgrade guide

Step 2 | Launching the SCCM 1610 update

We are now ready to launch the SCCM 1610 update. At this point, plan about 45 minutes for the update installation.

  • Right click the Configuration Manager 1610 update and select Install Update Pack

SCCM 1610 upgrade guide

  • On the General tab, click Next

SCCM 1610 upgrade guide

  • On the Features tab, select the features you want to update

SCCM 1610 upgrade guide

  • If you don’t select one of the feature 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

SCCM 1602 upgrade guide

  • In the Client Update Options, select the desired option for your client update

SCCM 1610 upgrade guide

  • On the License Terms tab, accept the licence terms and click Next

SCCM 1610 upgrade guide

  • On the Summary tab, review your choices and click Next

SCCM 1610 upgrade guide

  • On the Completion tab, close the wizard. The whole process took a minute but the installation is not over, it has been initiated

SCCM 1610 upgrade guide

  • During installation, the State column changes to Installing

SCCM 1610 upgrade guide

  • You can  monitor installation by going to Monitoring / Site Servicing Status, right-click your Update Name and select Show Status

SCCM 1610 upgrade guide

  • … or you can follow detailed installation progress in SCCM Installation Directory\Logs\CMUpdate.log

SCCM 1610 upgrade guide

Warning
We’ve done numerous SCCM 1610 installation. 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 greyed out. There’s actually no officially documented methods by Microsoft to fix that. Patience is the key !
  • 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

SCCM 1610 upgrade guide

  • Refresh the Updates and Servicing node, the State column will be Installed

SCCM 1610 upgrade guide

Updating the consoles

As 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 starts automatically

SCCM 1602 upgrade guide

SCCM 1602 upgrade guide

  • 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

Verification

Consoles

After setup is completed, verify the build number of the console. If the console upgrade was successful, the build number will be 5.0.8458.1500. You can also notice that Version 1610 is stated.

SCCM 1610 upgrade guide

Servers

  • Go to Administration \ Site Configuration \ Sites
  • Right-click your site and select Properties
  • Verify the Version and Build number

SCCM 1610 upgrade guide

Clients

The client version will be updated to 5.00.8458.1005 (after updating, see section below)

SCCM 1610 upgrade guide

SCCM 1610 Client Package distribution

You’ll see that the 2 client packages are updated :

  • Navigate to Software Library \ Application Management \ Packages

SCCM 1602 upgrade guide

  • Check if both package were updated, if not, select both package and initiate a Distribute Content to your distribution points

Boot Images

Boot images are automatically updated during setup. See our post on upgrade consideration in 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

SCCM 1610 upgrade guide

Monitor SCCM Client Version Number

SCCM Reports Client Version

You can see our SCCM Client version reports to give detailed information about every clients versions in your environment. It’s the easiest way to track your client updates.

SCCM 2012 - System Health Configuration Manager SS

Collections

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)

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.ClientVersion != '5.00.8458.1005'

Happy updating ! 🙂

Founder of System Center Dudes. Based in Montreal, Canada, Senior Microsoft SCCM Consultant, 4 times Enterprise Mobility MVP. Working in the industry since 1999. His specialization is designing, deploying and configuring SCCM, mass deployment of Windows operating systems, Office 365 and Intunes deployments.
Step-by-Step SCCM 1610 Upgrade Guide
5 - 5 votes
Comments
  • KACouillard
    Posted at 3:01 PM May 15, 2017
    KACouillard
    Reply
    Author

    We seem stuck in installing mode… 55 minutes after starting Install Update Pack on 1610, no files populating CMUpdate.log, or Monitoring Site Servicing Status. The state says Installing… but can see nothing happening.

    The prereq check was good. Even ran the pre-database test on a copy and that was good. The only thing I can think of is we stopped all component services with preinst /stopsite command, instead of stopping each individually. Any thoughts please?

    Its also strange the choices of Install Update Pack and Retry Installation are still available even thought the state is Installing… Is that normal or necessary to retry?

    thank you!

    • KacCouillard
      Posted at 9:11 AM May 16, 2017
      KacCouillard
      Reply
      Author

      Good morning,
      Well it hung at installing, with no logs or monitoring activity all night.

      So with Service Manager, I started the Site Component Manager as I think that was my mistake. Sitecomp.log shows it started successfully and sitectrl.log good. All Components are running (except the ones I stopped in Site Maintenance)

      Monitoring\Overview\Site Servicing Status\Configuration Manager 1610 Status says:
      Content replication succeeded 5/16/2017 8:54am
      No entries in the Update Pack Installation Status as of 10:05am.

      \Administration\Overview\Cloud Services\Updates and Servicing\Configuration Manager 1610 Status says:
      Checking prerequisites

      The CMUpdate.log has no entries at all.

      Hung here. Any ideas please?
      thank you.

      • KacCouillard
        Posted at 12:41 PM May 18, 2017
        KacCouillard
        Reply
        Author

        I have solved this issue. These steps were necessary:

        1. Disable AV on the CM server, because the CPU was being pegged

        (or add all these exclusions https://www.systemcenterblog.nl/2012/05/09/anti-virus-scan-exclusions-for-configuration-manager-2012/)

        2. Delete all SQL update packages

        3. Delete the same packages from EasySetupPayload

        4. Restart sms_executive service

        5. The packages re-downloaded

        6. Run pre-check and Install Update Package on the FIRST released 1610, not the second

        7. After in installed successfully, 3 hotfixes for 1610 downloaded, plus 1702

        8. I plan to install the 3 hotfixes first, then 1702

        • Jonathan Lefebvre
          Posted at 1:41 PM May 18, 2017
          Jonathan Lefebvre
          Reply
          Author

          Hi KacCouillard,

          You shoud go straight to 1702. No need to go through all the updates.

          Jonathan

  • Allan
    Posted at 6:37 AM April 5, 2017
    Allan
    Reply
    Author

    Everything went smooth with the exception that the Boot Images did not update and nor will they. They still have an old date of 8/6/2016 and when trying to update DPs, it fails with both x86 and x64 images with error:

    • Description = “Failed to inject OSD binaries into mounted WIM file (often happens if unsigned drivers are inserted into x64 boot image)”;
    • ErrorCode = 2152205056;
    • File = “e:\\qfe\\nts\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp”;
    • Line = 5004;
    • ObjectInfo = “CSspBootImagePackage::PreRefreshPkgSrcHook”;
    • Operation = “ExecMethod”;
    • ParameterInfo = “SMS_BootImagePackage.PackageID=\”AA100004\””;
    • ProviderName = “WinMgmt”;
    • StatusCode = 2147749889;

    This is with and without any drivers.

    • Hanumanth
      Posted at 1:54 AM May 25, 2017
      Hanumanth
      Reply
      Author

      Hi Allan

      We are getting the same error? are you able to resolve this issue?

      Regards
      Hanumanth

    • feku chand
      Posted at 7:53 AM June 10, 2017
      feku chand
      Reply
      Author

      I faced similar issue, McAfee exceptions policy applied to all SCCM servers helped to fix the issue

  • KACouillard
    Posted at 1:46 PM April 4, 2017
    KACouillard
    Reply
    Author

    We want to update from 1511 to 1610. I know it is not required, but I wanted to run the TestDBupgrade setup.exe. Doing so resulted in an error I have not been able to solve thus unwilling to update my production servers.

    Using a backed up DB from the SQL server and source files copied from the EasySetupPayload package on the SCCM server, I mounted all on a separate test computer. The SQL version matches the production server.

    From ConfigMgrSetup.log below, not sure what this error message is telling me. During “PreUpgrade Cleanup scripts”.

    I have checked the SQL Server and Agent logs, they are normal.

    Thank you so much for your assistance!

    KACouillard

    SQL MESSAGE: – End – Creating SchemaChanges Trigger
    Configuration Manager Setup 4/3/2017 3:43:22 PM
    10052 (0x2744)

    INFO: Beginning SQL Server script execution. Configuration Manager Setup 4/3/2017 3:43:44 PM
    10052 (0x2744)

    INFO: Executing PreUpgrade Cleanup scripts.
    Configuration Manager Setup 4/3/2017 3:43:44 PM
    10052 (0x2744)

    *** ~– adjusting the index to reduce table size for bug 309097 ~IF EXISTS (SELECT * FROM dbo.SMSData WHERE SMSBuildNumber < 7730) ~BEGIN ~ IF EXISTS (SELECT * FROM sys.indexes WHERE object_id = OBJECT_ID(N'[dbo].[INSTALLED_SOFTWARE_DATA]') ~ AND name = N'sw_data_hash_code') ~ DROP INDEX sw_data_hash_code ON INSTALLED_SOFTWARE_DATA ~ ~ IF EXISTS (SELECT * FROM sys.indexes WHERE object_id = OBJECT_ID(N'[dbo].[INSTALLED_SOFTWARE_DATA]') ~ AND name = N'sw_data_idx1') ~ DROP INDEX sw_data_idx1 ON INSTALLED_SOFTWARE_DATA ~ ~ IF EXISTS (SELECT * FROM sys.indexes WHERE object_id = OBJECT_ID(N'[dbo].[INSTALLED_SOFTWARE_DATA]') ~ AND name = N'sw_data_idx2') ~ DROP INDEX sw_data_idx2 ON INSTALLED_SOFTWARE_DATA ~ ~ IF EXISTS (SELECT * FROM sys.indexes WHERE object_id = OBJECT_ID(N'[dbo].[INSTALLED_SOFTWARE_DATA_Summary]') ~ AND name = N'INSTALLED_SOFTWARE_DATA_Summary_idx_ByCode') ~ DROP INDEX INSTALLED_SOFTWARE_DATA_Summary_idx_ByCode ON INSTALLED_SOFTWARE_DATA_Summary ~END
    Configuration Manager Setup 4/3/2017 3:43:59 PM
    10052 (0x2744)

    *** [HY000][0][Microsoft][SQL Server Native Client 11.0]Unspecified error occurred on SQL Server. Connection may have been terminated by the server.
    Configuration Manager Setup 4/3/2017 3:43:59 PM
    10052 (0x2744)

    ERROR: SQL Server error: [HY000][0][Microsoft][SQL Server Native Client 11.0]Unspecified error occurred on SQL Server. Connection may have been terminated by the server.
    Configuration Manager Setup 4/3/2017 3:43:59 PM
    10052 (0x2744)

    *** ~– adjusting the index to reduce table size for bug 309097 ~IF EXISTS (SELECT * FROM dbo.SMSData WHERE SMSBuildNumber < 7730) ~BEGIN ~ IF EXISTS (SELECT * FROM sys.indexes WHERE object_id = OBJECT_ID(N'[dbo].[INSTALLED_SOFTWARE_DATA]') ~ AND name = N'sw_data_hash_code') ~ DROP INDEX sw_data_hash_code ON INSTALLED_SOFTWARE_DATA ~ ~ IF EXISTS (SELECT * FROM sys.indexes WHERE object_id = OBJECT_ID(N'[dbo].[INSTALLED_SOFTWARE_DATA]') ~ AND name = N'sw_data_idx1') ~ DROP INDEX sw_data_idx1 ON INSTALLED_SOFTWARE_DATA ~ ~ IF EXISTS (SELECT * FROM sys.indexes WHERE object_id = OBJECT_ID(N'[dbo].[INSTALLED_SOFTWARE_DATA]') ~ AND name = N'sw_data_idx2') ~ DROP INDEX sw_data_idx2 ON INSTALLED_SOFTWARE_DATA ~ ~ IF EXISTS (SELECT * FROM sys.indexes WHERE object_id = OBJECT_ID(N'[dbo].[INSTALLED_SOFTWARE_DATA_Summary]') ~ AND name = N'INSTALLED_SOFTWARE_DATA_Summary_idx_ByCode') ~ DROP INDEX INSTALLED_SOFTWARE_DATA_Summary_idx_ByCode ON INSTALLED_SOFTWARE_DATA_Summary ~END
    Configuration Manager Setup 4/3/2017 3:43:59 PM
    10052 (0x2744)

    *** [22007][211][Microsoft][SQL Server Native Client 11.0][SQL Server]Possible schema corruption. Run DBCC CHECKCATALOG.
    Configuration Manager Setup 4/3/2017 3:43:59 PM
    10052 (0x2744)

    ERROR: SQL Server error: [22007][211][Microsoft][SQL Server Native Client 11.0][SQL Server]Possible schema corruption. Run DBCC CHECKCATALOG.
    Configuration Manager Setup 4/3/2017 3:44:00 PM
    10052 (0x2744)

    INFO: Executing SQL Server command: < ~– adjusting the index to reduce table size for bug 309097 ~IF EXISTS (SELECT * FROM dbo.SMSData WHERE SMSBuildNumber
    Configuration Manager Setup 4/3/2017 3:44:00 PM
    10052 (0x2744)

    ERROR: Failed to execute SQL Server command ~– adjusting the index to reduce table size for bug 309097 ~IF EXISTS (SELECT * FROM dbo.SMSData WHERE SMSBuildNumber < 7730) ~BEGIN ~ IF EXISTS (SELECT * FROM sys.indexes WHERE object_id = OBJECT_ID(N'[dbo].[INSTALLED_SOFTWARE_DATA]') ~ AND name = N'sw_data_hash_code') ~ DROP INDEX sw_data_hash_code ON INSTALLED_SOFTWARE_DATA ~ ~ IF EXISTS (SELECT * FROM sys.indexes WHERE object_id = OBJECT_ID(N'[dbo].[INSTALLED_SOFTWARE_DATA]') ~ AND name = N'sw_data_idx1') ~ DROP INDEX sw_data_idx1 ON INSTALLED_SOFTWARE_DATA ~ ~ IF EXISTS (SELECT * FROM sys.indexes WHERE object_id = OBJECT_ID(N'[dbo].[INSTALLED_SOFTWARE_DATA]') ~ AND name = N'sw_data_idx2') ~ DROP INDEX sw_data_idx2 ON INSTALLED_SOFTWARE_DATA ~ ~ IF EXISTS (SELECT * FROM sys.indexes WHERE object_id = OBJECT_ID(N'[dbo].[INSTALLED_SOFTWARE_DATA_Summary]') ~ AND name = N'INSTALLED_SOFTWARE_DATA_Summary_idx_ByCode') ~ DROP INDEX INSTALLED_SOFTWARE_DATA_Summary_idx_ByCode ON INSTALLED_SOFTWARE_DATA_Summary ~END
    Configuration Manager Setup 4/3/2017 3:44:00 PM
    10052 (0x2744)

    Failed to create process of SetupWpf.exe. return value 1
    1/1/1601 12:00:00 AM
    2003259403 (0x7767500B)

    Setup cannot upgrade the ConfigMgr database. Contact your SQL administrator.

  • SK
    Posted at 3:42 PM March 10, 2017
    SK
    Reply
    Author

    Hi, I tried to upgrade SCCM 1602 to 1610
    hanged the CS server.
    after CS rebooting it’s working fine.

    Do I have to upgrade client by creating separate package (for manual update).

    Also Post Installation still Installing SMS_Executive Service stuck
    (We have Primary site MPs and DPs)

    Please let me know answer

    • Matt
      Posted at 2:33 PM March 13, 2017
      Matt
      Reply
      Author

      We have the exact same issue…

    • KACouillard
      Posted at 2:40 PM May 5, 2017
      KACouillard
      Reply
      Author

      The issue was with corrupt SQL tables.  We moved the ConfigMan_DB to a new SQL server, obtained a clean backup copy of the DB, successfully ran the test database upgrade procedure. 
      thanks
      KACouillard

  • Tony
    Posted at 8:43 PM February 16, 2017
    Tony
    Reply
    Author

    In our environment we have many distributed workstation support groups, so due to political reasons we are not able to “auto update SCCM clients”. Instead we have to create a package that each workstation admin group can deploy when they are ready. To build a package to upgrade the existing clients to SCCM 1610, which source content should be used?

    \\\SMS_\Client\
    \\\SMS_\ClientUpgrade\

    -Tony

  • Josh
    Posted at 10:55 AM February 15, 2017
    Josh
    Reply
    Author

    FYI My client version shows as 5.00.8458.1007 Not 5.00.8458.1005 as your did.

  • David G
    Posted at 5:24 PM January 30, 2017
    David G
    Reply
    Author

    Great article, and helpful. I noticed a question above about the ADK update – I have the same question as to that timing. Same question with the MDT update.

  • Paul B
    Posted at 4:24 PM January 12, 2017
    Paul B
    Reply
    Author

    do you know if /testdbupgrade is still something we need to do before we upgrade to 1610? If so, how do we go about that, since there is no direct access to the installation media.

  • JJ
    Posted at 5:08 AM January 5, 2017
    JJ
    Reply
    Author

    Great site! Testing 1610 update in the lab. I have a hierarchy CAS and Primary and Secondary. How do I stop the Primary getting auto updated (that would be a disaster in prod!) Service window? but how to configure? Thanks

    • JJ
      Posted at 6:50 AM January 5, 2017
      JJ
      Reply
      Author

      Ok after the install starts (!) on the down level Primary there is a step “Check Service Window” and it sits there waiting…if you’ve got the Service Window set up correctly that is!

  • Paul
    Posted at 6:01 PM December 28, 2016
    Paul
    Reply
    Author

    Great guide. Was a nice smooth upgrade for me from 1602. One thing I did notice is my client version ends in 1007

    • Benoit Lecours
      Posted at 2:58 PM January 5, 2017
      Benoit Lecours
      Reply
      Author

      Yes it can vary depending of the ring you’ve installed it.

  • EddieM(13)
    Posted at 4:24 PM December 16, 2016
    EddieM(13)
    Reply
    Author

    I’m having an issue. I did the prereq check and it finished ok. When I started the install, it got to the updating the database step and hung. Not 1610 says installing and wont error or finish. It obviously tanked everything else as the db won’t update.
    from cmupdate.log
    *** [23000][515][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot insert the value NULL into column ‘LogTime’, table ‘CM_OPS.dbo.Logs’; column does not allow nulls. INSERT fails. : spLogEntry CONFIGURATION_MANAGER_UPDATE 12/16/2016 4:10:40 PM 1456 (0x05B0)
    ERROR: Failed to executive [spCMUAddMonitorMessage N’OPS’, 0, 3, 1] to save site status. CONFIGURATION_MANAGER_UPDATE 12/16/2016 4:10:40 PM 1456 (0x05B0)
    Failed to report status 30001 CONFIGURATION_MANAGER_UPDATE 12/16/2016 4:10:40 PM 1456 (0x05B0)

    • Mr. Macy
      Posted at 6:34 PM December 29, 2016
      Mr. Macy
      Reply
      Author

      Same issue here. mine is stuck in the installation status, no way to remove it.

    • Don
      Posted at 5:14 AM March 14, 2017
      Don
      Reply
      Author

      Same issue here. Prereq check passed, but now hangs on DB Upgrade with same error message.

  • Adam
    Posted at 10:31 AM December 15, 2016
    Adam
    Reply
    Author

    Is it still recommended to uninstall existing ADK, update to 1610, and then install the new ADK and update Boot Images?

  • Fabian
    Posted at 10:14 AM December 13, 2016
    Fabian
    Reply
    Author

    Do you hap[pen to know In what future version of SCCMwill the production version of ‘Server Groups’ be released??

    • Jonathan Lefebvre
      Posted at 1:45 PM December 13, 2016
      Jonathan Lefebvre
      Reply
      Author

      Hi,
      we don’t know that information. If we compare to 1606, Windows Store for business integration was in Pre-release… now with 1610, it is release.
      Can’t say it will be the same with those features…
      Jonathan

  • Matthew Stout
    Posted at 8:21 AM December 7, 2016
    Matthew Stout
    Reply
    Author

    Seeing a stange issue after updating my small SCCM CB infrastructure (currently building it side by side with 2012 R2). After performing the 1610 upgrade, in my FSPStateMessage.log file I’m seeing the following error…

    Failed to create HTTP connection
    [CCMHTTP] ERROR: URL=HTTP:///SMS_FSP/.sms_fsp, Port=80, Options=224, Code=12005, Text=ERROR_WINHTTP_INVALID_URL
    Successfully queued event on HTTP/HTTPS failure for server ‘[]’.
    State message with TopicType 1000 and TopicId CCM Framework Communication State has been sent to the FSP

    It appears to be missing the server name in the URL. On my Primary and Secondary (which have been upgraded w/upgraded clients) are experiencing the issue. My clients, which are still running the older 1606 client, are not displaying this behavior. Wondering if you’re seeing this as well. Thanks!

  • Terrence
    Posted at 3:34 PM December 1, 2016
    Terrence
    Reply
    Author

    How does the dialog branding work? I cannot find any documentation.

  • J
    Posted at 10:20 AM November 30, 2016
    J
    Reply
    Author

    Another great article!

    I have a quick question regarding the new features – how do I turn off previously enabled features? (Under Administration > Cloud Services > Updates and Servicing > Features)

    Cheers,
    J

  • erikbennett
    Posted at 9:11 PM November 29, 2016
    erikbennett
    Reply
    Author

    We have 1511 installed, and I see 1602 and 1606 in our console, but not 1610. I know 1511 is stated as the minimum, but has anyone confirmed this? (And yes, I’ve already tried running the PowerShell script with no luck.)

  • Enort
    Posted at 3:39 PM November 25, 2016
    Enort
    Reply
    Author

    Any error list out there for 1610? I see and here stuff about discovery method not working as well as maintenance tasks After Upgrade

  • Ryan Engstrom
    Posted at 11:37 AM November 23, 2016
    Ryan Engstrom
    Reply
    Author

    Has the automatic client upgrade behavior changed in the last two builds? If I remember correctly from 1511, once clients checked in, they would have a scheduled task created to upgrade the client to the current version. I saw with 1606 and now with 1610 that no scheduled task appears (running task scheduler as a standard user or as admin). In the past, I would manually run the upgrade from the scheduled task. I do see clients are automatically upgrading throughout my network, but is there a way to force it for a client that has not yet updated? Thanks!

    • Jonathan Lefebvre
      Posted at 12:35 PM November 23, 2016
      Jonathan Lefebvre
      Reply
      Author

      Hi Ryan,

      to force a client to upgrade, simply use the Install Client from the console.
      That will force the upgrade right away!
      Jonathan

  • Eric D
    Posted at 11:01 AM November 23, 2016
    Eric D
    Reply
    Author

    About this step: SCCM 1610 Client Package distribution – You’ll see that the 2 client packages are updated. It’s only true if you selected to Upgrade Without Validating. If you selected Validate in Pre-production Collection like I did, only Configuration Manager Client Piloting Package will be update.

  • Sunil
    Posted at 3:17 PM November 22, 2016
    Sunil
    Reply
    Author

    I get the below error in Dmpdownloader.log while upgrading from 1606 to 1610, please help me

    – I have already tried restarting the service
    – Reg fix is also not working which is mentioned in below link
    https://docs.microsoft.com/en-us/sccm/core/servers/deploy/install/release-notes

    ERROR: Failed to download redist for c43a89e4-b642-4fc8-abf0-255bf5d88d82 with command /RedistUrl http://go.microsoft.com/fwlink/?LinkID=831290 /LnManifestUrl http://go.microsoft.com/fwlink/?LinkID=831291 /RedistVersion 112015 /NoUI

  • Jamie M
    Posted at 4:41 AM November 19, 2016
    Jamie M
    Reply
    Author

    Excellent article, thank you. 😀

    • Benoit Lecours
      Posted at 1:52 PM November 22, 2016
      Benoit Lecours
      Reply
      Author

      Thanks

      • express kredit selbstaendig machen
        Posted at 10:45 AM February 8, 2017
        express kredit selbstaendig machen
        Reply
        Author

        Hi, I really enjoyed this post, it’s enabled me to put some affilate ads in my “Pages” on my Word Press blog.Thanks a bunch & please stop by. I’m going to add you to my blog roll, and feature some of your articles in my “Sunday Seven” posts.Thanks!

  • Leave a Reply