Update 2 for Configuration Manager current branch, version 1706 first wave is now available


Administrators who opted-in to the first (early) wave deployment for System Center Configuration Manager current branch, version 1706, have an update available in the Updates and Servicing node of the Configuration Manager console. This update, made available on August 31, 2017, addresses important late-breaking issues that were discovered during the final release process for version 1706. 

For more information, including the issues fixed and the applicability of the update, please read:

4036267 : Update 2 for System Center Configuration Manager version 1706, first wave - https://support.microsoft.com/help/4036267


Comments (7)
  1. Rick Crawford says:

    We are seeing an issue with the download of 4036267 using the offline service connection tool.  Once downloaded the cab has a GUID of 0F11CAA4-7F7F-454B-96D6-75F427D015CE.  In the console, the update has a GUID of C81C693D-33CF-4497-BB40-D4801ABBF284.  I thought the original downloaded manifest had not been updated with the correct GUID so I re-downloaded and imported this morning.  I am still seeing the same behavior.

    1. Hello Rick

      The service connection tool downloads all available updates identified by the manifest whether or not they are currently applicable to your site. ConfigMgr then figures out applicability and displays only the applicable updates in the console.

      The cab with GUID 0F11CAA4-7F7F-454B-96D6-75F427D015CE is a build of Update 1706. If the site already has 1706 installed, it is not applicable. It would be applicable to sites running 1702, 1610 etc.
      The cab with GUID C81C693D-33CF-4497-BB40-D4801ABBF284 is Update KB4036267. If you have 1706 installed (with one of specific the GUIDs listed in the KB) then this update is applicable to you and will show in the console.

      Hope this helps to clarify.
      Regards
      Yvette

  2. Jason Hill says:

    Hi this page says the update was made available on August 31’st but the support page for 4036267 says this update does not apply to sites that downloaded version 1706 from August 8, 2017 am I to assume if its showing in console its applicable to my site we upgraded 16th August.

    1. Hello Jason

      We have recently changed the update to apply to all revisions of 1706 and we updated the KB but it looks like we missed that sentence in the Summary section. The I’ll ask the KB writers to remove it. The correct applicability information is in the section titled ” Update information for System Center Configuration Manager, version 1706″. If the update appears in the console for you, then it is applicable to your site.

      Sorry for the confusion.
      Yvette

  3. Chris DAmico says:

    I installed the update on my brand new Primary site the other day. This is a side-by-side install as we prepare to migrate from SCCM 2012. The site had KB4039380 installed. After installing the KB4036267 update, the versions are as follows.

    1. The Primary site version still shows 5.00.8540.1000.
    2. I did a recovery of the secondary sites per the instructions and those site versions show 5.00.8540.1000.
    3. The client version shows 5.00.8540.1007 but the console shows 5.00.8540.1005.
    4. Console version 5.0.8540.1601.

    Is this correct?
    Thanks!

    1. Chris DAmico says:

      Also:

      select dbo.fnGetSecondarySiteCMUpdateStatus (‘SiteCode_of_secondary_site’) does not work. It throws an error.

    2. Hello Chris

      Yes this is correct.
      The displayed site versions will always be the base version (regardless of hotfixes applied) which for 1706 is 5.00.8540.1000.
      Console version you see 5.0.8540.1601 is the version of the console that came with Update 2 KB4036267.
      Client version 5.00.8540.1005 shipped with Update 1 KB4039380. Client version 5.00.8540.1007 shipped with Update 2 KB4036267. The discrepancy you see may be due to the hardware inventory cycle.

      Best regards
      Yvette

Comments are closed.

Skip to main content