Microsoft has released new version of in-console update 1910 for SCCM Current Branch. This is the first version of the new Microsoft Endpoint Configuration Manager, We can apply this update on sites that run version on 1806 or later.

In this post i will be implementing SCCM 1910 Upgrade as in-console update from SCCM 1906 version.

SCCM 1910 New Features

As part of the new features:

  • Configuration Manager is now part of Microsoft Endpoint Manager.
    • Configuration Manager
    • Intune
    • Desktop Analytics
    • Autopilot
  • Other features in the Device Management Admin Console
  • Deploy Microsoft Edge, version 77 and later
  • Search the task sequence editor
  • Copy and paste task sequence conditions
  • Task Sequence download on demand over the internet
  • Import a single index of an OS Upgrade package
  • Improved language support in task sequence
  • Office 365 ProPlus Pilot and Health Dashboard

SCCM 1910 Upgrade Prerequisites

  • Update 1910 for Configuration Manager current branch is available as an in-console update. There is no SCCM 1910 baseline version.
  • 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.

Get Configuration Manager 1910 Update in Console

In order to get the Configuration Manager 1910 Update in Console, Please follow the below link

Begin the installation

Once you complete enable early update process as per above link, We will be able to see “Configuration Manager 1910” under “Updates and Servicing”, running of script also starts executing the update which can be monitored through dmpdownloader.log and the location of update will be: <Installed Drive>\Microsoft Configuration Manager\EasySetupPayload\ <Filename.Cab>

It will initially download in cab format as per screenshot below, Once cab file is downloaded, it will extract the content with same folder. Original downloaded cab file will be deleted.

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

Once update is download, We will see the status as “Ready to Install” for “Configuration Manager 1910” .

Now Select “configuration Manager 1910” -Right Click and select “Run Prerequisite Check”.

Once Checking Prerequisites complete, Now Select “configuration Manager 1910” -Right Click and Run “Install Update Pack”.

This will initiate “Configuration Manager Updates Wizard”. Ignore the Prerequisite warnings and select next.

Under “Features included in update pack”, check boxes on the features you want to enable during the update

Next screen shows Client Update Settings, its always better to use option “Validate in pre-production collection” so that you can test new client agent on few systems before rolling out in production. Here i have selected “Upgrade without validating”

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

On the Summary tab, review your choices, click Next and close the wizard on the Completion tab. This will take some time to update SCCM.

Installation can be verified through cmupdate.log as well.

Once installation is done, and you try to open the SCCM console, this will ask you to update your console. Click ok to continue. New console version is 5.1910.1067.1600. which will uninstall old console version.

Downloading & installation of console can be verified through log file c:\ConfigMgrAdminUISetupVerbose.log

Once completed you can verify the site version and control version by clicking “About Configuration Manager”

Thank You!

Configuration Manager 1910 Update Not Available in Console

Recently Microsoft has released Configuration Manager update 1910 and It should take few weeks of time to reflect in the console. Until then we can either wait for the update to be globally available or we run the EnableEarlyUpdateRing 1910 script to enable fast ring for 1910 update package available in ConfigMgr Current Branch.

EnableEarlyUpdateRing 1910 script

Download the Powershell script from Technet . This script will allow us to enable fast Update-ring in ConfigMgr Current Branch.
On your SCCM server, run the PowerShell as administrator and run the script. Enter the site server name and script gets the update 1910 in console for you.

Before running the Script ,

After executing the Script , Configuration Manager update 1910 available to download in Console.

Windows 10 Deployment Using SCCM 1902 OSD Step by Step Guide

This guide provides step by step instructions to install PXE role, Creation of boot image, Creation of OS image, Creation of OSD task sequence and deploying Windows 10 OS via PXE boot on SCCM 1902 lab environment.

Enable SCCM PXE Role

First we need to prepare environment for configuration manager OSD. we have to create Network Access account in Active Directory and this account is used by the client to access the Configuration Manager Distribution point when booted under WinPE so make sure the account has the necessary permission for this action. Then we have to Enable PXE role on our SCCM server.

Follow the Below Steps to Enable PXE support,

