SCCM Hotfix Installation Guide

In this video guide, you would be able to understand how to install SCCM hotfix on your SCCM CAS, primary, and secondary servers. For all the SCCM upgrades and updates, you need to follow the Top-Down approach.

What is the Top-Down SCCM Update Approach?

You have to update the top level (SCCM tier 1 – Primary or CAS) server in your SCCM environment, and then you can go down to SCCM Tier 2 (Primary or Secondary) and Tier 3 (Secondary) server upgrades or updates. The last stage of SCCM hotfix/s installation is on the SCCM client side.

I have explained the SCCM hotfix/s installation steps in the following post “SCCM 1810 Rollup Hotfix Installation Guide“. I would recommend reading that to get more details about how to initiate or install the SCCM hotfix/s or roll-up update from SCCM console.

SCCM Hotfix Installation Approach?

  1. Install SCCM Hotfixes on the CAS server if you have CAS otherwise go to step 2.
  2. Install SCCM Hotfixes on the SCCM Primary server and make sure the hotfix got downloaded automatically & installed successfully.
  3. Install SCCM Hotfixes on the secondary server
  4. Install SCCM Hotfixes on the client machine.

SCCM Hotfixes Installation Issues?

How to tackle the SCCM troubleshooting related issues during the hotfix installation? I have a couple of other posts which can help you to troubleshoot with different issues with SCCM updates and Servicing.

Advantages of SCCM Hotfixes Download and Install within Console?

SCCM uses an in-console service method called Updates and Servicing. This in-console method makes it easy to find and install recommended updates for your SCCM infrastructure.

Out-of-band updates such as hotfixes supplement In-console servicing. The out-of-band updates (SCCM Hotfix/s) are intended for customers who need to resolve issues that might be specific to their environment.

SCCM OSD Front End Tools and User Driven Installation

Microsoft recently released latest MDT version 8456, and I have posted about more details in the post here. I have attached the MDT 8456 installation video in this post. Also, I will try to help you with some SCCM OSD front end tool like User-Driven Installation (UDI).

What is UDI? User Driven Installation

User Driven Installation (UDI) helps to simplify the Windows Operating System Deployment. The UDI is an SCCM OSD front end tool which can be used with SCCM. The UDI is part of the Microsoft Deployment Toolkit (MDT).

SCCM OSD Front End Tool?

UDI is very simple SCCM OSD Front end tool which can be used to provide end users and IT admins (helpdesk) to set options like regional settings, time zone, and OU details, etc…

You can also provide more security options like an administrative password to kick start the SCCM OSD process. So the UDI will help you to secure the OSD process in a scenario you are not performing the OSD process within your office premises, etc..


The UDI design wizard is part of MDT installation as I explained in the above video. UDI wizard can be integrated as your SCCM OSD front end tool for end users or help desk support (desk support) members of the team.

In most of the organizations help desk support might not have SCCM console access to setup different ODS images by assigning devices into the different collection and task sequences. Hence the UDI wizard will act as a “basic” SCCM front end tool.

Remember you might not get many rich features in UDI (out of the box). But, it’s easy to customize options add new features into UDI using custom XML files.

How to Use UDI for your SCCM Task Sequences?

First of all, you need to install MDT on the device where you have installed SCCM console. Once the MDT is installed, you can launch “UDI Wizard Designer tool” to start building user custom front end screens for SCCM OSD.

Before you begin creating your own custom wizard pages and SCCM OSD UDI wizard page editors, perform the following steps to prepare the UDI development environment:

  1. Prepare the UDI development environment prerequisites as described in Prepare the UDI Development Environment Prerequisites.
  2. Configure the UDI development environment as described in Configure the UDI Development Environment.
  3. Verify that the UDI development environment is configured correctly as described in Verify the UDI Development Environment.


SCCM Client Versions Production and Preview Releases

In this post, you will see the details of SCCM client version numbers of SCCM CB production releases. I have covered all the client versions from SCCM CB 1511 release till date.

[Related PostsSCCM Full Version Numbers Build Number Client Version and SCCM Build Numbers – How to Check SCCM Build Number]

