MECM SCCM 1910 Update Step by Step Guide

MECM is the new name of SCCM. In this post, you will see how to upgrade the SCCM infra to 1910 version. Let’s see SCCM 1910 Update Step by Step details.

Related Post What is New in MECM SCCM 1910 Features a Walkthrough

MECM 1910 Released
MECM 1910 Released Microsoft Docs here

How to Download SCCM 1910?

Don’t you see the SCCM 1910 production version in your console? How did I get the SCCM 1910 production version? There is no secret here.

Steps to Follow

  • You can download the PowerShell Script from Microsoft ( these instructions on how to use the PowerShell script  )
  • Run the Script with the account which has Full Admin access
  • Make sure you have successfully run the script
  • SCCM 1910 is Generally Available
  • Open the SCCM console and click Check updates as you can see in the below screenshot
MECM 1910 Released
MECM 1910 Released

Check out Microsoft’s Announcement about the 1910 release. MECM 1910 Fast Ring (opt-in version) now. This version of MECM is not generally available for all applicable SCCM Infra.

MECM 1910 Applicability Checks

With each version of SCCM, there will be an SQL applicability script that will check whether this particular update 1910 should be made available or not.

I have a blog post about this applicability script and the logic of the SQL script in detail. More details “SCCM Update is Not Visible in Console – Here is the Reason.”

SCCM 1910 Applicability Check - SCCM 1910 Update
SCCM 1910 Applicability Check – SCCM 1910 Update

Prerequisites of 1910 Version

As I mentioned above, the MECM 1910 production version will be available within the SCCM console after you run the PowerShell command and your SCCM site meet the following conditions:

  1. If your MECM CB version is SCCM 1810 or SCCM 1902, or SCCM 1906 (Read More details about SCCM Life Cycle)
  2. If your MECM CB version has online Service Connection Point

NOTE! – Make sure you have gone through best practice check list before starting the upgrade.

More Details

Update 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 1910 Download stuck and upgrade issues here and here.

FIX SCCM Updates Stuck in Downloading State & CM Update Reset Tool Fixes SCCM CB Update Download Issue

Microsoft Doc ➡

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

SCCM 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 1910 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 –

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

SCCM CB Prerequisite Checks - SCCM 1910 Prerequisites - SCCM 1910 Update
SCCM 1910 Prerequisites – SCCM 1910 Update

Install Update Pack

Once the prerequisite checks completed successfully, you can start the installation or update of MECM 1910.

  • Select Configuration Manager 1910 update
  • Click on Install Update Pack to start the installation wizard
Install Update Pack
Install Update Pack
  • Features Included in Update Pack
  • Select the features you want to enable after the upgrades
    • Bitlocker Management
  • Click on Next to continue
 Bitlocker Management SCCM 1910 Update
Bitlocker Management – SCCM 1910 Update
  • Client Update Settings
    • Upgrade without validating
    • Validate in pre production collection
  • Click NEXT button to continue
SCCM 1902 Client Upgrade Options Promote Pre-Production Client - SCCM 1910 Update
Direct Production Client Package Update – SCCM 1910 Update

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

1910 Update Completed Successfully

The installation or update process might take more than a couple of hours, depending on the size of the database and performance, etc..

1910 version update completed
1910 version update completed

Upgrade SCCM Remote Console

The 1910 update process completes the installation of the latest version of the console. The console installation on the site servers (primary and CAS) are straight forward.

More details about the remote console installations/updates are explained in the following post. More information, “Install SCCM Remote Console on a Windows 10 Machine.”

  • Version 1910
  • Console Version 5.1910.1067.1300
  • Site Version 5.0.8913.1000
Endpoint Configuration Manager v1910
Endpoint Configuration Manager v1910

Client and Server Version

Let’s check the client and server versions of 1910.

  • Version 1910
  • Full Version 5.00.8913.1000
  • Client Version 5.00.8913.1006
1910 Full Version Client Version
1910 Full Version Client Version

Pre-Released Features

Following are the pre-release features of 1910 version!

Pre-Released Features - SCCM 1910 Update
Pre-Released Features – SCCM 1910 Update

New Features of 1910

I have explained all the new features in the following blog post. More details “What is New in MECM SCCM 1910 Features a Walkthrough.”

Resources – SCCM 1910 Update

How to Publish RDS Remote Apps with PowerShell Commands

