SCCM 1902 Preview 7 New Features – Console Connections Node

SCCM 1902 production version is nearing the release date. I hope the feature list of 1902 production version has been finalized. It seems most of the new features released in SCCM 1902 preview version will be available in the production version of SCCM 1902.

UPDATE! – If you are looking SCCM 1902 Production version upgrade and SCCM 1902 new features, please check out

[Related Post – SCCM 1902 Production Upgrade Step by Step Guide Video here]

SCCM 1902 Version Details

Microsoft released 1902 preview is released on 8th Feb 2019. I have upgraded the LAB version from SCCM 1901 to 1902.

  • SCCM 1902 (Preview) Client Version 5.00.8782.1000
  • SCCM 1902 (Preview) Full Site Version 5.00.8782.1000
  • SCCM 1902 (Preview) Console version 5.1902.1073.1000

SCCM 1902 Preview New Features

The most exciting feature for me changes in the toast notification. I have seen many occasions, and end users missed the notification mainly because of the small size of the notification window. Also, SCCM Console Connection Node is nice addition to the SCCM 1902 preview version.

Toast Notification to Dialog Windows Notification

There are two (2) changes in SCCM toast notifications:

  • Software Changes Toast Notification => Software Center Dialog Window for Software Changes
  • Restart Required Toast Notification =>Software Center Dialog Windows for Restart required

SCCM Task Sequence – Progress Status during Windows 10 in-place upgrade

There is a new change in the SCCM 1902 preview will build that will help IT admins and end users to check the status of the Windows 10 in-place upgrade task sequence.

SCCM New Compliance Setting Policy for Redirect Windows known folders to OneDrive

The new compliance policy to redirect Windows known folders to OneDrive is helpful in many Windows 10 migration scenarios. I hope, SCCM 1902 product version release will have this feature, and it will help IT Admins to reduce some pains of Windows 10 migration.

SCCM Remote Control Viewer – First Screen Only Option

SCCM Remote control is one of the features widely used within the organization. This remote control feature is used mainly by helpdesk and a support team to help end users. SCCM 1902 preview version details below.

SCCM remote control with multiple monitors is always a challenge. As the options are limited to see all monitors and if your end user has more than one monitor, then the remote control view is very small. This issue is resolved in the SCCM 1902 preview version.

I hope, this UserVoice feedback, a remote tools operator, can now choose between seeing All screens or the First screen only, will reach production version of SCCM 1902 as well.

SCCM Console Connections Node

SCCM 1902 preview version comes with another useful addition and that is SCCM console connections node.

  • Navigate via Administration -> Security -> Console Connections
  • You will able able to see how many consoles are connected to SCCM site (I don’t single or mutiple SMS provider/s?)
  • How many versions of SCCM console versions are used to connect to the site from Console Connections Node

SCCM CMG (Cloud Management Gateway) is Boundary Group Aware

Now you can assign an SCCM CMG to a specific boundary group. The SCCM CMG affinity was one of the most significant challenges similar to the SCCM MP rotation issue (back in SCCM 2012). Microsoft helped to redesign the SCCM CMG affinity issue by bringing boundary group awareness to SCCM 1902.

Rob York shared the following diagram to make you aware of new SCCM CMG boundary group awareness options in SCCM 1902 preview version.

This SCCM CMG affinity is the must in feature for SCCM 1902 production version.

Software Center List View and Tiles View

In the new SCCM 1902 Preview version software center client policies, you will get more configurations with the “Default” tab. In the default tab, you would be able to select what would be the default view for end users. You can choose either of the below options from the drop-down menu.

  • All Apps
  • Required Apps

Also, SCCM admins can decide between tiles and list view of applications in the software center. I love the list view when you have more than 10-15 applications in the software center.


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


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

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.


How to Convert MSI Packages to MSIX Using SCCM

Have you heard about SCCM MSIX conversion wizard? This MSIX conversion wizard gives you an option to convert existing application to MSIX packages. In this video post, you will see MSIX package conversion process.  The process which I explained in the above video is to Convert MSI Packages to MSIX.