I’ll try to keep the list of SCCM client versions up-to-date. Let me know if you know some client versions mentioned in the below table are incorrect or wrong.

List of Production SCCM Client Version

The following table will give you the details of SCCM client version.

SCCM Release Version SCCM Client Version DetailsDescription & SCCM What’s New Links
SCCM 1902 5.00.8790. 1025SCCM 1902 KB4500571
SCCM 19025.00.8790.1007SCCM 1902 Video Guide
SCCM 1810 5.00.8740.1042 SCCM 1810 Rollup Update 2
SCCM 1810 5.00.8740.1012 /
SCCM CB 1810 – KB4486457
SCCM CB 1810 5.00.8740.1012Slow Ring What’s New in SCCM CB 1810
SCCM CB 1810 5.00.8740.1004First Wave Update – SCCM CB 1810 – KB4477084
SCCM CB 1810 5.00.8740.1003Fast Ring – What’s New in SCCM CB 1810
SCCM CB 1806 5.00.8692.1509SCCM CB 1806 – KB4462978
SCCM CB 1806 5.00.8692.1505SCCM CB 1806 – KB4465865
SCCM CB 1806 5.00.8692.1010SCCM CB 1806 – KB4459354
SCCM CB 1806 5.00.8692.1008/5.00.8692.1009SCCM CB 1806 – KB4346645
SCCM CB 1806 5.00.8692.1007Slow Ring SCCM CB 1806
SCCM CB 1806 5.00.8692.1003Fast Ring – What’s new in SCCM CB 1806
SCCM CB 1802 5.0.8634.1815SCCM CB 1802 – KB4342419
SCCM CB 1802 5.00.8634.1014SCCM CB 1802 – KB4339794
SCCM CB 1802 5.00.8634.1013SCCM CB 1802 – KB4163547
SCCM CB 1802 5.00.8634.1013SCCM CB 1802 – KB4132447
SCCM CB 1802 5.00.8634.1010/5.00.8634.1011Baseline Version SCCM CB 1802
SCCM CB 1802 5.00.8634.1009?KB4295281 – SCCM CB 1802 – KB4295281
SCCM CB 1802 5.00.8634.1007Fast Ring – What’s New in SCCM CB 1802
SCCM CB 1710 5.00.8577.1115SCCM CB 1710 – KB4086143
SCCM CB 1710 5.00.8577.1111SCCM CB 1710 – KB4088970
SCCM CB 1710 5.00.8577.1108SCCM CB 1710 – KB4057517
SCCM CB 1710 5.00.8577.1000What’s New in SCCM CB 1710
SCCM CB 1706 5.00.8540.1611SCCM CB 1706 – KB4042949
SCCM CB 1706 5.00.8540.1007SCCM CB 1706 – KB4039380
SCCM CB 1706 5.00.8540.1005SCCM CB 1706 – KB4039380
SCCM CB 1706 5.00.8540.1000What’s New in SCCM CB 1706
SCCM CB 1702 5.00.8498.1711SCCM CB 1702 KB4019926
SCCM CB 1702 5.00.8498.1008SCCM CB 1702 KB4018732
SCCM CB 1702  5.00.8498.1000/5.00.8498.1007What’s New in SCCM CB 1702
SCCM CB 1610 5.00.8458.1526?SCCM CB 1610 KB4016483
SCCM CB 1610 5.00.8458.1520SCCM CB 1610 KB4010155
SCCM CB 1610 5.00.8458.1009SCCM CB 1610 KB3214042
SCCM CB 1610 5.00.8458.1007SCCM CB 1610 KB3209501
SCCM CB 1610 5.00.8458.1000What’s New in SCCM CB 1610
SCCM CB 1606 NA?SCCM CB 1606 KB3202796
SCCM CB 1606 NA?SCCM CB 1606 KB3192616
SCCM CB 1606 5.00.8412.1307SCCM CB 1606 KB3186654
SCCM CB 1606 5.00.8412.1205SCCM CB 1606 KB3184153
SCCM CB 1606 5.00.8412.1204/5.0.8412.1207SCCM CB 1606 KB3180992
SCCM CB 1606 5.00.8412.1000/5.00.8412.1006What’s New in SCCM CB 1606
SCCM CB 1602 5.00.8355.1307SCCM CB 1602 KB3174008
SCCM CB 1602 5.00.8355.1306SCCM CB 1602 KB3155482
SCCM CB 16025.00.8355.1000What’s new in SCCM CB 1602
SCCM CB 1511 NA?SCCM CB 1511 KB3163344
SCCM CB 1511 5.00.8325.1110SCCM CB 1511 KB3122677
SCCM CB 1511 5.00.8325.1104SCCM CB 1511 KB3118485
SCCM CB 15115.00.8325.1000What’s new in SCCM CB 1511