Video tutorial to help publish RDS Remote Apps (RDS Remote Apps) with PowerShell commands. WVD Powershell module can be downloaded and installed from the PowerShell Gallery.

Related Posts – RDS Remote Apps

Following are the posts about publishing remote apps and life cycle management of remote apps. RDS Remote Apps:

Download the WVD PowerShell Module

You have to download Windows Virtual Desktop module using following commands or you can download it from PowerShell Gallery.

Install-Module -Name Microsoft.RDInfra.RDPowerShell 
Import-Module -Name Microsoft.RDInfra.RDPowerShell

Create New WVD RemoteApp Group

Here is the PowerShell command to create a new remote app group. The New-RdsAppGroup cmdlet creates a new app group within the specified host pool.

More details –

New-RdsRemoteApp (RDS Remote Apps)

Adds a WVD Remote App program to a WVD Remote App app group. This helps to publish of the remote application installed in a VM which is part of WVD host pool.

This command will fail if you try to publish a Remote App to a desktop app group.

More Details –

WVD RDS Remote Apps
RDS Remote Apps


The following PowerShell command called Get-RdsAppGroupUser cmdlet lists the users to a WVD RemoteApp group. This action shall give access to the specified app group.

More Details –


How to Manage Devices Day Bangalore IT Pro Event SCCM Intune Free Training Event

Hello All, Registration for “How to Manage Devices Day” is starting today 18th Nov 2019 11:00 AM IST. The is the IT FREE community event for Device management admins.


Register NOW ▶➡➡➡

Ticket Schedules

  1. Sales start on 18 Nov 2019 11:00 AM IST
  2. Sales start on 25 Nov 2019 11:00 AM IST
  3. Sales start on 2 Dec 2019 11:00 AM IST


Except big surprises at the end of the event!! More details coming soon. Keep looking at social media below:


I have been part of Bangalore IT Pro since 2015. Following are some of the examples:

This How to Manage Devices event is powered by PatchMyPc, 1E, and Microsoft.

When? & Where?

When ➡➡▶ Saturday 14th Dec 2019

Where ➡➡▶ Microsoft Prestige Ferns Galaxy, 6/18, Bellandur Gate Rd, Bellandur, Bengaluru, Karnataka 560103, India. Google Map!

Agenda – How to Manage Devices Day

Following are the agenda (we will keep on updating it)

Introduction House Keeping/Agenda for the day Anoop9:00 to 9:15
TBA9:15 to 10:00
Intune for SCCM Admins Anoop10:00 to 10:45
Tea Break 10:45 to 11:00
SCCM Troubleshooting TipsRajul11:00 to 11:45
Intune Enrollment Saurabh Sarkar11:45 to 12:30
Free Networking Lunch 12:30 to 1:30
TBA1:30 to 2:15
ESR + Autopilot Hybrid ScenarioVimal Das2:15 to 3:00
Tea Break 3:00 to 3:15
SCCM Bandwidth Enhancements OptionsGuru/Vimal3:15 to 4:00
Task Sequence TroubleshootingVishal Goyel4:00 to 4:45
Giveaways Quizzzzz?? 4:45 to 5:00

More details about speakers are &


Microsoft Ignite 2019 Overview from SCCM Intune Admin Perspective

In this video post you’re going to see an overview of Microsoft Ignite 2019 which was on last week. This video post is Microsoft ignite 2019 overview from SCCM and Intune admin perspective. This post is very high-level overview.


As an SCCM and into an admin my main focus area is obviously Microsoft endpoint manager in this video (SCCM Intune Admin Perspective).

If you want to have more deep level details of each subject, then I have 14 posts (more coming) which explain each topic in bit more details.

  • What are the changes in SCCM an Intune licensing model?
  • What are the changes in cloud attached strategies?
  • What are the changes in Intune reporting strategies?
  • What are the changes in SCCM Cloud Console strategies?
  • What are the changes in SCCM task sequence and Windows Autopilot?
  • What are the expectation about Microsoft endpoint manager?
  • What does Microsoft intelligent edge? (Which I don’t know)?

Ignite Coverage Posts

Ignite 2019 Takeaways from an SCCM and Intune Admin Perspective – Microsoft Endpoint Manager (MEM) – Microsoft Configuration Manger (MEMCM) & Microsoft Intune (MEMMI).

