Create Custom Intune Helpdesk Operator Role Deploy

Let’s create a custom Intune Helpdesk Operator Role as per your organizational requirement. Once the custom helpdesk operator role is created in Intune portal, you can deploy that to a group of admin users.

More RBAC Related posts

Create Custom Intune Helpdesk Operator

  • Login to endpoint.microsoft.com with global admin or Intune Service Admin (Intune admin) permission
  • Navigate to Tenant Admin – Roles
  • Select Help Desk Operator role from All Roles
  • Click on Duplicate
Custom Intune Helpdesk Operator
Custom Intune Helpdesk Operator
  • Enter the name of custom HelpDesk operator role
  • Click NEXT
Create Custom Intune Helpdesk Operator Role Deploy 1
Create Custom Intune Helpdesk Operator Role Deploy 8
  • As per requirement – Select a category below to configure access rights
  • Click on NEXT
Create Custom Intune Helpdesk Operator Role Deploy 2
Create Custom Intune Helpdesk Operator Role Deploy 9
  • Select SCOPE tag
  • Click on NEXT
Create Custom Intune Helpdesk Operator Role Deploy 3
Create Custom Intune Helpdesk Operator Role Deploy 10
  • Click on CREATE button to continue
Create Custom Intune Helpdesk Operator Role Deploy 4
Create Custom Intune Helpdesk Operator Role Deploy 11

Deploy

Create Custom Intune Helpdesk Operator Role Deploy 5
Create Custom Intune Helpdesk Operator Role Deploy 12

Resources

SCCM Client Troubleshooting Advanced Level with Real-World Experience by Deepak

I have conducted a How to Manage Devices (HTMD) Community Teams meeting session (weekend learning) to share my real-world experience of SCCM Client Troubleshooting. The recording is available in this post is available in the below section of the post.

Stay Connected with HTMD Communityhttps://howtomanagedevices.com/stay-connected/

Agenda – SCCM Client Troubleshooting

Download Presenation

You can download the presentation here.

HTMD Community Blogs

Other Community Posts

Chat Transaction

Registry Key Path of SCCM ConfigMgr Client:

  • Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCMSetup
  • Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS
  • Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM

Recording

Resources

SCCM Client Troubleshooting
SCCM Client Troubleshooting

Intune Basics for SCCM Admins | ConfigMgr Admins to Learn EndPoint Manager

Intune Basics for Configuration Manager Admins

I have taken a session called Intune Basics for Configuration Manager Admins (Intune Basics for SCCM Admins) during  “How to Manage Devices Live Digital Events Weekend Learning.”

Related Posts! – Learn about the Microsoft Intune for SCCM Admins training posts. 1. Microsoft Intune for SCCM Admins Part 1 2. Microsoft Intune for SCCM Admins Part 2

Topics Discussed – Intune Basics for SCCM Admins

  • Intune Vs SCCM Admin Experience
  • Intune Vs SCCM Architecture
  • Intune Vs SCCM Server Architecture
  • Azure Service Fabric Clusters
  • Active Directory Vs Azure Active Directory
  • SCCM Client Vs Intune Client (MDM Component)
  • Intune Targeting Vs SCCM Targeting (Azure AD Groups Vs Collections)

SCCM Vs Intune Architecture

Intune Architecture - Diagram Credits to Brad Anderson Microsoft CVP Intune Basics for SCCM Admins
Intune Architecture – Diagram Credits to Brad Anderson Microsoft CVP (Intune Basics for SCCM Admins)

How to Manage Devices Community

Would you like to join the community and stay connected? Go through the following blog post “How to Manage Devices Live Digital Events Weekend Learning” and joint HTMD Teams Channel to learn more about device management technologies.

Many How To Manage Device Community members were looking for the recording of the session. So I thought of sharing the same with you all.

Learn Intune from SCCM Admin

We have started an online Free Intune Training classes for SCCM Admins. Following are video recording!

