Step-by-Step SCCM 1606 Upgrade Guide

Benoit LecoursSCCM73 Comments

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

Update 2016/10/12

SCCM 1606 is now available as a new baseline media. You can use this new media to install a new site, or upgrade from System Center 2012 Configuration Manager with Service Pack 2 or System Center 2012 R2 Configuration Manager with Service Pack 1. See the Technet documentation for more information about the new media.

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

SCCM 1606 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 (1603 and up).

Consult this Technet article for a full features list. 1606 also applies the latest KB/fixes to fix known bugs…. Including KB3155482 but not KB3174008 (which was release a week prior to 1606). If you had already installed KB3174008, 1606 will revert the fixes included in KB3174008. Microsoft recommendation is to skip this KB (unless you are really blocked by this), update to 1606 and wait for a new KB that will be available for 1606 soon. (Which will include KB3174008).

This is also the SCCM version that will bring support for the Windows 10 Anniversary update.

Here’s our list of favorite features :

  • Option for clients to switch to a new software update point
    • You can enable the option for Configuration Manager clients to switch to a new software update point when there are issues with the active software update point.
  • Per-app VPN for Windows 10 devices
    • For Windows 10 devices managed using Configuration Manager with Intune, you can add a list of apps that automatically open a VPN connection that you have configured through the Configuration Manager admin console. You have the option of restricting VPN traffic to those apps, or you can continue to allow all traffic through the VPN connection.
  • Customize the RamDisk TFTP block size and window size on PXE-enabled distribution points
    • You can customize the RamDisk TFTP block size and window size for PXE-enabled distribution points. If you have customized your network, it could cause the boot image download to fail with a time-out error because the block or window size is too large. The RamDisk TFTP block size and window size customization allow you to optimize TFTP traffic when using PXE to meet your specific network requirements
  • Improvements to the Install software updates task sequence
    • A new task sequence variable, SMSTSSoftwareUpdateScanTimeout, is available to give you the ability to control the timeout on the software updates scan during the Install software updates task sequence step. The default value is 30 minutes.
    • There have been improvements to logging. The smsts.log log file will contain new log entries that reference other log files that will help you to troubleshoot issues during the software updates installation process.

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 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, console 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

15689 (6)

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

15689 (3)

  • The update state will change to Downloading

15689 (4)

  • You can follow the download in Dmpdownloader.log

15689 (5)

  • The update files are stored in the EasyPayload folder in your SCCM Installation directory

15689 (7)

 

SCCM 1606 Upgrade guide

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

15689 (8)

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

15689 (10)

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

15689 (11)

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

15689 (12)

  • When completed the State column will show Prerequisite check passed

15689 (13)

Step 2 | Launching the SCCM 1606 update

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

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

15689 (9)

  • On the General tab, click Next

15689 (14)

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

15689 (15)

  • 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
    • This new feature allows to update only clients member of a specific collection. Refer to the Technet article for more details

15689 (16)

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

15689 (17)

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

15689 (18)

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

15689 (19)

  • 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

15689 (21)

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

15689 (20)

Warning
We’ve done numerous SCCM 1606 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

15689 (22)

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

15689 (23)

Updating the consoles

As in 1602, 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.8412.1003. You can also notice that Version 1606 is stated.

15689 (24)

Servers

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

15689 (25)

Clients

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

15689 (27)

SCCM 1606 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 :

  • 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

15689 (28)

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.8412.1006'

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 1606 Upgrade Guide
5 - 10 votes