✔Microsoft Intune (MEMMI)
✔Microsoft Endpoint Manager (MEM)
✔Microsoft Configuration Manger (MEMCM)
✔Microsoft Endpoint Manager Administration Console (MEMAC)

SCCM Intune Admin Perspective
SCCM Intune Admin Perspective

▶Microsoft Endpoint Management SCCM Intune Windows Updates –
▶Microsoft Endpoint Manager is the future of SCCM Intune MEMMI MEMCM –
▶iOS Android macOS Mobile Enrollment Options with Intune –
▶Basics of Windows Dynamic Update Explained Update Management –
▶WVD End User Experience Availability Updates –
▶MSIX Updates from Ignite Reliability Network Disk-space –
▶Microsoft Learning Certification Exams Updates –
▶On-Prem WVD Options Azure Quantum Qualys Scan Integration –
▶Intune Reporting Strategies Advanced Reporting –
▶Intune Endpoint Security Policies Enhancements –
▶Intune Policy Sets Collection of Workflows –
▶Windows Autopilot Updates Timelines –
▶Microsoft Connected Cache Container Instances in Azure via Intune –
▶SCCM and Microsoft Connected Cache Integration –
▶Windows 10 Bandwidth Management DO Delivery Optimization with LEDBAT in LAN –

Resources (SCCM Intune Admin Perspective)

Intune Line Of Business Application Google Chrome Deployment

Let’s learn how to download and update Google Chrome using Microsoft Intune. I have explained the steps in the above video (Google Chrome Deployment).

Related Post SCCM Helps To Update Google Chrome 0-Day Patch & Intune Application Deployment Guide Google Chrome Browser

Introduction Google Chrome Deployment

Recently Google published a post about the latest vulnerabilities of Google Chrome. And they highlighted this as Zero- day Patch. 0-day patches are highly critical, and you need to update the browsers as soon as possible.

Let’s download the Patch or the latest version of Google MSI from Google server and follow the steps mentioned in the above video to deploy Chrome update to Windows 10 devices.

Create Intune Line of Business Application (LOB)

To create Intune line of business (LOB) application, you need to log into device management portal. Once you login to device management portal you can go to windows application and start creating Intune LOB application.

The creation of application is straightforward as I have shown in the video (Google Chrome Deployment options). I don’t think you have to worry about the application version shown Intune console. I don’t know how it is getting that MSI version details when we select the Google Chrome MSI.

Thoughts – If you check the MSI version of the properties of that MSI file and compare that with the version which shows in Intune portal, you will get confused. So, don’t worry about that at the moment. There could be some bug in Intune.

Upload Intune Line of Business Application

Once you save the Google Chrome application, Intune will start uploading the MSI 2 Microsoft cloud. This process it’s going to take same depending on your Internet speed and the size of the MSI.  

You can see the starters of the upload in intunes console itself.  You can see the percentage of upload do Intune in device management portal itself as you can see in the video (Google Chrome Deployment scenarios).

Thoughts – This % of upload notification is very useful instead of some gas works which we used to do in previous versions of Intune.

Deploy Intune Line of Business Application

Deployement is called assignment in Intune. I have explained How do assign an application like Google Chrome the 2 Azure Active Directory device group. There are different types of assignment types in Intune.

Similar to SCCM, required and available are 2 prominent options. Apart from these 2, you will have other option which is called available for all enrolled devices. This option will make the application available for all MDM enrolled devices.

Thoughts – If you select available for all enrolled devices, you are in turn removing the dependency of Azure AD assignments. I think this will help to improve the performance of Microsoft Intune in some way.

This will also help to reduce the workload for Azure Active Directory to analyze different groups different logics for dynamic groups etc similar to dynamic collections in SCM world.  I have used required option in this Chrome application deployement or assignment.


The Chrome update got installed on Windows 10 device as you can see below.

Google Chrome Deployment Windows 10
Google Chrome Deployment


SCCM Helps to Update Google Chrome 0-day Patch

Let’s check this video to know more about Google Chrome updates with SCCM 1910. I have used SCCM’s application model to deploy the updated version of Chrome in this video tutorial.

Related Post Deploy Google Chrome Update with SCCM Step by Step Guide 0-Day Bug


Google recently released a blog post revealing 0 day bug for their browser called Chrome. 0 day bug means you need to fix it as soon as possible or you need to update it as soon as possible. Otherwise, it will be a big risk for your organization where the previous versions of Chrome is running.