More DetailsFree Intune Training from How to Manage Devices Community via HTMD Teams Channel

Watch this playlist on YouTube

Resources

SCCM CMG Cloud Management Gateway Questions Answered by Rajul Recording | ConfigMgr | HTMD Live

I have conducted a How to Manage Devices Community Teams meeting session to share my real-world experience of SCCM CMG Cloud Management Gateway design and implementation for more than dozen customers. The recording is available in this post is available in the below section of the post.

How to Manage Devices Community

Would you like to join the community and stay connected? Go through the following blog post “How to Manage Devices Live Digital Events Weekend Learning” and joint HTMD Teams Channel to learn more about device management technologies.

Many How To Manage Device Community members were looking for the recording of the session. So I thought of sharing the same with you all.

How to Find Out Devices Connected to CMG?

I have a couple of posts where I explained more details of Configuration Manager Cloud Management Gateway and troubleshooting of CMG with SCCM logs. You can refer below:

Recording – Cloud Management Gateway Questions Answered

SCCM ConfigMgr CMG | Cloud Management Gate Questions by 👌Rajul OS | Answered FAQs | HTMD 📌Live Ep #6

Resources

How to Disable Microsoft Teams Automatic Update During SCCM | ConfigMgr Application Installation for VDI

I have seen a discussion about controlling Microsoft Teams’ automatic updates (Disable Microsoft Teams Automatic Update) from the internet when most of the workforce is working from home. The idea is not to update Microsoft Teams automatically when the user is connected from home. There could be two potential options to stop Microsoft Teams Automatic Update to new versions.

Introduction

As per Microsoft, Teams desktop client updates are released every two weeks. I think this update is not on the same channel as of Office 365 pro plus updates. MSTeams update usually takes place on a Tuesday.

I don’t think Microsoft provides any direct way to control Teams automatic update via Group policy or some other method. The desktop client updates itself automatically. Teams desktop application checks for updates every few hours, downloads it (if there is any), and then wait for the Windows 10 to be idle before silently installing the update.

I have a couple of posts to help IT Pros to install Microsoft Teams using Configuration Manager (a.k.a SCCM). More details about the MSTeams installation are explained in the following post. If you are looking for step by step MSTeams installation guide using SCCM|ConfigMgr, then refer to the following guide.

In this post, you could help you to find out some potential solutions to block Microsoft Teams automatic update. I don’t think this method is optimal or recommended by Microsoft for the Teams installation on Windows 10 devices.

Block Microsoft Teams Automatic Update
Block Microsoft Teams Automatic Update – Disable Automatic Update for Microsoft Teams

Create MS Teams Application with Disable Automatic Update for VDI & WVD

As I mentioned in the above section, you need to go through the step by step guide of MSI installation and deployment of Microsoft Teams using SCCM. The following method only works for Windows Virtual Devices(WVD) and VDI environments.

⏬⏬You can download Microsoft Teams from Microsoft:🔰🔰🔰

Application name: Teams Machine-Wide Installer
Publisher:Microsoft
Software version:
Deployment type name: Teams Machine-Wide Installer - Windows Installer (*.msi file)
Product Code: {731F6BAA-A986-45A4-8936-7C3AAAAA760B}
Installation behavior: Install for Machine
Content location: \cmmemcm\Sources\Package Sources\MSTeams for VDI\
Number of files: 1
Content files:Teams_windows_x64.msi
  • Make sure that you use the following command line to Diable Microsoft Teams Automatic Update
msiexec /i "Teams_windows_x64.msi" /l*v TeamsInstall.log ALLUSER=1 ALLUSERS=1
  • The ALLUSER=1 parameter is used only to specify a per-machine installation.
  • The ALLUSERS=1 parameter is used only if you want to have options – “all users can uninstall Teams if they have admin credentials.”
  • Install Behaviour – Make sure you selected -> Install for System
Disable Microsoft Teams Automatic Update
Block or Disable Microsoft Teams Automatic Update

