microsoft system center configuration manager latest

For example, a client may still be marked as compliant when reporting different versions, one value in Client Version and a different value in Last Detail Message.Īn incorrect value for the client installation process is recorded in the Compliance Last Error column of device reporting for Assets and Compliance. The information reported in the Compliance Status, Client Version, and Last Detail Message values of the device compliance view in the Administrator Console are inconsistent. This update prevents this issue when you upgrade to version 1606 but does not re-select Windows 10 as a platform for any previously affected packages or task sequences. Windows 10 is deselected as a client platform in package and task sequence requirements after the upgrade to Configuration Manager current branch. You do not have permission to access this page Users who have the ConfigMgr Report Users role assigned will receive the following error message when they click the Subscribe link on a SQL Reporting Services report page: The Administrator Console may exit unexpectedly when you use the Group By option to reorder columns and then refresh the current view. Issues that are fixed Administrator Console For more information, see Checklist for installing update 1606 for System Center Configuration Manager.

Version 1606 is available as an in-console update to be installed at the top-most site in a hierarchy.

Many of these changes are the result of customer feedback on product issues and ideas for product improvement. The 'Issues that are fixed' list is not inclusive of all changes but instead captures what our product development team believes is most relevant to our broad customer base. Release version 1606 of System Center Configuration Manager Current Branch contains many changes that are intended to prevent issues and improve features. System Center Configuration Manager (current branch - version 1606) More.

Microsoft system center configuration manager latest