In this critical scenario, I’m trying to help SCCM admins to batch or update Google Chrome browser on the managed devices. There might be thousands of devices which they want to update. Manual updation or group policy based updation of Chrome it’s not the best practice full larger organizations.

Download Latest version of Chrome

You can download the latest version of Google Chrome MSI from Google’s enterprise portal for free. you don’t have to log into Google to download this version of Google Chrome.

SCCM Application Model

SCCM application model is the feature rich option to update Chrome for a large organization. If you are using SCCM for managing the devices in your enterprise, then you should use SCCM application model to update Google Chrome as described in the video.

I have gone through step by step documentation and explanation in the elbow video tutorial. I think the video will be helpful to you to update Chrome version for your thousands of devices.

SCCM application deployment

once the application is created For Google Chrome update, you can right click on that application and deploy this updated version of MSI to a collection of devices. This activity is also explained in the above video.

Windows 7 Windows 10 Devices

You can deploy Chrome application which you created in SCCM to Windows 7 and Windows 10 devices in your organization.

Automation Phased Deployments

I would recommend deploying this application using phased deployments in SCCM. The phased deployments in SCCM will help you to reduce the risks of large scale deployments.

In this scenario you would be able to deploy Chrome application update to pilot collection in the 1st phase. Depending upon the success rate of the first deployment SCCM will automatically take a decision to proceed or not to proceed with the Phase 2 of the deployment. this is called phased deployment in SCCM.

Google Chrome – Resource

How to Delete Azure AD Stale Device Records

In one of the recent blog posts, I shared step by step guide to Setup Automatic Intune Device Cleanup Rules. In this video post, you will be able to delete Azure AD stale device records (Old device records).

Introduction – Delete Azure AD Stale Devices

Microsoft announced the options to Delete Azure AD Stale Devices in session from Microsoft Ignite 2018. Microsoft helps IT Pro to keep device lifecycle issues by deleting the stale device records from Azure AD.

List of Azure AD Stale Device

Navigate to Azure AD -> Devices blade, you might be able to see a column called “Activity.” The “Activity” column entries will provide you the details of approximate last logon timestamp for a device.

Azure AD device attribute called ApproximateLastLogonTimestamp helps to delete Azure AD stale devices. I would recommend going through Microsoft documentation to have more details.

  • Connect-MsolService
  • Get-MsolDevice -all | select-object -Property Enabled, DeviceId, DisplayName, DeviceTrustType, ApproximateLastLogonTimestamp | export-csv C:\AzureAD_Stale_devicelist-summary.csv

Disable Azure AD Stale Device Records

Feel free to use your scripting skills to disable stale devices using the following command 🙂 I mean, if you want to disable all Azure AD obsolete devices, you can use scripting skills.

  • Disable-MsolDevice -DeviceId “b6ccb307-ba46-4f05-a22f-15938634ae45” -Force

Remove Azure AD Stale Device Records

Once the devices are disabled, you can remove Azure AD stale devices using the following command.

  • Remove-MsolDevice -DeviceId “b6ccb307-ba46-4f05-a22f-15938634ae45” -Force


SCCM Third Party Patching Fujitsu NotePad++ More

Third Party Patching is one of my favorite features as SCCM admin. I have had a chance to present live demo in a recent Webinar with Manage Engine. In this post, I will share the video recording of the webinar, which I did with Aravind Ekanath.


I have been testing SCCM third party patching feature since the 1806 version. It was a bit sketchy with the initial releases but got stabilized with the later technical preview versions of SCCM.

In Manage Engine’s webinar, I did a live demo:

  • How to add Third part custom catalog (Fujistu)
  • How to subscribe to Fujitsu’s catalog
  • How to Publish Content of Third Party software called NotePad++ from ManageEgnine’s paid catalog (blue to green journey 👍)

More Details

Here is the cheat sheet I had during the demo 🙂

  1. Enable 3rd Party update
  2. Certificate – Self signed Cert from SCCM
  3. Classifications (Updates) & Products
  4. Software Update – 3rd Software Update
  5. Subscribe to Catalog, Sync,
  6. Select the products and Sync
  7. Blue Icons and SYNC (optional) to Publish to Green Icon and sync
  8. Deploy !!

More detailed Video of Third Party Patching


Backup Your Intune Settings Using Script|MEM

