Step-by-Step Easy SCCM 2002 Upgrade Guide

ByPrajwal Desai Hours

The SCCM 2002 update is available as an in-console update. This upgrade guide helps you to upgrade to SCCM 2002 on sites running SCCM version 1806 or later.

In other words, you can upgrade to Microsoft Endpoint Configuration Manager (MECM) 2002 if you are running the following versions SCCM 1806, SCCM 1810, SCCM 1902 or SCCM 1906 or SCCM 1910.

Most of all if you are installing SCCM 2002 on a new site, it’s also available as a baseline version. This post summarizes the changes and new features in Configuration Manager version 2002.

Configuration Manager 2002 Servicing Support

Configuration Manager 2002 is the first current branch release of year 2020. When you see a new update version, it remains in support for 18 months from its general availability release date.

With Configuration Manager 2002 update, the product will receive Security and Critical updates for first four months. And for next 14 months, it will receive only Security Updates. The below SCCM servicing support pic should give you a clear idea of servicing phases.

Configuration Manager 2002 Servicing Support
Configuration Manager 2002 Servicing Support

SCCM 2002 New Features

There are several new features in SCCM 2002 update. Most of the features were already part of technical preview builds. You can read about all the new features of Configuration Manager 2002 here.

For now I will be listing some of the update 2002 new features. In a separate post, I will be covering all the new features in detail.

  • Remove a central administration site
  • Several new management insight rules
  • The administration service automatically uses the site’s self-signed certificate
  • Proxy support for Azure Active Directory discovery and group sync
  • Token-based authentication for cloud management gateway
  • Critical status message ID 11488 shows up when server connection errors to required endpoints
  • Desktop Analytics Connection Health dashboard shows client connection issues
  • CMPivot Improvements
  • Boundary Groups – Exclude certain subnets for peer content download
  • Client log collection – Collect SCCM log files from remote client computer
  • Shiny Microsoft Edge management dashboard
  • Wake up a device from the central administration site
  • Task sequence as an app model deployment type
  • Task Sequence and OSD improvements
  • Orchestration groups enhancements
  • Improvements to BitLocker Management
  • Integrate PowerBI report server with Configuration Manager
  • Attach Files during feedback

SCCM 2002 Upgrade Prerequisites Checklist

Here are some of the prerequisites checklist that you need to look into before you install Configuration Manager current branch 2002 update.

  • Update 2002 for Configuration Manager current branch is available as an in-console update.
  • Yes, there is SCCM 2002 baseline version also available.
  • To apply this update on your sites, ensure you have installed SCCM version 1806 or later.
  • 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.
  • Ensure that you are running a supported Operating System and SQL Server version.
  • If you’re running SCCM version older than 1806, check the SCCM In-place upgrade paths.
  • After you upgrade your site to 2002, you must also update clients to the latest version. In the last section, I will cover how to upgrade client agents in your hierarchy.

Install SCCM 1910 Hotfixes ?

I believe there were lot of hotfixes released for SCCM 1910. Probably you may not have installed any or installed just few hotfixes. You might see some 1910 hotfixes still in the console. Should you install these hotfixes first and then install SCCM 2002 update or can these hotfixes be skipped ?.

Answer – A hotfix contain either one individual fix or a bundle (a rollup of fixes). All the hotfixes released for Configuration Manager 1910 will be included in SCCM 2002. So if you see any hotfixes in your console while installing version 2002, you may skip them and directly install 2002 update.

Get Configuration Manager 2002 Update

First of all the Configuration Manager 2002 update will not be available for everyone yet. If you have been installing these updates, you would know why. Usually it take few weeks for the Configuration Manager update 2002 to get rolled out globally.

Some organizations prefer to wait until the update it’s made globally available or when it made available to slow ring. There is an advantage behind the wait. In case any bugs are reported, Microsoft fixes them and it will be part of global release.

However if you decide to upgrade to SCCM 2002, you can run the EnableEarlyUpdateRing 2002 script to enable fast ring for 2002 update package in ConfigMgr.

You can download the EnableEarlyUpdateRing 2002 PowerShell script by clicking this link. Running this script will get the update 2002 in the console.

On your SCCM server, run the PowerShell as administrator and run the script. Enter the site server name (Top level site server name or IP address) and script gets the update 2002 in console for you.

EnableEarlyUpdateRing 2002 PowerShell script
EnableEarlyUpdateRing SCCM 2002 PowerShell script

After you run the above script, you don’t need to restart SMS_EXECUTIVE service. However if you don’t see the update downloading in the console, you can go ahead and restart the service.

In my case, the ConfigMgr 2002 update is in downloading state and has a package GUID AA9975F2-160A-4910-A698-B7A4AF35D727.

Tip – When the download completes, the update state changes from Downloading to Ready to Install.

Download Configuration Manager 2002 update
Download Configuration Manager 2002 update

You can monitor the update download by opening dmpdownloader.log file. At this point if your SCCM 2002 update gets stuck in downloading state, here is a post to help you – https://www.prajwaldesai.com/fix-sccm-update-stuck-downloading-state/.

SCCM 2002 Prerequisite Check

