Академический Документы
Профессиональный Документы
Культура Документы
To install ConfigMgr 1810 update, you must have installed at least SCCM 1710, SCCM 1802 or SCCM 1806.
Ensure that you are running a supported Operating System and SQL version.
If you’re running a multi-tier hierarchy, start at the top-level site in the hierarchy. First perform the CAS upgrade,
later you can begin the upgrade of each child site. Complete the upgrade of each site before you begin to upgrade
the next site.
Quick Info – The package GUID for SCCM 1810 is C8799F92-DC23-42A0-96FA-1862414C3967. The approx download size
of this update is 2.22 GB.
The Configuration Manager 1810 errors and warnings are covered in below post.
Once you see the update is downloaded, right click Configuration Manager 1810 and click Run prerequisite check.
Ope
n the ConfigMgrPrereq.log file located on C: drive of site server. Look for the line at the end which reads Prerequisite
checking is completed. That confirms the prerequisite check is passed/complete. If you see any warnings or errors during
prerequisite check, that should be logged in log file.
At this point i will check the box “Ignore any prerequisite check warnings and install the updates regardless of missing
requirements”. Click Next.
Select the New features that you want to enable. If not you can enable them later. Click Next.
If you wish to validate client update on members of pre-prod collection, click Validate in pre-prod collection. Else go with
upgrade without validating and click Next.
Click Next on rest of the pages and on Completion page click Close.
Step 3 – Monitor Installation Progress
While the SCCM 1810 update is installing, you can monitor installation progress. Click Overview > Updates and
Servicing Status. Select the Configuration Manager 1810 update and click Show Status.
You can now see the detailed status for Configuration Manager 1810 installation. Keep clicking Refresh button until you
see all the steps marked with green check.
Step 4 – SCCM Console Upgrade
Once the update is installed, either refresh or close and re-open the console. You will see the console upgrade box.
Click OK to begin the console upgrade. The old version of console 5.1806.1074.1500 will be upgraded to
version 5.1810.1075.1300.
If you see any errors during console upgrade, there are two logs that can help you
– ConfigMgrAdminUISetup.log and ConfigMgrAdminUISetupVerbose.log. Both of these are present on C: drive of site
server.
Step 5 – Verify Update Installation
In this step we will verify update installation. After the console upgrade, the console will re-launch. Click on drop-down at
top left and click About Configuration Manager. You should see the following details.
Version 1810
Console Version: 5.1810.1075.1300
Site Version: 5.0.8740.1000
Let’s check the site properties. The version is 5.00.8740.1000 and build number is 8740.
Step 6 – Update Boot Images
Once you complete Configuration Manager 1810 upgrade, the next steps are :-
Update Boot Images to all the distribution points.
Update Configuration Manager client package to all DP’s if they are not updated. You can check the content status
to see last update.
Make sure that Upgrade all clients in hierarchy using production client box is selected. You also also choose to not
upgrade servers.
select
SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.Res
ourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.ClientVersion != '5.00.8740.1003'