Step-by-Step SCCM 1802 Upgrade Guide

Benoit LecoursSCCM34 Comments

Consulting Services
Need help to upgrade or migrate your site ? Consult our fixed price consulting plans to see our rates !

Microsoft has released a new version of SCCM Current Branch. It’s now time to stay current and upgrade your environment! This post is a complete step-by-step SCCM 1802 upgrade guide. If you’re looking for a comprehensive SCCM installation guide, see our blog series which covers it all. You will be able to install 1802 if you are running SCCM 2012, this new version is a new baseline version.

To install SCCM 1802 as an update, you must have SCCM 1702 installed.

Keeping your infrastructure up to date is essential. You can benefit from the new features and fixes issues, which some of them can be related to your SCCM. It’s also easier to upgrade to the latest version since Microsoft has implemented the new model of update servicing which is the in-console upgrade.

SCCM 1802 New Features and Fixes

SCCM 1802 includes lots of new features and enhancements in the site infrastructure, management insights, client management, co-management, compliance settings, application management, operating system deployment, software center, software updates, reporting, protect devices, configuration manager console.

You can consult the What’s new in version 1802 of System Center Configuration Manager Technet article for a full list of changes.

Here’s our list of favorite features:

Support for SCCM Current Branch Versions

Ensure to apply this update before you fall into an unsupported SCCM version. Read about the support end date of the prior version of the following Technet article.

Windows and SQL Support

Before installing, make sure that you are running a supported Operating System and SQL version. Older SCCM version was giving a warning during Prerequisite check but 1802 is giving an error which prevents the installation from continuing.

1802 supports only Windows 2012+ and SQL 2012 SP3+.

Before you Begin

Downloading and installing this update is done entirely from the console. There’s no download link, the update will appear on your console once the Service Connection Point is synchronized.

If you’re running a multi-tier hierarchy, start at the top-level site in the hierarchy. After the CAS upgrade, you can begin the upgrade of each child site. Complete the upgrade of each site before you begin to upgrade the next site. Until all sites in your hierarchy are upgraded, your hierarchy operates in a mixed version mode.

Before applying this update, we strongly recommend that you go through the upgrade checklist provided on Technet. Most importantly, initiate a site backup before your upgrade.

In this post, we will update a stand-alone primary site server, consoles, and clients. Before installing, check if your site is ready for the update:

  • Open the SCCM console
  • Go to Administration \ Updates and Servicing
  • In the State column, ensure that the update Configuration Manager 1802 is Available

  • If it’s not available, right-click Updates and Servicing and select Check for Updates
Warning

The SCCM 1802 update is not yet available for everyone. If you need it right away you can run the Fast-Ring script and the update will show up.

  • If the update is not downloading, click on the button Download on the upper node. The update state will change to Downloading
  • You can follow the download in Dmpdownloader.log or by going to Monitoring / Updates and Servicing Status, right-click your Update Name and select Show Status

  • The process will first download the .CAB file and will then extract the file in the EasyPayload folder in your SCCM installation directory.
    • GUID : c78e7992-75db-4cd2-b89e-8024fc99884b
  • It can take up to 15 minutes to extract all files.

SCCM 1802 Upgrade Guide

Step 1 | SCCM 1802 Prerequisite Check

Before launching the update, we recommend launching the prerequisite check first. To see the prerequisite checklist, see the Microsoft Documentation

  • Open the SCCM console
  • Go to Administration \ Updates and Servicing
  • Right-click the Configuration Manager 1802 update and select Run prerequisite check

  • Nothing will happen, the prerequisite check runs in the background and all menu are unavailable during the check
  • One way to see progress is by viewing C:\ConfigMgrPrereq.log

  • You can also monitor prerequisite check by going to Monitoring / Update and Servicing Status, right-click your Update Name and select Show Status

  • When completed the State column will show Prerequisite check passed

Step 2 | Launching the SCCM 1802 update

We are now ready to launch the SCCM 1802 update. At this point, plan about 45 minutes to install the update.

  • Right-click the Configuration Manager 1802 update and select Install Update Pack

  • On the General tab, click Next

  • On the Features tab, checkboxes on the features you want to enable during the update

  • Don’t worry, if you don’t select one of the features now and want to enable it later, you’ll be able to so by using the console Administration \ Updates and Servicing \ Features