The following metadata of Microsoft Teams application is the one that you should use for blocking the Microsoft Teams auto-updates behavior. As you can see in the below section, this is applicable only for VDI environments.

General Information:
• Application name: Teams Machine-Wide Installer
• Administrator comments:
• Publisher: Microsoft
• Software version:
• Optional reference:
Categories:
Deployment type name: Teams Machine-Wide Installer - Windows Installer (*.msi file)
Requirement rules:
Content:
• Content location: \cmmemcm\Sources\Package Sources\MSTeams for VDI\
• Installation program: msiexec /i "Teams_windows_x64.msi" /l*v TeamsInstall.log ALLUSER=1 ALLUSERS=1
Detection Method:
• Product code: {731F6BAA-A986-45A4-8936-7C3AAAAA760B}
User Experience:
• Installation behavior: Install for system

The secret to Disable Microsoft Teams Automatic Update?

The secret to Disable Microsoft Teams Automatic Update?
The secret to Disable Microsoft Teams Automatic Update? Microsoft documentation

So what is the secret here to Block Microsoft Teams Automatic Updates while installing an application using ConfigMgr?

As per Microsoft documentation, PER-Machine based installation helps to DISABLE automatic updates for Microsoft Teams.

Verification

The installation Microsoft Teams failed with an error “Installation has Failed – Cannot install for all users when a VDI environment is not detected.” The following are some of the snippets of Microsoft Teams installation log file.

As you can see in the above error, this is applicable only for VDI environments. I feel this is because of custom action checked included in the Teams MSI installation file. So what is the option to Disable Microsoft Teams automatic update? Let’s check the last section to get details.

CustomAction RunInstalledExecutable returned actual error code -2147467259 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (EC:58) [22:28:49:375]: Note: 1: 1722 2: RunInstalledExecutable 3: C:\Program Files (x86)\Teams Installer\Teams.exe 4: --allUsers
MSI (s) (EC:58) [22:28:49:375]: Note: 1: 2205 2: 3: Error
MSI (c) (40:2C) [22:28:49:391]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action RunInstalledExecutable, location: C:\Program Files (x86)\Teams Installer\Teams.exe, command: --allUsers
Cannot install for all users when a VDI environment is not detected - Disable Automatic Update for Microsoft Teams
Cannot install for all users when a VDI environment is not detected – Disable Automatic Update for Microsoft Teams

Solution

I think Microsoft Teams update might be part of Office 365 pro plus update channel in near future. The only workaround which I came to know while writing this post is given below.

1. It seems you can disable the Microsoft Teams Automatic Update by blocking the traffic to update URLs via corporate proxy solutions.

2. Many other Options (changing settings.json & permissions to DownloadedUpdate folder) are available in the Tech Community forum – https://techcommunity.microsoft.com/t5/microsoft-teams/how-to-disable-check-for-updates-in-microsoft-teams/m-p/54644 (Test, Test, and Test before you implement these in production).

Resources

What is Dead File Microsoft Teams Detection Method

What is Dead File Microsoft Teams? Are you looking for a script logic to confirm the uninstallation of Microsoft Teams? Is this a funny fact 🤣🤣😎 You can check for the existence of a file named “.dead”. You can find this “.DEAD” file in the AppData folder of the user profile.

Introduction

You can refer to the following blog posts to understand the installation option of Microsoft Teams MSI! .However, in this post, we will see more about the DEAD file? What does this DEAD file mean? Why the DEAD file is empty? Does the presence of a “.DEAD” file in the application folder means the Teams application is uninstalled from the Windows 10 device? YES! 🙂

The .DEAD file can be used as one of the detection methods for the un-installation of Microsoft Teams. Can’t we use MSI product code as a detection method? Of course yes.

.Dead file is just an empty file 😋😋

Before Uninstall

Before the uninstall of Microsoft Teams, you would be able to see all these folders for per-user installation.

