New Impressive SCCM 1902 Console Improvements
This post covers the improvements and additions to the SCCM Console that were added to current branch version 1902. We know SCCM 1902 is released and there are loads of new features baked in the version 1902. Most of the time we look for only major features and tend to ignore those small features or sometimes they go unnoticed.
If you have noticed there are lot of console improvements in SCCM 1902. Most of the ideas implemented were requested by users. This also shows that Microsoft is constantly listening to it’s customers. I can tell this based on the UV items that are implemented in current branch versions so far.
Table of Contents
SCCM 1902 Console Improvements
Before you read further, you must first upgrade your Configuration Manager to version 1902. Here is a upgrade guide for SCCM 1902. In addition to that, check out the SCCM 1902 new features here. Let’s look at some of cool console improvements and additions in SCCM 1902.
To make your experience even better, Configuration Manager console now notifies you for the following events:
- When there is a Configuration Manager update available.
- When lifecycle and maintenance events occur in the environment
This notification bar appears on top of the console window just below the ribbon. The information that you see are in-console notifications. They usually display critical information, but they don’t interfere while you work. Note that you can’t dismiss critical notifications.
If i am correct, the below screenshot is an example of SCCM console notification (got this when i was installing technical preview 1903).
Configuration Manager Console Feedback
In SCCM 1902 console, when you send feedback, it now shows a confirmation message. To send the feedback, look for the smiley icons in top right corner of Configuration Manager console. You can either send a smile or a frown and append your feedback.
That’s the confirmation message which says Feedback sent – Your feedback has been submitted. This message includes a Feedback ID, which you can give to Microsoft as a tracking identifier.
SCCM Console Connections
With SCCM console connections, you can now view the most recent connections for the Configuration Manager console. Probably the best feature that you can try right after installing SCCM 1902. The view includes active connections and those that recently connected.
To view SCCM Console Connections
- Launch Configuration Manager console.
- Navigate to Administration > Overview > Security.
- Now click Console Connections.
Configuration Manager Documentation within Console
In SCCM 1902, the console includes Configuration Manager documentation. Just go to Community workspace within the Configuration Manager console and click Documentation. In addition to that you get links to the following.
- Recommended articles
- Trending articles
- Recently Updated articles
- SCCM Troubleshooting articles
- New and Updated Support articles
Search Device Views by MAC address in Console
The SCCM admins can now search for a MAC address in a device view of the Configuration Manager console. Very helpful feature for OS deployment administrators while troubleshooting PXE-based deployments.
To Search Device Mac Address in SCCM Console
- Launch Configuration Manager console
- Go to Assets and Compliance workspace
- Select the Devices node
- From list of devices, add the MAC Address column to the view.
- Use the search field to add the MAC Address search criteria.
Use .Net 4.7 for improved Console accessibility
To improve the accessibility features of the Configuration Manager console, update .NET to version 4.7 or later on the computer running the console. If you have installed the console on Windows Server 2019, the .NET framework 4.7.2 comes installed by default.
i installed sccm console on a client computer that connects to the site database, however on the server’s console, i cannot see who’s connected and at what time. it’s just empty.
what am i missing?
Can we configure to auto disconnect the SCCM console connections after a period of time ?
I can see people are having multiple connections from different machines to the same console ..
Hi Prajwal ,
Recently i have upgraded my SCCM console to 1902 from 1810 , but unfortunately SMS Agent Host unable to start , its getting failed with Error 1053 . Tried many solutions but nothing works , can you suggest me if you faced any issues related to this.
Hi Nandhakumar, I haven’t come across any such issues. Can you log this issue here in forums please.
I’m seeing the same symptoms in two separate environments. A site reset resolved the issue for one environment but not the other.
Same here 🙁
If your running your console from a sccm server, make sure the sccm client is upgraded to the 1902 version i.e. 5.00.8790.1007 , when i upgraded to 1902 i didnt upgrade the agents on the sccm management servers at the same time , then when they restarted the sms agent host would not start , until i also upgraded the sccm client on them as well – source files will be located here Program Files\Microsoft Configuration Manager\StagingClient
I never observed the SCCM documentation in the console. Thanks Prajwal for the post.
Can SCCM 1902 installed on Windows Server 2019 ??. Please confirm.
Yes it can, we recently upgraded our environment to Server 2019, SQL 2017 onbox and SCCM 1902.
So far it’s working without issues.
Excellent post Prajwal. You are an asset to SCCM community. Keep adding such excellent posts.