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

Merged PR 13623: 1/08 AM Publish

Browse Source
This commit is contained in:
Huaping Yu (Beyondsoft Consulting Inc) 2019-01-08 18:30:07 +00:00
commit 69f8018b57
2 changed files with 38 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

41
windows/client-management/mdm/policy-csp-deviceinstallation.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: MariciaAlforque author: MariciaAlforque
ms.date: 12/14/2018 ms.date: 01/08/2019
--- ---
# Policy CSP - DeviceInstallation # Policy CSP - DeviceInstallation
@ -139,7 +139,7 @@ To enable this policy, use the following SyncML. This example allows Windows to
</SyncML> </SyncML>
``` ```
To verify the policies are applied properly, check C:\windows\INF\setupapi.dev.log and see if the following is listed near the end of the log: To verify the policy is applied, check C:\windows\INF\setupapi.dev.log and see if the following is listed near the end of the log:
```txt ```txt
>>> [Device Installation Restrictions Policy Check] >>> [Device Installation Restrictions Policy Check]
@ -256,7 +256,7 @@ Enclose the class GUID within curly brackets {}. To configure multiple classes,
</SyncML> </SyncML>
``` ```
To verify the policies are applied properly, check C:\windows\INF\setupapi.dev.log and see if the following is listed near the end of the log: To verify the policy is applied, check C:\windows\INF\setupapi.dev.log and see if the following is listed near the end of the log:
```txt ```txt
@ -339,6 +339,37 @@ ADMX Info:
<!--/Validation--> <!--/Validation-->
<!--/Policy--> <!--/Policy-->
To enable this policy, use the following SyncML. This example prevents Windows from retrieving device metadata.
``` syntax
<SyncML>
<SyncBody>
<Replace>
<CmdID>$CmdID$</CmdID>
<Item>
<Target>
<LocURI>./Device/Vendor/MSFT/Policy/Config/PreventInstallationOfDevicesNotDescribedByOtherPolicySettings</LocURI>
</Target>
<Meta>
<Format xmlns="syncml:metinf">integer</Format>
</Meta>
<Data><enabled/><Data id="1"/></Data>
</Item>
</Replace>
</SyncBody>
</SyncML>
```
To verify the policy is applied, check C:\windows\INF\setupapi.dev.log and see if the following is listed near the end of the log:
```txt
>>> [Device Installation Restrictions Policy Check]
>>> Section start 2018/11/15 12:26:41.659
<<< Section end 2018/11/15 12:26:41.751
<<< [Exit status: SUCCESS]
```
<hr/> <hr/>
<!--Policy--> <!--Policy-->
@ -499,7 +530,7 @@ To enable this policy, use the following SyncML. This example prevents Windows f
</SyncML> </SyncML>
``` ```
To verify the policies are applied properly, check C:\windows\INF\setupapi.dev.log and see if the following is listed near the end of the log: To verify the policy is applied, check C:\windows\INF\setupapi.dev.log and see if the following is listed near the end of the log:
```txt ```txt
>>> [Device Installation Restrictions Policy Check] >>> [Device Installation Restrictions Policy Check]
@ -599,7 +630,7 @@ Enclose the class GUID within curly brackets {}. To configure multiple classes,
</SyncML> </SyncML>
``` ```
To verify the policies are applied properly, check C:\windows\INF\setupapi.dev.log and see if the following is listed near the end of the log: To verify the policy is applied, check C:\windows\INF\setupapi.dev.log and see if the following is listed near the end of the log:
```txt ```txt
>>> [Device Installation Restrictions Policy Check] >>> [Device Installation Restrictions Policy Check]

4
windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control.md
View File

@ -8,7 +8,7 @@ ms.sitesec: library
ms.pagetype: security ms.pagetype: security
ms.localizationpriority: medium ms.localizationpriority: medium
author: jsuther1974 author: jsuther1974
ms.date: 11/28/2018 ms.date: 01/08/2019
--- ---
# Windows Defender Application Control # Windows Defender Application Control
@ -38,7 +38,7 @@ WDAC policies also block unsigned scripts and MSIs, and Windows PowerShell runs
## WDAC System Requirements ## WDAC System Requirements
WDAC policies can only be created on computers beginning with Windows 10 Enterprise or Professional editions or Windows Server 2016. WDAC policies can only be created on computers beginning with Windows 10 Enterprise or Professional editions or Windows Server 2016.
They can be applied to computers running any edition of Windows 10 or Windows Server 2016 and managed via Mobile Device Management (MDM), such as Microsoft Intune. They can be applied to computers running any edition of Windows 10 or Windows Server 2016 and optionally managed via Mobile Device Management (MDM), such as Microsoft Intune.
Group Policy or Intune can be used to distribute WDAC policies. Group Policy or Intune can be used to distribute WDAC policies.
## New and changed functionality ## New and changed functionality