Skip to content

Commit 9ff6606

Browse files
authored
Merge pull request #6950 from mestew/clientmsi
add managedinstaller client.msi property
2 parents 99c2ca1 + bed5a42 commit 9ff6606

1 file changed

Lines changed: 7 additions & 1 deletion

File tree

memdocs/configmgr/core/clients/deploy/about-client-installation-properties.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Client installation parameters and properties
33
titleSuffix: Configuration Manager
44
description: Learn about the ccmsetup command-line parameters and properties for installing the Configuration Manager client.
5-
ms.date: 02/16/2022
5+
ms.date: 03/03/2022
66
ms.prod: configuration-manager
77
ms.technology: configmgr-client
88
ms.topic: reference
@@ -606,6 +606,12 @@ If you set this property to `TRUE`, the client installer doesn't check the minim
606606
607607
Example: `CCMSetup.exe IGNOREAPPVVERSIONCHECK=TRUE`
608608
609+
### `MANAGEDINSTALLER`
610+
611+
If you set this property to `1` then ccmsetup.exe and client.msi are set as managed installers. For more information, see [Automatically allow apps deployed by a managed installer with Windows Defender Application Control](/windows/security/threat-protection/windows-defender-application-control/configure-authorized-apps-deployed-with-a-managed-installer).
612+
613+
Example: `CCMSetup.exe MANGEDINSTALLER=1`
614+
609615
### `NOTIFYONLY`
610616
611617
When you enable this property, the client reports status, but doesn't remediate problems that it finds.

0 commit comments

Comments
 (0)