Folder Location: C:\Users\anoop.MEMCM\AppData\Local\Microsoft\Teams

.Dead File Microsoft Teams
.Dead File Microsoft Teams

After Uninstall -.Dead File Microsoft Teams

After the uninstall of Microsoft Teams, you can see the following files in the MS Teams application.

Folder Location:- C:\Users\anoop.MEMCM\AppData\Local\Microsoft\Teams

.Dead File Microsoft Teams
.Dead File Microsoft Teams

Resources

How to Manage Devices Live Digital Events Weekend Learning

“How to manage devices (HTMD)” team is arranging a series of LIVE digital events. We have already started the live online events on the following weekend. Recording Details are given below.

  • March 30th, 2020
  • April 4th and 5th April 2020
  • April 11th and 12th April 2020
  • April 18th and 19th April 2020
  • April 25th and 26th April 2020
  • May 2nd and 3rd May 2020

NOTE! – The recording of all the events are available in the following YouTube Channel.

Day #1 Free Intune Training via HTMD Teams Channel – 🔰Trial Subscription – 📌Get Started – Episode#1 – YouTube

(3) HTMD SCCM0️⃣1️⃣How to Setup ConfigMgr Lab in Azure-Create Azure Resource Group Virtual Network – YouTube

(3) 🛠HTMD Live Episode #3 OSD SMSTS Log by ✊Vishal Goyel ✊ #SCCM #ConfigMgr #MEMCM❤ How To Manage Device – YouTube

How to Manage Devices Live Digital Events
How to Manage Devices Live Digital Events

Recordings Videos

Watch this playlist on YouTube

Who are We?

We are a bunch of technical people trying to help the device management community (SCCM, ConfigMgr, Intune, etc) by sharing our experiences within the IT industry!

The Team - How to Manage Devices Digital Events
The Team – How to Manage Devices Live Digital Events

We arranged in-person events in Bangalore and we are part of Bangalore IT Pro user group! More details here.

 How to Manage Devices Digital Events Enrollment Types in Intune WIP Intune App Protection - HTMD
How to Manage Devices Live Digital Events

Want to Join Our Digital Events?

  • Be part of How to Manage Devices Teams channel
  • How can you be part of How to Manage Devices Teams Channel?
  • You shall get an invitation to join the channel
  • Once you are part of the Channel, you are all set to join Teams Digital Meetings for the coming days!!
  • Also, be part of our Whatsapp and Telegram groups to get immediate information about the changes in the schedule of these events. If you are already part of these groups. Don’t join!

NOTE! – We already arranged a virtual/digital event on the 30th of March 2020 (Sunday) for two hours with more than 150+ participants!!

How to Manage Devices Live Digital Events Weekend Learning 12
How to Manage Devices Live Digital Events

Schedule

  • April 4th, 2020 – 6 PM to 8 PM IST (Convert TimeZone)
  • April 5th 2020 – 6 PM to 8 PM IST

Resources

SCCM List of Full Features Vs Pre-Release Features | 2002

Let’s see the list of SCCM pre-release features vs full features after the release of the SCCM 2002 release. Excited to see many features are fully developed now and out of the PREVIEW tag with the 2002 version of ConfigMgr.

More Latest and Updated postSCCM Pre-Release Features Are Grayed Out | Enable | ConfigMgr

Resources

Download PowerShell Script to Enable Opt-In Version of SCCM 2006 Early Update Ring

Yes, there is a PowerShell Script to Enable Opt-In version of SCCM. I get many questions related to PowerShell script which you need to use to enable the FAST (Early/Opt-in) Ring version of Configuration Manager.

2006 Upgrade Guide – https://www.anoopcnair.com/sccm-primary-server-upgrade-to-2006-configmgr-guide-step-by-step/

Download PowerShell Script to Enable Opt-In Version of SCCM

You can download the script from the link here. And see the instructions here.