Open the SCCM Console
Go to Administration / Site Configuration / Servers and Site System Roles
Select your distribution point and right-click on the Distribution point role on the bottom, select Properties

Select the PXE tab
Enable the Enable PXE support for Clients check-boxandanswer Yes when prompted about firewall ports (UDP ports 67, 68, 69 and 4011 )

Check the Allow this distribution point to respond to incoming PXE requests check box
Check the Enable unknown computer support check box
Ensure that the Respond to PXE request on all network interfaces is selected Click OK

Go to Monitoring / Distribution Status / Distribution Point Configuration Status
Click your distribution point on the top and select the Details tab on the bottom
We will see that the distribution point PXE settings has changed

BOOT Image Distribution

Here we are going to use the default SCCM boot image,
Open the SCCM Console, Go to Software Library / Operating Systems / Boot Images, Right-click Boot Image (X64) and distribute to DPs.

Add Operating System Image

Launch the Configuration Manager console, click on Software Library, click Operating Systems, right click on Operating systems images and click on Add Operating System Image.

Specify the path where the install.wim is present. Click Next.

Provide details for the operating system image. Click Next.

Click Next and click close.

Distribute the image into DPs

Select the Distribution Point

Click Next and Close

Configure Network Access account and this account is used by the client to access the Configuration Manager Distribution point when booted under WinPE

Specify Network Access account

Task Sequence Creation

Launch the Configuration Manager console, click on Software Library, expand Overview, expand Operating Systems, right click Task Sequences and click Create Task Sequence.

Type Task sequence Name

Select Boot Image

Select Operating System Image

Select Image Index ,type the Product Key ,type Local Administrator password and Next

Configure Domain Join Account

Select Join a Domain and browse the Domain OU and Click Next

Select Configuration Manager Client Package

Click Next since we are not using State Migration here

Select the Appropriate Software Update option, here i have selected Do not install any software updates

Select the Application Which we want to install during the task sequence

Click Next and Close

Task sequence has been created successfully, below is our basic win 10 task sequence view

Deploy task sequence into Unknown Computer Collection

Select task sequence right click and Click Deploy

Select All unknown Computers collection

And Select Pupose & Make available to PXE and Click Next

Select the Deployment schedule and click Next

Select User experience Option as per below and Click Next

Select deployment options as download locally and click Next

Verify the Summary and click Next

The Deploy task sequence wizard completed Successfully

Deploying Windows 10 via PXE boot

Here I have prepared another hyper V host and deploying windows 10 via configured PXE boot

Press F12 to boot from the network and the machine will get IP from DHCP, Contacting PXE server,Downloading and initiating the Boot Image

Task sequence wizard will appear and type task sequence password

Click Next

Task sequence variable will appear and Type the OSDComputerName

Click Next

Partition Disk stage Running

Applying Operating system stage Running

Setup Windows and Configuration Manger Stage Running

Setup Windows completed and Auto reboot initiated

Post Reboot, System Initiating

Imaging Completed and type the Administrator password to login,

Verify the same from smsts.log

Windows 10 deployment completed Successfully.

Thank You:-)

Deploying Application Using SCCM CB1902

This guide will shows, how to Create & deploy MSI application Using SCCM, Now lets go ahead and deploy an application to a device in SCCM CB 1902. The first step would be creating an application. To create an application, we need the MSI source file, here i have downloaded winzip.msi and placed the setup file in folder called softlib and shared the folder to access via SCCM console.

Create an Application

On the SCCM Server, login with SCCM admin account and launch the configuration manager console. Select Software Library, Under Application Management select Applications. Right click Applications and select Create Application

Select Automatically detect information.. and choose the type as Windows Installer, Specify the location of winzip.msi file.

Click Next.

On the next screen, lets specify some details about the software and for Install behavior select Install for a system if resource is device, otherwise install for user. Click Next.

Click Next.

The Application has been created successfully , click Close.

Right click the application and select Distribute,

To add the Distribution Points, click in Add and choose your distribution point.

Click Next

Deploy an Application

The Applications that are created can be seen by clicking Applications under Application Management. Right click the application and click Deploy.

Click Browse and specify the collection . Click Next.

Choose Action as “Install” and Purpose as “Required“.

