This update is available in the Updates and Servicing node of the Configuration Manager console for environments that were installed by using builds of version 1806 and that were downloaded before August 24, 2018.
To verify which build is installed, look for a package GUID by adding the Package GUID column to the details pane of the Updates and Servicing node in the console. This update applies to installations of version 1806 from packages that have the following GUID:
284366B8-7D7C-41FF-A407-A3D61EF98C85
This update does not apply to installations of version 1806 from packages that have the following GUIDs:
AEEEDD26-D507-4840-9881-EBA398A33B8C
058CA7DF-DBA5-4441-85AF-6AAF31F57E7F
DB2EB391-D92F-47D5-9B4B-BE521C65B7A2
B54DB0D0-FD7F-480C-BC2F-099C28781581
5B823327-92D9-4908-A24C-8D8C6625F407
If you have any of these GUIDs, refer to KB 4346645 Update for System Center Configuration Manager version 1806, first wave.
Restart information
You do not have to restart the computer after you apply this update.
Update replacement information
This update does not replace any previously released update.
Additional installation information
After you install this update on a primary site, pre-existing secondary sites must be manually updated. 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.
Run 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:
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.