Microsoft released an update 1910 for Configuration Manager. This update is available as an in-console update and not a baseline version. You can apply this update on sites that run version 1806 (Min version 5.00.8692.0000) or later.
If you want to install a new Configuration Manager, then you must use the baseline version which is 1902 and then perform an in-console update to receive update 1910.
Recently, at Ignite 2019, Microsoft announced ,that they are integrating Microsoft Intune, Configuration Manager, and more into a single solution called Microsoft Endpoint Manager. For more information about Microsoft Endpoint Manager, please read here
The following Microsoft management solutions are all now part of the Microsoft Endpoint Manager brand:
- Configuration Manager
- Desktop Analytics
- Other features in the Device Management Admin Console
From this update 1910, system center configuration manager is changed to Microsoft Endpoint Configuration Manager and no more part of system center suite (MEMCM/MECM ,no #SCCM).
Configuration Manager console
Extend and migrate on-premises site to Microsoft Azure
Improvements to console search
At this time, update 1910 is released for the early update ring. To install this update via an in-console update, you need to opt-in.
How tp opt-in ?
Microsoft has released PowerShell script that helps you to get this update in your console using an early update ring.
Before you start updating your site, please read through the pre-requisites check for things like a supported version of ADK, SQL and others.
Once you validated the prerequisites checks and running on supported configuration, you can run the PowerShell script.
Download the Powershell script from Technet
Launch an elevated command prompt and run the enableearlyupdatering1910.ps1 script.
.\enableearlyupdatering1910.ps1 -site server CAS/Primary site name|IP address -Verbose
The command completed successfully.
If your sccm server has a service connection point with internet access, you will now see a 1910 update in the console.
If the update 1910 is applicable or not to your site, you can monitor hman.log
Once we know that, the update is applicable, we can now launch the console and download the update.
Lunch the SCCM Console, click administration bar and under updates and servicing, you will see 1910 with state ‘available to download’
If you are not seeing the update, force a check for the update by clicking click "Check for Updates" in the updates and servicing console.
Once the update is available, click on the update and choose download.
Monitor the download progress using log: dmpdownloader.log
Depending on your internet connectivity, download takes a while.
you can also monitor ConfigMgrSetup.log to see If the download finished successfully or not.
Now the update is downloaded and ready to install.
Here is a nice flowchart that explains how the in-console update installation and replication works. Please read through https://docs.microsoft.com/en-us/configmgr/core/servers/manage/update-replication-flowchart
Now right click on the update and run a prerequisite check before installing the update. This will help you to be in a ready state.
You can monitor the status by looking at the log or from monitoring \Monitoring\Overview\Updates and Servicing Status\Configuration Manager 1910
Once the prerequisite check is passed, we are now ready to install the update.
Right-click on update and choose to install update pack.
Choose the features that you are interested in. You can also enable them after the update.
Choose the pre-production collection(a subset of clients) to validate the client update before you take this to production (all clients)
Accept the license terms and click next to install the update.
There is a nice flowchart that explains how the in-console update download works.Please read through https://docs.microsoft.com/en-us/configmgr/core/servers/manage/download-updates-flowchart
We will now monitor the status from the console and from the log (cmupdate.log/ConfigMgrSetup.log)
\Monitoring\Overview\Updates and Servicing Status\Configuration Manager 1910
There will be a hidden package created for this update(PS10006) and save the content to the content library and replicate it to site servers ONLY (Primary).
The installation takes a while to finish.
After a while, you will see a notification in the console appear on top, a new version of the console is available. Click on install.
If you didn’t notice this and close the console, next time when you launch console, you will be prompted with new version of the console available.
You will see that the Microsoft Endpoint Configuration Manager console is installing.
Console version: 5.1910.1067.1300
Client Version: 5.00.8913.1006
And the re-brand of system center configuration manager is now Microsoft Endpoint Configuration Manager (#MEMCM/#MECM)
Installed application name in programs and features is changed to Microsoft Endpoint Configuration Manager Console with version:5.1910.1067.1000
If you have any collections created that look for console install, please change the installed application to Microsoft Endpoint Configuration Manager Console.
What things change in Configuration Manager with Microsoft Endpoint Manager?
In version 1910, aside from the name change, Configuration Manager still functions the same. Some of the name changes may impact your use of the following components:
- Configuration Manager console: Find shortcuts to the console and the Remote Control Viewer under the Windows Start menu in the Microsoft Endpoint folder.
- Software Center: Find the Software Center shortcut under the Windows Start menu in the Microsoft Endpoint Manager folder.
In the next blog post, I will talk about new features in MEMCM/MECM