Now you can specify the drive that Configuration Manager uses when adding software updates to OS images and OS upgrade packages.
When a device runs a task sequence and needs to acquire content, it now uses boundary group behaviors similar to the Configuration Manager client.
Driver packages now have additional metadata fields for Manufacturer and Model which can be used to tag driver packages for general housekeeping.
You can now create phased deployments for software updates. Phased deployments allow you to orchestrate a coordinated, sequenced rollout of software based on customizable criteria and groups.
The Management Insights node now includes a graphical dashboard. This dashboard displays an overview of the rule states, which makes it easier for you to show your progress.
The Management Insights node has a new rule to identify clients that serve as a peer cache source but haven’t upgraded from a pre-1806 client version.
The product lifecycle dashboard now includes information for System Center 2012 Configuration Manager and later.
This new native Configuration Manager task sequence allows you to reimage and re-provision an existing Windows 7 device into an AAD joined, co-managed Windows 10 using Windows Autopilot user-driven mode.
The co-management dashboard is enhanced with more detailed information about enrollment status.
You can now define compliance policy rules in Configuration Manager for required applications. This app assessment is part of the overall compliance state sent to Microsoft Intune for co-managed devices.
The SMS Provider now provides read-only API interoperability access to WMI over HTTPS.
The Configuration Manager setup process no longer blocks installation of the site server role on a computer with the Windows role for Failover Clustering. With this change, you can create a highly available site with fewer servers by using SQL Always On and a site server in passive mode.
You can now specify the minimum authentication level for administrators to access Configuration Manager sites.
CMPivot now allows you to save your favorite queries and create collections from the query summary tab. Over 100 new queryable entities added, including for extended hardware inventory properties. Additional improvements to performance.
You can now wake up clients from the Configuration Manager console, even if the client isn’t on the same subnet as the site server.
Boundary groups now include two new settings to give you more control over content distribution in your environment.
There are two changes to collection evaluation scheduling behavior that can improve site performance.
you can now configure email notifications for application approval requests.
You can now specify a repair command line for Windows Installer and Script Installer deployment types.
Now you can convert your existing Windows Installer (.msi) applications to the MSIX format.
You can now synchronize more tables from the site database to the data warehouse.
Use Support Center for client troubleshooting, real-time log viewing, or capturing the state of a Configuration Manager client computer for later analysis. Find the Support Center installer on the site server in the cd.latest\SMSSETUP\Tools\SupportCenter folder.
Configuration Manager now supports Windows Server 2019 and Windows Server, version 1809, as site systems.
As with any update, you should make sure that you have all the prerequisites to install this update to Configuration Manager, prior to starting the upgrade process.
These prerequisites to SCCM 1810 are;
On the Configuration Manager Updates Wizard, you can choose to Ignore any prerequisite check warnings and install this update regardless of missing requirements if you so wish.
As with any production environment, it’s always best case to never ignore any warnings, but we have had none in the previous check, so do not need to click this checkbox.
When you are ready to start the update process, click next.