Find Out the List of MSI Packages?

First phase of convert MSI packages to MSIX is the inventory of MSI packages which should be converted to MSIX. Also, you need to make sure whether you would be able to convert all the packages to MSIX.

I do agree that all your MSI packages can’t be converted to MSIX packages without any manual efforts or coding. But, this is the stage where you should get a sponsor to analyze and test the existing MSI packages to understand compatibility.

This compatibility check to convert MSI packages to MSIX is important for your organization. This analysis will help to understand the efforts to convert MSI packages to MSIX.

How to Convert MSI Packages to MSIX

SCCM 1810 or above will help you to convert MSI packages to MSIX.  SCCM uses the MSIX conversion tool in the background to install MSI package on reference computer and capture the changes in the system to make MSIX package.

The following prerequisites should be in place to convert MSI packages to MSIX and test those MSIX packages.

  1. Purchase public cert – code signing certificate or Internal PKI cert or self signing cert
  2. SCCM 1810 Infrastructure
  3. Windows 10 1809
  4. SCCM 1810 or later installed on Windows 1809 or later
  5. Windows 1809 or later with local admin access
  6. Windows 10 SDK with SignTool.exe
  7. Clean Windows 1809 or later reference device without any previous installations of the MSI packages which are getting converted to MSIX
  8. The user should have access to MSI Package Source location and MSIX package SAVE location
  9. Enable sideloading of Windows apps on Windows 10 device


Step by Step guide to test MSI to MSIX package conversion process –

What is New in SCCM 1810 New Features Video Tutorial

Microsoft released SCCM 1810 version in the fast ring (opt-in). I have published a couple of posts and videos about SCCM 1810 upgrade. I would recommend reading those posts to get more details about the upgrade process. In this video post, I will give you a walkthrough experience of SCCM 1810 New Features (What is New in SCCM 1810).

[Related PostsSCCM 1810 Upgrade Video Guide – Best PracticesList of Improvements – Business Case for SCCM 1810 Upgrade and Known issues of SCCM 1810]

List of SCCM 1810 New Features

The following features are identified and explained in the video blog above. I would recommend going through the resources section as well to get more details about SCCM 1810 new features (What is New in SCCM 1810).

  1. Improvements to collection evaluation
  2. SCCM administrator authentication
  3. The Management insights rule for peer cache source client version
  4. Improvements to internet-based client setup
  5. Convert applications to MSIX
  6. Changes to client notification action to wake up a device
  7. Improvement to the client installation
  8. Required app compliance policy for co-managed devices
  9. Improvement to co-management dashboard
  10. New boundary group options
  11. Site system on Windows cluster node
  12. Logging Improvements to CMPivot
  13. Improvements to scripts
  14. New client notification action to wake up the device
  15. Task sequence support for boundary groups
  16. Management insights dashboard
  17. In-console documentation dashboard (Not Released in this SCCM 1810 new features)
  18. Improvements to driver maintenance (Model details)
  19. Task sequence support of Windows Autopilot for existing devices (Out of box Support)
  20. Improvements to CMPivot (80KB or above in msg size)
  21. Improvement to lifecycle dashboard
  22. Improvement to the data warehouse
  23. Improvement of maintenance windows for software updates
  24. Phased deployment of software updates
  25. Improvement to repair applications
  26. Community Hub (Not Released in this SCCM 1810 new features)
  27. Specify the drive for offline OS image servicing  (Not Released in this SCCM 1810 new features – I couldn’t confirm this)
  28. Co-managed device sync activity from Intune
  29. Repair SCCM applications
  30. Approve application requests via email
  31. Improvement to script output
  32. Improvement of third-party software updates

Resource (SCCM 1810 New Features)

  1. SCCM ConfigMgr 1810 Upgrade #Video Guide
  2. SCCM 1810 Upgrade Step by Step Walkthrough Guide
  3. SCCM 1810 What is New ->
  4. Windows 10 Support as SCCM Client –
  5. Windows 10 ADK Support for SCCM 1810?