Home
Microsoft

In the 1902 update to Configuration Manager current branch, we continue to deliver value around our core themes of Cloud Value, Customer Voice, Get Current, and Simplification.

 

Get Current with Office is one of our key capabilities in the 1902 update and optional integration with the Readiness Toolkit for Office provides insights to help prepare for Office 365 ProPlus deployments. These insights can now complement your organization’s end-to-end ability to deploy Office 365 ProPlus, from readiness, to deployment, to monitoring.

 

The existing Office 365 client management dashboard now includes a new tile, Office 365 ProPlus Upgrade Readiness.

 

NewOffice365MgmgDashbord.pngOffice 365 client management dashboard

Select a readiness state to drill-through to a device list. This readiness report allows you to quickly identify devices with high confidence that are ready to upgrade to Office 365 ProPlus. It includes columns for the compatibility state of both Office add-ins and macros.

 

OfficeAddInsFromCMPivot.pngOffice Add-ins and Macros

 

Learn more about integration with the Readiness Toolkit for Office

 

Also, in update 1902 are improvements to Phased Deployments which now has its own dedicated monitoring node. From the lifecycle dashboard, organizations can now also view the support lifecycle for the versions of Office in their environment.  Additionally, ConfigMgr 1902 has added the ability to configure known folder mapping to OneDrive, providing a streamlined way to seamlessly move or redirect users’ known folders and data to OneDrive.

 

Some other key areas of investment in the other themes of the release include user comments in email notifications for approval requests from Software Center, improvements in client health with a dashboard with detailed breakdowns of client health status across your organization, and Windows software update improvements to better control the end user experience with software update downloads and installs.  There are new Management Insight rules for optimizing and simplifying collections and packages. You can now use CMPivot from the CAS and edit and copy existing PowerShell scripts used with RunScripts.

 

This release includes:

Cloud Value

  • Cloud Management Gateway (CMG) can be associated with boundary groups - Cloud Management Gateway deployments can now be associated with boundary groups to allow clients to default or fallback to the CMG for client communication according to boundary group relationships.
  • Stop cloud service when it exceeds threshold - Configuration Manager can now stop a cloud management gateway (CMG) service when the total data transfer goes over your limit.

Customer Voice

Application Management

  • Improvements to application approvals via email - When users request applications from Software Center, the email notification will now include their comments.

Configuration Manager console

  • Improvements to Configuration Manager console - Based on customer feedback aka the Cabana sessions at the Midwest Management Summit (MMS) Desert Edition 2018, this release includes several improvements to the Configuration Manager console.
  • View recently connected consoles - You can now view the most recent connections for the Configuration Manager console. The view includes active connections and those that recently connected.
  • View first monitor only during Configuration Manager remote control session - When connecting to a client with two or more monitors, a remote tools operator can now choose between seeing all monitors and the first monitor only.
  • Search device views using MAC address - you can now search for a MAC address in a device view of the Configuration Manager console.

Software Center

  • Replace toast notifications with dialog window - When deployments need a restart or software changes are required, you now have the option of using a more intrusive dialog window to replace toast notifications on the client
  • Configure default views in Software Center - You can now customize your end user’s default application layout and default application filter in Software Center.

OS Deployment

  • Improvements to task sequence media creation - When you create task sequence media, you can now customize the location that the site uses for temporary storage of data and add a label to the media.
  • Improvements to Run PowerShell Script task sequence step – The Run PowerShell Script task sequence step now allows you to specify a timeout value, alternate credentials, a working directory and success codes.
  • Import a single index of an Operating System Image - When importing a Windows image (WIM) file to Configuration Manager, you can now specify to automatically import a single index rather than all image indexes in the file.
  • Progress status during in-place upgrade task sequence - You now see a more detailed progress bar during a Windows 10 in-place upgrade task sequence.

Client Management

  • Client Health Dashboard - You can now view a dashboard with information about the client health of your environment. View your client health, scenario health, common errors along with breakdowns by operating system and client versions.
  • Specify a custom port for peer wakeup - You can now specify a custom port number for wake-up proxy.

Real-time management

  • Run CMPivot from the central administration site - Configuration Manager now supports running CMPivot from the central administration site in a hierarchy.
  • Edit or copy PowerShell scripts – You can now Edit or Copy an existing PowerShell script used with the Run Scripts feature.

Get Current

Phased deployments

  • Dedicated monitoring for phased deployments - Phased deployments now have their own dedicated monitoring node, making it easier to identify phased deployments you have created and navigate to the phased deployment monitoring view.
  • Improvement to phased deployment success criteria - Specify additional criteria for the success of a phase in a phased deployment. Instead of only a percentage, these criteria can now also include the number of devices successfully deployed.