How to Check the SCCM Client Version Number?

The best way is to check the SCCM client version from the SCCM client machine itself. Follow the steps:

  • Go to Control Panel and Search for “Configuration Manager” applet
  • Double click on Configuration Manager applet
  • In the General Tab, you would be able to see the SCCM client version number

SCCM Client Version from SCCM Console?

Another option is to check the SCCM client version from SCCM console, assets and compliance – Devices or from a particular collection.

Production Client Version on SCCM Site?

You can also check the latest SCCM client version number from the SCCM console:

  • SCCM console -> Administration\Overview\Site Configuration\Sites
  • Select the primary site server and click on Hierarchy settings 
  • Click on Client Upgrade tab
  • Check the production SCCM client version

SCCM Client Version Details for SCCM Technical Preview

SCCM Client Version NumbersWhat’s New of SCCM Technical Preview Version Document
5.00.8842.1001 SCCM 1906 Technical Preview
5.00.8827.1000SCCM 1905 Technical Preview
5.00.8817.1000SCCM 1904 Technical Preview
5.00.8800.1000SCCM 1903 Technical Preview
5.00.8787.1000 What’s New in SCCM 1902.2 Preview
5.00.8782.1000 SCCM Client Version of 1902 Preview
5.00.8772.1000SCCM Client Version of 1901
5.00.8756.1000SCCM Client Version of 1812
5.00.8748.1000SCCM Client version of 1811
5.00.8735.1000SCCM Client version of 1810.2
5.00.8729.1000SCCM Client Version of 1810
5.00.8717.1000SCCM Client Version of 1809
5.00.8707.1000SCCM Client Version of 1808
5.00.8700.1000SCCM Client Version of 1807
5.00.8685.1000What’s New in SCCM Client Version of 1806.2
5.00.8692.1000What’s New in SCCM Client Version of 1806
5.00.8659.1000What’s New in SCCM Client Version of 1805
5.00.8648.1000What’s New in SCCM Client Version of 1804
5.00.8636.1000What’s New in SCCM Client Version of 1803
5.00.8627.1000What’s SCCM 1802
5.00.8611.1000What’s SCCM 1801
5.00.8595.1000What’s SCCM 1712
5.00.8582.1000What’s SCCM 1711
5.00.8570.1000What’s SCCM 1710
5.00.8559.1000What’s SCCM 1709
5.00.8542.1000What’s New in SCCM 1708
5.00.8549.1000What’s SCCM 1707
5.008533.1000What’s SCCM 1706
5.00.8525.1000What’s SCCM 1705
5.00.8514.1000What’s SCCM 1704
5.00.8506.1000What’s SCCM 1703
5.00.8496.1000What’s SCCM 1702
5.00.8482.1000What’s SCCM 1701
5.00.8465.1000What’s SCCM 1612
5.00.8471.1000What’s SCCM 1611
5.00.8455.1000What’s SCCM 1610
5.00.8445.1000What’s SCCM 1609
5.00.8433.1000What’s SCCM 1608
5.00.8426.1000What’s SCCM 1607
5.00.8410.1000What’s SCCM 1606
5.00.8396.1000What’s SCCM 1605
5.00.8385.1000What’s SCCM 1604
5.00.8372.1000What’s SCCM 1603
5.00.8360.1000What’s SCCM 1602
5.00.8347.1000What’s SCCM 1601
5.00.8336.1000What’s SCCM 1512
5.00.8325.1000What’s SCCM 1511
5.00.8315.1000What’s SCCM 1510
5.00.8299.1000What’s SCCM 1509
5.00.8287.1000What’s SCCM TP V3
5.00.8271.1000What’s SCCM TP V2
5.00.8239.1000What’s SCCM TP V1


