First published on CloudBlogs on Jun 20, 2016
Updated 4/5/2018 Starting with Configuration Manger current branch version 1702, the managed installer technology is automatically leveraged by Configuration Manager’s Device Guard policies. When client PCs receive these policies Configuration Manger is automatically configured as a managed installer and apps that it deploys are automatically trusted by locked-down devices. The component that installs and upgrades the Configuration Manager client, ccmsetup.exe , is also configured as a managed installer so that the Configuration Manager client can be seamlessly upgraded on locked-down devices. For additional information, please read Device Guard Management with Configuration Manager .
Updated 4/5/2018 Starting with Configuration Manger current branch version 1702, the managed installer technology is automatically leveraged by Configuration Manager’s Device Guard policies. When client PCs receive these policies Configuration Manger is automatically configured as a managed installer and apps that it deploys are automatically trusted by locked-down devices. The component that installs and upgrades the Configuration Manager client, ccmsetup.exe , is also configured as a managed installer so that the Configuration Manager client can be seamlessly upgraded on locked-down devices. For additional information, please read Device Guard Management with Configuration Manager .
Published Sep 08, 2018
Version 1.0Dune Desormeaux
Microsoft
Joined June 19, 2017
Security, Compliance, and Identity Blog
Follow this blog board to get notified when there's new activity