The application will be available once you distribute the content to content servers. If you want to schedule the availability of application, then select “schedule the application to be available at“. We will not schedule the application availability and distribute the content immediately to the Content servers. Select the Installation deadline “as soon as possible“. Click Next.

Select the User Notifications, Click next.

Verify the selected options

We see that the deploy Software Wizard has completed successfully. Click Close.

Verify the same from Client machine, Open Software center

And Check the deployed application visible and started installing. Here deployed application status shows as successful

Verify the same from Appenforce.log

Thank You 🙂

CWmi::Connect() failed to connect to \\SCCM01.VCLOUD.COM\root\MicrosoftIISv2. Error = 0x8004100E

Package distribution failed on my DP server, When i referred the distmgr.log file, we could see the below error

CWmi::Connect() failed to connect to \SCCM01.VCLOUD.COM\root\MicrosoftIISv2. Error = 0x8004100E

ERROR DPConnection::ConnectRemoteIISManagementWMI() – Failed to connect to SCCM01.VCLOUD.COM. error = 0x8004100e

Cause: IIS 6 WMI Compatibility was not enabled on the distribution point, hence we are getting the above error

Post installation of IS 6 WMI Compatibility and restart IIS service, Redistributed the package and we could see the packages are started distributing

Review package distribution on distmgr.log file

Thank You!

Configuring Discovery And Boundaries In SCCM

Configuring SCCM Discovery

Configure discovery methods to find resources to manage from from network and Active Directory. Discovery creates a discovery data record (DDR) for each discovered object and stores this information in the SCCM database. When a resource is discovered the information about the resource is put in a file that is referred to as a discovery data record (DDR).
For More Info:-

Discovery Methods

Active Directory Forest Discovery – This method discovers Active Directory sites and subnets.
Active Directory Group Discovery – This method discovers groups from the defined location in the Active Directory.
Active Directory System Discovery –This method discovers the computers in your organization from specified AD locations.
Configuration Manager Active Directory User Discovery – This Discovery process discovers the user accounts from your Active Directory domain.
HeartBeat Discovery – This is the only discovery method that is enabled by default. The HeartBeat Discovery runs on every SCCM client and is used by Active Configuration Manager clients to update their discovery records in the database. Furthermore the records are sent to the management point in specified duration of time.
Network Discovery – The Network Discovery searches your network infrastructure for network devices that have an IP address. It can search the domains, SNMP devices and DHCP servers to find the resources. This includes printers, routers, and bridges.

Below is the discovery methods from Console

Enable Active Directory Forest Discovery

  In the Configuration Manager console, click on Administration and select Hierarchy Configuration, click on Discovery Methods. The first discovery method listed is Active Directory Forest Discovery. To discover Active Directory network locations and convert those locations into boundaries right click Active Directory Forest Discovery for the primary site and right click, choose Properties. Enable Active Directory Forest Discovery


Review the discovery of objects via ADForestDisc.log file located in <InstallationPath>\LOGS path

Enable Active Directory Group Discovery 

In the ConfigMgr console, in the Administration workspace, select Hierarchy Configuration, then select Discovery Methods and right click Active Directory Group Discovery and choose properties.  The Active Directory Group Discovery Properties window appears. Select the option to Enable Active Directory Group Discovery and click on Add to see two more choices, Groups and Location. Select Location and select the previously created windowsnoob Organizational Unit (OU) which will contain your servers, users, computers and devices.

Review the discovery of objects via ADsgDis.log file

Enable Active Directory System Discovery 

In the ConfigMgr console, in the Administration workspace, select Hierarchy Configuration, then select Discovery Methods and right click Active Directory System Discovery and choose Properties, place a check mark in Enable Active Directory System Discovery. Click on the yellow starburst to add Active Directory containers. For path click on browse and browse to the location you want to discover systems in.

Review the discovery of objects via ADsysDis.log file

Enable Active Directory User Discovery 

In the ConfigMgr console, in the Administration workspace, select Hierarchy Configuration, then select Discovery Methods and right click Active Directory User Discovery and choose Properties. Place a checkmark in Enable Active Directory User Discovery  and click on the yellow starburst to add active directory locations to discover users.

Review the discovery of objects via ADusrDis.log file