Intune Tenant Status Page – How to Get the Release Version of Intune Tenant?

In this post, you will learn how to get the details of your Intune version of your tenant. Many times I was wondering why I didn’t had the newer features in my Intune console? Microsoft mentioned in the blog post that these features are released. But those new Intune features are not available in my Intune? What is Intune Tenant Status blade?

Update – Service Health section doesn’t have anything to do with the cases raised by a customer, it’s any service incidents/outages active on that tenant.

[Related TopicList of Intune Versions since 2009] Coming Soon

You can get better answers to all the above questions related to Intune new features and versions in the new Intune Status page.

Intune Version Details – Where in Intune console?

  • Login to Azure Portal –
  • Navigate to Intune blade
  • Click on Intune > Tenant Status
  • Intune Tenant Status blade – Tenant Details section will give you the following details
    • Tenant Name – [email protected]
    • Tenant Location – Asia Pacific 0201
    • MDM Authority – Microsoft Intune
    • Account Status -Active
    • Service Release – 1812
    • Total Enrolled Devices – 1000?
    • Total Licensed Users – 4000?
    • Total Intune Licenses – 6000?
  • Intune Tenant Status blade -> Connector Status section will give you the following details
    • Header Details – Connector Status – 0 unhealthy
    • Status – Connector Name – Time Stamp
      • Not Enabled – APNS Expiry Date – 08‎-‎02‎-‎2019‎ ‎11‎:‎20‎:‎06
      • Healthy – DEP Last Sync Date – 08‎-‎02‎-‎2019‎ ‎11‎:‎20‎:‎06
      • Warning – VPP Last Sync Date – 07-‎02‎-‎2019‎ ‎1‎:‎23‎:‎12
      • Not Enabled – Managed Google Play App Sync – N/A
      • Healthy – Microsoft Auto Pilot Last Sync Date – 08‎-‎02‎-‎2019‎ ‎11‎:‎20‎:‎06
  • Intune Tenant Status blade -> Intune Service Health section will give you the following details
    • Intune Service Health – 0 total
      • Status – ID – Title – User Impact – Start Time – Updated
      • No active Intune incidents or advisories
    • Intune Service Health – 0 total
      • You don’t have permissions to see this. Click to add your account to the appropriate role in to gain access
      • Status – ID – Title – User Impact – Start Time – Updated
      • See past Incidents/Advisories
  • Intune Tenant Status blade -> Intune News section will give you the following details
    • Intune News – 0 active
      • You don’t have permissions to see this. Click to add your account to the appropriate role in to gain access
      • Act By – Category – Message Title – Published – Message ID
Intune Tenant Status Page
Intune Tenant Status Page

Access Issues – Intune Tenant Status

Intune Blade Access

Do you have access issues with Intune tenant status? You need to have related access to Intune blade. More details about Intune RBAC blog post.

Intune Service Health Access

You need to have following access to review or check whether you have appropriate access. You should have Service Administrator or global administrator access to check Intune Service Health section. (Intune Tenant Status)

  • To assign these permissions, sign in to the Microsoft 365 admin center with Global Administrator permissions.
  • Select Users > Active Users, and then select the account that requires access.
  • Select Edit for Roles, select Service Administrator or Global Administrator
  • Save your edit to assign the permissions.

Intune News Access

View Intune news communications from the Intune service team, you need to have additional permissions. Otherwise, you will get access denied errors as you can see below.

You don’t have permissions to see this. Click to add your account to the appropriate role in to gain access.

To view information for Intune News details, your user account must have the Global Administrator or Service Administrator role in AAD. Otherwise, you need be assigned the Message Center reader role in the Office Admin portal.

  • Sign in to the Microsoft 365 admin center with administrator permissions.
  • Select Users > Active Users, and then select the account that requires access.
  • Select Edit for Roles, select Teams Communications Administrator,
  • Save your edit to assign the permissions.