In this video post you are going to learn how to take backup of your Intune settings into a word file automatically. Thomas Kur as an excellent GitHub repository with PowerShell scripts to help you. Backup Intune Settings using the scripts.


Intune settings documentation is important in many scenarios. you need to make sure that you have properly documented the settings within in tune console. this would be helpful for knowledge transfer and change management scenarios wait in your organization.

Also, in some cases, Intune settings documentation can help you to recover from some of the manual or human error in the real world scenarios.

The following settings are covered in Intune backup script

  • Configuration Policies
  • Compliance Policies
  • Device Enrollment Restrictions
  • Terms and Conditions
  • Applications (Only Assigned)
  • Application Protection Policies
  • AutoPilot Configuration
  • Enrollment Page Configuration
  • Apple Push Certificate
  • Apple VPP
  • Device Categories
  • Exchange Connector
  • Application Configuration
  • PowerShell Scripts
  • ADMX backed Configuration Profiles


you can download the scripts to backup Intune settings from GitHub. check out the following link to have more details.


Before downloading the script you need to make sure that the scripts are not saved with some special characters from GitHub. When I first downloaded the script from GitHub, there were special characters in the script.

NOTE! – Big shout out to Oliver who helped me to properly download and save the script from GitHub without any special characters.

I had showed how to save the scripts from GitHub in the above video. please refer to that before downloading Intune setting backup script.

Backup Intune Settings - Download Script
Download Script

Backup Intune Settings – Execution

You need to make sure that you have installed two of the following PowerShell modules in your system before running the script. Those PowerShell modules (Backup Intune Settings) are:

  • Install-Module Microsoft.Graph.Intune
  • Install-Module PSWord

Run the following command to build the documentation on Intune Settings.

Install-Module IntuneDocumentation
Invoke-IntuneDocumentation -FullDocumentationPath c:\temp\IntuneDoc.docx
Backup Intune Settings - Script Running
Script Running


The result of the backup Intune settings script is the word files which has all the details you require.

Backup Intune Settings  - Word File with Intune Settings
Backup Intune Settings – Word File with Intune Settings


Install SCCM Client Manually Using Command Line

In this video guide, you are going to see all about how to install SCCM client manually on Windows 10 machine. I’m going to use a command-line option to install SCCM Client on Windows 10 machine.


The SCCM client can be installed in different ways. There are many blogs about installing SCCM clients in different ways. This is one of the way to install SCCM clients manually on a Windows 10 machine for beginners.

SCCM clients can be installed using group policy, client push, software update options, imaging/task sequence etc… (more details below).

install SCCM client manually - Results
install SCCM client manually – Results

This manual installation of SCCM client on Windows 10 device I will provide you a more significant idea of how exactly SCCM client is being installed what the process is is behind it.

I would recommend installing the SCCM client manually if you are new to SCCM. And this post would be helpful to you with the same.

SCCM client Manual Installation

You can start the installation from CCMsetup.exe. The source files to CCMsetup.exe will be available in your primary server or CAS. You can copy it manually from primary server to Windows 10 device.

install SCCM client manually  - Source
install SCCM client manually – Source

Once you have copied it, you can start a command prompt with admin rights. Source Files ▶▶ \\<site server name>\SMS_<site code>\Client\

NOTE! – You must have administrator permissions to access the Manual SCCM client installation files.

Command Line which I used in the above video is :- CCMSetup.exe /Source:”C:\SCCM\Client” SMSSITECODE=TP4

Install SCCM Client Manually - Command Line
Install SCCM Client Manually – Command Line

Install SCCM Client Manually

When you select the command-line options to install the SCCM client manually, there are two (2) types of parameters:

  • CCMSetup.exe parameter
  • Client.msi Parameters

Install SCCM Client Manually – Command Line Parameters are mentioned below.

Install SCCM Client Manually - Command Line Parameters
Install SCCM Client Manually – Command Line Parameters

SCCM CCMSetup parameter

  • /mp:SMSMP01
  • /logon

SCCM Client.msi properties

  • Client.msi property
  • /source:
  • /retry:
  • /noservice
  • /service
  • /uninstall
  • /logon
  • /forcereboot
  • /BITSPriority:
  • /downloadtimeout:
  • /UsePKICert
  • /NoCRLCheck
  • /config:
  • /skipprereq:
  • /forceinstall
  • /ExcludeFeatures:

More About Install SCCM Client Manually

client installation parameters and properties –