deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-13 13:57:22 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Indented content in list items, added missing end punctuation

Browse Source
This commit is contained in:
Gary Moore 2020-04-20 16:35:23 -07:00 committed by GitHub
parent 127ca6c050
commit 58f802b84e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 18 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
windows/security/threat-protection/microsoft-defender-atp/import-export-exploit-protection-emet-xml.md
View File

@ -59,11 +59,11 @@ When you have configured exploit protection to your desired state (including bot
![Highlight of the Export Settings option](../images/wdsc-exp-prot-export.png) ![Highlight of the Export Settings option](../images/wdsc-exp-prot-export.png)
> [!NOTE] > [!NOTE]
> When you export the settings, all settings for both app-level and system-level mitigations are saved. This means you don't need to export a file from both the **System settings** and **Program settings** sections - either section will export all settings. > When you export the settings, all settings for both app-level and system-level mitigations are saved. This means you don't need to export a file from both the **System settings** and **Program settings** sections—either section will export all settings.
### Use PowerShell to export a configuration file ### Use PowerShell to export a configuration file
1. Type **powershell** in the Start menu, right click **Windows PowerShell** and click **Run as administrator** 1. Type **powershell** in the Start menu, right click **Windows PowerShell** and click **Run as administrator**.
2. Enter the following cmdlet: 2. Enter the following cmdlet:
```PowerShell ```PowerShell
@ -72,7 +72,8 @@ When you have configured exploit protection to your desired state (including bot
Change `filename` to any name or location of your choosing. Change `filename` to any name or location of your choosing.
Example command Example command:
**Get-ProcessMitigation -RegistryConfigFilePath C:\ExploitConfigfile.xml** **Get-ProcessMitigation -RegistryConfigFilePath C:\ExploitConfigfile.xml**
> [!IMPORTANT] > [!IMPORTANT]
@ -86,7 +87,7 @@ After importing, the settings will be instantly applied and can be reviewed in t
### Use PowerShell to import a configuration file ### Use PowerShell to import a configuration file
1. Type **powershell** in the Start menu, right click **Windows PowerShell** and click **Run as administrator** 1. Type **powershell** in the Start menu, right click **Windows PowerShell** and click **Run as administrator**.
2. Enter the following cmdlet: 2. Enter the following cmdlet:
```PowerShell ```PowerShell
@ -95,7 +96,8 @@ After importing, the settings will be instantly applied and can be reviewed in t
Change `filename` to the location and name of the exploit protection XML file. Change `filename` to the location and name of the exploit protection XML file.
Example command Example command:
**Set-ProcessMitigation -PolicyFilePath C:\ExploitConfigfile.xml** **Set-ProcessMitigation -PolicyFilePath C:\ExploitConfigfile.xml**
> [!IMPORTANT] > [!IMPORTANT]
@ -116,7 +118,7 @@ You can only do this conversion in PowerShell.
> >
> You can then convert that file using the PowerShell cmdlet described here before importing the settings into Exploit protection. > You can then convert that file using the PowerShell cmdlet described here before importing the settings into Exploit protection.
1. Type **powershell** in the Start menu, right click **Windows PowerShell** and click **Run as administrator** 1. Type **powershell** in the Start menu, right click **Windows PowerShell** and click **Run as administrator**.
2. Enter the following cmdlet: 2. Enter the following cmdlet:
```PowerShell ```PowerShell