SCCM 1710 Upgrade Guide

  • In the Client Update Options, select the desired option for your client update

  • On the License Terms tab, accept the license terms and click Next

  • On the Summary tab, review your choices, click Next and close the wizard on the Completion tab

The whole process took a minute but the installation begins on the back end.

  • During installation, the State column changes to Installing

  • We suggest you monitor the progress, by navigating to Monitoring / Updates and Servicing Status, right-click your Update Name and select Show Status

Unfortunately, the status is not updated in real time. Use the Refresh button to update.

  • Open the SCCM log SCCM Installation Directory\Logs\CMUpdate.log with CMTrace

Important Info
We’ve done numerous SCCM upgrades. Some installation start a couple of minutes after you complete the wizard but we’ve seen some installation starts after a 10 minutes delay. Do not reboot or restart any services during this period or your update can be stuck in “Prerequisite check passed” status. There’s actually no officially documented methods by Microsoft to fix that. Patience is the key!
  • When completed, you’ll notice the message There are no pending update package to be processed in the log file
  • Monitoring / Updates and Servicing Status, right-click your Update Name and select Show Status, the last step will be Installation Succeeded

  • Refresh the Updates and Servicing node in Administration, the State column will be Installed

Updating the Outdated Consoles

As a previous Cumulative update, the console has an auto-update feature. At console opening, if you are not running the latest version, you will receive a warning and the update will start automatically.

  • Since all updates operations were initiated from the console, we didn’t close it during the process. We received a warning message when clicking certain objects. You will have the same message when opening a new console

  • Click OK,  console update will start automatically

SCCM 1710 Upgrade Guide

SCCM 1710 Upgrade Guide

  • Wait for the process to complete. You can follow the progress in C:\ConfigMgrAdminUISetup.log and C:\ConfigMgrAdminUISetupVerbose.log. Once completed, the console will open and you’ll be running the latest version

Verification

Consoles

After setup is completed, verify the build number of the console. If the console upgrade was successful, the build number will be X and the version is now Version 1802.

Beginning with 1802, this is a new version nomenclature for the console. The console will no longer include the main build number (8634). The last 2 numbers refer to the admin console build number. For example, in Configuration Manager version 1802 the initial site version is 5.0.8634.1000, and the initial console version is 5.1802.1082.1700. The build (1082) and revision (1700) numbers may change with future hotfixes to the 1802 release.

Servers

  • Go to Administration \ Site Configuration \ Sites
  • Right-click your site and select Properties
  • Verify the Version and Build number

SCCM 1802 Upgrade Guide

Clients

The client version will be updated to 5.00.8634.1007 (after updating, see section below)

SCCM 1802 Client Package distribution

You’ll see that the 2 client packages are updated:

  • Navigate to Software Library \ Application Management \ Packages

SCCM 1710 Upgrade Guide

  • Check if the update is successful, otherwise, select both packages and initiate a Distribute Content to your distribution points

Boot Images

Boot images will automatically update during setup. See our post on upgrade consideration in a large environment to avoid this if you have multiple distribution points.

  • Go to Software Library / Operating Systems / Boot Images
  • Select your boot image and check the last Content Status date. It should match your setup date

Updating the Clients

Our preferred way to update our clients is by using the Client Upgrade feature: (You can refer to our complete post documenting this feature)

  • Open the SCCM Console
  • Go to Administration / Site Configuration / Sites
  • Click the Hierarchy Settings in the top ribbon
  • Select Client Upgrade tab
  • The Upgrade client automatically when the new client update is available to check box is enabled
  • Review your time frame and adjust it to your needs

SCCM 1802 Upgrade Guide

Monitor SCCM Client Version Number

SCCM Reports Client Version

You can see our SCCM Client version reports to give detailed information about every client version in your environment. It’s the easiest way to track your client updates.

SCCM 2012 - System Health Configuration Manager SS

Collections

In conclusion, you can create a collection that targets clients without the latest client version because is very useful when it comes to monitoring non-compliant client.

Here’s the query to achieve this: (You can also refer to our Set of Operational Collection Powershell Script which contains this collection)

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.ClientVersion != '5.00.8634.1007'

Share this Post

1 Star2 Stars3 Stars4 Stars5 Stars (1 votes, average: 5.00 out of 5)
Loading...