73 Comments on “Step-by-Step SCCM 1606 Upgrade Guide”

  1. Hi,

    We’re running SCCM 2012 R2 SP1 on a Windows Server 2008 R2 machine. Having a CAS and 2 Primary Sites.

    We’re planning for an upgrade to 1606 Baseline (as per the above guide).

    But I’ve just learnt that there might be some limitations around WSUS version, if you’re using SCCM for pushing updates.

    For e.g. products like Office 365 require atleast WSUS 4.0 which is only compatible on Windows Server 2012 and higher.

    Is there more I need to be concerned about regarding WSUS given the above roadmap?

    1. Hi Samuel,
      First question, why a CAS?

      Considering that the OS (2008R2) is no longer supported on SCCM 1702 and above, your SCCM 1606 will “soon” be unsupported, you might want to do a side-by-side migration.
      here our post about it. https://www.systemcenterdudes.com/sccm-1511-migration/

      You could benifit from this by :
      – Review the structure of SCCM and remove the CAS
      – Use latest OS for site server
      – Use latest WSUS for O365 updates

      Jonathan

  2. Hi Benoit Lecours,
    First of all Thanks for this great post!
    I am currently running SCCM 2012 R2 SP1, and looking for upgrading to 1606(Build 5.00.8412.1307) baseline version.
    I want to understand, whether or not I can use the similar steps of upgrading SCCM 2012R2 SP1 to SCCM 1511, for upgrading to 1606((5.00.8412.1307) baseline version? Since this is a baseline version after 1511, I believe in console upgrade won’t be available, so is it recommended to follow the 1511 upgrade guide or is there any separate prerequisite required for 1606 upgrade.
    Also in the above post we see, KB3186654 hotfix is required as one of the fixes to the known bugs, so is that a separate download or a rollup bundled with 1606 baseline .iso download, if separate download, is that recommended to install before or after upgrade?

  3. Pingback: Step-by-step sccm 1606 upgrade guide windows 10 download process

  4. Pingback: Top 10 Improvements in ConfigMgr 1606 | Sccm 2012

  5. Hi Guys,

    Trying to do a brand new SCCM 1606 Install…

    We’ve got a dedicated SQL Server running on a non-standard SQL port (and I know there’s articles that say it should be done locally, but we need to keep them separate), and I cannot get the install to pick up the instance.

    I also read that the SQL Browser is not required (although I do have it active and it still won’t work).

    Watching the behaviour of the setup via netstat and it only attempts to connect on TCP/1433. I cannot use “:port” or “,port” in the SQL Server name during the setup either.

    Can you please advise how we can accomplish this?

    Cheers,
    Ray

  6. My System Center is on 1511 and trying to upgrade to 1606, few days back I did the pre-requisite check for 1606 and it was passed but now all options are disabled including Update Install Pack so how I can enable the option to do the upgrade? please advise.Thanks

  7. Installation fails for me, when checking install status, but is still installing, is this also normal behavior and just takes some time ? Means it is always stating “failed” and then “installing” again…
    Dont know what i should try. 😀

    1. Solved it after a while.
      Following.

      Deleted the Update from DB.
      Started the update of Hotfix 1 1606
      In the CMUpdate.log i found a error which leads to a failure.
      Then i saw many files like *.xcs. I found those files in another folder from the Main upgrade package (i guess). i copied them to the Source dir (.\EasySetupPayload\76…..), then i ran it again, after putting all the missing files (took me several runs) the upgrade installed successfully, and also recovered my SCCM from disastrous status.

      Text me by mail if you need help with my steps. It worked for me, but it is probably completely unsupported.
      Thanks Microsoft for leaving us alone with such stupid malfunctions of this shitty piece of Software.

      Reagrads

      Dennis

  8. Hi,

    Thanks to Benoit for such awesome guide, we’ve upgraded to CM1606 with Hotfix (KB3186654) and it works great. But there is something weird happening in CMUpdate.log shows below: every 10 minutes since.

    There are no pending update package to be processed.
    Waiting for changes to the “C:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box” directories, updates will be polled in 600 seconds…

    I may be over worried as the site are running well but this has been repeating non stop for 2 days…

        1. Your smile looks great. All the black and blue and trips to the orthodontist were well worth it — you look incredible! We are fans of adult braces in this family, as you know, but I was lucky enough to have them twice in my teens, so here’s hoping I don’t have to revisit it as an adult.

  9. After the upgrade, did your boot image version change? mine looks to be still showing 1511 version number even though I selected to update boot images.

  10. Hi,

    I thought the in console servicing was a great idea, till now. My first two updates 1511 and 1602 prereq and install tasks went without a hitch. When the 1602 hotfix came out, it became stuck at “Checking Prerequisites” and eventually the status reported “Replication failure”. This is a single primary site, nothing complicated. I followed the TechNet article and removed the update from the database (yes, I know, don’t do that!). It reappeared after restarting sms_exec and checking updates again. I started researching the issue and the community seemed to feel that just going 1606 was the best way to go. Same failure. I would appreciate some guidance on this and feel that Microsoft is making it very difficult on Config Manager customers by doing away with the manual updates, as you get detailed feedback if problems are encountered. Where to turn for help?, except for getting out the credit card to pay for a support case. Worst part is it worked fine for the first two updates, but is now broken. There doesn’t seem to be any way to resync / rerun prerequisite jobs or to reset the Site Servicing component to a clean state.

    1. That’s exactly what I’m dealing with right now for the auto upgrades. It wouldn’t be so bad if there was a way to retry and/or transfer the files.

      We’re actually have a lot of distribution issues with 1610 and previously issues with distribution/validation of patches on 1602. There’s KBs to install that have potential fixes for these but what can you do if it won’t distribute the KB?

      I’ve been working with support on these issues for almost a month with partner support. Terrible support by the way, they kept telling me I needed to rebuild the apps, packages, patches, OS images and of course that would also require us to rebuild our tasks and anything else referencing these items. That alone is a terrible “fix” let alone ignoring that we can’t do that for their own packages that are distributed and managed by SCCM, including the updates.

  11. Hi Dudes, We’re looking to upgrade from SCCM 2012 R2 SP1 to SCCM 1606. I already understand that we’ll need to upgrade to SCCM 1511 first and then to SCCM 1606, but I’m hoping we don’t have to update all our existing console and clients twice to do this. Can you go from SCCM 2012 R2 SP1 client and consoles directly to SCCM 1606 client and consoles?. Don’t want to wait after SCCM 1511 upgrade for clients to update to 1511 before we go to SCCM 1606.

    1. Hi Gordon,
      You don’t have to upgrade clients between version.
      the console MUST match the major version release in order to work.

      The local console on the primary server will auto-upgrade as part of the installation of 1511 and 1606. As for remote console, I suggest to wait until the server is up to 1606 prior to upgrade them.

      You may want to consider upgrading your 2012 to 1606 directly.
      Microsoft as released a new baseline ISO. It should be available to you on your volume licensing :https://blogs.technet.microsoft.com/enterprisemobility/2016/10/12/configuration-manager-a-progress-update-on-the-current-branch-and-a-new-servicing-branch/

      we haven’t tested or documented to process so far.

      Jonathan

      1. Hello, I have SCCM 2012 R2 Version 5.0.7958.1401
        Can I go and upgrade straight to version 1606 then?

        Thanks,

        Goran

  12. Hi
    I am upgrading from 1602…I was upgrading from 1511 but when I got MS Support to assist they pushed 1602 without asking me. So I am trying to upgrade from 1602 to 1606…the prerequisites failed with one failure:[Failed]:Checking whether there are custom Client Agent Settings that enable NAP
    everything else has passed. is there a way for me to get through this check with clicking ignore pre-requisites on the install wizard?

    1. encore faut-il en trouver un de travail de nos jours c&ssruo;eqt un luxe … En ce moment je fais des ourlets le mardi pour une association bénévole, les petits riens.

  13. Hello,

    If we have a Independent Primary Site version 1606 and we want expand to with CAS server.

    what version sccm install in the CAS server? if we can not install version 1606 and we have install version 1511 in the CAS, there would be no compatibility problems with the replication primary site?

    Thanks.

    1. Hi David,

      You will need to use the CD.latest to install your CAS.
      follow the information here : https://technet.microsoft.com/en-us/library/mt703293.aspx?f=255&MSPPError=-2147217396

      “To expand a stand-alone primary site: When you are expanding a stand-alone primary site by installing a new central administration site, you must use Setup and the source files from the CD.Latest folder from the primary site to install the new central administration site. When run from a copy of the CD.Latest folder from the primary site, it uses installation source files that match the version of the primary site. For more information see Expand a stand-alone primary site) in Use the Setup Wizard to install sites”

      Jonathan

  14. We are attempting to upgrade ConfigMgr from 1602 to 1606 and it keeps getting stuck in “Installing” state. We tried restarting SMS_Executive service with no luck. We also tried running the CM_UpdatePackageSiteStatus so that it sets the state back to “Available” and tried the install again, repeatedly getting stuck in the “Installing” state. The installation files downloaded to (1.7GB) EasySetupPayload folder. We don’t see any errors in logs besides seeing “Waiting for changes to the “C:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box” directories, updates will be polled in 600 seconds…” in the CMUpdate.log file. hman.log shows no errors that stick out either. Anyone out there have any ideas? Willing to post more information as needed. Thanks.

    1. Hi Ricardo

      Have the same problem, and have opened a case by Microsoft

      Have you find any solutions

      Flemming

  15. Pingback: ConfigMgr Updates and Servicing Download Issues – deploymentramblings

  16. Maybe someone can confirm this: I have test site that I update prior to production. I updated my test site to 1606 and now can’t connect with the newer console to my production 1602 Site.

    1. Hi Mark,
      historically, the console must be at the same ‘major release’ level as the site.

      With SCCM 2012 that would mean same service pack.
      With SCCM CB, that mean same CB version.

      Jonathan

  17. Hi I am trying to upgrade from 1602 to 1606 and I am stuck at the precheck during the install. I checked the forums regarding critical inboxes, but they only mention ccretry and I had nothing in it, so I went ahead with the install. See CMUPdate log entires below:

    Log file shows waiting for CCMUPdate directory updates, but nothing in the directory at all. Any thoughts about how to fix this problem, so the install will succeed.?

    There are site server reporting WARNING in prereq check. Setup will not continue.. CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:12:47 PM 1516 (0x05EC)
    Waiting for changes to the “C:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box” directories, updates will be polled in 600 seconds… CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:12:47 PM 1516 (0x05EC)
    Detected a change to the “C:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box” directory. CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:14:15 PM 1516 (0x05EC)
    INFO: setup type: 1, top level: 1. CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:14:15 PM 1516 (0x05EC)
    Content replication succeeded. Start extracting the package to run prereq check… CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:14:15 PM 1516 (0x05EC)
    Checking if the CMU Staging folder already has the content extracted. CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:14:15 PM 1516 (0x05EC)
    Creating hash for algorithm 32780 CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:14:15 PM 1516 (0x05EC)
    Staging folder has hash = 007BD3681B97290543667F0BB386F95FBAD7A781D25102237981327A20FFA5FC CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:16:56 PM 1516 (0x05EC)
    Staging folder (C:\Program Files\Microsoft Configuration Manager\CMUStaging\0D256560-ED2C-45B5-8D75-4D38AB3F758C\) has hash AA0C1A133C1F095384128EDC63545C7D52AB7CABB190EBCFF41E7454A8BAB9BF which does not match hash from content library 007BD3681B97290543667F0BB386F95FBAD7A781D25102237981327A20FFA5FC CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:16:56 PM 1516 (0x05EC)
    Delete folder C:\Program Files\Microsoft Configuration Manager\CMUStaging\0D256560-ED2C-45B5-8D75-4D38AB3F758C\ returned 0 CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:17:00 PM 1516 (0x05EC)
    update package content 0D256560-ED2C-45B5-8D75-4D38AB3F758C has been expanded to foler C:\Program Files\Microsoft Configuration Manager\CMUStaging\0D256560-ED2C-45B5-8D75-4D38AB3F758C\ CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:18:32 PM 1516 (0x05EC)
    File ‘C:\Program Files\Microsoft Configuration Manager\CMUStaging\0D256560-ED2C-45B5-8D75-4D38AB3F758C\SMSSetup\update.map.cab’ is signed and trusted. CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:18:32 PM 1516 (0x05EC)
    Signing root cert’s thumbprint: cdd4eeae6000ac7f40c3802c171e30148030c072 CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:18:32 PM 1516 (0x05EC)
    Extracting file C:\Program Files\Microsoft Configuration Manager\CMUStaging\0D256560-ED2C-45B5-8D75-4D38AB3F758C\SMSSetup\update.map.cab to C:\Program Files\Microsoft Configuration Manager\CMUStaging\0D256560-ED2C-45B5-8D75-4D38AB3F758C\SMSSetup\ CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:18:32 PM 1516 (0x05EC)
    Extracted C:\Program Files\Microsoft Configuration Manager\CMUStaging\0D256560-ED2C-45B5-8D75-4D38AB3F758C\SMSSetup\update.map CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:18:32 PM 1516 (0x05EC)
    Successfully read file C:\Program Files\Microsoft Configuration Manager\CMUStaging\0D256560-ED2C-45B5-8D75-4D38AB3F758C\SMSSetup\update.map CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:18:32 PM 1516 (0x05EC)
    FQDN for server SCCM is SCCM.seta.net CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:18:32 PM 1516 (0x05EC)
    INFO: Target computer is a 64 bit operating system. CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:18:32 PM 1516 (0x05EC)
    INFO: Checking for existing setup information. CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:18:32 PM 1516 (0x05EC)
    INFO: Setting setup type to 1. CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:18:32 PM 1516 (0x05EC)
    INFO: Checking for existing SQL information. CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:18:32 PM 1516 (0x05EC)
    INFO: ‘SCCM.seta.net’ is a valid FQDN. CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:18:32 PM 1516 (0x05EC)
    INFO: Verifying the registry entry for Asset Intelligence installation CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:18:32 PM 1516 (0x05EC)
    INFO: Found registry key for installation of Asset Intelligence full version CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:18:32 PM 1516 (0x05EC)
    INFO: Setup detected an existing Configuration Manager installation. Currently installed version is 8355 CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:18:32 PM 1516 (0x05EC)
    INFO: Phase is 1C7 CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:18:32 PM 1516 (0x05EC)
    INFO: SDK Provider is on SCCM.seta.net. CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:18:32 PM 1516 (0x05EC)
    Set working directory to the staging folder C:\Program Files\Microsoft Configuration Manager\CMUStaging\0D256560-ED2C-45B5-8D75-4D38AB3F758C\SMSSetup CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:18:32 PM 1516 (0x05EC)
    INFO: Setting the default CSV folder path CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:18:32 PM 1516 (0x05EC)
    INFO: Language: Mobile Device (INTL), LangPack: 0. CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:18:32 PM 1516 (0x05EC)
    INFO: Configuration Manager Build Number = 8412 CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:18:33 PM 1516 (0x05EC)
    INFO: Configuration Manager Version = 5.0 CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:18:33 PM 1516 (0x05EC)
    INFO: Configuration Manager Minimum Build Number = 800 CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:18:33 PM 1516 (0x05EC)
    Preparing prereq check for site server [SCCM.seta.net]… CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:18:33 PM 1516 (0x05EC)
    prereqcore has hash value SHA256:D6A00BE674533A027A240E60B46C81B5384B58AD20652D907F4DE26C0803D9A9 CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:18:34 PM 1516 (0x05EC)
    Running prereq checking against Server [SCCM.seta.net] … CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:18:34 PM 1516 (0x05EC)
    Waiting for changes to the “C:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box” directories, updates will be polled in 240 seconds… CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:18:47 PM 1516 (0x05EC)
    Detected a change to the “C:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box” directory. CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:18:47 PM 1516 (0x05EC)
    Waiting for changes to the “C:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box” directories, updates will be polled in 240 seconds… CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:18:47 PM 1516 (0x05EC)
    Detected a change to the “C:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box” directory. CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:18:47 PM 1516 (0x05EC)
    Waiting for changes to the “C:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box” directories, updates will be polled in 240 seconds… CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:18:47 PM 1516 (0x05EC)
    INFO: setup type: 1, top level: 1. CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:22:47 PM 1516 (0x05EC)
    There are site server reporting WARNING in prereq check. Setup will not continue.. CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:22:47 PM 1516 (0x05EC)
    Waiting for changes to the “C:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box” directories, updates will be polled in 600 seconds… CONFIGURATION_MANAGER_UPDATE 8/26/2016 3:22:47 PM 1516 (0x05E

  18. I have a question in regards to migrating from SCCM2012 to SCCM1606. I am wanting to migrate from a Server 2008 R2 with SCCM 2012 to SCCM 1606. If I choose to setup a new Windows Server 2012 install SCCM 1511 do I have to create migration job between 1511 and the SCCM 2012 system or can I go ahead and upgrade SCCM 1511 to SCCM1606 and the perform the migration job between SCCM 2012 and SCCM 1606? I cannot find any documentation specifying if this can be done. I only see documentation specifying that you cannot upgrade directly from SCCM 2012 to 1606 without first installing 1511 by my question is more specifically related to the possibility of migration after upgrading to 1606.
    Thanks for your help.

    1. Hi Dave,

      Not sure if you got your question answered but we just migrated our environment from a primary site server running 2008 R2 to a new matching server running 2012 R2. In our case we first upgraded all the way to 1602, waited about a month to verify everything was working properly, we then built a new server running 2012 R2 and match it across. That meant, roles, applications (ADK version), firewall rules, same IP/MAC and even same hostname. Then we basically did a site back up, shutdown old (2008 R2) and restored onto new 2012 R2 using the ConfigMgr installation located inside the CD.Latest folder from your site backup. I have some documentation about the process if you’re interested.

      1. I would be very interested in any documentation you had on this process. I am researching right now to do the very same thing.

      2. Hi Ricardo, will you be able to share the documentation of your migration from OS 2008R2 to 2012 R2.Thanks

      3. Ricardo, I am about ready to do the same and would appreciate your documentation if you still have it. Thanks Tom

  19. Hi Benoit,

    I have a test SCCM setup where I have 1 CAS and 3 primary sites all at 1602. I tried running pre req check to upgrade the environment to 1602. In site servicing status, it says content replication succeeded on 1 CAS and 2 primaries while one primary is stuck at replicating content from past 16 days. Nothing is happening in CMUPDATE, DMPDOWNLOADER or CONFIGMGRPREREQ logs.

  20. Just finished upgrading from 1602 to 1606 and everything seemed to go OK except under Hierarchy Settings>Client Upgrade, it still shows client version 5.00.8355.1306

  21. Hello All,

    We have 1 CAS and 4 primary server in our Infra. All servers are recently Upgrared from SCCM 2012 R2 SP1 to SCCM 1606
    I am looking for recommended plan to roll back to SCCM 1511 or SCCM 2012 r2 SP1.

    Looking for your support on this!!!

    1. குற்றம் செய்தவர்களை பற்றிய பதிவில் அவர்கள் மேல் குறை தான் வைக்க முடியும். அவர்களை பாராட்டவா முடியும்?பிரியாணி பொட்டலம் முதல் டீ வடை கணக்கு வரை கண்கானிக்கும் எலக்‌ஷ்ன் கமிஷன் ஏன் ஹெலிகாப்ட்டர் செலவை கண்கானிப்பதில்லை? ஏதோ குறையாக தெரியவில்லை.தீர்வு என்ன? செயல் திட்டம் என்ன என்று கேட்டுள்ளீர்கள்.நிச்சயம் உள்ளது. விரிவாக விவதங்கள் வழியே பார்க்க்லாம். நீங்கள் விவாதத்தை தொடர்ந்தால்…

  22. Hi – I am looking for information on uninstalling SCCM 1606 (and SCCM altogether) as I need to rebuild my lab. Historically, you would just relaunch the install media and select to uninstall, however my uninstall option is grayed out now. I believe this is because I am no longer on 1511 but rather on 1606 so it doesn’t detect the right version (just a guess). Anyways, please inform how to uninstall 1606 SCCM.

    1. Just use the media in the CD.Latest folder from your SCCM installation path. You’ll have the option to uninstall.

  23. Pingback: Deploying Configuration Manager Console 1606 (and hotfixes) with SCCM 1606 | Project: SCCM

  24. Pingback: SCCM 1606 – Disponible mondialement depuis le 04 août. – L2T

  25. Hello, I just upgraded our environment to 1606. A little while after starting the upgrade, I got a notice to close the console and allow the console to be upgraded. I did that, logged back in, and everything seemed ok. When I went back to the Updates and Servicing node, it says that it’s still installing. When I went to the Monitoring > Updates and Servicing Status it says that it’s Installed. If I check the about within the console, it shows it’s running the same versions that you demonstrated in the screenshots above. When I go to Sites and then properties of my site, it shows I’m running 8412 just like your screenshot. The weird thing is that when I check Monitoring > All Status Messages, it’s not showing anything recent, only messages from before the upgrade was initiated. I’m not even sure where to go from here. Does anyone have any ideas?

    1. From what you’re telling you should be on 1606. Double check that you SMS_Executive service is running.

      1. Ryan is right, I made my install using fast ring deployment (before it was release GA). Client version can differ from 1006 to 1007

  26. Pingback: EUC Weekly Digest – July 30, 2016 – Carl Stalhood

  27. For those who may be concerned. The SCCM client on Windows 2003 server (maybe XP, Vista and 2008 (non R2) stop working after applying 1606. The cache tab is no longer settable, and the Software Center (SCClient.exe) return error code 0x80041001 . The shortcut for Software Center stop running with 1511 on Windows 2003, but the SCClient.exe still works.

  28. Hello,

    for some reason I cant´t see update 1606 offer in SCCM (1606). Last update what I have there is KB3174008. I´ve tried to start check for new updates option, but still no upldate for 1606 is visible. Can you give me some hint? Thank you.

    M.

    1. @Martin – Before you install 1606, you get a intermediate update which is KB3174008. When you install the update, you need to check for the updates. This will take sometime but the update will appear in the updates and servicing node. In case it doesn’t appear, restart your SCCM server and then check for the updates.

      1. Thank you for fast answer, but now I´ll totally lost. In the beginning of this article I can see that MS doesn´t recommended to install KB3174008. Also on screenshots here I can see that KB3174008 is not installed in SCCM, but update 1606 is visible. So where is the truth 🙁

        1. @Martin: sorry for reaction on your post, but I have also the same issue and update is not visible till now (I haven´t installed KB3155482 and KB3174008 yet). But what I´ve read here and also on MS pages, KB3155482 is included in 1606 installation and KB3174008 is not recommented to install, just wait till new update for 1606 will be realised (or install it, but just if you have issue with freezing updates during the Win10 TS).

          1. Sam Issue here. No Update 1606 visible in Updates and Servicing (both Hotfixes are not installed).

    2. Hi,

      As for 1602, Microsoft is rolling it out slowly as stated in this blog post :
      https://blogs.technet.microsoft.com/enterprisemobility/2016/07/22/now-available-update-1606-for-system-center-configuration-manager/

      “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 needed, you can run this PowerShell script to Opt-in right away.
      https://gallery.technet.microsoft.com/ConfigMgr-1606-Enable-043a8c50

      For what I know, there is NO intermediate updates to be applied before 1606.
      Both KB available are NOT mandatory to upgrade to 1606

      Jonathan

  29. Hi Guys,

    thank you for info. I´d like to ask, is it necessary to use new boot images or I can use older boot images based on 1602 and with all features what I have in them? Thank you.

  30. Pingback: SCCM Current Branch Update 1606 | Build Numbers

Leave a Reply

Your email address will not be published. Required fields are marked *