In this post, let’s see from where you can get the PowerShell Script to enable SCCM 2006.

Related Post – The Rings Story of SCCM – https://www.anoopcnair.com/slow-ring-vs-fast-ring-detailsearly-update-ring/

Introduction

You need to have an ONLINE Service connection point to enable the Opt-in (early update) ring of SCCM 2006.

NOTE! – You need to use the PowerShell script to enable the Opt-in version of ConfigMgr 2002 or Fast ring or Early Update ring version of 2006.

Once the 2002 version of Configuration Manager is Generally Available, then all your SCCM infra with the online service connection point will automatically get the 2006 update.

ONLINE Persistent Connection - PowerShell Script to Enable Opt-In Version of SCCM
ONLINE Sevice Connection Point – More details https://www.anoopcnair.com/learn-how-to-install-reinstall-sccm-service-connection-point-configmgr/ PowerShell Script to Enable Opt-In Version of SCCM

How to Run the PowerShell Script to Enable Opt-in RIng

  • You can open PowerShell ISE or prompt with administrative access.
  • You also need appropriate admin access within your SCCM environment (Full Admin is good).
  • Run the PowerShell Script to enable the opt-in ring
  • Enter the Site Server Name (FQDN)
  • Check the return message and confirm whether the command is the completed successfully or not
PowerShell to Enable Opt-in Ring -  Slow Ring Vs Fast Ring Details - Site Server Name (FQDN)
Site Server Name (FQDN) – PowerShell Script to Enable Opt-In Version of SCCM

Resources

SCCM 2002 Installation Step by Step Guide | MEMCM | ConfigMgr

I know you have seen many steps by step videos and installation guides to update Configuration Manager current version. This guide is another one that shows how to upgrade from SCCM 1910 to 2002 version.

New Features of Configuration Manager (A.K.A SCCM) 2002 version is given in the following post https://www.anoopcnair.com/configmgr-2002-list-of-new-features-enhancements-memcm-sccm/

NOTE! – Well, I know it’s not SCCM. It’s called Microsoft Endpoint Manager Configuration Manager (MEMCM) or Microsoft Endpoint Configuration Manager (MECM).

Prerequisites of 2002 Version

NOTE! – If you have SCCM DPs and PXE servers running on Windows server 2008 R2. You need to plan to upgrade it before the latest supported version before upgrading to the ConfigMgr 2002 version of the current branch. Server 2008 R2 DP and PXE are not supported anymore. More details – here.

  1. The following SCCM versions are supported for the upgrade to 2002.
  2. Install update 2002 at the top-level site of your hierarchy (CAS or Standalone Primary)
  3. SCCM version should have online Service Connection Point
  4. Evaluate Checklist
  5. Evaluate SQL Requirements for SCCM 2002 Upgrade – here
  6. Evaluate Windows Server OS Requirements for SCCM 2002 site server – here
  7. Evaluate Supported OS versions for clients and devices – here
  8. Evaluate Supported OS versions for ConfigMgr consoleshere
  9. Evaluate Recommended hardwarehere
  10. Support for Windows features and networkshere
  11. Evaluate Support for virtualization environments – here
  12. Evaluate the Firewall Rules – More details here and here

NOTE! – To download the update when your service connection point is offline, use the service connection tool.

SCCM 2002 Installation Step by Step Guide
SCCM 2002 Installation Step by Step Guide

Upgrade Check List

The following are the high-level checklist provided by Microsoft. Let’s go through this list before starting the upgrade in a production environment.

  • All sites run a supported version of Configuration Manager
  • Review the status of your product licensing
  • Review Microsoft .NET versions
  • Review the version of the Windows ADK for Windows 10
  • Review SQL Server Native Client version
  • Review file and data replication between sites
    • Database replication
    • File-based replication
  • Install all applicable critical Windows updates
  • Disable database replicas for management points at primary sites
  • Set SQL Server AlwaysOn availability groups to manual failover
  • Disable site maintenance tasks at each site
  • Temporarily stop any antivirus software
  • Back up customized files
  • Plan for client piloting
  • Plan to use service windows
  • Review supported extensions
  • Run the setup prerequisite checker (I recommend to run prerequisite check 3-4 day before the production upgrade)
  • Update sites

