ConfigMgr 2006 Hotfix KB4578605 SCCM | Update Rollup | 22 Fixes

0
ConfigMgr 2006 Hotfix KB4578605

Microsoft released a major rollup update for ConfigMgr 2006 with 22 fixes. Let’s check more details about ConfigMgr 2006 Hotfix KB4578605. Also, there could be many more undocumented fixes and features made available in this Hotfix Rollup Microsoft KB Article KB4578605 for ConfigMgr 2002 production version.

There is some additional Tenant attach feature with HFRU and that is firewall policies. The update rollup will be available for all the applicable (SQL applicability rules) online service connection point SCCM implementations.

NOTE! – Install the latest Revised ConfigMgr 2006 Hotfix Rollup Update KB4575789.

Known Issue with Update Rollup

NOTE! – Configuration Manager upgrade with an Offline Service Connection Point is a different scenario altogether.

I have posted about the known issues of Configuration Manager 2006. Another 22 known issues of the SCCM 2006 production version is fixed with this HFRU.

The following KBs are superseded with SCCM Hotfix Rollup KB4578605.

NOTE! – The Supersedence KB details are available in the Admin console. This is very useful information for Admins. So if you are installing KB 4578605, you don’t need to install the superseded KBs.

ConfigMgr 2006 Hotfix KB4578605  SCCM | Update Rollup | 22 Fixes
ConfigMgr 2006 Hotfix KB4578605 SCCM | Update Rollup | 22 Fixes

Install Hotfix Rollup for ConfigMgr 2006 Primary Server

The installation process of Hotfix Rollup for ConfigMgr 2006 Primary Server is similar to all the other hotfix installations. You need to install the hotfix either on the CAS or stand-alone primary server.

The child primary servers shall get automatically updated.

  • Launch the Configuration Manager Console,
  • Select the Administration tab,
  • Expand Overview -> Select Updates and Services
  • The update Configuration Manager 2006 Hotfix Rollup KB4578605 is Ready to install stage
  • Right-click on the update and click on Install Update Pack
ConfigMgr 2006 Hotfix KB4578605  SCCM | Update Rollup | 22 Fixes
ConfigMgr 2006 Hotfix KB4578605 SCCM | Update Rollup | 22 Fixes
  • Click Next
ConfigMgr 2006 Hotfix KB4578605  SCCM | Update Rollup | 22 Fixes
ConfigMgr 2006 Hotfix KB4578605 SCCM | Update Rollup | 22 Fixes
ConfigMgr 2006 Hotfix KB4578605  SCCM | Update Rollup | 22 Fixes
ConfigMgr 2006 Hotfix KB4578605 SCCM | Update Rollup | 22 Fixes
  • Accept the license and click on Next to continue.
ConfigMgr 2006 Hotfix KB4578605  SCCM | Update Rollup | 22 Fixes
ConfigMgr 2006 Hotfix KB4578605 SCCM | Update Rollup | 22 Fixes
  • Click Next, Next, and close to start the ConfigMgr 2006 Hotfix Rollup update (KB4578605).
Summary of update package installation
Install Update Package Configuration Manager 2006 Hotfix Rollup (KB4578605)
Prerequisite warnings will be ignored
Test new version of the client in production
ConfigMgr 2006 Hotfix KB4578605  SCCM | Update Rollup | 22 Fixes
ConfigMgr 2006 Hotfix KB4578605 SCCM | Update Rollup | 22 Fixes

Install Hotfix on Secondary Server

I will let you read through the Secondary Server Hotfix Installation Guide, Fix Secondary Server Recovery Failed Issue, and Secondary Server Hotfix Installation Status.

Follow the steps mentioned below:

  • To update a secondary site in the ConfigMgr console.
  • Click Administration, click Site Configuration, click Sites, click Recover Secondary Site
  • Then select the secondary site you want to upgrade.
  • The primary site then reinstalls that secondary site by using the updated files.
ConfigMgr 2006 Hotfix KB4578605  SCCM | Update Rollup | 22 Fixes
ConfigMgr 2006 Hotfix KB4578605 SCCM | Update Rollup | 22 Fixes

NOTE! – Configurations and settings for the secondary site are not affected by this reinstallation.

Known Issues Fixed with ConfigMgr 2006 Hotfix Rollup KB4578605

You can get the similar information in the Hotfix Rollup KB4578605 update as well. However, I thought the following table would be easy to read and understand.

SLKnown Issues fixed with ConfigMgr 2006 Hotfix Rollup KB4578605
1During client policy download, the execmgr.log repeats the following log entry multiple times every minute.
2Client computers that are performing a PXE boot to install a new operating system are unable to find the boot WIM file. This occurs when the WIM file is stored in a content library split across multiple drives. Errors resembling the following are recorded in the SMSPXE.log file.
3Computers are unexpectedly removed from orchestration groups. This occurs if the site has the option to Use this boundary group for site assignment enabled, but the target computers are not in that boundary group.
4Clients are unable to communicate over a custom port for a management point when other communications changes are made to the site.
5State messages from clients may not be properly recorded if the client computer restarts within 10 seconds of state message generation. This results in inconsistent or unexpected state message values, affecting the accuracy of the task sequence and software deployment reporting.
6Clients incorrectly attempt to use PKI certificates for communication, even if the option Use PKI client certificate (client authentication capability) when available is disabled on the Communication Security tab of Site Properties.
7After updating to ConfigMgr current branch, version 2006, client installation using the PROVISIONTS property fails if the “Allow access to cloud distribution point” device setting is set to “No”.  The client is unable to download content, and an error resembling the following is recorded in the tsagent.log file.
8The installation of a passive site server fails if orphaned.JOB files are present in the \inboxes\schedule.box folder. A message resembling the following is repeated in the FailOverMgr.log file.
9Adding a passive site into a ConfigMgr infrastructure with at least 1 secondary site and client language packs installed will trigger a re-installation of all secondary sites.
10The SCCM client installed on a Windows Embedded device stays in servicing mode if the maximum run time of deployment is greater than the duration of the maintenance window.
11Improvements are made to the download process in the case of a timeout when the Download delta content when available client setting is enabled.
12The content download step of a task sequence may fail to download files to clients. This occurs if the BranchCache Windows feature is enabled, and the environment is using enhanced HTTP for communication with distribution points.
13Improvements are made to the synchronization and processing of policy assignments and policy data between the Intune portal admin center and the SCCM admin console. This prevents issues such as creating a policy in the admin center that is not visible in the on-premises console.
14The SCCM admin console may generate an exception resembling the following when attempting to complete the Co-management Configuration Wizard.
15ConfigMgr clients deployed to Mac computers receive duplicate GUIDs. This occurs if the same user name is provided as a parameter to the CMEnroll tool during client installation.
16Clients may receive the incorrect policy, including scripts or settings, when multiple orchestration groups are present. Consider the following scenario:
17Client 1 may receive policy from orchestration group 2, causing it to run the pre- and post-scripts intended for group 2 when installing an update intended for group 1.
18The setting Allow access to cloud distribution points is not configured when clients are deployed using the Autopilot service and the PROVISIONS parameter.  This causes Install Application and Install Software Updates task sequence steps to fail.
19Client connections to a cloud management gateway may fail when multiple clients perform full software update scans in a short amount of time. Errors resembling the following are recorded in the SMS_Cloud_ProxyConnector.log file.
20After installing the Windows update KB 4579311, ConfigMgr clients are unable to download Office 365 updates. Errors resembling the following are recorded in the PatchDownloader.log located in the temp directory on the client.
21Windows 10 feature updates may fail to install on client computers using fast physical hardware. Errors resembling the following are recorded in the UpdatesHandler.log.
22Clients may randomly fail to install an update, or series of updates, due to a timing condition when they are deployed to a software update group. Errors resembling the following are recorded in the UpdatesHandler.log.

Results

As you can see in the below screen shot below, the installation of update rollup KB4578605 for Configuration Manager 2006 is completed.

  • \Monitoring\Overview\Updates and Servicing Status\Configuration Manager 2006 Hotfix Rollup (KB4578605)
ConfigMgr 2006 Hotfix KB4578605  SCCM | Update Rollup | 22 Fixes
ConfigMgr 2006 Hotfix KB4578605 SCCM | Update Rollup | 22 Fixes

Console Upgrade is the last stage of the update in a normal scenario:

  • Client Version 5.00.9012.1052
  • Site Version 5.00.9012.1052
  • Console Version 5.2006.1026.3000
ConfigMgr 2006 Hotfix KB4578605  SCCM | Update Rollup | 22 Fixes 1

Resources

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.