Office Management

  • Integration with analytics for Office 365 ProPlus readiness - Use Configuration Manager to identify devices with high confidence that are ready to upgrade to Office 365 ProPlus.
  • Additional languages for Office 365 updates - Configuration Manager now supports all supported languages for Office 365 client updates.
  • Office products on lifecycle dashboard - The product lifecycle dashboard now includes information for installed versions of Office 2003 through Office 2016.
  • Redirect Windows known folders to OneDrive - Use Configuration Manager to move Windows known folders to OneDrive for Business. These folders include Desktop, Documents, and Pictures.

OS servicing

  • Optimized image servicing - When you apply software updates to an OS image, there's a new option to optimize the output by removing any superseded updates.
  • Specify thread priority for feature updates in Windows 10 servicing - Adjust the priority with which clients install a feature update through Windows 10 servicing.

Simplification

  • Management insight rules for collections - Management insights has new rules with recommendations on managing collections. Use these insights to simplify management and improve performance.
  • Distribution Point Maintenance Mode - You can now set a distribution point in maintenance mode. Enable maintenance mode when you're installing software updates or making hardware changes to the server.
  • Configuration Manager Console Notifications - To keep you better informed so that you can take the appropriate action, the Configuration Manager console now notifies you when lifecycle and maintenance events occur in the environment.
  • In-console documentation dashboard – There is a new Documentation node in the new Community workspace. This node includes up-to-date information about Configuration Manager documentation and support articles.

 

For more details and to view the full list of new features in this update check out our What’s new in version 1902 of System Center Configuration Manager documentation.

 

Updated 4/18/2019 Note: The update is now globally available to all customers. The script to enable the first wave is no longer necessary.

 

For assistance with the upgrade process please post your questions in the Site and Client Deployment forum. Send us your Configuration Manager feedback through Send-a-Smile in the Configuration Manager console or by using the Feedback Hub app built-in to Windows 10.

 

Continue to use our UserVoice page to share and vote on ideas about new features in Configuration Manager.

 

Thank you,

The System Center Configuration Manager team

 

Additional resources:

14 Comments

SCCM 1902 is baseline version?

Occasional Visitor

Yes!

Occasional Visitor

Will the "SQL change tracking cleanup" become automated? Every Prerequisite Check requires it to be resolved through a diagnostic connection. Thank you!

 

 

https://docs.microsoft.com/en-us/sccm/core/servers/deploy/install/list-of-prerequisite-checks#bkmk_c...

 

 

Microsoft

Does this mean that SCCM clients that are in a boundary group but connected over the internet to the CMG can now leverage SCCM Peer Cache?

Senior Member

Are there any compatibility problems or known issues running SCCM 1902 with Azure Stack 1808 or 1809?

It appears many functionalities of the newer SCCM versions are related to Office 365.   Other than Office 365, what are the significant features we will miss out if we continue to use SCCM 1802 with Azure Stack 1808 or 1809?

Occasional Contributor

If 1902 is a baseline version, does that mean we can create a new SCCM installation directly from the 1902 install media? Or do i still have to start with 1802 first? I ask because i only see 1802 in my VLSC portal.  The exact download is named "System Center Config Mgr (current branch 1802) MultiLanguage".

Occasional Visitor
Senior Member

Upgrade to 1902 broke SMS Agent Host (error 1053) when trying to start the service. As a result MP getting http 500.19 error. A site reset using the 1902 media fixed the issue.

 

Windows Server 2016 (1607) 

SQL 2016 

ConfigMgr 1902

 

As an MSP we have two (2) reported cases of this problem.

Occasional Visitor

@Neil Pickersgill What was the process you followed for this - we re-ran the CD.latest to no avail - it appears we're still seeing 500 errors

 

Senior Member

You need to ensure that the SMS Agent Host service is STOPPED otherwise  it will fail trying to stop it. you will probably need to end the process via task manager unfortunately (never a fan of killing a service like that), however in this case needs must. You have followed the correct line of action though. Run the cd.latest install media and choose site reset as you did before. just make sure that service in particular is STOPPED.

Regular Visitor

Since upgrading to SCCM 1902 and it's subsequent console update, the remote control viewer is only displaying the first screen when All Screens selected. Or more to the point, it's kind of showing 1 1/8 screens:

SCCM.JPG

 

Is this is a known issue? This has been attempted on several dual screen monitors with the same result. I can't seem to find any other reports of this...

Occasional Visitor

@Neil Pickersgill - Man, I don't understand your response with regard to site reset. 

 

I am troubleshooting SMS Host Agent Service issue that I cannot start after 1902 upgrade.  With site reset the SMS Host Agent service is already stopped.  What is your point of saying the service has to be stopped.  If the service is running, I don't need to troubleshoot Error 1053 (which is SMS Host agent) cannot start.  You should make your point clear.

Occasional Visitor

The proper approach to fix the issue is:

1. Stop all services 

2. Run Site reset from cd.latest

3. Remove MP and Reinstall MP (I did this because MP had error 500)

4. Restart the server

5. Check all services are running including SMS Host Agent

Regular Visitor

Is there a hotfix or cumulative update available/released for CM 1902 ? Thanks