Before installing the update 2002, I recommend you to run SCCM 2002 Prerequisite check.

  • Launch the SCCM console.
  • Navigate to Administration > Overview > Updates and Servicing Node.
  • Right click Configuration Manager 2002 update and click Run Prerequisite check.
SCCM 2002 Prerequisite Check
SCCM 2002 Prerequisite Check

Open the ConfigMgrPrereq.log file to monitor the Prerequisite check process. Look for this line Prerequisite checking is completed.

ConfigMgrPrereq.log
SCCM 2002 Prerequisite Check – ConfigMgrPrereq.log

In the console, we see the Configuration Manager 2002 prerequisite check passed successfully. I did not see any errors or warnings which is a good thing.

Listed below are some of common reasons why the SCCM 2002 prerequisite check could fail. Click the Solution to fix the issues.

  • The site database has a backlog of SQL change tracking data – Solution.
  • Configuration Manager Pending System Restart – Solution.
  • SQL Server Native Client Version – Solution.
Prerequisite check passed
Prerequisite check passed

Perform SCCM 2002 Upgrade / Install SCCM 2002 Update

To begin the Configuration Manager 2002 Upgrade process

  • Launch Configuration Manager console.
  • Navigate to Administration > Overview > Updates and Servicing Node.
  • Right click Configuration Manager 2002 update and click Install Update Pack.
Install Configuration Manager 2002 Update
Install Configuration Manager 2002 Update

The Configuration Manager version 2002 includes :-

  • Configuration Manager site server updates
  • Configuration Manager console and client updates
  • Fixes for known issues
  • New features

Click Next.

Install Configuration Manager 2002 Update

You can enable the new features post installing the update. Click Next.

Configuration Manager 2002 Upgrade Guide Snap8

Click Next and finally on Completion page, click Close.

Configuration Manager 2002 Upgrade Guide Snap9

Monitor SCCM 2002 Update Installation Status

To monitor the SCCM 2002 update installation

  • In ConfigMgr Console, go to Monitoring node.
  • Click Overview > Updates and Servicing Status.
  • Select the Configuration Manager 2002 update and click Show Status.
Monitor ConfigMgr 2002 Update Installation Status
Monitor ConfigMgr 2002 Update Installation Status
Monitor SCCM 1910 Update Installation Status

In addition to above method, you can also monitor the update installation status by opening cmupdate.log.

SCCM 2002 Console Upgrade

To get the SCCM 2002 console upgrade box, either refresh the ConfigMgr console or close and re-open it. The new version of console 5.2002.1083.1700 will be installed over old console version 5.1910.1067.2100. Click OK to proceed with console upgrade.

SCCM 2002 Console Upgrade
SCCM 2002 Console Upgrade

Verify Configuration Manager 2002 Upgrade

In the Configuration Manager console, click drop-down at top left corner of console and click About Configuration Manager. This should show following details.

  • Microsoft Endpoint Configuration Manager Version 2002
  • Console Version – 5.2002.1083.1700
  • Site Version – 5.0.8968.1000

Click OK.

About Configuration Manager
About Configuration Manager

Next, check the primary site properties. You should see version as 5.00.8968.1000 and build number as 8968.

Current Branch Site properties
Current Branch Site properties

Update Boot Images to Distribution Points

The Configuration Manager 2002 update installation is complete. Now you must update SCCM boot images to all the distribution points in your setup.

In the console, navigate to Software Library > Operating Systems > Boot Images. Right click Boot Image and click Update Distribution Points. Repeat the same for x86 boot image as well.

Update Boot Images
Update Boot Images

ConfigMgr 2002 Client Upgrade

As mentioned in the beginning of this post, after you update the site, update client agents to latest version. I am covering this because sometimes the admins skip this step and as a result, after the upgrade, they don’t see the new features. You can upgrade client agents using client upgrade feature.

To upgrade SCCM client agents to latest version.

  • Go to Administration > Site Configuration > Sites.
  • Click the Hierarchy Settings on top ribbon. Select Client Upgrade tab.
  • Ensure Upgrade all clients in hierarchy using production client box is selected.
  • Specify the number of days within which you want to automatically upgrade client agents.
  • Click OK.
ConfigMgr 2002 Client Upgrade
ConfigMgr 2002 Client Upgrade

Furthermore you can use the below query to find out the devices without the latest SCCM client version 5.00.8968.1008.

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.8968.1008'
Avatar photo

Prajwal Desai is a Microsoft MVP in Intune and SCCM. He writes articles on SCCM, Intune, Windows 365, Azure, Windows Server, Windows 11, WordPress and other topics, with the goal of providing people with useful information.

