Skip to content

Commit 7b26f42

Browse files
committed
Update enable-network-protection.md
1 parent fea5d7a commit 7b26f42

File tree

1 file changed

+20
-18
lines changed

1 file changed

+20
-18
lines changed

defender-endpoint/enable-network-protection.md

Lines changed: 20 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -207,24 +207,26 @@ Use the following procedure to enable network protection on domain-joined comput
207207

208208
7. From the ribbon, select **Deploy** to deploy the policy to a collection.
209209

210-
> [!IMPORTANT]
211-
> Once you deploy an Exploit Guard policy from Configuration Manager, the Exploit Guard settings will not be removed from the clients if you remove the deployment. `Delete not supported` is recorded in the Configuration Manager client's ExploitGuardHandler.log if you remove the client's Exploit Guard deployment. <!--CMADO8538577-->
212-
> The following PowerShell script can be run under SYSTEM context to remove these settings:<!--CMADO9907132-->
213-
>
214-
> ```powershell
215-
> $defenderObject = Get-WmiObject -Namespace "root/cimv2/mdm/dmmap" -Class "MDM_Policy_Config01_Defender02" -Filter "InstanceID='Defender' and ParentID='./Vendor/MSFT/Policy/Config'"
216-
> $defenderObject.AttackSurfaceReductionRules = $null
217-
> $defenderObject.AttackSurfaceReductionOnlyExclusions = $null
218-
> $defenderObject.EnableControlledFolderAccess = $null
219-
> $defenderObject.ControlledFolderAccessAllowedApplications = $null
220-
> $defenderObject.ControlledFolderAccessProtectedFolders = $null
221-
> $defenderObject.EnableNetworkProtection = $null
222-
> $defenderObject.Put()
223-
>
224-
> $exploitGuardObject = Get-WmiObject -Namespace "root/cimv2/mdm/dmmap" -Class "MDM_Policy_Config01_ExploitGuard02" -Filter "InstanceID='ExploitGuard' and ParentID='./Vendor/MSFT/Policy/Config'"
225-
> $exploitGuardObject.ExploitProtectionSettings = $null
226-
> $exploitGuardObject.Put()
227-
>```
210+
#### Important information about removing Exploit Guard settings from a device
211+
212+
Once an Exploit Guard policy is deployed using Configuration Manager, Exploit Guard settings aren't removed from the clients if you remove the deployment. Furthermore, if you remove the client's Exploit Guard deployment, `Delete not supported` is recorded in the client's `ExploitGuardHandler.log` in Configuration Manager. <!--CMADO8538577-->
213+
214+
Use the following PowerShell script in the SYSTEM context to remove Exploit Guard settings correctly:<!--CMADO9907132-->
215+
216+
```powershell
217+
$defenderObject = Get-WmiObject -Namespace "root/cimv2/mdm/dmmap" -Class "MDM_Policy_Config01_Defender02" -Filter "InstanceID='Defender' and ParentID='./Vendor/MSFT/Policy/Config'"
218+
$defenderObject.AttackSurfaceReductionRules = $null
219+
$defenderObject.AttackSurfaceReductionOnlyExclusions = $null
220+
$defenderObject.EnableControlledFolderAccess = $null
221+
$defenderObject.ControlledFolderAccessAllowedApplications = $null
222+
$defenderObject.ControlledFolderAccessProtectedFolders = $null
223+
$defenderObject.EnableNetworkProtection = $null
224+
$defenderObject.Put()
225+
226+
$exploitGuardObject = Get-WmiObject -Namespace "root/cimv2/mdm/dmmap" -Class "MDM_Policy_Config01_ExploitGuard02" -Filter "InstanceID='ExploitGuard' and ParentID='./Vendor/MSFT/Policy/Config'"
227+
$exploitGuardObject.ExploitProtectionSettings = $null
228+
$exploitGuardObject.Put()
229+
```
228230

229231
## See also
230232

0 commit comments

Comments
 (0)