SCCM MSIX Application Deployment Tutorial – Video

In this video, you will learn how to create, deploy, and install MSIX automatically with SCCM. SCCM application deployment guide is here to help you understand end to end application deployment process. As an example, I have taken 7Zip.MSIX application deployment in this video tutorial.

In the following steps, you will be able to learn about the high-level steps about SCCM application creation, deployment, and automatic installation on Windows 10 devices.

SCCM Application Deployment Process

  • Copy the SCCM application source files to Package Source Folder ( UNC path).
  • Identify the target users you want to deploy the application via SCCM.
  • Document the way you want to deployment application (Required or Available).
  • Document the application installation method – Silent or interactive (99% of the apps are deployed using silent switch in my experience).
  • Identify the command line switches which you want to use for the SCCM application Deployment.
  • Or You can also use automation methods to complete SCCM ConfigMgr application deployment life cycle.
  • Open the latest version of SCCM console with appropriate access (SCCM RBAC).
  • Navigate to SCCM Console – Software Library – Application
  • Click on Application and create a New Application
  • Follow select the Application type you want to create. This selection depends on the application source you have. Depending on Application source, select any of the following application type (MSI, APPX, EXE, MSIX, AppV, etc).
  • If it’s MSI and if the application MSI is developed as per the best industry practices, SCCM will automatically fetch the details from MSI and it will create the SCCM application.
  • Once SCCM application is created, make sure that the content of the application is distributed to the SCCM DPs or Cloud DPs.
  • Create new SCCM Application Deployment and select the targeted collections. Best practices of using collections are explained in my previous blog post here.
  • Depending on the Client policy setting and schedule, the SCCM application deployment will happen on the client machines.
  • The client machines shall download the SCCM application content from DP or peer cache or branch cache depending on the configuration.
  • Or there are option to run the Apps from DP or stream the App-V application from DP.
  • Do you find issues with SCCM Application deployments? You can refer to SCCM log files and troubleshooting tips mentioned in my previous post. The following SCCM deployment issues cab be troubleshooted.
    • The users are not able to get the application?
    • The SCCM application is not available in Software Center
    • SCCM application download failed?
    • SCCM application installing stuck while installing stage?
    • SCCM application got stuck in downloading phase?


SCCM Application Deployment

Change Multi-Factor Authentication Phone Number

In this video, you will learn how to change multi-factor authentication phone number. This video will learn to change multi-factor authentication phone number from portal.

How to Setup Multi-Factor Authentication Phone?

Before enabling Azure Multi-Factor Authentication, your organization must determine what verification options they allow. For the purpose of this exercise, you enable call to phone and text message to phone as they are generic options that most are able to use.

More information regarding authentication methods, and their usage, can be found in the article, What are authentication methods?

  • Browse to Azure Active Directory, Users, Multi-Factor Authentication.
  • In the new tab that opens browse to service settings.
  • Under verification options, check all of the boxes for methods available to users.
  • Click on Save.
  • Close the service settings tab.

Change Azure MFA Authentication Phone Number

Change MFA Authentication Phone Number from MyApps Portal. In this video you will learn how to change #AzureAuthentication Phone Number with end users access! #MFA Multi Factor Authentication Phone Number. More details

AzureADMFA #Azure #ChangeMFAPhone #HowToGuide


More Blog posts related to SCCM/Intune/Windows 10/Hyper-V/Cloud/IT Pro/Azure –

Learn SCCM Read

Learn Intune Read –
Learn Windows 10 Read –

Learn Hyper-V Read –

Learn About Cloud Read –

Learn about Azure Read –

Learn About IT Pros Events –

Learn about me –

HyperVVideos #Hyper_V #HyperVBackup #ITProVideos #ITtraining #HowToManageDevices #AzureVideos

Learn about How to Manage Devices via Video Tutorials –

Troubleshooting Plantronics Voyager 4220 Series – BT600

I had an issue with Plantronics Voyager 4220 issue. Plantronics BT600 device was giving trouble connecting to Windows 10 device. In the above video you will see how to upgrade the Firmware of Plantronics Voyager 4220 series + BT600. In the below blog post, you will see how to troubleshoot on Plantronics Voyager 4220 Series – BT600.

