Configuration Manager 1902 is released–What’s in and what’s out?

Microsoft released the 1902 version of Configuration Manager the week after the official MVP Summit and it’s a bumper packed edition. I’m going to cover some of the highlighted features in their own posts which are linked below, this post will summarise what’s in and what’s out.

The official link for the what’s new article can be found here –

Worth remembering that this doesn’t necessarily include every little change, just the major features.

First things first, we have a few deprecations. These things rarely come as a surprise as Microsoft tend to announce them around 12 months in advance so we can’t say we weren’t warned.

What’s out?

Deprecation of Unix/Linux agent for Configuration Manager

Microsoft removed support for the existing agent for Unix and Linux, simple as that really. This doesn’t mean your existing clients will stop working, just that there’s no more client updates from 1902. I understand the reasoning behind this as the actual uptake on this client is very low, however I for one will be sad to see that being removed having implemented some clients over the years. Whilst the client functionality is limited, it does provide a basic service for things like inventory and application deployments. The suggestion from Microsoft is to use alternatives such as Azure based management which primarily provides native patching services. I have also worked with this, spoken publicly on it and indeed was on the TAP for this technology and it does provide a good solution – if you’re in Azure. The overwhelming majority of the Unix/Linux machines I’ve worked with were not cloud attached or even exposed to the internet so this won’t be an option. We’re told openly that Microsoft love Linux however. In my mind the reason the uptake on the *nix client was so low is because it was so basic. Add a little functionality to it and I’m sure the uptake would increase.

Deprecation of a standalone Cloud Distribution point

To be clear, this is the standalone cloud DP that has been around since CM 2012 SP1. The ‘newer’ functionality simply rolls this into a cloud management gateway (CMG) which does make a lot of sense. However, if you only want a cloud DP and not a CMG then you’re out of luck. Again, not a bad thing but it will cost you more than a DP on its own. One scenario to watch out for here though, if you have an existing cloud DP and you have an issue with it (which is not unheard of) which causes you to redeploy, then presumably you’re out of luck. I’ll try and get some clarification on that one and report back.

What’s in?

Site infrastructure

  • Client health Dashboard
  • New management insight rules
  • Improvements to enhanced HTTP (E-HTTP)
  • Improvements to setup pre-requisites

Cloud-attached management

  • Stopping a CMG when it exceeds your data transfer threshold
  • All new CMG and Cloud DP deployments based on ARM
  • Adding a CMG to boundary groups

Real-time management

  • Run CMPivot from a Central Administration Site (CAS)
  • Edit or copy PowerShell scripts within Run Scripts

Content Management

  • Distribution Point maintenance mode

Client management

  • Client provisioning mode timeout
  • First screen only in remote control
  • Custom port for peer wake up

Application management

  • Improvements to app approvals via email
  • Improvements to Package Conversion Manager

OS Deployment

  • Progress status during an in-place upgrade (IPU) task sequence
  • Improvements to task sequence media creation
  • Import a single index of an OS image
  • Optimized image servicing
  • Improvements to the Run PowerShell Script task sequence step
  • Other improvements to OSD

Software Center

  • Replace toast notifications with a dialog box
  • Configure User affinity in Software Center
  • Configure default views in Software Center

Software Updates

  • Specify priority for feature updates in Windows 10 servicing

Office Management

  • Redirect Windows known folders to OneDrive
  • Integration with analytics for Office 365 ProPlus readiness
  • Additional Languages for Office 365 updates
  • Office products on lifecycle dashboard

Phased Deployments

  • Dedicated monitoring for phased deployments
  • Improvements to phased deployment success criteria

Configuration Manager console

  • New notifications within the console
  • Confirmation of console feedback
  • View recently connected consoles
  • In-console documentation dashboard
  • Search device views by MAC address
  • Use .Net 4.7 for improved console accessibility

12 thoughts on “Configuration Manager 1902 is released–What’s in and what’s out?

  1. Pingback: Configuration Manager 1902–Configuration Manager Console | More than patches

  2. Pingback: Configuration Manager 1902–Phased Deployments | More than patches

  3. Pingback: Configuration Manager 1902–Office Management | More than patches

  4. Pingback: Configuration Manager 1902–Software Updates | More than patches

  5. Pingback: Configuration Manager 1902–Software Center | More than patches

  6. Pingback: Configuration Manager 1902–OS Deployment | More than patches

  7. Pingback: Configuration Manager 1902–Application Management | More than patches

  8. Pingback: Configuration Manager 1902–Client Management | More than patches

  9. Pingback: Configuration Manager 1902–Content Management | More than patches

  10. Pingback: Configuration Manager 1902–Real-time Management | More than patches

  11. Pingback: Configuration Manager 1902–Cloud-Attached Management | More than patches

  12. Pingback: Configuration Manager 1902–Site infrastructure improvements | More than patches

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.