More detailed information about the ConfigMgr 2002 installation checklist is given below https://docs.microsoft.com/en

Download and Install 2002 version fo ConfigMgr

  • As this 2002 version of SCCM is part of the opt-in (early update) ring, you need to opt-in to have this update available in the console.
  • Opt-in using PowerShell command. Download and Run the PowerShell command.
  • Launch ConfigMgr console & navigate through \Administration\ Overview \Updates and Servicing.
  • Check 2002 fast or Opt-in version update of ConfigMgr is already available or not?
  • If not, click on the “Check for Updates” button from the ribbon menu
  • Click OK to continue
SCCM 2002 Installation Step by Step Guide
SCCM 2002 Installation Step by Step Guide
  • Configuration Manager 2002 update is available and Downloading

SCCM 2002 Download Stuck

This stuck download issue is a common scenario in enterprise organizations and LAB environments. This issue is mostly because of proxy or some other internet-related issues.

There are a couple of ways to fix this kind of issue if it’s not related to proxy and internet. You can refer to the previous blog posts to solve Update Download stuck problems.

More troubleshooting help on SCCM 2002 Download stuck and upgrade issues here and here .

Microsoft Doc ➡ https://support.microsoft.com/en-us/help/4490424/understand-and-troubleshoot-updates-and-servicing-in-configmgr

Downloading - SCCM 2002 Installation Step by Step Guide
Downloading – SCCM 2002 Installation Step by Step Guide

Log Files are Your Friend

  • DMPDownloader.log for SCCM 1910 source file download issues
  • ConfigMgrSetup.log for Redist Files Download Issue
  • CMUpdate.log for all the upgrade related activities
  • If the update displays as Downloading and doesn’t change, review the hman.log and dmpdownloader.log for errors.
    • The dmpdownloader.log may indicate that the dmpdownloader process is waiting for an interval before checking for updates. To restart the download of the update’s redistribution files, restart the SMS_Executive service on the site server.
    • Another common download issue occurs when proxy server settings prevent downloads from silverlight.dlservice.microsoft.comdownload.microsoft.com, and go.microsoft.com.
  • For more information about installing updates, see In-console updates and servicing.
  • For more information about current branch versions, see Baseline and update versions.

Download Completed

  • SCCM 2002 download is completed successfully
  • 2002 update is Ready to Install
  • Right Click on the Update “Configuration Manager 2002” Update
  • Select PreRequisite Check
    • Once the Prerequisite Check is completed successfully proceed to the next step
  • Right Click on the Update “Configuration Manager 2002” Update
  • Click on Install Update to start the SCCM 2002 installation
Ready to Install - SCCM 2002 Installation Step by Step Guide
Ready to Install – SCCM 2002 Installation Step by Step Guide

SCCM 2002 Update Prerequisite Check Stuck?

The SCCM upgrade prerequisite check can take many hours, depending on your hierarchy/infra. When you have CAS and many primary servers, the 2002 update source files will be copied to primary servers.

You can check the status of the prerequisite checks from the monitoring node. More details about SCCM prerequisite checks here.

Microsoft Documentation – https://docs.microsoft.com/en-us/configmgr/core/servers/deploy/install/prerequisite-checker

NOTE! – Make sure you start the prerequisite checks 3-4 days before the production update/upgrade of SCCM infra.

Configuration Manager Update Wizard

Let’s continue with SCCM 2002 update wizard:

  • Click on “Ignore any prerequisite check settings and install the update regardless of missing requirements” box
  • Click on Next button
  • Select the features you want to enable after the upgrades from Features Included in Update Pack page
    • ….
    • …..
  • Click on Next to continue