77 Comments

  1. Hi Prajwal

    I have an issue after updating to 2002. My console won’t upgrade from 5.1910.1067.2100 to 5.2002.1083.2000. When i open my console it asks me to upgrade and later errors out and when i click the report to see logs , see below. would this fix work for me

    “”https://support.microsoft.com/en-us/topic/office-updates-fail-to-download-in-configuration-manager-current-branch-version-2002-cb77b9d9-5cd8-88c2-044e-f98e11c32f80″”

    AdminUI.ExtensionInstaller.exe Warning: 0 : Downloaded file does NOT match Hash, delete the file.
    DateTime=2021-03-17T05:16:35.7745475Z

    AdminUI.ExtensionInstaller.exe Error: 0 : Microsoft.ConfigurationManagement.ManagementProvider.SmsException\r\nDownloaded file does NOT pass Hash validation.\r\n at Microsoft.ConfigurationManagement.AdminConsole.ExtensionInstaller.WmiInstallationDataDownloader.DownloadFile(IExtensionFile file, String downloadPath, Boolean validateHash)
    at Microsoft.ConfigurationManagement.AdminConsole.ExtensionInstaller.WmiInstallationDataDownloader.DownloadPackage(IInstallationPackage package, String downloadPath, Boolean validateHash)
    at Microsoft.ConfigurationManagement.AdminConsole.ExtensionInstaller.ExtensionHandler.ReinstallConsole()\r\nNo details are available for this error.\r\n
    DateTime=2021-03-17T05:16:35.7745475Z

    Reply
  2. Avatar photo shahzaib Khan says:

    Hi, I am Shahzaib khan, I have been working in an organization as a system engineer, I am planning to upgrade my SCCM version from 1606 to 2002, the question is can I upgrade 1606 directly to 2002 with a baseline media of version 2002?

    I know there is also an option of in console upgrade, but I want to avoid the hopes in between like going from 1606 to 1706 and 1706 to 1806 and so on.
    Looking forward to hear from you soon.

    Thanks,
    Shahzaib

    Reply
  3. Avatar photo Gary L. Eshelman says:

    I would like to install MEM 2002 Baseline onto a MS 20012 R2 server. I have a valid OS license so I would like to keep it. I am currently running SCCM 2012 Configuration Manager with SQL 2014. I have one Site configured. I want to continue learning the latest CM current branch. I have downloaded MEM 2002 180 trial from MS. What are your thoughts?

    Is this possible or do you recommend another path? Help greatly appreciated.

    Thank You,

    Reply

  4. HI,
    I have configuration manager version 1906,
    I was trying to download the Config Manager 2002 but its not downloading.
    what could be the issue?

    Reply

  5. Completed the install of the Configuration Manager 2002 Upgrade along with the Hotfix (KB4560496). Ever since every DP in our environment is failing to PXE and giving a 0xc0000098 error instead. I have done all the steps in another of your articles (https://www.prajwaldesai.com/sccm-osd-error-code-0xc0000098/) with no success. Also rebuilt my boot images after updating the ADK and even went so far as to completely rebuild one DP with no success.

    My environment is set with HTTP and “Create self-signed certificates” in each DP Properties. Does this have to change with the 2002 upgrade?

    Reply

  6. I’m running into this issue that every time I restart my SCCM server, the bindings of port 80 (HTTP) change to HTTPS in IIS. I have to delete the port 80 HTTPS and re-add it as port 80 HTTP. The only other site in IIS is WSUS Administration. I pulled some information from event viewer, but can’t pin-point what is causing this switch in IIS.

    Reply

    1. I see this issue when I hit the Check Box for “Use Configuation Manager-Generated certificates for HTTP site Systems”

      Reply

  7. Prajwal,

    Withe the screenshot it is better…

    Reply

  8. Hi Prajwal,

    I’m currently running SCCM 1910. I’m trying to upgrade to 2002 but the upgrade fails…
    On cmupdate.log I can see where the process fails but I do not understand why (see joined screenshot).

    From my understanding the upgrade process ALTER a table to “NOT NULL” and then try to insert NULL in the column… and it fails which is normal. From this point, the settup start a revert and fails.

    Do you have an idea about why it’s doing this and how can I update my SCCM environnement?

    Thanks by advance!
    Regards,
    Adri

    Reply

    1. I have no idea why that’s happening. Have you modified anything in the CM database before ?.

      Reply

      1. Hi Prajwal,

        Nothing modified in the database… just turned on Bitlocker in SCCM console since the last update…
        May yhou know if I can found the script somewhere in order to put this step as a comment?

        Reply
  9. Avatar photo Gavin Bruce says:

    Great guide once again Prajwal.

    We are quite far behind on Config Mgr versions and looking to upgrade.

    If we went from 1706 > 1806 > 2002 in a row, would that be ok, or not advised?

    Thank you

    Reply

    1. Hi Gavin, you can upgrade to Microsoft Endpoint Configuration Manager (MECM) 2002 if you are running the following versions SCCM 1806 and above. So yes, first upgrade you ConfigMgr environment to 1806 and then you can directly upgrade to version 2002.

      Reply

  10. This may be a daft question but do i need to upgrade the ADK on my server to 2004 version before doing this upgrade? Currently have 1903 installed. Or is this now part of SCCM?

    Reply

  11. Is there a guide for offline upgrade for isolated networks?

    Reply
  12. Avatar photo Dhaval Patel says:

    Please create step by step document for new site installation of MEMCM 2002 as it is available as baseline version. It will help many of new beginners like me. Since long everyone is creating for upgrading site only.

    Reply

  13. In an envionment with multi DPs, apart from redistributing the boot disks, what else needs doing to make sure the DPs are up-to-date?
    They do not seem to have Configuration Manager installed.

    Reply

  14. Is anyone having issues with extremely slow download and install times after upgrading to SCCM 2002? I thought everything went good with the upgrade (no issues during Install process, it completed with no warnings and a status of Installed), but now that I’m creating new application packages and new Windows Updates have been downloaded I’m starting to have major problems. Applications and updates are either not showing up at all or when they do the download/install process is very slow. I am not finding anything helpful in client or server logs at this point.

    I also have noticed that even though the install and hotfix for 2002 show Installed and had no errors or warning cmupdate.exe is still running and the cmupdate.log files keeps stating “Waiting for changes to the “C:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box” directories, updates will be polled in 600 seconds…”. Is this normal behavior?

    Any help is greatly appreciated!

    Reply
  15. Avatar photo Michael H. says:

    Hello Prajwal,
    I have tried to upgrade my SCCM, but is stuck. It has ran the Prereqs but now I have no option to install. I have checked the EasyLoad folder and the files are there but the console is not allowing me to do the actual install. Any way to do it through Powershell?

    Reply
    1. Avatar photo Michael H. says:

      I do not have the Install option on 2002 or 1910 Hotfix

      Reply
      2. Avatar photo Prajwal Desai says:

        Examine those warnings and see what those are..

        Reply

  16. hi i on version 1910 but i dont see any update even after ruining the PS script
    can you help please/

    Reply
  17. Avatar photo Peggy Gordon says:

    Hi Prajwal,
     
    After updating Configuration Manager 1910 to 2002, TFTP stopped working and I am no longer able to boot PXE to image devices. I am running Server 2012r2, prerequisites passed, the install seems to go fine but when we try to boot PXE we get an IP address and then TFTP comes up and sits – then errors with error code PXE E32 TFTP Open Timeout.
     
    Any ideas?

    Reply

    1. Check the Windows Deployment Service ( WDS ) or Configuration PXE Responder service ( SCCMPXE) status on DP, restart the service

      Reply
      1. Avatar photo Peggy Gordon says:

        I’ve tried both of those. I’ve tried changing the setting to “Enable a PXE responder without Windows Deployment Service”. That turns off WDS and turns on the Configuration PXE Responder service – but I get the same error when I try to PXE boot.
        There was a KB update when I checked today – installed that hoping maybe it would fix it, but I get the same error with either configuration. Windows is up to date. I have restarted the server. Restarted the services. I have turned the PXE support for clients off, restarted, turned it back on. Still same error.

        Reply
  18. Avatar photo nilesh patel says:

    Prajawal. I updated to sccm 2002 all good.. but boot images not update. How do I update that manually? Or is there a location where these files are stored at on the server?

    Reply
  19. Avatar photo Marcos Fontana says:

    I am facing a problem with the following error: ERROR: Failed to download Admin UI content payload with exception: Unable to connect to the remote server.

    I cant know what is this remote server. Is it in some other log file?

    Reply
  20. Avatar photo Aishwary Bohra says:

    Hi Prajwal,

    I have installed 2002 on a Windows server 2019 standard.

    All seems well but when i try to create a New task Sequence, the console crashes.

    It doesn’t crash when im importing a Task Sequence or creating a TS media.

    Here’s the error from SMSAdminUI log

    [1, PID:1512][06/03/2020 08:01:35] :System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> System.Xml.XmlException: Could not find the PropertyPage with ID: {DBEFDCBB-A1B1-43ee-B15C-40987FCA53F3}.
    Microsoft.ConfigurationManagement.AdminConsole.SmsWizardForm.CreateWizardPage(String pageId)
    Microsoft.ConfigurationManagement.AdminConsole.SmsWizardForm.AddBranches(SmsWizardPage page)
    Microsoft.ConfigurationManagement.AdminConsole.SmsWizardForm.AddPages()
    Microsoft.ConfigurationManagement.AdminConsole.NewTaskSequenceWizard.NewTaskSequenceWizardWizardForm.AddPages()
    Microsoft.ConfigurationManagement.AdminConsole.SmsWizardForm.Initialize()
    Microsoft.ConfigurationManagement.AdminConsole.ShowDialogTaskHandler.DoTask(NavigationModelNodeBase node, SccmTaskConfiguration sccmTask, PropertyDataUpdated dataUpdatedDelegate, Boolean readOnly)
    Microsoft.ConfigurationManagement.AdminConsole.SccmTaskHandlerBase.DoTask(IList1 navigationNodes, NavigationModelNodeTask task)
    Microsoft.EnterpriseManagement.ConsoleFramework.WindowTaskHandler.WindowTaskOperation.ExecuteTaskJob(Object sender, ConsoleJobEventArgs jobArguments)
    Microsoft.ConfigurationManagement.AdminConsole.ConsoleJobExceptionHandler.ExecuteJob(IComponent component, EventHandler    1 job, Object sender, ConsoleJobEventArgs args)
    Microsoft.EnterpriseManagement.ConsoleFramework.ConsoleJobsService.RunJob(ConsoleJobDescription jobDescription)
    Microsoft.EnterpriseManagement.ConsoleFramework.WindowJobsService.RunJob(ConsoleJobDescription jobDescription)
    Microsoft.EnterpriseManagement.ConsoleFramework.WindowJobsService.RunJob(IComponent jobOwner, EventHandler1 jobMethod, EventHandler1 errorHandler, Object[] arguments)
    Microsoft.EnterpriseManagement.ConsoleFramework.WindowTaskHandler.WindowTaskOperation.ExecuteTask()
    — End of inner exception stack trace —
    System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
    System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
    System.Delegate.DynamicInvokeImpl(Object[] args)
    System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
    System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
    System.Windows.Threading.DispatcherOperation.InvokeImpl()
    System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
    System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
    System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
    System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
    MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state)
    System.Windows.Threading.DispatcherOperation.Invoke()
    System.Windows.Threading.Dispatcher.ProcessQueue()
    System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
    MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
    MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
    System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
    System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
    System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
    MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
    MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
    System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
    System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
    System.Windows.Window.ShowHelper(Object booleanBox)
    System.Windows.Window.Show()
    System.Windows.Window.ShowDialog()
    Microsoft.EnterpriseManagement.ConsoleFramework.WindowManager.GenericWpfWindowConstructor.BeginShow(ShowViewContext showViewContext, Object parent, Object view, AsyncCallback callback, Object state)
    Microsoft.EnterpriseManagement.ConsoleFramework.ViewConstructor.BeginShow(ShowViewContext showViewContext, AsyncCallback callback, Object state)
    Microsoft.EnterpriseManagement.ConsoleFramework.WindowManager.WpfWindowRecord.ShowWindow()
    — End of inner exception stack trace —
    System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
    System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
    System.Delegate.DynamicInvokeImpl(Object[] args)
    System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
    System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
    System.Windows.Threading.DispatcherOperation.InvokeImpl()
    System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
    System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
    System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
    System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
    MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state)
    System.Windows.Threading.DispatcherOperation.Invoke()
    System.Windows.Threading.Dispatcher.ProcessQueue()
    System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
    MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
    MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
    System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
    System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
    System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
    MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
    MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
    System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
    System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
    System.Windows.Application.RunDispatcher(Object ignore)
    System.Windows.Application.RunInternal(Window window)
    System.Windows.Application.Run(Window window)
    Microsoft.EnterpriseManagement.ConsoleFramework.ConsoleApplication.LaunchWindow()
    Microsoft.EnterpriseManagement.ConsoleFramework.ConsoleApplication.Run()
    Microsoft.ConfigurationManagement.AdminConsole.Program.Main()
    [7, PID:8764][06/03/2020 08:16:53] :Missing management class description for class ‘SMS_ActionAccountResult’
    [7, PID:8764][06/03/2020 08:16:53] :Missing management class description for class ‘SMS_AfwAppConfigSettings’
    [7, PID:8764][06/03/2020 08:16:53] :Missing management class description for class ‘SMS_CoManagementSettings’
    [7, PID:8764][06/03/2020 08:16:53] :Missing management class description for class ‘SMS_M365ASettings’
    [7, PID:8764][06/03/2020 08:16:53] :Missing management class description for class ‘SMS_OneDriveKnownFolderMigrationSettings’
    [7, PID:8764][06/03/2020 08:16:53] :Missing management class description for class ‘SMS_Report’
    [7, PID:8764][06/03/2020 08:16:53] :Missing management class description for class ‘SMS_UacComplianceSettings’
    [1, PID:8764][06/03/2020 08:17:29] :System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> System.Xml.XmlException: Could not find the PropertyPage with ID: {DBEFDCBB-A1B1-43ee-B15C-40987FCA53F3}.
    Microsoft.ConfigurationManagement.AdminConsole.SmsWizardForm.CreateWizardPage(String pageId)
    Microsoft.ConfigurationManagement.AdminConsole.SmsWizardForm.AddBranches(SmsWizardPage page)
    Microsoft.ConfigurationManagement.AdminConsole.SmsWizardForm.AddPages()
    Microsoft.ConfigurationManagement.AdminConsole.NewTaskSequenceWizard.NewTaskSequenceWizardWizardForm.AddPages()
    Microsoft.ConfigurationManagement.AdminConsole.SmsWizardForm.Initialize()
    Microsoft.ConfigurationManagement.AdminConsole.ShowDialogTaskHandler.DoTask(NavigationModelNodeBase node, SccmTaskConfiguration sccmTask, PropertyDataUpdated dataUpdatedDelegate, Boolean readOnly)
    Microsoft.ConfigurationManagement.AdminConsole.SccmTaskHandlerBase.DoTask(IList1 navigationNodes, NavigationModelNodeTask task)
    Microsoft.EnterpriseManagement.ConsoleFramework.WindowTaskHandler.WindowTaskOperation.ExecuteTaskJob(Object sender, ConsoleJobEventArgs jobArguments)
    Microsoft.ConfigurationManagement.AdminConsole.ConsoleJobExceptionHandler.ExecuteJob(IComponent component, EventHandler    1 job, Object sender, ConsoleJobEventArgs args)
    Microsoft.EnterpriseManagement.ConsoleFramework.ConsoleJobsService.RunJob(ConsoleJobDescription jobDescription)
    Microsoft.EnterpriseManagement.ConsoleFramework.WindowJobsService.RunJob(ConsoleJobDescription jobDescription)
    Microsoft.EnterpriseManagement.ConsoleFramework.WindowJobsService.RunJob(IComponent jobOwner, EventHandler1 jobMethod, EventHandler1 errorHandler, Object[] arguments)
    Microsoft.EnterpriseManagement.ConsoleFramework.WindowTaskHandler.WindowTaskOperation.ExecuteTask()
    — End of inner exception stack trace —
    System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
    System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
    System.Delegate.DynamicInvokeImpl(Object[] args)
    System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
    System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
    System.Windows.Threading.DispatcherOperation.InvokeImpl()
    System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
    System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
    System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
    System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
    MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state)
    System.Windows.Threading.DispatcherOperation.Invoke()
    System.Windows.Threading.Dispatcher.ProcessQueue()
    System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
    MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
    MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
    System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
    System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
    System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
    MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
    MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
    System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
    System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
    System.Windows.Window.ShowHelper(Object booleanBox)
    System.Windows.Window.Show()
    System.Windows.Window.ShowDialog()
    Microsoft.EnterpriseManagement.ConsoleFramework.WindowManager.GenericWpfWindowConstructor.BeginShow(ShowViewContext showViewContext, Object parent, Object view, AsyncCallback callback, Object state)
    Microsoft.EnterpriseManagement.ConsoleFramework.ViewConstructor.BeginShow(ShowViewContext showViewContext, AsyncCallback callback, Object state)
    Microsoft.EnterpriseManagement.ConsoleFramework.WindowManager.WpfWindowRecord.ShowWindow()
    — End of inner exception stack trace —
    System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
    System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
    System.Delegate.DynamicInvokeImpl(Object[] args)
    System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
    System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
    System.Windows.Threading.DispatcherOperation.InvokeImpl()
    System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
    System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
    System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
    System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
    MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state)
    System.Windows.Threading.DispatcherOperation.Invoke()
    System.Windows.Threading.Dispatcher.ProcessQueue()
    System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
    MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
    MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
    System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
    System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
    System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
    MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
    MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
    System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
    System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
    System.Windows.Application.RunDispatcher(Object ignore)
    S

    In Event Viewer, i see the error below-

    Application: Microsoft.ConfigurationManagement.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.Xml.XmlException
    Microsoft.ConfigurationManagement.AdminConsole.SmsWizardForm.CreateWizardPage(System.String)
    Microsoft.ConfigurationManagement.AdminConsole.SmsWizardForm.AddBranches(Microsoft.ConfigurationManagement.AdminConsole.SmsWizardPage)
    Microsoft.ConfigurationManagement.AdminConsole.SmsWizardForm.AddPages()
    Microsoft.ConfigurationManagement.AdminConsole.NewTaskSequenceWizard.NewTaskSequenceWizardWizardForm.AddPages()
    Microsoft.ConfigurationManagement.AdminConsole.SmsWizardForm.Initialize()
    Microsoft.ConfigurationManagement.AdminConsole.ShowDialogTaskHandler.DoTask(Microsoft.EnterpriseManagement.ConsoleFramework.NavigationModelNodeBase, Microsoft.ConfigurationManagement.AdminConsole.SccmTaskConfiguration, Microsoft.ConfigurationManagement.AdminConsole.PropertyDataUpdated, Boolean)
    Microsoft.ConfigurationManagement.AdminConsole.SccmTaskHandlerBase.DoTask(System.Collections.Generic.IList1<Microsoft.EnterpriseManagement.ConsoleFramework.NavigationModelNodeBase>, Microsoft.EnterpriseManagement.ConsoleFramework.NavigationModelNodeTask)
    Microsoft.EnterpriseManagement.ConsoleFramework.WindowTaskHandler+WindowTaskOperation.ExecuteTaskJob(System.Object, Microsoft.EnterpriseManagement.ConsoleFramework.ConsoleJobEventArgs)
    Microsoft.ConfigurationManagement.AdminConsole.ConsoleJobExceptionHandler.ExecuteJob(System.ComponentModel.IComponent, System.EventHandler    1<Microsoft.EnterpriseManagement.ConsoleFramework.ConsoleJobEventArgs>, System.Object, Microsoft.EnterpriseManagement.ConsoleFramework.ConsoleJobEventArgs)
    Microsoft.EnterpriseManagement.ConsoleFramework.ConsoleJobsService.RunJob(Microsoft.EnterpriseManagement.ConsoleFramework.ConsoleJobDescription)
    Microsoft.EnterpriseManagement.ConsoleFramework.WindowJobsService.RunJob(Microsoft.EnterpriseManagement.ConsoleFramework.ConsoleJobDescription)
    Microsoft.EnterpriseManagement.ConsoleFramework.WindowJobsService.RunJob(System.ComponentModel.IComponent, System.EventHandler1<Microsoft.EnterpriseManagement.ConsoleFramework.ConsoleJobEventArgs>, System.EventHandler1<Microsoft.EnterpriseManagement.ConsoleFramework.ConsoleJobErrorEventArgs>, System.Object[])
    Microsoft.EnterpriseManagement.ConsoleFramework.WindowTaskHandler+WindowTaskOperation.ExecuteTask()

    Exception Info: System.Reflection.TargetInvocationException
    System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean)
    System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(System.Object, System.Object[], System.Object[])
    System.Delegate.DynamicInvokeImpl(System.Object[])
    System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
    System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
    System.Windows.Threading.DispatcherOperation.InvokeImpl()
    System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
    System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
    System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
    System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
    MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
    System.Windows.Threading.DispatcherOperation.Invoke()
    System.Windows.Threading.Dispatcher.ProcessQueue()
    System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
    MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
    MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
    System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
    System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
    System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
    MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
    MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
    System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
    System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
    System.Windows.Window.ShowHelper(System.Object)
    System.Windows.Window.Show()
    System.Windows.Window.ShowDialog()
    Microsoft.EnterpriseManagement.ConsoleFramework.WindowManager+GenericWpfWindowConstructor.BeginShow(Microsoft.EnterpriseManagement.ConsoleFramework.ShowViewContext, System.Object, System.Object, System.AsyncCallback, System.Object)
    Microsoft.EnterpriseManagement.ConsoleFramework.ViewConstructor.BeginShow(Microsoft.EnterpriseManagement.ConsoleFramework.ShowViewContext, System.AsyncCallback, System.Object)
    Microsoft.EnterpriseManagement.ConsoleFramework.WindowManager+WpfWindowRecord.ShowWindow()

    Exception Info: System.Reflection.TargetInvocationException
    System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean)
    System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(System.Object, System.Object[], System.Object[])
    System.Delegate.DynamicInvokeImpl(System.Object[])
    System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
    System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
    System.Windows.Threading.DispatcherOperation.InvokeImpl()
    System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
    System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
    System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
    System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
    MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
    System.Windows.Threading.DispatcherOperation.Invoke()
    System.Windows.Threading.Dispatcher.ProcessQueue()
    System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
    MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
    MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
    System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
    System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
    System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
    MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
    MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
    System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
    System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
    System.Windows.Application.RunDispatcher(System.Object)
    System.Windows.Application.RunInternal(System.Windows.Window)
    System.Windows.Application.Run(System.Windows.Window)
    Microsoft.EnterpriseManagement.ConsoleFramework.ConsoleApplication.LaunchWindow()
    Microsoft.EnterpriseManagement.ConsoleFramework.ConsoleApplication.Run()
    Microsoft.ConfigurationManagement.AdminConsole.Program.Main()

    Reply
    1. Avatar photo Jan Grundmann says:

      Hi, I got the same error message. Did you find out what was the root cause of the console crashes?

      Reply
      1. Avatar photo Jiri Stransky says:

        I worked on the issue with Jan and we fixed it. Problem was in xml form used for the TS creation wizard. We are using Nomad, and it adds on normal circumstances into this form new part about Nomad config. But, after 2002 installation the change was missing (even after integration process) and due this Wizard was failed. We fixed it manual add the missing information into the form regard previous version.

        Reply
  21. Avatar photo Jobish George says:

    Hi Prajwal,
    Is there a way to reinstall the 2002 update. After the installation of 2002 I see a lot of issues to my sccm services. Many of the IIS virtual directories vanished. Client upgrade is not happening at all. ccmsetup.log shows,
     

    1. GetDirectoryList failed with a non-recoverable failure, 0x80004005.
    2. Failed to get directory list from CCM_Client. 0x80004005.
    3. Failed to correctly receive a WBDAV HTTP request.
    4. Failed to check url ccmsetup.cab. Error 0x80004005.

     
    In the IIS I see only three virtual directories as below
     

    1. SMS_DP_SMSPKG$
    2. SMS_DP_SMSSIG$
    3. SMS_FSP (If I browse this directory directory from IIS, the directory is empty).

     
    Could you be able to advice on this. Is there a way to re apply the 2002 update. Currently it shows as installed under Console node Updates and Servicing.
     
     
     

    Reply

  22. I updated my SCCM server from 1902 to 2002 and the pre-production client has a compliance status of Not Compliant. I have two Windows 10 v1909 machines and they both show client version of 5.00.8790.1007. I’m still learning SCCM. I’ve verified that the Configuration Manager Client Piloting Package was updated and that the content was successfully distributed. What am I missing?
     

    Reply

  23. Hello Prajwal,

    First thank you very much for your website.

    I’m trying to upgrade from 1910 to 2002 an SQL AO and HA lab.

    I runned the prerequisite check but it’s failed on the ” Unsupported site server operating system version ” task.

    In the ConfigMgrPrereq.log I can see the error is on the listener 🙁

    Do you understand why the listener is checked for the OS ? and how I can avoid this failed ?

    TIA.

    Regards.

    Reply

    1. Can you tell what is the Windows server version on which you have installed ConfigMgr 1910 ?.

      Reply

      2. Other information … my lab is in Azure … my listener is linked with a loadbalancer

        Reply
        1. Avatar photo Pavan Ayyagari says:

          Hello There, I believe you need to change the sql failover from automatic to manual before doing the upgrade.

          Reply
  24. Avatar photo Abdul Jalil says:

    I received the below issue after upgrading to version 2002

    Reply

  25. Hi,
    is there still possible to install the client on Windows 2008 / 2008 R2?

    Reply

  26. Hi Prajwal,

    I am begginer in SCCM. I have downloaded the sccm 2002 ( current branch) from Microsoft evaluation.
    It gets successfully installed.

    Now I want to add system roles. But the application catalogue website and application catalogue web servises options are not available.

    Could you please help how to add that?

    Thanks in advance.

    Reply

    1. Starting in version 1906, updated clients automatically use the management point for user-available application deployments. You also can’t install new application catalog roles. Support ends for the application catalog roles with version 1910.

      Reply

      1. Could you please provide me the link to install sccm 1902 or 1910 evaluation version.

        Thanks in advance.

        Reply

          1. Hi Prajwal,

            The links which you mentioned i.e Microsoft eval-center are navigating to the same page which results in downloading SCCM 2002. 🙁

            Not able to find link to download “System Center Configuration Manager and Endpoint Protection (current branch – version 1902)”

            Could you please help?

            Reply

          2. Hi Prajwal,

            The link you have mentioned are navigating to the same page i.e MIcrosoft Evalcenter which result in SCCM 2002 download.

            I am unable to download : “System Center Configuration Manager and Endpoint Protection (current branch – version 1902)”

            Could you please help me?

            Thanks.

            Reply

            1. Hi Rutuja,

              You may not find the 1902 baseline version in Eval center because it has been replaced with version 2002. You might need to download it from VLSC or MSDN. Until now the eval center had version 1902 available for download but now you can only get latest version i.e. 2002.

              Reply

              1. Ok I will check on VLSC /MSDN.

                Thank you very much for the information.

                Best wishes.

                Regards,
                Rutuja

                Reply

  27. Hi Prajwal,

    I upgraded to latest version 2002 and the only issue or bug that I have is MP “Http test request failed, status code is 500, ‘Internal Server Error’ from mpcontrol.log”

    What I checked was that the sql sccmadmin account was removed from MP database at roles during upgrade, I re assigned it but the http error 500 is still.

    Please do you know something what is wrong, how to fix this issue?

    Thank you.

    Reply

  28. Great question that I need to know a well. Given Extended Support, I would sure hope so but it would be great to get confirmation if anyone knows. Thank you.

    Reply
  29. Avatar photo Jitu Patro says:

    Thanks and you’re posts are allways very easy to understand with full of information. very helpful !

    I have a question 🙂 How do we check if its now globally available as in for the slow ring as an in-console Update.

    We are running a project and we need to installl ASAP to try new features. However, dont want to take risks.

    Best wishes !
    zitupee

    Reply

  30. Boot images that are pointed to the default Data Source (boot.wim) will automatically update during the setup. You only need to manually update the boot images that point to a custom boot.wim

    Reply

    1. You are right but some times the default boot images aren’t updated to DP’s. I have seen this issue in some environments so I usually advise to redist it manually.

      Reply
      1. Avatar photo Jitu Patro says:

        I had a similar Issue recently. Just 1 site/DP had this issue.It said deployment fine on the monitoring status. Came to know only when the issue was reported from the build site. Thank god for SCCM it tells me which file to look and the file was missing from DP. I manually copied the file and its working well since. It does do it automatically, but better to start a redistribute after a successful upgrade and have a peace of mind. 🙂

        Best Wishes !
        Zitupee

        Reply
  31. Avatar photo Tom Shepherd says:

    Prajwal, firstly thank you so much for all the information provided on your website. There are very, very helpful.

    I current have running an SCCM 1910 Evaluation running. Am I able to activate it by using a 1902 Product Key? I would like to activate it first before updating it to 2002.

    Reply

  32. The outdated ConfigMgr clients version should be 5.00.8968.1014. I upgraded 22-04-2020 to MECM 2002 and pushes the latest ConfigMgr client.

    Reply

  33. Hi Prajwal, I am running script on top layer of SCCM server and giving same name as parameter but I am still receiving error ” Please provide top level site server name or IP”. Can you please assist.

    Reply

    1. That is strange. Can you check if you are entering the right server name or try entering the IP address and check if that works.

      Reply

  34. Hi Prajwal, thank you so much for all you’ve done!
    After the installation of 2002 in the Client Device Settings, the tab “Install Endpoint Protection client on client computers” is still grey (I’ve already create a Custom Client settings) and I can’t disable Endopoint push cause I’ve always grey all tabs of Endpoint Protection! Have you got the same problem in your environment?
    Best Regards

    Reply

    1. PS. Problem solved: I’ve reinstalled Endpoint Protection Point

      Reply

      1. That’s great. Always monitor the log files to determine the role installation.

        Reply

  35. Prajwal you are the best. Thanks for your information

    Reply
  36. Avatar photo Marcel R. says:

    When will the update be available for those guys in the slow ring?

    Greetings from Germany
    Marcel R.

    Reply
  37. Avatar photo Devrath P says:

    Nice guide Prajwal. Do you know when will SCCM 2002 be made available for everyone ?. My organisation doesn’t permit the fast ring script.

    Reply

      1. dont you have a guide on enabling endpoint protection for 2002

        Reply

Leave a Reply

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