What’s new in ConfigMgr 1810 – Compressed Highlights

  1. To take advantage of new Configuration Manager features, first, update clients to the latest version. While new functionality appears in the Configuration Manager console when you update the site and console, the complete scenario isn’t functional until the client version is also the latest.
  2. Site system on Windows cluster node: The Configuration Manager setup process no longer blocks installation of the site server role on a computer with the Windows role for Failover Clustering. SQL Always On requires this role, so previously you couldn’t colocate the site database on the site server. 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.
  3. Pending system restart: This prerequisite check is now more resilient. It checks additional registry keys for Windows features.
  4. SQL change tracking cleanup: A new check if the site database has a backlog of SQL change tracking data.
  5. SQL Native Client version: This prerequisite check is updated for versions of SQL Native Client that support TLS 1.2. The minimum version is SQL 2012 SP4.
  6. Client notification actions now require the Notify Resource permission on the SMS_Collection class.
  7. Prefer distribution points over peers with the same subnet: By default, the management point prioritizes peer cache sources at the top of the list of content locations. This setting reverses that priority for clients that are in the same subnet as the peer cache source.
  8. Prefer cloud distribution points over distribution points: If you have a branch office with a faster internet link, you can now prioritize cloud content.
  9. 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 new rule is Upgrade peer cache sources to the latest version of the Configuration Manager client, and is part of the new Proactive Maintenance rule group. Pre-1806 clients can’t be used as a peer cache source for clients that run version 1806 or later. Select Take action to open a device view that displays the list of clients.
  10. When installing the Configuration Manager client, the ccmsetup process contacts the management point to locate the necessary content. Previously in this process the management point only returns distribution points in the client’s current boundary group. If no content is available, the setup process falls back to download content from the management point. There’s no option to fall back to distribution points in other boundary groups that might have the necessary content. Now the management point returns distribution points based on boundary group configuration.
  11. This release further simplifies the Configuration Manager client setup process for clients on the internet. The site publishes additional Azure Active Directory (Azure AD) information to the cloud management gateway (CMG). An Azure AD-joined client gets this information from the CMG during the ccmsetup process, using the same tenant to which it’s joined. This behavior further simplifies enrolling devices to co-management in an environment with more than one Azure AD tenant. Now the only two required ccmsetup properties are CCMHOSTNAME and SMSSiteCode.
  12. 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.
  13. The co-management dashboard is enhanced with the following more detailed information:
    1. The Co-management enrollment status tile includes additional states
    2. A new Co-management status tile with a funnel chart shows states of the enrollment process
    3. A new tile with counts of Enrollment errors
  14. Starting in version 1806, Configuration Manager supports deployment of the new Windows 10 app package (.msix) format. Now you can convert your existing Windows Installer (.msi) applications to the MSIX format.
  15. You can use Windows PowerShell scripts for detection methods on applications and settings in configuration items. When these scripts run on clients, the Configuration Manager client now calls PowerShell with the -NoProfile parameter. This option starts PowerShell without profiles.
  16. Windows Autopilot for existing devices, is now available with Windows 10, version 1809 or later. This new feature allows you to reimage and provision a Windows 7 device for Windows Autopilot user-driven mode using a single, native Configuration Manager task sequence.
  17. Now specify the drive that Configuration Manager uses when adding software updates to OS images and OS upgrade packages. This process can consume a large amount of disk space with temporary files, so this option gives you flexibility to select the drive to use.
  18. When a device runs a task sequence and needs to acquire content, it now uses boundary group behaviors similar to the Configuration Manager client.
  19. Driver packages now have additional metadata fields for Manufacturer and Model. Use these fields to tag driver packages with information to assist in general housekeeping, or to identify old and duplicate drivers that you can delete.
  20. Create phased deployments for software updates. Phased deployments allow you to orchestrate a coordinated, sequenced rollout of software based on customizable criteria and groups.
  21. The following client setting is in the Software Updates group to control the installation behavior of software updates in maintenance windows: Enable installation of updates in “All deployments” maintenance window when “Software update” maintenance window is available. By default, this option is No to keep consistent with the existing behavior. Change it to Yes to allow clients to use other available maintenance windows to install software updates.
  22. The product lifecycle dashboard now includes information for System Center 2012 Configuration Manager and laterThere’s also a new report, Lifecycle 05A – Product lifecycle dashboard. It includes similar information as the in-console dashboard. Which I have improved and updated here
  23. You can now synchronize more tables from the site database to the data warehouse. This change allows you to create more reports based on your business requirements.
  24. You can now specify the minimum authentication level for administrators to access Configuration Manager sites. This feature enforces administrators to sign in to Windows with the required level. To configure this setting, find the Authentication tab in the Hierarchy Settings.
  25. Use Support Center for client troubleshooting, real-time log viewing, or capturing the state of a Configuration Manager client computer for later analysis. Support Center is a single tool to combine many administrator troubleshooting tools. Find the Support Center installer on the site server in the cd.latest\SMSSETUP\Tools\SupportCenter folder.
  26. 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 dashboard includes the following tiles:
  27. 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.
  28. CMPivot includes the following improvements: Save Favorite queries. On the Query Summary tab, select the count of Failed or Offline devices, and then select the option to Create Collection.
  29. You can now view detailed script output in raw or structured JSON format. This formatting makes the output easier to read and analyze.
  30. The following performance and troubleshooting improvements apply to both CMPivot and scripts: Updated clients return output less than 80 KB to the site over a fast communication channel. This change increases the performance of viewing script or query output. Additional logs for troubleshooting.
  31. The on-premises MDM prerequisite to configure a Microsoft Intune subscription is no longer required. Your organization still requires Intune licenses to use this feature.

Don’t forget the following: