4,285 total views, 3 views today
Author Nawaz Kazi
Microsoft has released a revised Hotfix Rollup KB457589
- The revised version (KB 4575789) of the update rollup supersedes the original (KB 4578605) and will not appear in the Updates and Servicing node of the Configuration Manager console for customers that previously installed the original version.
- The revised version will appear in the console for customers that previously downloaded but did not yet install the original version.
- This update is available in the Updates and Servicing node of the Configuration Manager console for environments that were installed by using early update ring or globally available builds of version 2006.
This revision contains the following new updates in addition to the fixes also documented in KB 4578605.
-
- KB 4575786 Configuration Manager console terminates unexpectedly on Configuration Manager current branch, version 2006
- KB 4575787 Co-management enrollment takes longer than expected for Configuration Manager clients
- KB 4575790 Client setup is unable to download contents from a cloud distribution point in Configuration Manager current branch, version 2006
Running Prerequisites
Check Completion status can be seen under \Monitoring\Overview\Updates and Servicing Status
Installing Update
\Administration\Overview\Updates and Servicing –> Right Click — Install Update Pack
Update Wizard –> Click Next
Client Update Settings –> Next
Accept License Terms and Privacy Statement –> Next
Confirm the Settings –> Next
Wizard Completion Summary
Let’s check from the back end what all is happening during the upgrade. We can use the Monitoring Console to track the status progress from the CMUpdate.log file.
Check Installation status can be seen under \Monitoring\Overview\Updates and Servicing Status
Upgrade Completed
On Completion, Console will prompt to upgrade Console.
Secondary Server Upgrade
Run the following SQL Server command on the site database to check whether the update version of a secondary site matches that of its parent primary site:
select dbo.fnGetSecondarySiteCMUpdateStatus (‘SiteCode_of_secondary_site’)
If the value 1 is returned, the site is up to date, with all the hotfixes applied on its parent primary site.
If the value 0 is returned, the site has not installed all the fixes that are applied to the primary site, and you should use the Recover Secondary Site option to update the secondary site.
Current output on my Site
To update a secondary site in the Configuration Manager console, click Administration, click Site Configuration, click Sites, click Recover Secondary Site, and then select the secondary site. The primary site then reinstalls that secondary site by using the updated files. Configurations and settings for the secondary site are not affected by this reinstallation. The new, upgraded, and reinstalled secondary sites under that primary site automatically receive this update.
Check C:\ConfigmgPrereq.Log
The upgrade package is copied to Secondary Server on Successful pre-requisites completion
Recovery Successful Completion
Running the following SQL Server command on the site database to check whether the updated version of a secondary site matches that of its parent primary site, Value returned should be “1”
select dbo.fnGetSecondarySiteCMUpdateStatus (‘SiteCode_of_secondary_site’)
Production Client Version is 5.00.9012.1056, so you need to plan a Client Upgrade too.
Thanks.