Apply Microsoft Configuration Manager Updates

Now that the site is up and running, it is time to apply the latest Configuration Manager updates. If you enabled the Service Connection Point as part of the installation any new updates should already be available. By default, this role will periodically check for updates and download them. There is an option to run it in an off-line mode and require running the ServiceConnectionTool.exe command line tool from cd.latest\SMSSETUP\TOOLS\ServiceConnectionTool.

1. Launch the Configuration Manager Console with an account with administrative rights.
2. Go to Administration > Updates and Servicing.
3. From this pane you can see CM updates, Hotfixes, and Hotfix Rollups. The most recent update should show a State of 'Ready to install'.
4. Right click the latest update and select 'Run prerequisite check.' This will run about 125 checks to validate everything should work when the upgrade is in place.
5. Either click 'Show Status' in the bottom right under Related Objects or navigate to Monitoring > Updates and Servicing Status. Right click the Update Package and select Show Status.
6. The prerequisite check does take a while to start and run the tests so be patient and grab a cup of coffee or spam refresh as often as desired. Content needs to be download and replicated before the checks begin so if nothing has moved in a bit, check distmgr.log for signs of movement. Closing the console and relaunching may be necessary to show correct status.
7. In my lab the ODBC Driver 18 for SQL Server failed. This was a simple fix by downloading and running  https://go.microsoft.com/fwlink/?linkid=2220989. Some warnings can safely be ignored as they are for features that are not in use or for upcoming feature depreciation that will require attention. Once any failures or warnings have been remediated you can run the check again if desired.
8. If there are warnings that you plan on ignoring at this point, go back to Administration > Updates and Services and install the Update Pack from the ribbon or right click menu. Ignore any perquisite check warnings.
9. Review the features and make changes if necessary.
10. On Client Update Settings you can specify whether to automatically update all clients in the site or validate in a pre-production collection that you specify before rolling it out to everyone else.
11. Accept the license terms.
12. As Cloud Attach has not been set up yet, uncheck the box to enable it.
13. Review the summary and click Next.
14. Monitoring can be done the same way as the prerequisite check. As replication completed for the previous step install should kick off much faster but several of the steps do take a while. From past experiences as long as it starts going it is a fine line between watching the status and chasing the logs and maintaining sanity. There are many steps that may fail because a previous step isn't done and will need to wait 5 minutes until it retries which will generate a lot of warnings/errors in the logs but they are to be expected. I generally step away and check back periodically rather than watching status real time.
15. At some point the SMS Provider will be updated and the console will need to be restarted and updated to the latest version.
16. Once the CAS is updated, any downstream servers will automatically update as well.