Review discovered resources in the console

Discover enabled view from Console

Discovered System resources

Discovered User resources

Configure SCCM Boundaries

As per Microsoft, a boundary is a network location on the intranet that can contain one or more devices that you want to manage. Boundaries can be either an IP subnet, Active Directory site name, IPv6 Prefix, or an IP address range.
To use a boundary, you must add the boundary to one or more boundary groups. Boundary groups are collections of boundaries. By using boundary groups, clients on the intranet can find an assigned site. In addition to that they can locate content such as applications, software updates, and operating system images. Active Directory Forest Discovery discovers boundaries automatically.

To create boundries in SCCM,
Open the SCCM Console-Go to Administration / Hierarchy Configuration / Boundary-Right-click Boundaries and select Create Boundary

Here i have used Active Directive Site

Here boundary has been created and reflected in Console

Create Boundary Group

We need to add the Boundary to the Boundary groups. To do so Select Boundary Groups, right Click and create a boundary group. Provide a name as First Boundary Group. Click Add. Select the boundary which we created AD Site and Click OK. Click on references tab, check Use this Boundary group for site assignment. To add the site system servers, click Add and select the Site System Server. Click OK.

Newly Created Boundary group reflected in Console

System Center Operations Manager (SCOM) 2016 Installation Guide


The following installation guide will cover a basic install of System Center Operations Manager 2016 on Windows Server 2016 with SQL 2016.

In this article, we will be deploying a single Operations Manager that will contain all components of the solution on a single server. However, in a corporate environment, the administrator will plan to distribute the roles and design high availability to the monitoring system.

Single server deployment of Operations Manager

The single server management scenario combines all the management group roles that can coexist onto a single server running as a member server in an Active Directory domain. This instance can be on dedicated hardware or on a virtual computer. You can deploy the Operations console to computers other than the single server, and access the web console with a browser.

You deploy Operations Manager in a single-server management group when you want to use it for evaluation, testing, and management pack development, usually in a lab, development, or non-production environment.

Reference link:-

Operations Manager services

The single server management group configuration supports the following services:Monitoring and alerting

  • Monitoring and alerting
  • Reporting (available in the Operations console but not in the web console)
  • Audit collection
  • Agent-less exception management
  • Data (accessed by using the web console and the Operations console)

My LAB environment Setup

I have hosted all the servers in Hyper-V and Windows Server 2016 has been installed as the base OS for all Servers.
Installed two Windows 2016 servers for AD & SCCM
AD server Name : ADS01(Configured Active directory Domain services,DNS & DHCP)
Domain Name: VCLOUD.COM
SCOM Management Server Name : SCOM01 (SQL 2016 installed on the same Server)

Operations Manager service accounts

As part of the installation process, we must create the Service Accounts/Security Group from AD which will be used during Operations Manager installation

  1. DOMAIN\OMSAA              OM Server Action Account
  2. DOMAIN\OMDAS              OM Config and Data Access Account
  3. DOMAIN\OMREAD           OM Datawarehouse Reader Account
  4. DOMAIN\OMWRITE         OM Datawarehouse Write Account
  5. DOMAIN\MSSQL               SQL Service Account
  6. DOMAIN\OMAdmins        OM Administrators security group( Add the OMSAAOMDASOMREAD, and OMWRITE accounts to the “OMAdmins” global group)

SCOM server Prerequisites

1.Install Web Server Roles

Open Powershell and run the following command to Install required Web Server roles (IIS)

Add-WindowsFeature Web-Server, Web-WebServer, Web-Common-Http, Web-Default-Doc, Web-Dir-Browsing, Web-Http-Errors, Web-Static-Content, Web-Health, Web-Http-Logging, Web-Request-Monitor, Web-Performance, Web-Stat-Compression, Web-Security, Web-Filtering, Web-Windows-Auth, Web-App-Dev, Web-Net-Ext, Web-Net-Ext45, Web-Asp-Net, Web-Asp-Net45, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Mgmt-Tools, Web-Mgmt-Console, Web-Mgmt-Compat, Web-Metabase, NET-Framework-45-ASPNET, NET-WCF-HTTP-Activation45, WAS, WAS-Process-Model, WAS-Config-APIs