Founder of System Center Dudes. Based in Montreal, Canada, Senior Microsoft SCCM Consultant, 5 times Enterprise Mobility MVP. Working in the industry since 1999. His specialization is designing, deploying and configuring SCCM, mass deployment of Windows operating systems, Office 365 and Intunes deployments.

34 Comments on “Step-by-Step SCCM 1802 Upgrade Guide”

  1. we are trying to upgrading version from 1802 to 1806. we are facing error in install files stage.

    SCCM PRI = windows server 2016 + SCCM CB 1802
    SCCM SQL = Windows server 2012 + SQL 2012 SP4

    Cannot create D:\Program Files\Microsoft Configuration Manager\tools\UploadOfflineFeedback, [error code: 5, error message: Access is denied.]. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:26 PM 17800 (0x4588)
    ERROR: Failed to create directory D:\Program Files\Microsoft Configuration Manager\tools\UploadOfflineFeedback CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:26 PM 17800 (0x4588)
    Setup has encountered fatal errors while performing file operations. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:26 PM 17800 (0x4588)
    Failed to install update files. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:26 PM 17800 (0x4588)
    STATMSG: ID=11001 SEV=E LEV=M SOURCE=”SMS Server” COMP=”CONFIGURATION_MANAGER_UPDATE” SYS=PKKHISCCMMS.DOMESTIC.HBL.COM SITE=C01 PID=10448 TID=17800 GMTDATE=Tue Sep 04 07:12:26.065 2018 ISTR0=”F420D72A-4A0B-40B2-B4D8-275489CC32D0″ ISTR1=”” ISTR2=”” ISTR3=”” ISTR4=”” ISTR5=”” ISTR6=”” ISTR7=”” ISTR8=”” ISTR9=”” NUMATTRS=0 CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    Successfully reported ConfigMgr update status (SiteCode=C01, SubStageID=0xd0012, IsComplete=4, Progress=100, Applicable=1) CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    Successfully reverted SQL function fnCurrentSiteVersion. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    Successfully reverted SQL function fnCurrentSiteVersion_INT. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    Successfully reverted SQL function fnCurrentSiteVersion_INT_TABLE. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    Successfully restored DB schema changes needed for retrying the upgrade. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: Creating table Defaults… CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object AADDiscovery_Settings_DeltaSyncEnabled_DEF with hash SHA256:1C9C95FE4850D2E64F6C7EAE258EF509E6AED879ED3A61966237EEA0F3918D4D already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object AADDiscovery_Settings_FullSyncEnabled_DEF with hash SHA256:22C2052F7681E8225BCB4766E4A7E770D21E398CB97FADE6BC7E59DCF39887F2 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object Alert_EnabledSMSDefaultOne with hash SHA256:420954DBE7F098F404749819487B05771BD56455BB534DC0E6C217DF3736EC9F already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object Alert_OccurrenceCountDefaultZero with hash SHA256:65AF313CCA14B03D4F249CE37DD08D3A7597A759583067AAE349B413BF0C05FE already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object AlertClass_ScopeDefaultZero with hash SHA256:44C8CAB3A907A6ECF14320C2124A9C93DD2C76B0B84D3D702AE19B9B47CE91DF already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object AlertEvents_IsClosed_DEF with hash SHA256:D2E78B93FEDDF2C62DDA6265776AFB319B99DEB0C5427FAF7CB1FC268BCDFC30 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object AlertEvents_SiteCode_DEF with hash SHA256:0A468B42C83DD43050E447325A2675A8FBAC2CDA85DFFFC21E5CCD6E6FF8FA0A already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object AlertForTrigger_OccurrenceCount_DEF with hash SHA256:763948B43992D002B174C45D9F920FE89B1E76618163D606CBA99596D115FD04 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object ArticleData_OptionalFlagSMSDefaultZero with hash SHA256:DCCFA6000172CD4D8FE36B9161E4C9EEEE963C0A57ED07012BB2C4DC926ECC35 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object Azure_CloudServicesTask_TaskCreationTimeDefaultNow with hash SHA256:D18246EBCCDEDD391E6D38CB972D8C1F4379519F0D28B45724505CAA611993FA already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object CI_CIAssignments_OfferTypeIDSMSDefaultZero with hash SHA256:6AB9E962FAF349DF88A3C1F794502A46900EB9D21391188171789F0B1045A437 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object CI_CIAssignments_UpdateSupersedenceSMSDefaultZero with hash SHA256:345EEF7DF1D202BED6E766BC928FEE1E7F6B9B661B0CDBC87D7933B605F051A0 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object CI_CIStatus_IsBrokenSMSDefaultZero with hash SHA256:5FF2425F0062F70987A1A2CD53995402F8276C1D4CFA8A9A81A90737841E24B7 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object CI_ComplianceSummary_SummaryTypeSMSDefaultOne with hash SHA256:DCF821114DA01868A36B1D4A3A18233E7E9912FF6F80C35CEC97DA6DCA87CBE9 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object CI_ConfigurationItemRelations_IsBrokenSMSDefaultZero with hash SHA256:8514566868077F8FC9288CBD7201636B15D2918E92E91E79E412EDF9C016A186 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object CI_ConfigurationItems_IsExpiredSMSDefaultZero with hash SHA256:3D929705567279572E5E802A504FA3E3C27821E7501E52CD9EF9F98969CC98A9 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object CI_ConfigurationItems_IsLatestSMSDefaultOne with hash SHA256:97D81BBC5436DA69D3BF516DF411B7C6E51C7FFB341C3265DDAF3B530DEFC366 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object CI_ConfigurationItems_SedoComponentIDDefault with hash SHA256:A4DB3509176F3D06B66F6C6A9B6EFA6CFF6CD9C0D6EC55BF883CCD128D47D304 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object CI_CurrentComplianceStatus_ComplianceStateSMSDefaultZero with hash SHA256:9242DF5AD60DA950F0C78A6AE8F83711A4BBE13FC36ADF58DA5C43F86F5CF46C already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object CI_CurrentComplianceStatus_DesiredStateSMSDefaultZero with hash SHA256:E330380BC4BEABEB08F1D60DFD685C673DAE2CFED4A666313E2A7CA1D01CDA18 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object CI_LocalizedCIClientProperties_IconId with hash SHA256:24C66CC0037598668737C9266CB79C92C7DD693CE44907BB21741F64B8186F66 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object CI_Models_CIGUID with hash SHA256:FBBC0E07EA617795E0BC3BF030E993731CBD5C3D935C111B6301D9BEE7E233C8 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object CI_RelationTypes_IsRecursiveSMSDefaultZero with hash SHA256:557484DEE043577B2F9D5DCB939D93AD3039A9502744CA5995FCA30268A8521B already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object CI_Settings_ExecutionContextSMSDefaultZero with hash SHA256:30CEDDB2FED8F1DAA23DAAB95B660D95A02C13DAFE60B000B5C40CAE382D620D already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object CI_UpdateCIs_RequiresExclusiveHandlingSMSDefaultZero with hash SHA256:C7B080A9656A3EC5B43CA424F1851DE25734B67CBD8160B2D097CB18FB3B2E2A already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object CI_UpdateSources_IsExpiredSMSDefaultZero with hash SHA256:A358FD0C25D47718ACEC3475E6A01BFC3A98A92468DAFFB7904ABC51EF7D7473 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object CI_UpdateSources_IsPublishingEnabledSMSDefaultZero with hash SHA256:0A5EB93F86B1EE6EA05D40092DD84ADB1AC3DEBAA70788E306597D32E459DE36 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object ClientDeploymentSettings_EnablePeerCacheDefaultOne with hash SHA256:5F09D0750B46D8065B3B1A57C32270CC2511B0A902A3683548692F72341F7B22 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object ClientKeyData_AlwaysInternetSMSDefaultZero with hash SHA256:29C9EB8697F62065FB7BEDA3CD47113E1DE1E4A5F795556B4B0FB92D807B17B2 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object ClientKeyData_ApprovalStatusSMSDefaultTwo with hash SHA256:D698A122B6B503D7CCF5AC1775F5AC845C251ABCAF7345FC07AAC304B70A1FDF already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object ClientKeyData_InternetEnabledSMSDefaultZero with hash SHA256:54B1EEBCEF60D04AA8266E014EF6D53D35A69FF94CECE7A5D32F27EA2B3E4FD5 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object ClientKeyData_IsIntegratedAuthSMSDefaultZero with hash SHA256:FE2442D7E99A130E6B7451226B7E7DA5084B03B9F40300345CF7A959FF3D507D already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object ClientKeyData_IsRevokedSMSDefaultZero with hash SHA256:78917C648DD33A32C2D60ACE168CF16002164CF87C06284476C3168221B5DA49 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:33 PM 17800 (0x4588)
    INFO: sql object ClientKeyData_ParentIDSMSDefaultZero with hash SHA256:8AAE60A38906E011E096339D3F87C94F143476EAF9800BDD80E640A03D0CF40F already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:34 PM 17800 (0x4588)
    INFO: sql object ClientOperation_IsActionsDependent with hash SHA256:2D3B7D17F9283E3A2316E4F0C97047B03F1463D4BFA077D2A963A44799194351 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:34 PM 17800 (0x4588)
    INFO: sql object ClientOperation_ModifiedOnUtcNow with hash SHA256:1964FD8281183C94724EB6C49165CA8542A65EB603AE4D2647EEC6F2B02652ED already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:34 PM 17800 (0x4588)
    INFO: sql object ClientOperation_Priority with hash SHA256:91A016F7F0463DAD9706693EBB3A9DBFD8F0A14542E4C522A9C9876801BBF0EE already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:34 PM 17800 (0x4588)
    INFO: sql object ClientOperation_State with hash SHA256:C6D4705B913381E4A4540E64F64473CA34AFF9006093604EFBB07BA912AD7059 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:34 PM 17800 (0x4588)
    INFO: sql object ClientOperation_TargetType with hash SHA256:2036BB211A84F006C4C8E179B30C7F1DECA4A43784367669DC8B2101D3FF78DE already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:34 PM 17800 (0x4588)
    INFO: sql object Collection_MemberChg_Notif_TimeUpdatedSMSDefaultToday with hash SHA256:FF6C6552B13FFB459414D8E3761BD9CDD7DE85ED894789E5D864E3C5E76DEFDA already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:34 PM 17800 (0x4588)
    INFO: sql object Collection_Rules_ArchitectureKeySMSDefaultZero with hash SHA256:63EDA3412F4E24D586F3BD78E47A392C8BFC97BED1C57BADA2FA52C50571589A already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:34 PM 17800 (0x4588)
    INFO: sql object Collection_Rules_QueryCollectionIDSMSDefaultBlank with hash SHA256:0ACB4E4635CBCBE9A742F72FC5C9FC234F8ED1A50A12DC9412EB7124E67BCD37 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:34 PM 17800 (0x4588)
    INFO: sql object Collection_Rules_QueryCommentSMSDefaultBlank with hash SHA256:23B50A38218D7871DCAC046D666E1176ACFB125F924822B3D04F7250CF7C3AA4 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:34 PM 17800 (0x4588)
    INFO: sql object Collection_Rules_QueryNameSMSDefaultBlank with hash SHA256:D4F2DFDE20A18646185394EDFCF7BC7106B3D04AF880730A233872CCC5C1F840 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:34 PM 17800 (0x4588)
    INFO: sql object Collection_Rules_ReferencedCollectionID_DEF with hash SHA256:DF50712F65CFA30162E2F400481C05700028E4580DE5D190AEA4839B2013CF9A already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:34 PM 17800 (0x4588)
    INFO: sql object CollectionNotifications_ChangeTime_DEF with hash SHA256:6AF5C352EC4D06AFFD1E8E4F51E7B42D25DFD47FD163D0A117C9198DDA8C4A92 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:34 PM 17800 (0x4588)
    INFO: sql object Collections_G_CollectionCommentSMSDefaultBlank with hash SHA256:B14BF3F84A2D72BA2395F49B57842779D0D77C72FDCAFE767404C955D797BA10 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:34 PM 17800 (0x4588)
    INFO: sql object Collections_G_CollectionTypeDEF with hash SHA256:54FF62299E33E42C859CBEAE7E1AC00D6154312A45716D6B878C9F6D2A2B0137 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:34 PM 17800 (0x4588)
    INFO: sql object Collections_G_LastChangeTimeSMSDefaultToday with hash SHA256:FDE8B04E7D8853D9C5941E83F97E3C4398C4DF2F6031CD765D094AA38CE5D20D already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:34 PM 17800 (0x4588)
    INFO: sql object Collections_G_ResultTableNameSMSDefaultBlank with hash SHA256:F630432FCDE202F302CC01386D42A4E899BD1F965BC685B31ED5961973FA9C94 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:34 PM 17800 (0x4588)
    INFO: sql object Collections_G_ScheduleSMSDefaultBlank with hash SHA256:BBC885B9416BD666943ED850A7D267E79B903773FFA8D3C8B63425730C330ADC already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:34 PM 17800 (0x4588)
    INFO: sql object Collections_L_BeginDateSMSDefaultToday with hash SHA256:8B199595FFAD1C01F6C89D4A443A5C9FD0678098094083D69D535BF87332BDD3 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:34 PM 17800 (0x4588)
    INFO: sql object Collections_L_CurrentStatusSMSDefaultZero with hash SHA256:85DD19311B9F5DA92DBA143301D060B44992B1D03C5B0627F6F0C67238581114 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:34 PM 17800 (0x4588)
    INFO: sql object Collections_L_CurrentStatusTimeSMSDefaultToday with hash SHA256:74F9E80ABDB1039CE057D8EF957329C3B143D90CA4ABEA4603AD6DE19E376030 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:34 PM 17800 (0x4588)
    INFO: sql object Collections_L_LastMemberChangeTimeSMSDefaultToday with hash SHA256:1C20C2DE22E80E3FF3FD96F8963270ECB5F7F07F4E2AF20A9E5D17987400E04D already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:34 PM 17800 (0x4588)
    INFO: sql object Collections_L_LastRefreshTimeSMSDefaultBlank with hash SHA256:A23296D1B95C1EBD108BBB880F0436F21E321D8BF1C0980E3D713FB39CDEE1B6 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:34 PM 17800 (0x4588)
    INFO: sql object ConditionAccessManagement_ExclusionGroupsIDSMSDefaultBlank with hash SHA256:6EBA1088C9369AA2AC642F5877752CB343ED10C1DA0952B8640F5FFB7C9578D5 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:34 PM 17800 (0x4588)
    INFO: sql object ConditionAccessManagement_ExclusionGroupsSMSDefaultBlank with hash SHA256:41A72B55C201512F96182CA512625B4DD386B7F254D08E3DF44DCCF5B7F1475E already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:34 PM 17800 (0x4588)
    INFO: sql object ConditionAccessManagement_InclusionGroupsIDSMSDefaultBlank with hash SHA256:E27F8E8819A1F6D388952BDEDCB8813ABC0ABD8ECD1E0DCE2C43586CBA6F55B3 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:34 PM 17800 (0x4588)
    INFO: sql object ConditionAccessManagement_InclusionGroupsSMSDefaultBlank with hash SHA256:E4746F8FAB7921C0A3F317D5E1404E16E8C27EE37B5F1A08C634207E3FE3E899 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:34 PM 17800 (0x4588)
    INFO: sql object ContentDPMap_StateSMSDefaultZero with hash SHA256:6529BA2B8FCAFAC72DCC6562C946E1059B3364219136A0A5B2F8217E5DCD1DB3 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:34 PM 17800 (0x4588)
    INFO: sql object DistributionJobs_DynamicOrderDefaultZero with hash SHA256:A025FB2B680C9F93F9FEBA71EFBF84DF1968BA5E006627C728A71B3289D28291 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:34 PM 17800 (0x4588)
    INFO: sql object DRS_MessageActivity_SendConversationGroupIDSMSDefaultNewID with hash SHA256:A75654553C693238E755C3C7DBD60DF0FA73E77E959B0705C2C8109E7E7A863F already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:34 PM 17800 (0x4588)
    INFO: sql object Drs_Signals_DateCreated_DEF with hash SHA256:64CA07B6D98BF908342591B8DA888B6999A0D846F6C4F696E666CEBCD5EE515A already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:34 PM 17800 (0x4588)
    INFO: sql object DrsConflictInfo_ConflictTimeSMSDefaultTodayUTC with hash SHA256:4130192DFAE4378FCCEA64C577B94555BCA0C5CA998F0C92BB00ED7C9890E953 already exists. CONFIGURATION_MANAGER_UPDATE 9/4/2018 12:12:34 PM 17800 (0x4588)
    INFO: sql object DRSReceivedMessages_ProcessedTimeDefaultToda

  2. Seems that existing systems are auto-upgrading the clients as expected. However, imaging new clients results in the newest patch not being applied to the client. Any suggestions?

  3. Hi SCDudes!
    Have you come across the scenario where clients are failing to auto upgrade? We have 8 devices in our Pilot client upgrade collection, of which only one device has automatically upgraded to the latest hotfix client. This also happens when we release to production. We end up having to either force repair or force install the clients again.

    Cheers
    Phil

  4. We are currently running 2012 R2 SP1 – 5.0.8239.1000

    Can we upgrade straight to version 1802, if so, how as we do not have the option to run the upgrade within the console and can’t seem to find any advice on the best way (we already have sql server 2012 and updated to Windows 10 ADK).

    Thanks
    Ben

    1. Did you have any luck with this? | I’m in the same boat as you.
      Updates and Servicing is missing from Administration
      System Center 2012 Configuration Manager SP2 | console version 5.0.8239.1000

      https://www.reddit.com/r/SCCM/comments/8s4vhd/sccm_upgrade_50082391000_build_8239_to/

      I have downloaded the 1802 current branch media ISO but am unsure if I should try and proceed..
      Independently ran “prereqchk.exe /LOCAL” but it fails detecting previous installation; which is true.
      I’m in a test environment so I can always restore.

      Is your SQL 2012; SP3 or SP4?

      1. No I have just got back from annual leave.
        I assume it is a simple as running the setup from the 1802 ISO, but I can’t seem to find anyone who has done it this way.
        It seems like it could be very destructive if this is not the correct method.

        We are running SQL 2012 SP3, which is the minimum required for the update.

        I found that problem with the checks, but running the prereqchk.exe straight from the folder but as an admin seemed to work fine.

  5. great article, but no one tells whether ADK and MDT needs to be updated or not and what versions they should be before upgrading to 1802
    also the boot image update process

  6. We will also need to Upgrade Secondary Servers once CAS and Primary are updated, in guide its not mentioned. was that missed on purposely ? just curios to know.

  7. Hallo, we have an issue happened after upgrade to SCCM 1802:

    Site Component Manager failed to reinstall this component on this site system.

    Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager will automatically retry the reinstallation in 60 minutes. To force Site Component Manager to immediately retry the reinstallation, stop and restart Site Component Manager using the Configuration Manager Service Manager.

  8. Hi,

    We have a simple single site, single server setup which is currently on 1606 and needs to get to 1802. I understand that server-side we will need to run 2 phases: 1606 –> 1706 and then 1706 –> 1802. For the clients though, can we skip rolling out 1706 to the clients and just upgrade them from 1606 to 1802 directly by rolling out the client update package of 1802 once the server is up to that version? (I get that idea from MS: https://docs.microsoft.com/en-us/sccm/core/clients/manage/upgrade/upgrade-clients-for-windows-computers –> Tip: If you are upgrading your server infrastructure from a previous version of Configuration Manager (such as Configuration Manager 2007 or System Center 2012 Configuration Manager), we recommend that you complete the server upgrades including installing all current branch updates, before upgrading the Configuration Manager clients. The latest current branch update contains the latest version of the client, so it’s best to do client upgrades after you have installed all of the Configuration Manager updates you want to use.)

    Thanks!
    Jon

    1. Hi Jon,

      Sure, you can just push the latest 1802 client, you can skip 1706 client without problem.

  9. Hi, thanks for the detailed guide. I’m new to System Center and upgraded to 1802 from 1702. When I check Software Library -> Application Management -> Packages there is no version no. for Config Mgr Client Package. Delete and deploy options are greyed out and properties are greyed out. Is this normal? I just want to check the upgrade has been successful.

  10. after the upgrade I’m getting this error and I can’t use PXE anymore….

    Your Pc/Device need to be repaired
    The windows Boot Configuration Data (BCD) file from PXE server does not contain a valid operating system entry. Ensure that the server has boot images installed for this architecture.
    FIle\temp\x86x64….
    code 0xc0000098

    1. Have you distribute both Boot Image (x64,x86) to your distribution point that host the PXE service?

      1. Hi,
        Before the Upgrade there were Boot Images working. Have I to redistribute that images again?

        Or Have I to create new boot images and distribute?

  11. Hi’ great article, helped me in the upgrade to 1802
    Q: is the Configuration Manager Remote Control tool, suppose to be upgrade also with 1802 ???
    cause it seems it didnt

Leave a Reply

Your email address will not be published. Required fields are marked *