Upgrade the Firmware?

You need to install an application called Plantronics Hub from on your Windows 10 device where your BT600 is connected. Firmware Update – How to Upgrade Plantronic Voyager 4220. Do you think firmware update will fix Plantronics Voyager 4220 issue? No I don’t think so.

Download Plantronics Hub for Windows10

Checkout the following plantronics website to download Plantronics hub application. Once downloaded, you can install it on your Windows 10 device.

Plantronics Voyager 4220 Issue

In this section, you will see how to Troubleshoot and fix Plantronics Voyager 4220 Series related issues with BT600 device. The device BT600 and
Plantronics Voyager 4220 issue is that those are not getting connected with Windows 10 device. The sound and mic are not working. Issues of Plantronics Voyager 4220 Series headphone and mic + BT600?

Do you think this is a driver issue? Plantronics Voyager 4220 Series + BT600 Driver issues with Windows 10? No I don’t think it would be a driver issue as per Plantronics, there is NO driver required for Plantronics Voyager 4220 Series + BT600 headphone and mic. The drivers are already there in Windows 10 as out of box. How to fix Plantronics Voyager 4220 Series + BT600 connectivity issues?

Fix Plantronics Voyager 4220

  1. You need to make sure Plantronics Voyager 4220 headphone + mic is paired with BT600 device before you connect to WIndows 10 device.
  2. Don’t connect Plantronics Voyager 4220 headphone and mic directly to Windows 10 device via bluetooth. Always connect
    plantronics Voyager 4220 headphone and mic through BT600 device. Otherwise it won’t give you best performance.
  3. Even if step#1 and #2 are not helping you, then you need to make sure – you have followed the below troubleshooting steps.
  4. Navigate to Control Panel\Hardware and Sound\Devices and Printers and find out BT600 device.
  5. Most probably there will be an Yellow Exclamation mark (!) on the Plantronics BT600.
  6. Right click on the device Plantronics BT600 device and click on Troubleshooting.
  7. Go through the Windows 10 troubleshooting wizard as mentioned in the above step. This will surely fix plantronics Voyager 4220 issue
  8. WIndows 10 will identify the problem or issue with Plantronics BT600 device (BT600 comes with Plantronics Voyager 4220).
  9. Windows 10 will ask you to click on FIX the issue button after identifying the issue with Plantronics Voyager 4220.
  10. Click on FIX button to resolve the issues related to Plantronics BT600 device.
  11. After fixing the issue Windows 10 may ask to restart the Windows 10 device (#Plantronics #BT600 device).
  12. Restart Windows 10 device which is connected BT 600 device (with Plantronics Voyager 4220).
  13. The Windows 10 restart fixed the issue #Plantronics #BT600 device.
  14. I was able to connect #Plantronics #BT600 device with Plantronics Voyager 4220 headphone + mic. ( Plantronics Voyager 4220 issue fixed by now?)
  15. Plantronics Voyager 4220 headphone + mic worked well with iOS/iPhone and Android tablets as well.


  • More details about Plantronics Voyager 4220 – BT600 – here
  • Windows 10 Backup and Restore – Guide

List of Online SCCM Intune Communities – 2019

Happy new year 2019 and wishing you all blessed year 2019! I would like to through back the list of Online SCCM Intune communities. Hopefully, these communities will help you to keep you updated with SCCM and Intune.

#Throwback A complete List of Online SCCM Intune Communities which you should be part of – in 2019 #MSIntune #Intune #SCCM #ConfigMgr #ITPros #MVPBuzz

I thought of giving the details of all the online IT Pro communities related to SCCM, Intune, Azure, and Windows. I’m going to provide all the online IT Pro communities. The following is the list of Online SCCM Intune IT Pro Communities for 2019.

Online SCCM Intune Communities - SCCM Intune Online IT Pro 2019 Communities
Online SCCM Intune Communities
Technet Forum

Online SCCM Intune Communities

Online SCCM Intune Communities -Online SCCM Intune Community
SCCM Intune Online Community 2019

SCCM Intune Online IT Pro Communities of 2019 – SCCM Community Groups – Facebook Community Groups – Linkedin Community Groups. Online Community Online IT Community More Details below. I would recommend joining the following online communities. Online SCCM Intune Communities?


Why Should You Download & Install Windows 10 SDK & Tools

SCCM Support Center Tool Video Review & Remote Client Support

In this video post, you will get video experience of Configuration Manager support center tool. SCCM Support center tool is a tool which will help you to troubleshoot client health for SCCM admins. Remote SCCM client support center tool helps you to connect client PowerShell.

[Related PostHow to Use Support Center Tool and SCCM Logs and Quick Tips to Read Logs]

SCCM Server Troubleshooting Tools

If you are looking for a solution where you want to troubleshoot SCCM server stuff, then I would recommend reading the following post SCCM Server Side Troubleshooting Tool Kit Guide. SCCM support center tool can be used for log viewing at the server side as well.

Remote SCCM Client Support Center Tool

SCCM support center tool helps to connect remotely to SCCM client devices. This support center tool when you have an appropriate communication channel opened between the remote client and the machine from where you are running the support center tool.

Support Center helps to reduce the challenges when troubleshooting SCCM client devices. Previously, when working with support to address an issue with SCCM clients, you would need to manually collect log files and other information to help troubleshoot the problem. It was easy to forget a crucial log file accidentally, causing additional headaches for you and the support personnel who you’re working with.

  • Use SCCM Support Center to streamline the support experience. It helps you:
    • Create a troubleshooting bundle (.zip file) that contains the SCCM client log files. You then have a single file to send to support personnel.
    • View SCCM client log files, certificates, registry settings, debug dumps, client policies.
    • Real-time diagnostic of inventory (replaces ContentSpy), policy (replaces PolicySpy), and client cache.

PowerShell SCCM Support Center

There are three PowerShell commandlets supported by SCCM Support Center or Configuration Manager Support Center. You can use these powershell cmdlets to create a remote connection to another SCCM client, to configure the data collection options, and to start data collection.

Get-CMDataCollectionTasksGets the data collection tasks that apply to a SCCM client computer.
Invoke-CMDataCollectionStarts collecting data for a SCCM client computer.
New-CMMachineConnectionCreates a connection to a SCCM client computer.
SCCM Support Center Tool
SCCM Support Center


SCCM Integration with Azure Log Analytics with OMS Connector

You can connect your SCCM environment to Azure Log Analytics (OMS) to sync device collection data. The SCCM OMS connection helps to create reference the device collections in Log Analytics and Azure Automation. In this video tutorial, you will see how to configure SCCM Azure Log Analytics.

SCCM Azure Log Analytics

Step by Step SCCM Azure Log Analytics Integration

With the above video guide, I will help you to integrate SCCM and Azure Log Analytics. The following steps will help you to understand the process of connecting SCCM with OMS (Azure Log Analytics).

Something you need to take care before integrating SCCM Azure Log Analytics (SCCM and OMS). Microsoft announced Desktop Analytics integration with SCCM. So make sure the roadmap of OMS connection with SCCM is still required or not.  

  • Login to the Azure portal with appropriate access rights to integrate SCCM with Log Analytics.
  • In the Azure portal, register SCCM as a Web Application and/or Web API app, and ensure that you have the client ID and client secret key from the registration from Azure AD. See Use portal to create an Azure AD application and service principal that can access resources for detailed information about how to accomplish this step.
  • In the Azure portal, grant SCCM (the registered web app) with permission to access Log Analytics.
  • In SCCM console, add a connection using the Add OMS Connection Wizard.
  • In SCCM, update the connection properties if the password or client secret key ever expires or is lost.
  • Download and install the Microsoft Monitoring Agent on the computer running the SCCM service connection point site system role. The agent sends SCCM data to the Log Analytics workspace.
  • In Log Analytics, import collections from SCCM as computer groups.
  • In Log Analytics, view data from SCCM as computer groups.
  • You can read more about connecting SCCM to Log Analytics at Sync data from SCCM to the Microsoft Log Analytics.