2.Install Microsoft CLR Types for SQL Server 2014
3.Install Microsoft Report Viewer 2014 Runtime

Install SQL 2016

In My lab, I have installed SQL 2016 on the same SCOM01 server. below are the step by step installation.

  • Run setup, choose Installation > New SQL Server stand-alone installation…
  • When prompted for feature selection, install ALL of the following:
    • Database Engine Services
    • Full-Text and Semantic Extractions for Search
    • Reporting Services – Native
  • On the Instance configuration, choose a default instance, or a named instance. Default instances are fine for testing, labs, and production deployments. Production clustered instances of SQL will generally be a named instance. For the purposes of the POC, choose default instance to keep things simple.
  • On the Server configuration screen, set SQL Server Agent to Automatic and type respective domain service account & password.
  • Check the box to grant Volume Maintenance Task to the service account for the DB engine.  This will help performance when autogrow is needed.
  • On the Account provisioning tab – add your personal domain user account and/or a group you already have set up for SQL admins. Alternatively, you can use the OMAdmins global group here. This will grant more rights than is required to all OMAdmin accounts, but is fine for testing purposes of the POC.
  • On the Data Directories tab – set your drive letters correctly for your SQL databases, logs, TempDB, and backup.
  • On the Reporting Services Configuration – choose to Install and Configure. This will install and configure SRS to be active on this server, and use the default DBengine present to house the reporting server databases. This is the simplest configuration. If you install Reporting Services on a stand-alone (no DBEngine) server, you will need to configure this manually.
  • Choose Install, and setup will complete.
  • When you complete the installation – Install SQL Server Management Studio Tools separatly to access the database. 

SCOM 2016 Step by Step Installation

Now we will start the SCOM installation, First extract setup file from the downloaded source. Once extraction complete, Run the setup now.
On the SCOM 2016 setup screen, Click Install (In order to get the latest update you can choose Download Check box and its an optional)

Here I am going to install all the features, select all the below features

Setup will verify hardware and software requirements

All prerequisites Passed, Click Next

Since its an new installation, Select Create the first management Server and Provide Management Group Name (Here i have used OPS-MGR)

Accept the license terms and click Next.

Provide Server Name and Instance Name and Click Next

Specify Server name and Click Next

Choose the SQL server instance for reporting services and click Next.

Select Default Web Site and click Next.

Select Mixed Authentication and click Next.

Enter respective Created service accounts as per below

Click Next.

You can choose use microsoft update to check for updates option If you enable internet, Otherwise Choose Off

Final check before you click Install.

Installation In progress

Setup is successfully Completed now and we have installed evaluation version of operations manager, hence its showing warning for management server

Lanch SCOM 2016 Console now. Below is the SCOM console View

Click Help > About to See the SCOM version. We have successfully installed SCOM 2016 now.

Thank you 🙂 Will post the configuration part soon.

Microsoft SCCM Current Branch 1902 Step-By-Step Installation Guide


The following guide will take you through the installation of SCCM Current Branch 1902 with a simple Primary Server approach and with the SQL 2016 server located on the same device hosted on Hyper-V

Setting Up the Lab

I have hosted all the servers in Hyper-V and Windows Server 2016 has been installed as the base OS for all Servers.

Installed two Windows 2016 servers for AD & SCCM

AD server Name : ADS01(Configured Active directory Domain services,DNS & DHCP)

Domain Name: VCLOUD.COM

SCCM Server Name : SCCM01

SCCM 1902 Prerequisites

1.Join SCCM01 to Domain, Create required Users,assign permissions and create the Systems Management container, delegate permission

2.Server role and feature installation

3.Install ADK and WDS

4. Install and configure SQL server (Here I have used SQL server 2016 SP2)

5.Download SCCM source from the below link

Creating the System Management Container and SCCM configuration user accounts

Open ADSI Edit, click on Action, then Connect To and click Ok, Double Click on Default Naming Context and the DC= that appears below it. Click on the > and scroll down to CN=System. Right Click on CN=System and choose NewObject

choose Container from the options, click Next

Enter System Management

as the value then click Next and then click Finish.

Complete the wizard and close ADSIEdit.