Features Included in Update Pack - SCCM 2002 Installation Step by Step Guide
Features Included in Update Pack – SCCM 2002 Installation Step by Step Guide
  • Client Update Settings page configuration
    • Upgrade without validating (Direct Production Upgrade)
    • Validate in pre-production collection (Test the client before the upgrade)
  • Click NEXT button to continue

Client Update Settings Option

Client Update Settings is another important option in Configuration Manager Update Wizard for SCCM 1810 upgrade. SCCM Client update settings include an update for SCCM client. You can upgrade your clients immediately. Or validate this client in pre-production collection before you upgrade all your SCCM clients.

I would recommend validating the client version with pre-production collection devices before upgrading the SCCM 1810 client package to all your clients directly.

Upgrade without validating

If you select the SCCM client upgrade without validating option, this overwrites your current SCCM client package with the new SCCM client update. All new client installations and client upgrades use this new client update.

Validate in Pre-production collection

If you select the “Validate in Pre-production collection” option, then you will get an option to validate the new client update on members of pre-production collection while you keep your production client package intact. Later once you are confident with the new client package, you can overwrite the production package using Client Update Options in the Updates and Servicing node of the SCCM console.

Client Update Settings page configuration - SCCM 2002 Installation Step by Step Guide
Client Update Settings page configuration – SCCM 2002 Installation Step by Step Guide

NOTE! – More details about SCCM Client Upgrade options “SCCM Client Upgrade Promote Pre-Production Client to Production.”

  • Click on “I accept these License Terms and Privacy Statement
  • Click on NEXT button to continue
License Agreement - SCCM 2002 Installation Step by Step Guide
License Agreement – SCCM 2002 Installation Step by Step Guide
  • Click on Close to continue to the installation process of 2002
Close - Start the Installation Process - SCCM 2002 Installation Step by Step Guide
Close – Start the Installation Process – SCCM 2002 Installation Step by Step Guide

Installation Progress

Once you complete the Configuration Manager update wizard, the SCCM 2002 upgrade process will kick start. And the updates and servicing node in the ConfigMgr console will show that the update is in installing state.

You can start monitoring ConfigMgr 2002 upgrade from this stage.

  • You can click on a link “Show Status” from related objects. 
  • Show status will show you the details about the installation status in monitoring workspace.

I would recommend following the below screenshot to see the real-time updates of the SCCM upgrade. Let’s monitor the installation Monitoring workspace:

  • Navigate to – \Monitoring\Overview\Updates and Servicing Status
Updates and Servicing Status - SCCM 2002 Installation Step by Step Guide
Updates and Servicing Status – SCCM 2002 Installation Step by Step Guide

Finish – SCCM 2002 Installation

The following sections have been successfully completed as part of the 2002 installation.

  • Download – Completed
  • Replication – Completed
  • Prerequisite Check – Completed with some warnings
  • Installation – Completed
  • Post Installation – Completed
Finish - SCCM 2002 Installation - SCCM 2002 Installation Step by Step Guide
Finish – SCCM 2002 Installation – SCCM 2002 Installation Step by Step Guide

Console Upgrade to 2002 Version

The last step of the ConfigMgr 2002 installation is by upgrading the console of Primary servers & CAS server.

You need to make sure all your remote SCCM console installations are upgraded to the latest version. This is not very critical if your remote SCCM console is already running with the n-1 version  (where n = 2002 in this scenario).

But, if your remote SCCM console is not n-1 then, you need to make sure your console is updated otherwise you won’t be able to connect to the SCCM console.

SCCM 2002 Version Numbers

Let’s see what are the Configuration Manager version numbers.

  • Site Server Full Version Number – 5.00.8968.1000
  • Site Server Version Number – 5.0.8968.1000
  • Console Version Number – 5.2002.1083.1700
  • Client Version Number – 5.00.8968.1008

Resource