deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-18 11:53:37 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Merge pull request #4285 from RAJU2529/patch-14

Browse Source 
added  two new commands for  exporting and importing .xml files
This commit is contained in:
Beth Levin
2019-07-18 09:02:41 -07:00
committed by GitHub
parent 55debb0b6a 886b7cc6ad
commit 2a4be69b72
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
windows/security/threat-protection/windows-defender-exploit-guard/import-export-exploit-protection-emet-xml.md
View File

@ -70,6 +70,9 @@ 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
**Get-ProcessMitigation -RegistryConfigFilePath C:\ExploitConfigfile.xml**
> [!IMPORTANT] > [!IMPORTANT]
> When you deploy the configuration using Group Policy, all machines that will use the configuration must be able to access the configuration file. Ensure you place the file in a shared location. > When you deploy the configuration using Group Policy, all machines that will use the configuration must be able to access the configuration file. Ensure you place the file in a shared location.
@ -91,6 +94,10 @@ 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
**Set-ProcessMitigation -PolicyFilePath C:\ExploitConfigfile.xml**
>[!IMPORTANT] >[!IMPORTANT]
> >
>Ensure you import a configuration file that is created specifically for exploit protection. You cannot directly import an EMET configuration file, you must convert it first. >Ensure you import a configuration file that is created specifically for exploit protection. You cannot directly import an EMET configuration file, you must convert it first.
@ -151,6 +158,7 @@ You can use Group Policy to deploy the configuration you've created to multiple
- C:\MitigationSettings\Config.XML - C:\MitigationSettings\Config.XML
- \\\Server\Share\Config.xml - \\\Server\Share\Config.xml
- https://localhost:8080/Config.xml - https://localhost:8080/Config.xml
- C:\ExploitConfigfile.xml
8. Click **OK** and [Deploy the updated GPO as you normally do](https://msdn.microsoft.com/library/ee663280(v=vs.85).aspx). 8. Click **OK** and [Deploy the updated GPO as you normally do](https://msdn.microsoft.com/library/ee663280(v=vs.85).aspx).