Next, launch Active Directory Users and Computers, Select View, Advanced, and then find System Management.

Right-click on System Management, select Properties, and then the Security Tab. Add the SCCM admin account and the SCCM server name — Full control. Click OK to close.

Next, Delegate control to the SCCM site server (SCCM01) to System Management container in AD Users and Computers.

Click Next then select Create a Custom Task to Delegate, click Next, make sure This folder, existing objects in this folder and creation of new objects in this folder is selected.

Click next, select the 3 permissions General, Property-Specific and Creation-deletion of specific child objects are selected then place a check mark in Full Control.

Click Next then click Finish.

Then Create Configuration Manager User Accounts as per below for SCCM installation/Configuration

CM_Build – For Imaging

CM_Domain Join – For joining computers to the domain

CM_Reporting, For Reporting Services.

CM_Client Push, For SCCM Client Push.

CM_NAA, (Network Access Account) For OSD

Web Server IIS Installation and Feature installation

To enable Web server role and other features, login to SCCM server. Launch Server Manager and click Manage > Add Roles and Features. Select Web Server (IIS) server role and click Next.

Enable/Install the following features :

.Net Framework 3.5 Features [Install all sub features]

.Net Framework 4.5 Features [Install all sub features]


Remote Differential Compression

Enable/Install the following Roles Services :

Common HTTP Features – Default Document, Static Content.

Application Development – .NET Extensibility 3.5 and 4.5. Select ASP.NET 3.5, ISAPI extensions, ASP.NET 4.5.

Security – Windows Authentication.

IIS 6 Management Compatibility – IIS Management Console, IIS 6 Metabase Compatibility, WMI Compatibility and IIS Management Scripts and Tools.

Click on Close when the feature installation has succeeded.

Install Windows ADK 1903 and install WDS

Download the Windows ADK for Windows 10, version 1903 & Windows PE add-on for the ADK from Microsoft download Centre

Install Windows ADK version 1903. Run the ADK setup and select the following features.

Deployment Tools

User State Migration Tool

Imaging and Configuration Designer (ICD)

Configuration Designer

and click Install to start the download and Installation of the Windows ADK

Once the ADK installation is complete, click Close.

Install the Windows Preinstallation Environment (Windows PE)

Click Next at the License agreement and click Install when prompted.

Click Close Once installation complete

To install Windows Deployment Services (WDS), open Server Manager, select Add roles and features and select the Windows Deployment Services role.

When prompted click on Add Features to include management tools.

and click through the wizard until completion, close the wizard when installation complete

Install SQL Server 2016 SP2

Mount the SQL server ISO. Launch the SQL server setup (run as administrator). On the installation window, click Installation and then click New SQL server stand-alone installation.

Feature Selection – Select Database Engine Services and click Next

Instance Configuration – Select Default Instance. Click Next.

Specify the service accounts. Note the you must use a separate account for each SQL server service.

Click Add Current User to add the account to SQL server administrators. Click Next. Complete the remaining steps. Close the setup wizard and finally reboot the server once.

Click Next and and install and Complete the installation

To Access SQL server, Download and Install SQL Server Management Studio Separately

Install SCCM Current Branch 1902

Download SCCM 1902 baseline media from Microsoft download Center

Run the Splash HTML application from the setup folder. This brings up the System Center Configuration Manager install wizard.

Click Next. then Select Install a Configuration Manager primary site. Check the box “Install a Configuration Manager Primary site“. Click Next.

If you have the SCCM product key, enter it else install the evaluation edition and click Next

Accept the license terms. Click Next.

The Configuration Manager setup requires some prerequisite files. You can either download them now or if you have previously downloaded it, provide the path. Click Next.

Specify the Site code, Site name. Click Next. Here My SITE code is VC1

click Next

On the Settings Summary page, verify all the settings and click Next.

Skip this warning and Begin Install

Once Installation Completed, Click Close

During the installation, click on View Log (opens C:\ConfigmgrSetup.log) to review the installation progress and we could see installation completed Successfully.

Open Console, the below is the Console View

Thank You 🙂 I will post Sccm Configuration, Application Deployment, Updates deployment & Image Deployment Guide soon..!