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

Merge branch 'master' of https://cpubwin.visualstudio.com/_git/it-client into URStep2

Browse Source
This commit is contained in:
jaimeo 2017-08-31 13:16:07 -07:00
commit af37e10962
78 changed files with 709 additions and 696 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
windows/access-protection/images/rdp-to-a-server-without-windows-defender-remote-credential-guard.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 15 KiB

BIN
windows/access-protection/images/windows-defender-remote-credential-guard-with-remote-admin-mode.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 26 KiB

130
windows/access-protection/remote-credential-guard.md
View File

@ -13,62 +13,108 @@ author: brianlic-msft
- Windows 10 - Windows 10
- Windows Server 2016 - Windows Server 2016
Introduced in Windows 10, version 1607, Windows Defender Remote Credential Guard helps you protect your credentials over a Remote Desktop connection by redirecting the Kerberos requests back to the device that's requesting the connection. It also provides single sign on experiences for Remote Desktop sessions. If the target device is compromised, your credentials are not exposed because both credential and credential derivatives are never sent to the target device. Introduced in Windows 10, version 1607, Windows Defender Remote Credential Guard helps you protect your credentials over a Remote Desktop connection by redirecting Kerberos requests back to the device that's requesting the connection. It also provides single sign-on experiences for Remote Desktop sessions.
You can use Remote Credential Guard in the following ways: Administrator credentials are highly privileged and must be protected. By using Windows Defender Remote Credential Guard to connect during Remote Desktop sessions, if the target device is compromised, your credentials are not exposed because both credential and credential derivatives are never passed over the network to the target device.
- Administrator credentials are highly privileged and must be protected. By using Remote Credential Guard to connect, you can be assured that your credentials are not passed over the network to the target device. > [!IMPORTANT]
> For information on Remote Desktop connection scenarios involving helpdesk support, see [Remote Desktop connections and helpdesk support scenarios](#helpdesk) in this article.
- Helpdesk employees in your organization must connect to domain-joined devices that could be compromised. With Windows Defender Remote Credential Guard, the helpdesk employee can use RDP to connect to the target device without compromising their credentials to malware. <a id="comparing-remote-credential-guard-with-other-remote-desktop-connection-options"></a>
## Comparing Windows Defender Remote Credential Guard with a server protected with Credential Guard
Use the following diagrams to help understand how Windows Defender Remote Credential Guard works, what it helps protect against, and how it compares with using a server protected with Credential Guard. As the diagram shows, Windows Defender Remote Credential Guard blocks NTLM (allowing only Kerberos), prevents Pass the Hash, and prevents usage of a credential after disconnection.
![Windows Defender Remote Credential Guard](images/remote-credential-guard.png)
## Comparing Windows Defender Remote Credential Guard with other Remote Desktop connection options ## Comparing Windows Defender Remote Credential Guard with other Remote Desktop connection options
Use the following table to compare different security options for Remote Desktop connections. The following diagram helps you to understand how a standard Remote Desktop session to a server without Windows Defender Remote Credential Guard works:
> [!NOTE] ![RDP connection to a server without Windows Defender Remote Credential Guard.png](images/rdp-to-a-server-without-windows-defender-remote-credential-guard.png)
> This table compares different options than are shown in the previous diagram.
| Remote Desktop | Windows Defender Remote Credential Guard | Restricted Admin mode | <br />
|---|---|---|
| Protection: Provides **less protection** than other modes in this table. | Protection: Provides **moderate protection**, compared to other modes in this table. | Protection: Provides **the most protection** of the modes in this table. However, it also requires you to be in the local “Administrators” group on the remote computer. |
| Version support: The remote computer can be running **any operating system that supports credential delegation**, which was introduced in Windows Vista. | Version support: The remote computer must be running **at least Windows 10, version 1607, or Windows Server 2016**. | Version support: The remote computer must be running **at least patched Windows 7 or patched Windows Server 2008 R2**.<br><br>For more information about patches (software updates) related to Restricted Admin mode, see [Microsoft Security Advisory 2871997](https://technet.microsoft.com/library/security/2871997.aspx). |
| NA | Helps prevent:<br><br>- **Pass the Hash**<br>- Usage of a **credential after disconnection** | Prevents:<br><br>- **Pass the Hash**<br>- Usage of **domain identity during connection** |
| Credentials supported from the remote desktop client device:<br><br>- **Signed on** credentials<br>- **Supplied** credentials<br>- **Saved** credentials | Credentials supported from the remote desktop client device:<br><br>- **Signed on** credentials only | Credentials supported from the remote desktop client device:<br><br>- **Signed on** credentials<br>- **Supplied** credentials<br>- **Saved** credentials |
| Access: **Users allowed**, that is, members of remote desktop users group of remote host. | Access: **Users allowed**, that is, members of remote desktop users group of remote host. | Access: **Administrators only**, that is, only members in administrators group of remote host. |
| Network identity: Remote desktop session **connects to other resources as signed on user**. | Network identity: Remote desktop session **connects to other resources as signed on user**. | Network identity: Remote desktop session **connects to other resources as remote host’s identity**. |
| Multi-hop: From the remote desktop, you **can connect through Remote Desktop to another computer**. | Multi-hop: From the remote desktop, you **can connect through Remote Desktop to another computer**. | No multi-hop: From the remote desktop, you **cannot connect through Remote Desktop to another computer**. |
| Supported authentication protocol: **Any negotiable protocol**. | Supported authentication protocol: **Kerberos only**. | Supported authentication protocol: **Any negotiable protocol**. |
## Hardware and software requirements The following diagram helps you to understand how Windows Defender Remote Credential Guard works, what it helps to protect against, and compares it with the [Restricted Admin mode](http://social.technet.microsoft.com/wiki/contents/articles/32905.how-to-enable-restricted-admin-mode-for-remote-desktop.aspx) option:
To use Windows Defender Remote Credential Guard, the Remote Desktop client and server must meet the following requirements: ![Windows Defender Remote Credential Guard](images/windows-defender-remote-credential-guard-with-remote-admin-mode.png)
- In order to connect using credentials other than signed-in credentials, the Remote Desktop client device must be running at least Windows 10, version 1703. <br />
As illustrated, Windows Defender Remote Credential Guard blocks NTLM (allowing only Kerberos), prevents Pass-the-Hash (PtH) attacks, and also prevents use of credentials after disconnection.
<br />
<br />
Use the following table to compare different Remote Desktop connection security options:
<br />
<br />
|**Feature** | **Remote Desktop** | **Windows Defender Remote Credential Guard** | **Restricted Admin mode** |
|---|---|---|---|
| **Protection benefits** | Credentials on the server are not protected from Pass-the-Hash attacks. |User credentials remain on the client. An attacker can act on behalf of the user *only* when the session is ongoing | User logs on to the server as local administrator, so an attacker cannot act on behalf of the “domain user”. Any attack is local to the server|
| **Version support** | The remote computer can run any Windows operating system|Both the client and the remote computer must be running **at least Windows 10, version 1607, or Windows Server 2016**.|The remote computer must be running **at least patched Windows 7 or patched Windows Server 2008 R2**. <br /><br />For more information about patches (software updates) related to Restricted Admin mode, see [Microsoft Security Advisory 2871997](https://technet.microsoft.com/library/security/2871997.aspx).
|**Helps prevent** &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; | &nbsp;&nbsp;&nbsp;&nbsp; N/A &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<ul><li> Pass-the-Hash</li> <li>Use of a credential after disconnection </li></ul>|<ul><li> Pass-the-Hash</li> <li>Use of domain identity during connection </li></ul>|
|**Credentials supported from the remote desktop client device**|<ul><li>**Signed on** credentials <li> **Supplied** credentials<li> **Saved** credentials </ul>|<ul><li> **Signed on** credentials only | <ul><li>**Signed on** credentials<li>**Supplied** credentials<li>**Saved** credentials</ul>
|**Access**|**Users allowed**, that is, members of Remote Desktop Users group of remote host.|**Users allowed**, that is, members of Remote Desktop Users of remote host.|**Administrators only**, that is, only members of Administrators group of remote host.
|**Network identity**|Remote Desktop session **connects to other resources as signed-in user**. | Remote Desktop session **connects to other resources as signed-in user**. |Remote Desktop session **connects to other resources as remote host’s identity**.|
|**Multi-hop**|From the remote desktop, **you can connect through Remote Desktop to another computer** | From the remote desktop, you **can connect through Remote Desktop to another computer**.|Not allowed for user as the session is running as a local host account|
|**Supported authentication** |Any negotiable protocol.| Kerberos only.|Any negotiable protocol|
<br />
For further technical information, see [Remote Desktop Protocol](https://msdn.microsoft.com/library/aa383015(v=vs.85).aspx)
and [How Kerberos works](https://technet.microsoft.com/en-us/library/cc961963.aspx(d=robot))
<br />
<a id="helpdesk"></a>
## Remote Desktop connections and helpdesk support scenarios
For helpdesk support scenarios in which personnel require administrative access to provide remote assistance to computer users via Remote Desktop sessions, Microsoft recommends that Windows Defender Remote Credential Guard should not be used in that context. This is because if an RDP session is initiated to a compromised client that an attacker already controls, the attacker could use that open channel to create sessions on the user's behalf (without compromising credentials) to access any of the user’s resources for a limited time (a few hours) after the session disconnects.
Therefore, we recommend instead that you use the Restricted Admin mode option. For helpdesk support scenarios, RDP connections should only be initiated using the /RestrictedAdmin switch. This helps ensure that credentials and other user resources are not exposed to compromised remote hosts. For more information, see [Mitigating Pass-the-Hash and Other Credential Theft v2](http://download.microsoft.com/download/7/7/A/77ABC5BD-8320-41AF-863C-6ECFB10CB4B9/Mitigating-Pass-the-Hash-Attacks-and-Other-Credential-Theft-Version-2.pdf).
To further harden security, we also recommend that you implement Local Administrator Password Solution (LAPS), a Group Policy client-side extension (CSE) introduced in Windows 8.1 that automates local administrator password management. LAPS mitigates the risk of lateral escalation and other cyberattacks facilitated when customers use the same administrative local account and password combination on all their computers. You can download and install LAPS [here](https://www.microsoft.com/en-us/download/details.aspx?id=46899).
For further information on LAPS, see [Microsoft Security Advisory 3062591](https://technet.microsoft.com/en-us/library/security/3062591.aspx).
<a id="reqs"></a>
## Remote Credential Guard requirements
To use Windows Defender Remote Credential Guard, the Remote Desktop client and remote host must meet the following requirements:
The Remote Desktop client device:
- Must be running at least Windows 10, version 1703 to be able to supply credentials.
- Must be running at least Windows 10, version 1607 or Windows Server 2016 to use the user’s signed-in credentials. This requires the user’s account be able to sign in to both the client device and the remote host.
- Must be running the Remote Desktop Classic Windows application. The Remote Desktop Universal Windows Platform application doesn't support Windows Defender Remote Credential Guard.
- Must use Kerberos authentication to connect to the remote host. If the client cannot connect to a domain controller, then RDP attempts to fall back to NTLM. Windows Defender Remote Credential Guard does not allow NTLM fallback because this would expose credentials to risk.
The Remote Desktop remote host:
- Must be running at least Windows 10, version 1607 or Windows Server 2016.
- Must allow Restricted Admin connections.
- Must allow the client’s domain user to access Remote Desktop connections.
- Must allow delegation of non-exportable credentials.
There are no hardware requirements for Windows Defender Remote Credential Guard.
> [!NOTE] > [!NOTE]
> Remote Desktop client devices running earlier versions, at minimum Windows 10 version 1607, only support signed-in credentials, so the client device must also be joined to an Active Directory domain. Both Remote Desktop client and server must either be joined to the same domain, or the Remote Desktop server can be joined to a domain that has a trust relationship to the client device's domain. > Remote Desktop client devices running earlier versions, at minimum Windows 10 version 1607, only support signed-in credentials, so the client device must also be joined to an Active Directory domain. Both Remote Desktop client and server must either be joined to the same domain, or the Remote Desktop server can be joined to a domain that has a trust relationship to the client device's domain.
- For Windows Defender Remote Credential Guard to be supported, the user must authenticate to the remote host using Kerberos authentication - For Windows Defender Remote Credential Guard to be supported, the user must authenticate to the remote host using Kerberos authentication.
- The remote host must be running at least Windows 10 version 1607, or Windows Server 2016. - The remote host must be running at least Windows 10 version 1607, or Windows Server 2016.
- The Remote Desktop classic Windows app is required. The Remote Desktop Universal Windows Platform app doesn't support Windows Defender Remote Credential Guard. - The Remote Desktop classic Windows app is required. The Remote Desktop Universal Windows Platform app doesn't support Windows Defender Remote Credential Guard.
## Enable Windows Defender Remote Credential Guard ## Enable Windows Defender Remote Credential Guard
You must enable Windows Defender Remote Credential Guard on the target device by using the registry. You must enable Restricted Admin or Windows Defender Remote Credential Guard on the remote host by using the Registry.
1. Open Registry Editor. 1. Open Registry Editor on the remote host.
2. Enable Windows Defender Remote Credential Guard: 2. Enable Restricted Admin and Windows Defender Remote Credential Guard:
- Go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa. - Go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa.
- Add a new DWORD value named **DisableRestrictedAdmin**. Set the value of this registry setting to 0 to turn on Windows Defender Remote Credential Guard. - Add a new DWORD value named **DisableRestrictedAdmin**.
- To turn on Restricted Admin and Windows Defender Remote Credential Guard, set the value of this registry setting to 0 to turn on Windows Defender Remote Credential Guard.
3. Close Registry Editor. 3. Close Registry Editor.
You can add this by running the following from an elevated command prompt: You can add this by running the following command from an elevated command prompt:
``` ```
reg add HKLM\SYSTEM\CurrentControlSet\Control\Lsa /v DisableRestrictedAdmin /d 0 /t REG_DWORD reg add HKLM\SYSTEM\CurrentControlSet\Control\Lsa /v DisableRestrictedAdmin /d 0 /t REG_DWORD
@ -76,7 +122,7 @@ reg add HKLM\SYSTEM\CurrentControlSet\Control\Lsa /v DisableRestrictedAdmin /d 0
## Using Windows Defender Remote Credential Guard ## Using Windows Defender Remote Credential Guard
You can use Windows Defender Remote Credential Guard on the client device by setting a Group Policy or by using a parameter with Remote Desktop Connection. Beginning with Windows 10 version 1703, you can enable Windows Defender Remote Credential Guard on the client device either by using Group Policy or by using a parameter with the Remote Desktop Connection.
### Turn on Windows Defender Remote Credential Guard by using Group Policy ### Turn on Windows Defender Remote Credential Guard by using Group Policy
@ -91,9 +137,9 @@ You can use Windows Defender Remote Credential Guard on the client device by set
> **Note:** Neither Windows Defender Remote Credential Guard nor Restricted Admin mode will send credentials in clear text to the Remote Desktop server. > **Note:** Neither Windows Defender Remote Credential Guard nor Restricted Admin mode will send credentials in clear text to the Remote Desktop server.
- If you want to require Windows Defender Remote Credential Guard, choose **Require Windows Defender Remote Credential Guard**. With this setting, a Remote Desktop connection will succeed only if the remote computer meets the [Hardware and software requirements](#hardware-and-software-requirements) listed earlier in this topic. - If you want to require Windows Defender Remote Credential Guard, choose **Require Windows Defender Remote Credential Guard**. With this setting, a Remote Desktop connection will succeed only if the remote computer meets the [requirements](#reqs) listed earlier in this topic.
- If you want to require Restricted Admin mode, choose **Require Restricted Admin**. For information about Restricted Admin mode, see the table in [Comparing Windows Defender Remote Credential Guard with other options for Remote Desktop connections](#comparing-remote-credential-guard-with-other-options-for-remote-desktop-connections), earlier in this topic. - If you want to require Restricted Admin mode, choose **Require Restricted Admin**. For information about Restricted Admin mode, see the table in [Comparing Windows Defender Remote Credential Guard with other Remote Desktop connection options](#comparing-remote-credential-guard-with-other-remote-desktop-connection-options), earlier in this topic.
4. Click **OK**. 4. Click **OK**.
@ -104,7 +150,7 @@ You can use Windows Defender Remote Credential Guard on the client device by set
### Use Windows Defender Remote Credential Guard with a parameter to Remote Desktop Connection ### Use Windows Defender Remote Credential Guard with a parameter to Remote Desktop Connection
If you don't use Group Policy in your organization, you can add the remoteGuard parameter when you start Remote Desktop Connection to turn on Windows Defender Remote Credential Guard for that connection. If you don't use Group Policy in your organization, or if not all your remote hosts support Remote Credential Guard, you can add the remoteGuard parameter when you start Remote Desktop Connection to turn on Windows Defender Remote Credential Guard for that connection.
``` ```
mstsc.exe /remoteGuard mstsc.exe /remoteGuard
@ -113,18 +159,12 @@ mstsc.exe /remoteGuard
## Considerations when using Windows Defender Remote Credential Guard ## Considerations when using Windows Defender Remote Credential Guard
- Windows Defender Remote Credential Guard does not include device claims. For example, if you’re trying to access a file server from the remote and the file server requires device claim, access will be denied. - Windows Defender Remote Credential Guard does not support compound authentication. For example, if you’re trying to access a file server from a remote host that requires a device claim, access will be denied.
- Windows Defender Remote Credential Guard cannot be used to connect to a device that is joined to Azure Active Directory. - Windows Defender Remote Credential Guard cannot be used to connect to a device that is not domain-joined to Active Directory, for example, remote hosts joined to Azure Active Directory.
- Remote Desktop Credential Guard only works with the RDP protocol. - Remote Desktop Credential Guard only works with the RDP protocol.
- No credentials are sent to the target device, but the target device still acquires the Kerberos Service Tickets on its own. - No credentials are sent to the target device, but the target device still acquires Kerberos Service Tickets on its own.
- Remote Desktop Gateway is not compatible with Windows Defender Remote Credential Guard.
- You cannot use saved credentials or credentials that are different than yours. You must use the credentials of the user who is logged into the device.
- Both the client and the server must be joined to the same domain or the domains must have a trust relationship.
- The server and client must authenticate using Kerberos. - The server and client must authenticate using Kerberos.

2
windows/client-management/mdm/policy-csp-abovelock.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - AboveLock # Policy CSP - AboveLock

2
windows/client-management/mdm/policy-csp-accounts.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - Accounts # Policy CSP - Accounts

4
windows/client-management/mdm/policy-csp-activexcontrols.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - ActiveXControls # Policy CSP - ActiveXControls
@ -64,7 +64,7 @@ Note: Wild card characters cannot be used when specifying the host URLs.
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Approved Installation Sites for ActiveX Controls* - GP English name: *Approved Installation Sites for ActiveX Controls*
- GP name: *ApprovedActiveXInstallSites* - GP name: *ApprovedActiveXInstallSites*
- GP path: *Windows Components/ActiveX Installer Service* - GP path: *Windows Components/ActiveX Installer Service*
- GP ADMX file name: *ActiveXInstallService.admx* - GP ADMX file name: *ActiveXInstallService.admx*

2
windows/client-management/mdm/policy-csp-applicationdefaults.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - ApplicationDefaults # Policy CSP - ApplicationDefaults

2
windows/client-management/mdm/policy-csp-applicationmanagement.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - ApplicationManagement # Policy CSP - ApplicationManagement

112
windows/client-management/mdm/policy-csp-appvirtualization.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - AppVirtualization # Policy CSP - AppVirtualization
@ -58,9 +58,9 @@ This policy setting allows you to enable or disable Microsoft Application Virtua
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Enable App-V Client* - GP English name: *Enable App-V Client*
- GP name: *EnableAppV* - GP name: *EnableAppV*
- GP path: *Administrative Templates/System/App-V* - GP path: *System/App-V*
- GP ADMX file name: *appv.admx* - GP ADMX file name: *appv.admx*
<!--EndADMX--> <!--EndADMX-->
@ -104,9 +104,9 @@ Enables Dynamic Virtualization of supported shell extensions, browser helper obj
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Enable Dynamic Virtualization* - GP English name: *Enable Dynamic Virtualization*
- GP name: *Virtualization_JITVEnable* - GP name: *Virtualization_JITVEnable*
- GP path: *Administrative Templates/System/App-V/Virtualization* - GP path: *System/App-V/Virtualization*
- GP ADMX file name: *appv.admx* - GP ADMX file name: *appv.admx*
<!--EndADMX--> <!--EndADMX-->
@ -150,9 +150,9 @@ Enables automatic cleanup of appv packages that were added after Windows10 anniv
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Enable automatic cleanup of unused appv packages* - GP English name: *Enable automatic cleanup of unused appv packages*
- GP name: *PackageManagement_AutoCleanupEnable* - GP name: *PackageManagement_AutoCleanupEnable*
- GP path: *Administrative Templates/System/App-V/PackageManagement* - GP path: *System/App-V/PackageManagement*
- GP ADMX file name: *appv.admx* - GP ADMX file name: *appv.admx*
<!--EndADMX--> <!--EndADMX-->
@ -196,9 +196,9 @@ Enables scripts defined in the package manifest of configuration files that shou
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Enable Package Scripts* - GP English name: *Enable Package Scripts*
- GP name: *Scripting_Enable_Package_Scripts* - GP name: *Scripting_Enable_Package_Scripts*
- GP path: *Administrative Templates/System/App-V/Scripting* - GP path: *System/App-V/Scripting*
- GP ADMX file name: *appv.admx* - GP ADMX file name: *appv.admx*
<!--EndADMX--> <!--EndADMX-->
@ -242,9 +242,9 @@ Enables a UX to display to the user when a publishing refresh is performed on th
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Enable Publishing Refresh UX* - GP English name: *Enable Publishing Refresh UX*
- GP name: *Enable_Publishing_Refresh_UX* - GP name: *Enable_Publishing_Refresh_UX*
- GP path: *Administrative Templates/System/App-V/Publishing* - GP path: *System/App-V/Publishing*
- GP ADMX file name: *appv.admx* - GP ADMX file name: *appv.admx*
<!--EndADMX--> <!--EndADMX-->
@ -298,9 +298,9 @@ Data Block Size: This value specifies the maximum size in bytes to transmit to t
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Reporting Server* - GP English name: *Reporting Server*
- GP name: *Reporting_Server_Policy* - GP name: *Reporting_Server_Policy*
- GP path: *Administrative Templates/System/App-V/Reporting* - GP path: *System/App-V/Reporting*
- GP ADMX file name: *appv.admx* - GP ADMX file name: *appv.admx*
<!--EndADMX--> <!--EndADMX-->
@ -344,9 +344,9 @@ Specifies the file paths relative to %userprofile% that do not roam with a user'
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Roaming File Exclusions* - GP English name: *Roaming File Exclusions*
- GP name: *Integration_Roaming_File_Exclusions* - GP name: *Integration_Roaming_File_Exclusions*
- GP path: *Administrative Templates/System/App-V/Integration* - GP path: *System/App-V/Integration*
- GP ADMX file name: *appv.admx* - GP ADMX file name: *appv.admx*
<!--EndADMX--> <!--EndADMX-->
@ -390,9 +390,9 @@ Specifies the registry paths that do not roam with a user profile. Example usage
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Roaming Registry Exclusions* - GP English name: *Roaming Registry Exclusions*
- GP name: *Integration_Roaming_Registry_Exclusions* - GP name: *Integration_Roaming_Registry_Exclusions*
- GP path: *Administrative Templates/System/App-V/Integration* - GP path: *System/App-V/Integration*
- GP ADMX file name: *appv.admx* - GP ADMX file name: *appv.admx*
<!--EndADMX--> <!--EndADMX-->
@ -436,9 +436,9 @@ Specifies how new packages should be loaded automatically by App-V on a specific
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Specify what to load in background (aka AutoLoad)* - GP English name: *Specify what to load in background (aka AutoLoad)*
- GP name: *Steaming_Autoload* - GP name: *Steaming_Autoload*
- GP path: *Administrative Templates/System/App-V/Streaming* - GP path: *System/App-V/Streaming*
- GP ADMX file name: *appv.admx* - GP ADMX file name: *appv.admx*
<!--EndADMX--> <!--EndADMX-->
@ -482,9 +482,9 @@ Migration mode allows the App-V client to modify shortcuts and FTA's for package
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Enable Migration Mode* - GP English name: *Enable Migration Mode*
- GP name: *Client_Coexistence_Enable_Migration_mode* - GP name: *Client_Coexistence_Enable_Migration_mode*
- GP path: *Administrative Templates/System/App-V/Client Coexistence* - GP path: *System/App-V/Client Coexistence*
- GP ADMX file name: *appv.admx* - GP ADMX file name: *appv.admx*
<!--EndADMX--> <!--EndADMX-->
@ -528,9 +528,9 @@ Specifies the location where symbolic links are created to the current version o
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Integration Root User* - GP English name: *Integration Root User*
- GP name: *Integration_Root_User* - GP name: *Integration_Root_User*
- GP path: *Administrative Templates/System/App-V/Integration* - GP path: *System/App-V/Integration*
- GP ADMX file name: *appv.admx* - GP ADMX file name: *appv.admx*
<!--EndADMX--> <!--EndADMX-->
@ -574,9 +574,9 @@ Specifies the location where symbolic links are created to the current version o
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Integration Root Global* - GP English name: *Integration Root Global*
- GP name: *Integration_Root_Global* - GP name: *Integration_Root_Global*
- GP path: *Administrative Templates/System/App-V/Integration* - GP path: *System/App-V/Integration*
- GP ADMX file name: *appv.admx* - GP ADMX file name: *appv.admx*
<!--EndADMX--> <!--EndADMX-->
@ -638,9 +638,9 @@ User Publishing Refresh Interval Unit: Specifies the interval unit (Hour 0-23, D
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Publishing Server 1 Settings* - GP English name: *Publishing Server 1 Settings*
- GP name: *Publishing_Server1_Policy* - GP name: *Publishing_Server1_Policy*
- GP path: *Administrative Templates/System/App-V/Publishing* - GP path: *System/App-V/Publishing*
- GP ADMX file name: *appv.admx* - GP ADMX file name: *appv.admx*
<!--EndADMX--> <!--EndADMX-->
@ -704,7 +704,7 @@ User Publishing Refresh Interval Unit: Specifies the interval unit (Hour 0-23, D
ADMX Info: ADMX Info:
- GP English name: *Publishing Server 2 Settings* - GP English name: *Publishing Server 2 Settings*
- GP name: *Publishing_Server2_Policy* - GP name: *Publishing_Server2_Policy*
- GP path: *Administrative Templates/System/App-V/Publishing* - GP path: *System/App-V/Publishing*
- GP ADMX file name: *appv.admx* - GP ADMX file name: *appv.admx*
<!--EndADMX--> <!--EndADMX-->
@ -766,9 +766,9 @@ User Publishing Refresh Interval Unit: Specifies the interval unit (Hour 0-23, D
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Publishing Server 3 Settings* - GP English name: *Publishing Server 3 Settings*
- GP name: *Publishing_Server3_Policy* - GP name: *Publishing_Server3_Policy*
- GP path: *Administrative Templates/System/App-V/Publishing* - GP path: *System/App-V/Publishing*
- GP ADMX file name: *appv.admx* - GP ADMX file name: *appv.admx*
<!--EndADMX--> <!--EndADMX-->
@ -830,9 +830,9 @@ User Publishing Refresh Interval Unit: Specifies the interval unit (Hour 0-23, D
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Publishing Server 4 Settings* - GP English name: *Publishing Server 4 Settings*
- GP name: *Publishing_Server4_Policy* - GP name: *Publishing_Server4_Policy*
- GP path: *Administrative Templates/System/App-V/Publishing* - GP path: *System/App-V/Publishing*
- GP ADMX file name: *appv.admx* - GP ADMX file name: *appv.admx*
<!--EndADMX--> <!--EndADMX-->
@ -894,9 +894,9 @@ User Publishing Refresh Interval Unit: Specifies the interval unit (Hour 0-23, D
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Publishing Server 5 Settings* - GP English name: *Publishing Server 5 Settings*
- GP name: *Publishing_Server5_Policy* - GP name: *Publishing_Server5_Policy*
- GP path: *Administrative Templates/System/App-V/Publishing* - GP path: *System/App-V/Publishing*
- GP ADMX file name: *appv.admx* - GP ADMX file name: *appv.admx*
<!--EndADMX--> <!--EndADMX-->
@ -940,9 +940,9 @@ Specifies the path to a valid certificate in the certificate store.
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Certificate Filter For Client SSL* - GP English name: *Certificate Filter For Client SSL*
- GP name: *Streaming_Certificate_Filter_For_Client_SSL* - GP name: *Streaming_Certificate_Filter_For_Client_SSL*
- GP path: *Administrative Templates/System/App-V/Streaming* - GP path: *System/App-V/Streaming*
- GP ADMX file name: *appv.admx* - GP ADMX file name: *appv.admx*
<!--EndADMX--> <!--EndADMX-->
@ -986,9 +986,9 @@ This setting controls whether virtualized applications are launched on Windows 8
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Allow First Time Application Launches if on a High Cost Windows 8 Metered Connection* - GP English name: *Allow First Time Application Launches if on a High Cost Windows 8 Metered Connection*
- GP name: *Streaming_Allow_High_Cost_Launch* - GP name: *Streaming_Allow_High_Cost_Launch*
- GP path: *Administrative Templates/System/App-V/Streaming* - GP path: *System/App-V/Streaming*
- GP ADMX file name: *appv.admx* - GP ADMX file name: *appv.admx*
<!--EndADMX--> <!--EndADMX-->
@ -1032,9 +1032,9 @@ Specifies the CLSID for a compatible implementation of the IAppvPackageLocationP
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Location Provider* - GP English name: *Location Provider*
- GP name: *Streaming_Location_Provider* - GP name: *Streaming_Location_Provider*
- GP path: *Administrative Templates/System/App-V/Streaming* - GP path: *System/App-V/Streaming*
- GP ADMX file name: *appv.admx* - GP ADMX file name: *appv.admx*
<!--EndADMX--> <!--EndADMX-->
@ -1078,9 +1078,9 @@ Specifies directory where all new applications and updates will be installed.
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Package Installation Root* - GP English name: *Package Installation Root*
- GP name: *Streaming_Package_Installation_Root* - GP name: *Streaming_Package_Installation_Root*
- GP path: *Administrative Templates/System/App-V/Streaming* - GP path: *System/App-V/Streaming*
- GP ADMX file name: *appv.admx* - GP ADMX file name: *appv.admx*
<!--EndADMX--> <!--EndADMX-->
@ -1124,9 +1124,9 @@ Overrides source location for downloading package content.
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Package Source Root* - GP English name: *Package Source Root*
- GP name: *Streaming_Package_Source_Root* - GP name: *Streaming_Package_Source_Root*
- GP path: *Administrative Templates/System/App-V/Streaming* - GP path: *System/App-V/Streaming*
- GP ADMX file name: *appv.admx* - GP ADMX file name: *appv.admx*
<!--EndADMX--> <!--EndADMX-->
@ -1170,9 +1170,9 @@ Specifies the number of seconds between attempts to reestablish a dropped sessio
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Reestablishment Interval* - GP English name: *Reestablishment Interval*
- GP name: *Streaming_Reestablishment_Interval* - GP name: *Streaming_Reestablishment_Interval*
- GP path: *Administrative Templates/System/App-V/Streaming* - GP path: *System/App-V/Streaming*
- GP ADMX file name: *appv.admx* - GP ADMX file name: *appv.admx*
<!--EndADMX--> <!--EndADMX-->
@ -1216,9 +1216,9 @@ Specifies the number of times to retry a dropped session.
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Reestablishment Retries* - GP English name: *Reestablishment Retries*
- GP name: *Streaming_Reestablishment_Retries* - GP name: *Streaming_Reestablishment_Retries*
- GP path: *Administrative Templates/System/App-V/Streaming* - GP path: *System/App-V/Streaming*
- GP ADMX file name: *appv.admx* - GP ADMX file name: *appv.admx*
<!--EndADMX--> <!--EndADMX-->
@ -1262,9 +1262,9 @@ Specifies that streamed package contents will be not be saved to the local hard
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Shared Content Store (SCS) mode* - GP English name: *Shared Content Store (SCS) mode*
- GP name: *Streaming_Shared_Content_Store_Mode* - GP name: *Streaming_Shared_Content_Store_Mode*
- GP path: *Administrative Templates/System/App-V/Streaming* - GP path: *System/App-V/Streaming*
- GP ADMX file name: *appv.admx* - GP ADMX file name: *appv.admx*
<!--EndADMX--> <!--EndADMX-->
@ -1308,9 +1308,9 @@ If enabled, the App-V client will support BrancheCache compatible HTTP streaming
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Enable Support for BranchCache* - GP English name: *Enable Support for BranchCache*
- GP name: *Streaming_Support_Branch_Cache* - GP name: *Streaming_Support_Branch_Cache*
- GP path: *Administrative Templates/System/App-V/Streaming* - GP path: *System/App-V/Streaming*
- GP ADMX file name: *appv.admx* - GP ADMX file name: *appv.admx*
<!--EndADMX--> <!--EndADMX-->
@ -1354,9 +1354,9 @@ Verifies Server certificate revocation status before streaming using HTTPS.
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Verify certificate revocation list* - GP English name: *Verify certificate revocation list*
- GP name: *Streaming_Verify_Certificate_Revocation_List* - GP name: *Streaming_Verify_Certificate_Revocation_List*
- GP path: *Administrative Templates/System/App-V/Streaming* - GP path: *System/App-V/Streaming*
- GP ADMX file name: *appv.admx* - GP ADMX file name: *appv.admx*
<!--EndADMX--> <!--EndADMX-->
@ -1400,9 +1400,9 @@ Specifies a list of process paths (may contain wildcards) which are candidates f
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Virtual Component Process Allow List* - GP English name: *Virtual Component Process Allow List*
- GP name: *Virtualization_JITVAllowList* - GP name: *Virtualization_JITVAllowList*
- GP path: *Administrative Templates/System/App-V/Virtualization* - GP path: *System/App-V/Virtualization*
- GP ADMX file name: *appv.admx* - GP ADMX file name: *appv.admx*
<!--EndADMX--> <!--EndADMX-->

8
windows/client-management/mdm/policy-csp-attachmentmanager.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - AttachmentManager # Policy CSP - AttachmentManager
@ -64,7 +64,7 @@ If you do not configure this policy setting, Windows marks file attachments with
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Do not preserve zone information in file attachments* - GP English name: *Do not preserve zone information in file attachments*
- GP name: *AM_MarkZoneOnSavedAtttachments* - GP name: *AM_MarkZoneOnSavedAtttachments*
- GP path: *Windows Components/Attachment Manager* - GP path: *Windows Components/Attachment Manager*
- GP ADMX file name: *AttachmentManager.admx* - GP ADMX file name: *AttachmentManager.admx*
@ -116,7 +116,7 @@ If you do not configure this policy setting, Windows hides the check box and Unb
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Hide mechanisms to remove zone information* - GP English name: *Hide mechanisms to remove zone information*
- GP name: *AM_RemoveZoneInfo* - GP name: *AM_RemoveZoneInfo*
- GP path: *Windows Components/Attachment Manager* - GP path: *Windows Components/Attachment Manager*
- GP ADMX file name: *AttachmentManager.admx* - GP ADMX file name: *AttachmentManager.admx*
@ -168,7 +168,7 @@ If you do not configure this policy setting, Windows does not call the registere
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Notify antivirus programs when opening attachments* - GP English name: *Notify antivirus programs when opening attachments*
- GP name: *AM_CallIOfficeAntiVirus* - GP name: *AM_CallIOfficeAntiVirus*
- GP path: *Windows Components/Attachment Manager* - GP path: *Windows Components/Attachment Manager*
- GP ADMX file name: *AttachmentManager.admx* - GP ADMX file name: *AttachmentManager.admx*

2
windows/client-management/mdm/policy-csp-authentication.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - Authentication # Policy CSP - Authentication

8
windows/client-management/mdm/policy-csp-autoplay.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - Autoplay # Policy CSP - Autoplay
@ -62,7 +62,7 @@ If you disable or do not configure this policy setting, AutoPlay is enabled for
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Disallow Autoplay for non-volume devices* - GP English name: *Disallow Autoplay for non-volume devices*
- GP name: *NoAutoplayfornonVolume* - GP name: *NoAutoplayfornonVolume*
- GP path: *Windows Components/AutoPlay Policies* - GP path: *Windows Components/AutoPlay Policies*
- GP ADMX file name: *AutoPlay.admx* - GP ADMX file name: *AutoPlay.admx*
@ -121,7 +121,7 @@ If you disable or not configure this policy setting, Windows Vista or later will
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Set the default behavior for AutoRun* - GP English name: *Set the default behavior for AutoRun*
- GP name: *NoAutorun* - GP name: *NoAutorun*
- GP path: *Windows Components/AutoPlay Policies* - GP path: *Windows Components/AutoPlay Policies*
- GP ADMX file name: *AutoPlay.admx* - GP ADMX file name: *AutoPlay.admx*
@ -181,7 +181,7 @@ Note: This policy setting appears in both the Computer Configuration and User Co
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Turn off Autoplay* - GP English name: *Turn off Autoplay*
- GP name: *Autorun* - GP name: *Autorun*
- GP path: *Windows Components/AutoPlay Policies* - GP path: *Windows Components/AutoPlay Policies*
- GP ADMX file name: *AutoPlay.admx* - GP ADMX file name: *AutoPlay.admx*

6
windows/client-management/mdm/policy-csp-bitlocker.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - Bitlocker # Policy CSP - Bitlocker
@ -85,6 +85,7 @@ ms.date: 08/09/2017
<a href="./bitlocker-csp.md#systemdrivesrequirestartupauthentication" id="systemdrivesrequirestartupauthentication">BitLocker/SystemDrivesRequireStartupAuthentication</a> <a href="./bitlocker-csp.md#systemdrivesrequirestartupauthentication" id="systemdrivesrequirestartupauthentication">BitLocker/SystemDrivesRequireStartupAuthentication</a>
</dd> </dd>
</dl> </dl>
<!--EndDescription--> <!--EndDescription-->
<!--EndPolicy--> <!--EndPolicy-->
<hr/> <hr/>
@ -95,4 +96,5 @@ Footnote:
- 2 - Added in Windows 10, version 1703. - 2 - Added in Windows 10, version 1703.
- 3 - Added in Windows 10, version 1709. - 3 - Added in Windows 10, version 1709.
<!--EndPolicies--> <!--EndPolicies-->

2
windows/client-management/mdm/policy-csp-bluetooth.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - Bluetooth # Policy CSP - Bluetooth

27
windows/client-management/mdm/policy-csp-browser.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/25/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - Browser # Policy CSP - Browser
@ -684,29 +684,6 @@ By default, the Microsoft compatibility list is enabled and can be viewed by vis
<!--StartPolicy--> <!--StartPolicy-->
<a href="" id="browser-alwaysenablebookslibrary"></a>**Browser/AlwaysEnableBooksLibrary** <a href="" id="browser-alwaysenablebookslibrary"></a>**Browser/AlwaysEnableBooksLibrary**
<!--StartSKU-->
<table>
<tr>
<th>Home</th>
<th>Pro</th>
<th>Business</th>
<th>Enterprise</th>
<th>Education</th>
<th>Mobile</th>
<th>Mobile Enterprise</th>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
</table>
<!--EndSKU-->
<!--StartDescription--> <!--StartDescription-->
<p style="margin-left: 20px"> <p style="margin-left: 20px">
@ -1311,7 +1288,7 @@ Employees cannot remove these search engines, but they can set any one as the de
<p style="margin-left: 20px">If you disable or don't configure this setting, employees will see the favorites they set in the Hub and Favorites Bar. <p style="margin-left: 20px">If you disable or don't configure this setting, employees will see the favorites they set in the Hub and Favorites Bar.
<p style="margin-left: 20px">Data type is string. <p style="margin-left: 20px">Data type is string.
<!--EndDescription--> <!--EndDescription-->
<!--EndPolicy--> <!--EndPolicy-->

2
windows/client-management/mdm/policy-csp-camera.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - Camera # Policy CSP - Camera

4
windows/client-management/mdm/policy-csp-cellular.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - Cellular # Policy CSP - Cellular
@ -56,7 +56,7 @@ ms.date: 08/09/2017
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Set Per-App Cellular Access UI Visibility* - GP English name: *Set Per-App Cellular Access UI Visibility*
- GP name: *ShowAppCellularAccessUI* - GP name: *ShowAppCellularAccessUI*
- GP path: *Network/WWAN Service/WWAN UI Settings* - GP path: *Network/WWAN Service/WWAN UI Settings*
- GP ADMX file name: *wwansvc.admx* - GP ADMX file name: *wwansvc.admx*

15
windows/client-management/mdm/policy-csp-connectivity.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - Connectivity # Policy CSP - Connectivity
@ -386,8 +386,9 @@ ms.date: 08/09/2017
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Turn off printing over HTTP* - GP English name: *Turn off printing over HTTP*
- GP name: *DisableHTTPPrinting_2* - GP name: *DisableHTTPPrinting_2*
- GP path: *Internet Communication settings*
- GP ADMX file name: *ICM.admx* - GP ADMX file name: *ICM.admx*
<!--EndADMX--> <!--EndADMX-->
@ -429,8 +430,9 @@ ADMX Info:
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Turn off downloading of print drivers over HTTP* - GP English name: *Turn off downloading of print drivers over HTTP*
- GP name: *DisableWebPnPDownload_2* - GP name: *DisableWebPnPDownload_2*
- GP path: *Internet Communication settings*
- GP ADMX file name: *ICM.admx* - GP ADMX file name: *ICM.admx*
<!--EndADMX--> <!--EndADMX-->
@ -472,8 +474,9 @@ ADMX Info:
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Turn off Internet download for Web publishing and online ordering wizards* - GP English name: *Turn off Internet download for Web publishing and online ordering wizards*
- GP name: *ShellPreventWPWDownload_2* - GP name: *ShellPreventWPWDownload_2*
- GP path: *Internet Communication settings*
- GP ADMX file name: *ICM.admx* - GP ADMX file name: *ICM.admx*
<!--EndADMX--> <!--EndADMX-->
@ -519,7 +522,7 @@ If you enable this policy, Windows only allows access to the specified UNC paths
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Hardened UNC Paths* - GP English name: *Hardened UNC Paths*
- GP name: *Pol_HardenedPaths* - GP name: *Pol_HardenedPaths*
- GP path: *Network/Network Provider* - GP path: *Network/Network Provider*
- GP ADMX file name: *networkprovider.admx* - GP ADMX file name: *networkprovider.admx*
@ -563,7 +566,7 @@ ADMX Info:
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Prohibit installation and configuration of Network Bridge on your DNS domain network* - GP English name: *Prohibit installation and configuration of Network Bridge on your DNS domain network*
- GP name: *NC_AllowNetBridge_NLA* - GP name: *NC_AllowNetBridge_NLA*
- GP path: *Network/Network Connections* - GP path: *Network/Network Connections*
- GP ADMX file name: *NetworkConnections.admx* - GP ADMX file name: *NetworkConnections.admx*

8
windows/client-management/mdm/policy-csp-credentialproviders.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - CredentialProviders # Policy CSP - CredentialProviders
@ -66,8 +66,9 @@ To configure Windows Hello for Business, use the Administrative Template policie
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Turn on convenience PIN sign-in* - GP English name: *Turn on convenience PIN sign-in*
- GP name: *AllowDomainPINLogon* - GP name: *AllowDomainPINLogon*
- GP path: *System/Logon*
- GP ADMX file name: *credentialproviders.admx* - GP ADMX file name: *credentialproviders.admx*
<!--EndADMX--> <!--EndADMX-->
@ -117,8 +118,9 @@ Note that the user's domain password will be cached in the system vault when usi
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Turn off picture password sign-in* - GP English name: *Turn off picture password sign-in*
- GP name: *BlockDomainPicturePassword* - GP name: *BlockDomainPicturePassword*
- GP path: *System/Logon*
- GP ADMX file name: *credentialproviders.admx* - GP ADMX file name: *credentialproviders.admx*
<!--EndADMX--> <!--EndADMX-->

6
windows/client-management/mdm/policy-csp-credentialsui.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - CredentialsUI # Policy CSP - CredentialsUI
@ -66,7 +66,7 @@ The policy applies to all Windows components and applications that use the Windo
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Do not display the password reveal button* - GP English name: *Do not display the password reveal button*
- GP name: *DisablePasswordReveal* - GP name: *DisablePasswordReveal*
- GP path: *Windows Components/Credential User Interface* - GP path: *Windows Components/Credential User Interface*
- GP ADMX file name: *credui.admx* - GP ADMX file name: *credui.admx*
@ -116,7 +116,7 @@ If you disable this policy setting, users will always be required to type a user
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Enumerate administrator accounts on elevation* - GP English name: *Enumerate administrator accounts on elevation*
- GP name: *EnumerateAdministrators* - GP name: *EnumerateAdministrators*
- GP path: *Windows Components/Credential User Interface* - GP path: *Windows Components/Credential User Interface*
- GP ADMX file name: *credui.admx* - GP ADMX file name: *credui.admx*

2
windows/client-management/mdm/policy-csp-cryptography.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - Cryptography # Policy CSP - Cryptography

2
windows/client-management/mdm/policy-csp-dataprotection.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - DataProtection # Policy CSP - DataProtection

6
windows/client-management/mdm/policy-csp-datausage.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - DataUsage # Policy CSP - DataUsage
@ -68,7 +68,7 @@ If this policy setting is disabled or is not configured, the cost of 3G connecti
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Set 3G Cost* - GP English name: *Set 3G Cost*
- GP name: *SetCost3G* - GP name: *SetCost3G*
- GP path: *Network/WWAN Service/WWAN Media Cost* - GP path: *Network/WWAN Service/WWAN Media Cost*
- GP ADMX file name: *wwansvc.admx* - GP ADMX file name: *wwansvc.admx*
@ -124,7 +124,7 @@ If this policy setting is disabled or is not configured, the cost of 4G connecti
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Set 4G Cost* - GP English name: *Set 4G Cost*
- GP name: *SetCost4G* - GP name: *SetCost4G*
- GP path: *Network/WWAN Service/WWAN Media Cost* - GP path: *Network/WWAN Service/WWAN Media Cost*
- GP ADMX file name: *wwansvc.admx* - GP ADMX file name: *wwansvc.admx*

138
windows/client-management/mdm/policy-csp-defender.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - Defender # Policy CSP - Defender
@ -740,6 +740,74 @@ Value type is string.
> [!Note] > [!Note]
> This feature depends on three other MAPS settings the must all be enabled- "Configure the 'Block at First Sight' feature; "Join Microsoft MAPS"; "Send file samples when further analysis is required". > This feature depends on three other MAPS settings the must all be enabled- "Configure the 'Block at First Sight' feature; "Join Microsoft MAPS"; "Send file samples when further analysis is required".
<!--EndDescription-->
<!--EndPolicy-->
<!--StartPolicy-->
<a href="" id="defender-controlledfolderaccessallowedapplications"></a>**Defender/ControlledFolderAccessAllowedApplications**
<!--StartSKU-->
<table>
<tr>
<th>Home</th>
<th>Pro</th>
<th>Business</th>
<th>Enterprise</th>
<th>Education</th>
<th>Mobile</th>
<th>Mobile Enterprise</th>
</tr>
<tr>
<td><img src="images/crossmark.png" alt="cross mark" /></td>
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
<td><img src="images/crossmark.png" alt="cross mark" /></td>
<td><img src="images/crossmark.png" alt="cross mark" /></td>
</tr>
</table>
<!--EndSKU-->
<!--StartDescription-->
> [!NOTE]
> This policy is only enforced in Windows 10 for desktop. The previous name was GuardedFoldersAllowedApplications and changed to ControlledFolderAccessAllowedApplications.
<p style="margin-left: 20px">Added in Windows 10, version 1709. This policy setting allows user-specified applications to the guard my folders feature. Adding an allowed application means the guard my folders feature will allow the application to modify or delete content in certain folders such as My Documents. In most cases it will not be necessary to add entries. Windows Defender Antivirus will automatically detect and dynamically add applications that are friendly. Value type is string. Use the Unicode &#xF000; as the substring separator.
<!--EndDescription-->
<!--EndPolicy-->
<!--StartPolicy-->
<a href="" id="defender-controlledfolderaccessprotectedfolders"></a>**Defender/ControlledFolderAccessProtectedFolders**
<!--StartSKU-->
<table>
<tr>
<th>Home</th>
<th>Pro</th>
<th>Business</th>
<th>Enterprise</th>
<th>Education</th>
<th>Mobile</th>
<th>Mobile Enterprise</th>
</tr>
<tr>
<td><img src="images/crossmark.png" alt="cross mark" /></td>
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
<td><img src="images/crossmark.png" alt="cross mark" /></td>
<td><img src="images/crossmark.png" alt="cross mark" /></td>
</tr>
</table>
<!--EndSKU-->
<!--StartDescription-->
> [!NOTE]
> This policy is only enforced in Windows 10 for desktop. The previous name was GuardedFoldersList and changed to ControlledFolderAccessProtectedFolders.
<p style="margin-left: 20px">Added in Windows 10, version 1709. This policy settings allows adding user-specified folder locations to the guard my folders feature. These folders will complement the system defined folders such as My Documents and My Pictures. The list of system folders will be displayed in the user interface and can not be changed. Value type is string. Use the Unicode &#xF000; as the substring separator.
<!--EndDescription--> <!--EndDescription-->
<!--EndPolicy--> <!--EndPolicy-->
<!--StartPolicy--> <!--StartPolicy-->
@ -974,74 +1042,6 @@ Value type is string.
   
<p style="margin-left: 20px">Each file type must be separated by a **|**. For example, "C:\\Example.exe|C:\\Example1.exe". <p style="margin-left: 20px">Each file type must be separated by a **|**. For example, "C:\\Example.exe|C:\\Example1.exe".
<!--EndDescription-->
<!--EndPolicy-->
<!--StartPolicy-->
<a href="" id="defender-controlledfolderaccessallowedapplications"></a>**Defender/ControlledFolderAccessAllowedApplications**
<!--StartSKU-->
<table>
<tr>
<th>Home</th>
<th>Pro</th>
<th>Business</th>
<th>Enterprise</th>
<th>Education</th>
<th>Mobile</th>
<th>Mobile Enterprise</th>
</tr>
<tr>
<td><img src="images/crossmark.png" alt="cross mark" /></td>
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
<td><img src="images/crossmark.png" alt="cross mark" /></td>
<td><img src="images/crossmark.png" alt="cross mark" /></td>
</tr>
</table>
<!--EndSKU-->
<!--StartDescription-->
> [!NOTE]
> This policy is only enforced in Windows 10 for desktop. The previous name was GuardedFoldersAllowedApplications and changed to ControlledFolderAccessAllowedApplications.
<p style="margin-left: 20px">Added in Windows 10, version 1709. This policy setting allows user-specified applications to the guard my folders feature. Adding an allowed application means the guard my folders feature will allow the application to modify or delete content in certain folders such as My Documents. In most cases it will not be necessary to add entries. Windows Defender Antivirus will automatically detect and dynamically add applications that are friendly. Value type is string. Use the Unicode &#xF000; as the substring separator.
<!--EndDescription-->
<!--EndPolicy-->
<!--StartPolicy-->
<a href="" id="defender-controlledfolderaccessprotectedfolders"></a>**Defender/ControlledFolderAccessProtectedFolders**
<!--StartSKU-->
<table>
<tr>
<th>Home</th>
<th>Pro</th>
<th>Business</th>
<th>Enterprise</th>
<th>Education</th>
<th>Mobile</th>
<th>Mobile Enterprise</th>
</tr>
<tr>
<td><img src="images/crossmark.png" alt="cross mark" /></td>
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
<td><img src="images/crossmark.png" alt="cross mark" /></td>
<td><img src="images/crossmark.png" alt="cross mark" /></td>
</tr>
</table>
<!--EndSKU-->
<!--StartDescription-->
> [!NOTE]
> This policy is only enforced in Windows 10 for desktop. The previous name was GuardedFoldersList and changed to ControlledFolderAccessProtectedFolders.
<p style="margin-left: 20px">Added in Windows 10, version 1709. This policy settings allows adding user-specified folder locations to the guard my folders feature. These folders will complement the system defined folders such as My Documents and My Pictures. The list of system folders will be displayed in the user interface and can not be changed. Value type is string. Use the Unicode &#xF000; as the substring separator.
<!--EndDescription--> <!--EndDescription-->
<!--EndPolicy--> <!--EndPolicy-->
<!--StartPolicy--> <!--StartPolicy-->

2
windows/client-management/mdm/policy-csp-deliveryoptimization.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - DeliveryOptimization # Policy CSP - DeliveryOptimization

5
windows/client-management/mdm/policy-csp-desktop.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - Desktop # Policy CSP - Desktop
@ -62,8 +62,9 @@ If you enable this setting, users are unable to type a new location in the Targe
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Prohibit User from manually redirecting Profile Folders* - GP English name: *Prohibit User from manually redirecting Profile Folders*
- GP name: *DisablePersonalDirChange* - GP name: *DisablePersonalDirChange*
- GP path: *Desktop*
- GP ADMX file name: *desktop.admx* - GP ADMX file name: *desktop.admx*
<!--EndADMX--> <!--EndADMX-->

2
windows/client-management/mdm/policy-csp-deviceguard.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - DeviceGuard # Policy CSP - DeviceGuard

6
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: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - DeviceInstallation # Policy CSP - DeviceInstallation
@ -62,7 +62,7 @@ If you disable or do not configure this policy setting, devices can be installed
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Prevent installation of devices that match any of these device IDs* - GP English name: *Prevent installation of devices that match any of these device IDs*
- GP name: *DeviceInstall_IDs_Deny* - GP name: *DeviceInstall_IDs_Deny*
- GP path: *System/Device Installation/Device Installation Restrictions* - GP path: *System/Device Installation/Device Installation Restrictions*
- GP ADMX file name: *deviceinstallation.admx* - GP ADMX file name: *deviceinstallation.admx*
@ -112,7 +112,7 @@ If you disable or do not configure this policy setting, Windows can install and
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Prevent installation of devices using drivers that match these device setup classes* - GP English name: *Prevent installation of devices using drivers that match these device setup classes*
- GP name: *DeviceInstall_Classes_Deny* - GP name: *DeviceInstall_Classes_Deny*
- GP path: *System/Device Installation/Device Installation Restrictions* - GP path: *System/Device Installation/Device Installation Restrictions*
- GP ADMX file name: *deviceinstallation.admx* - GP ADMX file name: *deviceinstallation.admx*

4
windows/client-management/mdm/policy-csp-devicelock.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - DeviceLock # Policy CSP - DeviceLock
@ -767,7 +767,7 @@ If you enable this setting, users will no longer be able to modify slide show se
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Prevent enabling lock screen slide show* - GP English name: *Prevent enabling lock screen slide show*
- GP name: *CPL_Personalization_NoLockScreenSlideshow* - GP name: *CPL_Personalization_NoLockScreenSlideshow*
- GP path: *Control Panel/Personalization* - GP path: *Control Panel/Personalization*
- GP ADMX file name: *ControlPanelDisplay.admx* - GP ADMX file name: *ControlPanelDisplay.admx*

2
windows/client-management/mdm/policy-csp-display.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - Display # Policy CSP - Display

2
windows/client-management/mdm/policy-csp-education.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - Education # Policy CSP - Education

2
windows/client-management/mdm/policy-csp-enterprisecloudprint.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - EnterpriseCloudPrint # Policy CSP - EnterpriseCloudPrint

13
windows/client-management/mdm/policy-csp-errorreporting.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - ErrorReporting # Policy CSP - ErrorReporting
@ -72,8 +72,9 @@ If you disable or do not configure this policy setting, then the default consent
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Customize consent settings* - GP English name: *Customize consent settings*
- GP name: *WerConsentCustomize_2* - GP name: *WerConsentCustomize_2*
- GP path: *Windows Components/Windows Error Reporting/Consent*
- GP ADMX file name: *ErrorReporting.admx* - GP ADMX file name: *ErrorReporting.admx*
<!--EndADMX--> <!--EndADMX-->
@ -121,7 +122,7 @@ If you disable or do not configure this policy setting, the Turn off Windows Err
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Disable Windows Error Reporting* - GP English name: *Disable Windows Error Reporting*
- GP name: *WerDisable_2* - GP name: *WerDisable_2*
- GP path: *Windows Components/Windows Error Reporting* - GP path: *Windows Components/Windows Error Reporting*
- GP ADMX file name: *ErrorReporting.admx* - GP ADMX file name: *ErrorReporting.admx*
@ -175,7 +176,7 @@ See also the Configure Error Reporting policy setting.
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Display Error Notification* - GP English name: *Display Error Notification*
- GP name: *PCH_ShowUI* - GP name: *PCH_ShowUI*
- GP path: *Windows Components/Windows Error Reporting* - GP path: *Windows Components/Windows Error Reporting*
- GP ADMX file name: *ErrorReporting.admx* - GP ADMX file name: *ErrorReporting.admx*
@ -225,7 +226,7 @@ If you disable or do not configure this policy setting, then consent policy sett
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Do not send additional data* - GP English name: *Do not send additional data*
- GP name: *WerNoSecondLevelData_2* - GP name: *WerNoSecondLevelData_2*
- GP path: *Windows Components/Windows Error Reporting* - GP path: *Windows Components/Windows Error Reporting*
- GP ADMX file name: *ErrorReporting.admx* - GP ADMX file name: *ErrorReporting.admx*
@ -275,7 +276,7 @@ If you disable or do not configure this policy setting, Windows Error Reporting
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Prevent display of the user interface for critical errors* - GP English name: *Prevent display of the user interface for critical errors*
- GP name: *WerDoNotShowUI* - GP name: *WerDoNotShowUI*
- GP path: *Windows Components/Windows Error Reporting* - GP path: *Windows Components/Windows Error Reporting*
- GP ADMX file name: *ErrorReporting.admx* - GP ADMX file name: *ErrorReporting.admx*

10
windows/client-management/mdm/policy-csp-eventlogservice.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - EventLogService # Policy CSP - EventLogService
@ -64,7 +64,7 @@ Note: Old events may or may not be retained according to the "Backup log automat
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Control Event Log behavior when the log file reaches its maximum size* - GP English name: *Control Event Log behavior when the log file reaches its maximum size*
- GP name: *Channel_Log_Retention_1* - GP name: *Channel_Log_Retention_1*
- GP path: *Windows Components/Event Log Service/Application* - GP path: *Windows Components/Event Log Service/Application*
- GP ADMX file name: *eventlog.admx* - GP ADMX file name: *eventlog.admx*
@ -114,7 +114,7 @@ If you disable or do not configure this policy setting, the maximum size of the
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Specify the maximum log file size (KB)* - GP English name: *Specify the maximum log file size (KB)*
- GP name: *Channel_LogMaxSize_1* - GP name: *Channel_LogMaxSize_1*
- GP path: *Windows Components/Event Log Service/Application* - GP path: *Windows Components/Event Log Service/Application*
- GP ADMX file name: *eventlog.admx* - GP ADMX file name: *eventlog.admx*
@ -164,7 +164,7 @@ If you disable or do not configure this policy setting, the maximum size of the
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Specify the maximum log file size (KB)* - GP English name: *Specify the maximum log file size (KB)*
- GP name: *Channel_LogMaxSize_2* - GP name: *Channel_LogMaxSize_2*
- GP path: *Windows Components/Event Log Service/Security* - GP path: *Windows Components/Event Log Service/Security*
- GP ADMX file name: *eventlog.admx* - GP ADMX file name: *eventlog.admx*
@ -214,7 +214,7 @@ If you disable or do not configure this policy setting, the maximum size of the
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Specify the maximum log file size (KB)* - GP English name: *Specify the maximum log file size (KB)*
- GP name: *Channel_LogMaxSize_4* - GP name: *Channel_LogMaxSize_4*
- GP path: *Windows Components/Event Log Service/System* - GP path: *Windows Components/Event Log Service/System*
- GP ADMX file name: *eventlog.admx* - GP ADMX file name: *eventlog.admx*

2
windows/client-management/mdm/policy-csp-experience.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - Experience # Policy CSP - Experience

10
windows/client-management/mdm/policy-csp-exploitguard.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/29/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - ExploitGuard # Policy CSP - ExploitGuard
@ -14,6 +14,11 @@ ms.date: 08/29/2017
> [!WARNING] > [!WARNING]
> Some information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here. > Some information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
<!--StartPolicies-->
<hr/>
## ExploitGuard policies
<!--StartPolicy--> <!--StartPolicy-->
<a href="" id="exploitguard-exploitprotectionsettings"></a>**ExploitGuard/ExploitProtectionSettings** <a href="" id="exploitguard-exploitprotectionsettings"></a>**ExploitGuard/ExploitProtectionSettings**
@ -80,4 +85,5 @@ Footnote:
- 2 - Added in Windows 10, version 1703. - 2 - Added in Windows 10, version 1703.
- 3 - Added in Windows 10, version 1709. - 3 - Added in Windows 10, version 1709.
<!--EndPolicies--> <!--EndPolicies-->

2
windows/client-management/mdm/policy-csp-games.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - Games # Policy CSP - Games

504
windows/client-management/mdm/policy-csp-internetexplorer.md
View File

File diff suppressed because it is too large Load Diff

12
windows/client-management/mdm/policy-csp-kerberos.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - Kerberos # Policy CSP - Kerberos
@ -62,7 +62,7 @@ If you disable or do not configure this policy setting, the Kerberos client does
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Use forest search order* - GP English name: *Use forest search order*
- GP name: *ForestSearch* - GP name: *ForestSearch*
- GP path: *System/Kerberos* - GP path: *System/Kerberos*
- GP ADMX file name: *Kerberos.admx* - GP ADMX file name: *Kerberos.admx*
@ -111,7 +111,7 @@ If you disable or do not configure this policy setting, the client devices will
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Kerberos client support for claims, compound authentication and Kerberos armoring* - GP English name: *Kerberos client support for claims, compound authentication and Kerberos armoring*
- GP name: *EnableCbacAndArmor* - GP name: *EnableCbacAndArmor*
- GP path: *System/Kerberos* - GP path: *System/Kerberos*
- GP ADMX file name: *Kerberos.admx* - GP ADMX file name: *Kerberos.admx*
@ -165,7 +165,7 @@ If you disable or do not configure this policy setting, the client computers in
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Fail authentication requests when Kerberos armoring is not available* - GP English name: *Fail authentication requests when Kerberos armoring is not available*
- GP name: *ClientRequireFast* - GP name: *ClientRequireFast*
- GP path: *System/Kerberos* - GP path: *System/Kerberos*
- GP ADMX file name: *Kerberos.admx* - GP ADMX file name: *Kerberos.admx*
@ -215,7 +215,7 @@ If you disable or do not configure this policy setting, the Kerberos client requ
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Require strict KDC validation* - GP English name: *Require strict KDC validation*
- GP name: *ValidateKDC* - GP name: *ValidateKDC*
- GP path: *System/Kerberos* - GP path: *System/Kerberos*
- GP ADMX file name: *Kerberos.admx* - GP ADMX file name: *Kerberos.admx*
@ -269,7 +269,7 @@ Note: This policy setting configures the existing MaxTokenSize registry value in
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Set maximum Kerberos SSPI context token buffer size* - GP English name: *Set maximum Kerberos SSPI context token buffer size*
- GP name: *MaxTokenSize* - GP name: *MaxTokenSize*
- GP path: *System/Kerberos* - GP path: *System/Kerberos*
- GP ADMX file name: *Kerberos.admx* - GP ADMX file name: *Kerberos.admx*

2
windows/client-management/mdm/policy-csp-licensing.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - Licensing # Policy CSP - Licensing

82
windows/client-management/mdm/policy-csp-localpoliciessecurityoptions.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - LocalPoliciesSecurityOptions # Policy CSP - LocalPoliciesSecurityOptions
@ -672,46 +672,6 @@ Valid values:
- 0 - disabled - 0 - disabled
- 1 - enabled (allow system to be shut down without having to log on) - 1 - enabled (allow system to be shut down without having to log on)
Value type is integer. Supported operations are Add, Get, Replace, and Delete.
<!--EndDescription-->
<!--EndPolicy-->
<!--StartPolicy-->
<a href="" id="localpoliciessecurityoptions-useraccountcontrol-runalladministratorsinadminapprovalmode"></a>**LocalPoliciesSecurityOptions/UserAccountControl_RunAllAdministratorsInAdminApprovalMode**
<!--StartSKU-->
<table>
<tr>
<th>Home</th>
<th>Pro</th>
<th>Business</th>
<th>Enterprise</th>
<th>Education</th>
<th>Mobile</th>
<th>Mobile Enterprise</th>
</tr>
<tr>
<td><img src="images/crossmark.png" alt="cross mark" /></td>
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
<td><img src="images/crossmark.png" alt="cross mark" /></td>
<td><img src="images/crossmark.png" alt="cross mark" /></td>
</tr>
</table>
<!--EndSKU-->
<!--StartDescription-->
User Account Control: Turn on Admin Approval Mode
This policy setting controls the behavior of all User Account Control (UAC) policy settings for the computer. If you change this policy setting, you must restart your computer.
The options are:
- 0 - Disabled: Admin Approval Mode and all related UAC policy settings are disabled. Note: If this policy setting is disabled, the Security Center notifies you that the overall security of the operating system has been reduced.
- 1 - Enabled: (Default) Admin Approval Mode is enabled. This policy must be enabled and related UAC policy settings must also be set appropriately to allow the built-in Administrator account and all other users who are members of the Administrators group to run in Admin Approval Mode.
Value type is integer. Supported operations are Add, Get, Replace, and Delete. Value type is integer. Supported operations are Add, Get, Replace, and Delete.
<!--EndDescription--> <!--EndDescription-->
@ -931,6 +891,46 @@ The options are:
- 0 - Disabled: An application runs with UIAccess integrity even if it does not reside in a secure location in the file system. - 0 - Disabled: An application runs with UIAccess integrity even if it does not reside in a secure location in the file system.
- 1 - Enabled: (Default) If an application resides in a secure location in the file system, it runs only with UIAccess integrity. - 1 - Enabled: (Default) If an application resides in a secure location in the file system, it runs only with UIAccess integrity.
Value type is integer. Supported operations are Add, Get, Replace, and Delete.
<!--EndDescription-->
<!--EndPolicy-->
<!--StartPolicy-->
<a href="" id="localpoliciessecurityoptions-useraccountcontrol-runalladministratorsinadminapprovalmode"></a>**LocalPoliciesSecurityOptions/UserAccountControl_RunAllAdministratorsInAdminApprovalMode**
<!--StartSKU-->
<table>
<tr>
<th>Home</th>
<th>Pro</th>
<th>Business</th>
<th>Enterprise</th>
<th>Education</th>
<th>Mobile</th>
<th>Mobile Enterprise</th>
</tr>
<tr>
<td><img src="images/crossmark.png" alt="cross mark" /></td>
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
<td><img src="images/crossmark.png" alt="cross mark" /></td>
<td><img src="images/crossmark.png" alt="cross mark" /></td>
</tr>
</table>
<!--EndSKU-->
<!--StartDescription-->
User Account Control: Turn on Admin Approval Mode
This policy setting controls the behavior of all User Account Control (UAC) policy settings for the computer. If you change this policy setting, you must restart your computer.
The options are:
- 0 - Disabled: Admin Approval Mode and all related UAC policy settings are disabled. Note: If this policy setting is disabled, the Security Center notifies you that the overall security of the operating system has been reduced.
- 1 - Enabled: (Default) Admin Approval Mode is enabled. This policy must be enabled and related UAC policy settings must also be set appropriately to allow the built-in Administrator account and all other users who are members of the Administrators group to run in Admin Approval Mode.
Value type is integer. Supported operations are Add, Get, Replace, and Delete. Value type is integer. Supported operations are Add, Get, Replace, and Delete.
<!--EndDescription--> <!--EndDescription-->

2
windows/client-management/mdm/policy-csp-location.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - Location # Policy CSP - Location

2
windows/client-management/mdm/policy-csp-lockdown.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - LockDown # Policy CSP - LockDown

2
windows/client-management/mdm/policy-csp-maps.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - Maps # Policy CSP - Maps

2
windows/client-management/mdm/policy-csp-messaging.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - Messaging # Policy CSP - Messaging

2
windows/client-management/mdm/policy-csp-networkisolation.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - NetworkIsolation # Policy CSP - NetworkIsolation

2
windows/client-management/mdm/policy-csp-notifications.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - Notifications # Policy CSP - Notifications

20
windows/client-management/mdm/policy-csp-power.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - Power # Policy CSP - Power
@ -62,7 +62,7 @@ If you disable this policy setting, standby states (S1-S3) are not allowed.
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Allow standby states (S1-S3) when sleeping (plugged in)* - GP English name: *Allow standby states (S1-S3) when sleeping (plugged in)*
- GP name: *AllowStandbyStatesAC_2* - GP name: *AllowStandbyStatesAC_2*
- GP path: *System/Power Management/Sleep Settings* - GP path: *System/Power Management/Sleep Settings*
- GP ADMX file name: *power.admx* - GP ADMX file name: *power.admx*
@ -114,7 +114,7 @@ ADMX Info:
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Turn off the display (on battery)* - GP English name: *Turn off the display (on battery)*
- GP name: *VideoPowerDownTimeOutDC_2* - GP name: *VideoPowerDownTimeOutDC_2*
- GP path: *System/Power Management/Video and Display Settings* - GP path: *System/Power Management/Video and Display Settings*
- GP ADMX file name: *power.admx* - GP ADMX file name: *power.admx*
@ -166,7 +166,7 @@ ADMX Info:
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Turn off the display (plugged in)* - GP English name: *Turn off the display (plugged in)*
- GP name: *VideoPowerDownTimeOutAC_2* - GP name: *VideoPowerDownTimeOutAC_2*
- GP path: *System/Power Management/Video and Display Settings* - GP path: *System/Power Management/Video and Display Settings*
- GP ADMX file name: *power.admx* - GP ADMX file name: *power.admx*
@ -219,7 +219,7 @@ ADMX Info:
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Specify the system hibernate timeout (on battery)* - GP English name: *Specify the system hibernate timeout (on battery)*
- GP name: *DCHibernateTimeOut_2* - GP name: *DCHibernateTimeOut_2*
- GP path: *System/Power Management/Sleep Settings* - GP path: *System/Power Management/Sleep Settings*
- GP ADMX file name: *power.admx* - GP ADMX file name: *power.admx*
@ -271,7 +271,7 @@ ADMX Info:
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Specify the system hibernate timeout (plugged in)* - GP English name: *Specify the system hibernate timeout (plugged in)*
- GP name: *ACHibernateTimeOut_2* - GP name: *ACHibernateTimeOut_2*
- GP path: *System/Power Management/Sleep Settings* - GP path: *System/Power Management/Sleep Settings*
- GP ADMX file name: *power.admx* - GP ADMX file name: *power.admx*
@ -321,7 +321,7 @@ If you disable this policy setting, the user is not prompted for a password when
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Require a password when a computer wakes (on battery)* - GP English name: *Require a password when a computer wakes (on battery)*
- GP name: *DCPromptForPasswordOnResume_2* - GP name: *DCPromptForPasswordOnResume_2*
- GP path: *System/Power Management/Sleep Settings* - GP path: *System/Power Management/Sleep Settings*
- GP ADMX file name: *power.admx* - GP ADMX file name: *power.admx*
@ -371,7 +371,7 @@ If you disable this policy setting, the user is not prompted for a password when
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Require a password when a computer wakes (plugged in)* - GP English name: *Require a password when a computer wakes (plugged in)*
- GP name: *ACPromptForPasswordOnResume_2* - GP name: *ACPromptForPasswordOnResume_2*
- GP path: *System/Power Management/Sleep Settings* - GP path: *System/Power Management/Sleep Settings*
- GP ADMX file name: *power.admx* - GP ADMX file name: *power.admx*
@ -423,7 +423,7 @@ ADMX Info:
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Specify the system sleep timeout (on battery)* - GP English name: *Specify the system sleep timeout (on battery)*
- GP name: *DCStandbyTimeOut_2* - GP name: *DCStandbyTimeOut_2*
- GP path: *System/Power Management/Sleep Settings* - GP path: *System/Power Management/Sleep Settings*
- GP ADMX file name: *power.admx* - GP ADMX file name: *power.admx*
@ -475,7 +475,7 @@ ADMX Info:
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Specify the system sleep timeout (plugged in)* - GP English name: *Specify the system sleep timeout (plugged in)*
- GP name: *ACStandbyTimeOut_2* - GP name: *ACStandbyTimeOut_2*
- GP path: *System/Power Management/Sleep Settings* - GP path: *System/Power Management/Sleep Settings*
- GP ADMX file name: *power.admx* - GP ADMX file name: *power.admx*

10
windows/client-management/mdm/policy-csp-printers.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - Printers # Policy CSP - Printers
@ -75,8 +75,9 @@ If you disable this policy setting:
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Point and Print Restrictions* - GP English name: *Point and Print Restrictions*
- GP name: *PointAndPrint_Restrictions_Win7* - GP name: *PointAndPrint_Restrictions_Win7*
- GP path: *Printers*
- GP ADMX file name: *Printing.admx* - GP ADMX file name: *Printing.admx*
<!--EndADMX--> <!--EndADMX-->
@ -137,7 +138,7 @@ If you disable this policy setting:
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Point and Print Restrictions* - GP English name: *Point and Print Restrictions*
- GP name: *PointAndPrint_Restrictions* - GP name: *PointAndPrint_Restrictions*
- GP path: *Control Panel/Printers* - GP path: *Control Panel/Printers*
- GP ADMX file name: *Printing.admx* - GP ADMX file name: *Printing.admx*
@ -189,8 +190,9 @@ Note: This settings takes priority over the setting "Automatically publish new p
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Allow printers to be published* - GP English name: *Allow printers to be published*
- GP name: *PublishPrinters* - GP name: *PublishPrinters*
- GP path: *Printers*
- GP ADMX file name: *Printing2.admx* - GP ADMX file name: *Printing2.admx*
<!--EndADMX--> <!--EndADMX-->

5
windows/client-management/mdm/policy-csp-privacy.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/21/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - Privacy # Policy CSP - Privacy
@ -2593,7 +2593,7 @@ Footnote:
<!--StartHoloLens--> <!--StartHoloLens-->
## <a href="" id="hololenspolicies"></a>Privacy policies supported by Windows Holographic for Business ## <a href="" id="hololenspolicies"></a>Privacy policies supported by Windows Holographic for Business
- [Privacy/AllowInputPersonalization](#privacy-allowinputpersonalization) - [Privacy/AllowInputPersonalization](#privacy-allowinputpersonalization)
- [Privacy/LetAppsGetDiagnosticInfo](#privacy-letappsgetdiagnosticinfo) - [Privacy/LetAppsGetDiagnosticInfo](#privacy-letappsgetdiagnosticinfo)
- [Privacy/LetAppsGetDiagnosticInfo_ForceAllowTheseApps](#privacy-letappsgetdiagnosticinfo-forceallowtheseapps) - [Privacy/LetAppsGetDiagnosticInfo_ForceAllowTheseApps](#privacy-letappsgetdiagnosticinfo-forceallowtheseapps)
- [Privacy/LetAppsGetDiagnosticInfo_ForceDenyTheseApps](#privacy-letappsgetdiagnosticinfo-forcedenytheseapps) - [Privacy/LetAppsGetDiagnosticInfo_ForceDenyTheseApps](#privacy-letappsgetdiagnosticinfo-forcedenytheseapps)
@ -2630,6 +2630,5 @@ Footnote:
- [Privacy/LetAppsRunInBackground_ForceDenyTheseApps](#privacy-letappsruninbackground-forcedenytheseapps) - [Privacy/LetAppsRunInBackground_ForceDenyTheseApps](#privacy-letappsruninbackground-forcedenytheseapps)
- [Privacy/LetAppsRunInBackground_UserInControlOfTheseApps](#privacy-letappsruninbackground-userincontroloftheseapps) - [Privacy/LetAppsRunInBackground_UserInControlOfTheseApps](#privacy-letappsruninbackground-userincontroloftheseapps)
- [Privacy/PublishUserActivities](#privacy-publishuseractivities) - [Privacy/PublishUserActivities](#privacy-publishuseractivities)
<!--EndSurfaceHub--> <!--EndSurfaceHub-->

10
windows/client-management/mdm/policy-csp-remoteassistance.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - RemoteAssistance # Policy CSP - RemoteAssistance
@ -68,7 +68,7 @@ If you do not configure this policy setting, the user sees the default warning m
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Customize warning messages* - GP English name: *Customize warning messages*
- GP name: *RA_Options* - GP name: *RA_Options*
- GP path: *System/Remote Assistance* - GP path: *System/Remote Assistance*
- GP ADMX file name: *remoteassistance.admx* - GP ADMX file name: *remoteassistance.admx*
@ -120,7 +120,7 @@ If you do not configure this setting, application-based settings are used.
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Turn on session logging* - GP English name: *Turn on session logging*
- GP name: *RA_Logging* - GP name: *RA_Logging*
- GP path: *System/Remote Assistance* - GP path: *System/Remote Assistance*
- GP ADMX file name: *remoteassistance.admx* - GP ADMX file name: *remoteassistance.admx*
@ -180,7 +180,7 @@ If you enable this policy setting you should also enable appropriate firewall ex
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Configure Solicited Remote Assistance* - GP English name: *Configure Solicited Remote Assistance*
- GP name: *RA_Solicit* - GP name: *RA_Solicit*
- GP path: *System/Remote Assistance* - GP path: *System/Remote Assistance*
- GP ADMX file name: *remoteassistance.admx* - GP ADMX file name: *remoteassistance.admx*
@ -263,7 +263,7 @@ Allow Remote Desktop Exception
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Configure Offer Remote Assistance* - GP English name: *Configure Offer Remote Assistance*
- GP name: *RA_Unsolicit* - GP name: *RA_Unsolicit*
- GP path: *System/Remote Assistance* - GP path: *System/Remote Assistance*
- GP ADMX file name: *remoteassistance.admx* - GP ADMX file name: *remoteassistance.admx*

14
windows/client-management/mdm/policy-csp-remotedesktopservices.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - RemoteDesktopServices # Policy CSP - RemoteDesktopServices
@ -68,7 +68,7 @@ You can limit the number of users who can connect simultaneously by configuring
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Allow users to connect remotely by using Remote Desktop Services* - GP English name: *Allow users to connect remotely by using Remote Desktop Services*
- GP name: *TS_DISABLE_CONNECTIONS* - GP name: *TS_DISABLE_CONNECTIONS*
- GP path: *Windows Components/Remote Desktop Services/Remote Desktop Session Host/Connections* - GP path: *Windows Components/Remote Desktop Services/Remote Desktop Session Host/Connections*
- GP ADMX file name: *terminalserver.admx* - GP ADMX file name: *terminalserver.admx*
@ -128,7 +128,7 @@ FIPS compliance can be configured through the System cryptography. Use FIPS comp
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Set client connection encryption level* - GP English name: *Set client connection encryption level*
- GP name: *TS_ENCRYPTION_POLICY* - GP name: *TS_ENCRYPTION_POLICY*
- GP path: *Windows Components/Remote Desktop Services/Remote Desktop Session Host/Security* - GP path: *Windows Components/Remote Desktop Services/Remote Desktop Session Host/Security*
- GP ADMX file name: *terminalserver.admx* - GP ADMX file name: *terminalserver.admx*
@ -182,7 +182,7 @@ If you do not configure this policy setting, client drive redirection and Clipbo
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Do not allow drive redirection* - GP English name: *Do not allow drive redirection*
- GP name: *TS_CLIENT_DRIVE_M* - GP name: *TS_CLIENT_DRIVE_M*
- GP path: *Windows Components/Remote Desktop Services/Remote Desktop Session Host/Device and Resource Redirection* - GP path: *Windows Components/Remote Desktop Services/Remote Desktop Session Host/Device and Resource Redirection*
- GP ADMX file name: *terminalserver.admx* - GP ADMX file name: *terminalserver.admx*
@ -232,7 +232,7 @@ If you disable this setting or leave it not configured, the user will be able to
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Do not allow passwords to be saved* - GP English name: *Do not allow passwords to be saved*
- GP name: *TS_CLIENT_DISABLE_PASSWORD_SAVING_2* - GP name: *TS_CLIENT_DISABLE_PASSWORD_SAVING_2*
- GP path: *Windows Components/Remote Desktop Services/Remote Desktop Connection Client* - GP path: *Windows Components/Remote Desktop Services/Remote Desktop Connection Client*
- GP ADMX file name: *terminalserver.admx* - GP ADMX file name: *terminalserver.admx*
@ -288,7 +288,7 @@ If you do not configure this policy setting, automatic logon is not specified at
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Always prompt for password upon connection* - GP English name: *Always prompt for password upon connection*
- GP name: *TS_PASSWORD* - GP name: *TS_PASSWORD*
- GP path: *Windows Components/Remote Desktop Services/Remote Desktop Session Host/Security* - GP path: *Windows Components/Remote Desktop Services/Remote Desktop Session Host/Security*
- GP ADMX file name: *terminalserver.admx* - GP ADMX file name: *terminalserver.admx*
@ -344,7 +344,7 @@ Note: The RPC interface is used for administering and configuring Remote Desktop
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Require secure RPC communication* - GP English name: *Require secure RPC communication*
- GP name: *TS_RPC_ENCRYPTION* - GP name: *TS_RPC_ENCRYPTION*
- GP path: *Windows Components/Remote Desktop Services/Remote Desktop Session Host/Security* - GP path: *Windows Components/Remote Desktop Services/Remote Desktop Session Host/Security*
- GP ADMX file name: *terminalserver.admx* - GP ADMX file name: *terminalserver.admx*

32
windows/client-management/mdm/policy-csp-remotemanagement.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - RemoteManagement # Policy CSP - RemoteManagement
@ -56,7 +56,7 @@ ms.date: 08/09/2017
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Allow Basic authentication* - GP English name: *Allow Basic authentication*
- GP name: *AllowBasic_2* - GP name: *AllowBasic_2*
- GP path: *Windows Components/Windows Remote Management (WinRM)/WinRM Client* - GP path: *Windows Components/Windows Remote Management (WinRM)/WinRM Client*
- GP ADMX file name: *WindowsRemoteManagement.admx* - GP ADMX file name: *WindowsRemoteManagement.admx*
@ -100,7 +100,7 @@ ADMX Info:
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Allow Basic authentication* - GP English name: *Allow Basic authentication*
- GP name: *AllowBasic_1* - GP name: *AllowBasic_1*
- GP path: *Windows Components/Windows Remote Management (WinRM)/WinRM Service* - GP path: *Windows Components/Windows Remote Management (WinRM)/WinRM Service*
- GP ADMX file name: *WindowsRemoteManagement.admx* - GP ADMX file name: *WindowsRemoteManagement.admx*
@ -144,7 +144,7 @@ ADMX Info:
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Allow CredSSP authentication* - GP English name: *Allow CredSSP authentication*
- GP name: *AllowCredSSP_2* - GP name: *AllowCredSSP_2*
- GP path: *Windows Components/Windows Remote Management (WinRM)/WinRM Client* - GP path: *Windows Components/Windows Remote Management (WinRM)/WinRM Client*
- GP ADMX file name: *WindowsRemoteManagement.admx* - GP ADMX file name: *WindowsRemoteManagement.admx*
@ -188,7 +188,7 @@ ADMX Info:
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Allow CredSSP authentication* - GP English name: *Allow CredSSP authentication*
- GP name: *AllowCredSSP_1* - GP name: *AllowCredSSP_1*
- GP path: *Windows Components/Windows Remote Management (WinRM)/WinRM Service* - GP path: *Windows Components/Windows Remote Management (WinRM)/WinRM Service*
- GP ADMX file name: *WindowsRemoteManagement.admx* - GP ADMX file name: *WindowsRemoteManagement.admx*
@ -232,7 +232,7 @@ ADMX Info:
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Allow remote server management through WinRM* - GP English name: *Allow remote server management through WinRM*
- GP name: *AllowAutoConfig* - GP name: *AllowAutoConfig*
- GP path: *Windows Components/Windows Remote Management (WinRM)/WinRM Service* - GP path: *Windows Components/Windows Remote Management (WinRM)/WinRM Service*
- GP ADMX file name: *WindowsRemoteManagement.admx* - GP ADMX file name: *WindowsRemoteManagement.admx*
@ -276,7 +276,7 @@ ADMX Info:
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Allow unencrypted traffic* - GP English name: *Allow unencrypted traffic*
- GP name: *AllowUnencrypted_2* - GP name: *AllowUnencrypted_2*
- GP path: *Windows Components/Windows Remote Management (WinRM)/WinRM Client* - GP path: *Windows Components/Windows Remote Management (WinRM)/WinRM Client*
- GP ADMX file name: *WindowsRemoteManagement.admx* - GP ADMX file name: *WindowsRemoteManagement.admx*
@ -320,7 +320,7 @@ ADMX Info:
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Allow unencrypted traffic* - GP English name: *Allow unencrypted traffic*
- GP name: *AllowUnencrypted_1* - GP name: *AllowUnencrypted_1*
- GP path: *Windows Components/Windows Remote Management (WinRM)/WinRM Service* - GP path: *Windows Components/Windows Remote Management (WinRM)/WinRM Service*
- GP ADMX file name: *WindowsRemoteManagement.admx* - GP ADMX file name: *WindowsRemoteManagement.admx*
@ -364,7 +364,7 @@ ADMX Info:
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Disallow Digest authentication* - GP English name: *Disallow Digest authentication*
- GP name: *DisallowDigest* - GP name: *DisallowDigest*
- GP path: *Windows Components/Windows Remote Management (WinRM)/WinRM Client* - GP path: *Windows Components/Windows Remote Management (WinRM)/WinRM Client*
- GP ADMX file name: *WindowsRemoteManagement.admx* - GP ADMX file name: *WindowsRemoteManagement.admx*
@ -408,7 +408,7 @@ ADMX Info:
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Disallow Negotiate authentication* - GP English name: *Disallow Negotiate authentication*
- GP name: *DisallowNegotiate_2* - GP name: *DisallowNegotiate_2*
- GP path: *Windows Components/Windows Remote Management (WinRM)/WinRM Client* - GP path: *Windows Components/Windows Remote Management (WinRM)/WinRM Client*
- GP ADMX file name: *WindowsRemoteManagement.admx* - GP ADMX file name: *WindowsRemoteManagement.admx*
@ -452,7 +452,7 @@ ADMX Info:
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Disallow Negotiate authentication* - GP English name: *Disallow Negotiate authentication*
- GP name: *DisallowNegotiate_1* - GP name: *DisallowNegotiate_1*
- GP path: *Windows Components/Windows Remote Management (WinRM)/WinRM Service* - GP path: *Windows Components/Windows Remote Management (WinRM)/WinRM Service*
- GP ADMX file name: *WindowsRemoteManagement.admx* - GP ADMX file name: *WindowsRemoteManagement.admx*
@ -496,7 +496,7 @@ ADMX Info:
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Disallow WinRM from storing RunAs credentials* - GP English name: *Disallow WinRM from storing RunAs credentials*
- GP name: *DisableRunAs* - GP name: *DisableRunAs*
- GP path: *Windows Components/Windows Remote Management (WinRM)/WinRM Service* - GP path: *Windows Components/Windows Remote Management (WinRM)/WinRM Service*
- GP ADMX file name: *WindowsRemoteManagement.admx* - GP ADMX file name: *WindowsRemoteManagement.admx*
@ -540,7 +540,7 @@ ADMX Info:
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Specify channel binding token hardening level* - GP English name: *Specify channel binding token hardening level*
- GP name: *CBTHardeningLevel_1* - GP name: *CBTHardeningLevel_1*
- GP path: *Windows Components/Windows Remote Management (WinRM)/WinRM Service* - GP path: *Windows Components/Windows Remote Management (WinRM)/WinRM Service*
- GP ADMX file name: *WindowsRemoteManagement.admx* - GP ADMX file name: *WindowsRemoteManagement.admx*
@ -584,7 +584,7 @@ ADMX Info:
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Trusted Hosts* - GP English name: *Trusted Hosts*
- GP name: *TrustedHosts* - GP name: *TrustedHosts*
- GP path: *Windows Components/Windows Remote Management (WinRM)/WinRM Client* - GP path: *Windows Components/Windows Remote Management (WinRM)/WinRM Client*
- GP ADMX file name: *WindowsRemoteManagement.admx* - GP ADMX file name: *WindowsRemoteManagement.admx*
@ -628,7 +628,7 @@ ADMX Info:
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Turn On Compatibility HTTP Listener* - GP English name: *Turn On Compatibility HTTP Listener*
- GP name: *HttpCompatibilityListener* - GP name: *HttpCompatibilityListener*
- GP path: *Windows Components/Windows Remote Management (WinRM)/WinRM Service* - GP path: *Windows Components/Windows Remote Management (WinRM)/WinRM Service*
- GP ADMX file name: *WindowsRemoteManagement.admx* - GP ADMX file name: *WindowsRemoteManagement.admx*
@ -672,7 +672,7 @@ ADMX Info:
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Turn On Compatibility HTTPS Listener* - GP English name: *Turn On Compatibility HTTPS Listener*
- GP name: *HttpsCompatibilityListener* - GP name: *HttpsCompatibilityListener*
- GP path: *Windows Components/Windows Remote Management (WinRM)/WinRM Service* - GP path: *Windows Components/Windows Remote Management (WinRM)/WinRM Service*
- GP ADMX file name: *WindowsRemoteManagement.admx* - GP ADMX file name: *WindowsRemoteManagement.admx*

6
windows/client-management/mdm/policy-csp-remoteprocedurecall.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - RemoteProcedureCall # Policy CSP - RemoteProcedureCall
@ -66,7 +66,7 @@ Note: This policy will not be applied until the system is rebooted.
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Enable RPC Endpoint Mapper Client Authentication* - GP English name: *Enable RPC Endpoint Mapper Client Authentication*
- GP name: *RpcEnableAuthEpResolution* - GP name: *RpcEnableAuthEpResolution*
- GP path: *System/Remote Procedure Call* - GP path: *System/Remote Procedure Call*
- GP ADMX file name: *rpc.admx* - GP ADMX file name: *rpc.admx*
@ -128,7 +128,7 @@ Note: This policy setting will not be applied until the system is rebooted.
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Restrict Unauthenticated RPC clients* - GP English name: *Restrict Unauthenticated RPC clients*
- GP name: *RpcRestrictRemoteClients* - GP name: *RpcRestrictRemoteClients*
- GP path: *System/Remote Procedure Call* - GP path: *System/Remote Procedure Call*
- GP ADMX file name: *rpc.admx* - GP ADMX file name: *rpc.admx*

16
windows/client-management/mdm/policy-csp-remoteshell.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - RemoteShell # Policy CSP - RemoteShell
@ -56,7 +56,7 @@ ms.date: 08/09/2017
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Allow Remote Shell Access* - GP English name: *Allow Remote Shell Access*
- GP name: *AllowRemoteShellAccess* - GP name: *AllowRemoteShellAccess*
- GP path: *Windows Components/Windows Remote Shell* - GP path: *Windows Components/Windows Remote Shell*
- GP ADMX file name: *WindowsRemoteShell.admx* - GP ADMX file name: *WindowsRemoteShell.admx*
@ -100,7 +100,7 @@ ADMX Info:
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *MaxConcurrentUsers* - GP English name: *MaxConcurrentUsers*
- GP name: *MaxConcurrentUsers* - GP name: *MaxConcurrentUsers*
- GP path: *Windows Components/Windows Remote Shell* - GP path: *Windows Components/Windows Remote Shell*
- GP ADMX file name: *WindowsRemoteShell.admx* - GP ADMX file name: *WindowsRemoteShell.admx*
@ -144,7 +144,7 @@ ADMX Info:
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Specify idle Timeout* - GP English name: *Specify idle Timeout*
- GP name: *IdleTimeout* - GP name: *IdleTimeout*
- GP path: *Windows Components/Windows Remote Shell* - GP path: *Windows Components/Windows Remote Shell*
- GP ADMX file name: *WindowsRemoteShell.admx* - GP ADMX file name: *WindowsRemoteShell.admx*
@ -188,7 +188,7 @@ ADMX Info:
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Specify maximum amount of memory in MB per Shell* - GP English name: *Specify maximum amount of memory in MB per Shell*
- GP name: *MaxMemoryPerShellMB* - GP name: *MaxMemoryPerShellMB*
- GP path: *Windows Components/Windows Remote Shell* - GP path: *Windows Components/Windows Remote Shell*
- GP ADMX file name: *WindowsRemoteShell.admx* - GP ADMX file name: *WindowsRemoteShell.admx*
@ -232,7 +232,7 @@ ADMX Info:
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Specify maximum number of processes per Shell* - GP English name: *Specify maximum number of processes per Shell*
- GP name: *MaxProcessesPerShell* - GP name: *MaxProcessesPerShell*
- GP path: *Windows Components/Windows Remote Shell* - GP path: *Windows Components/Windows Remote Shell*
- GP ADMX file name: *WindowsRemoteShell.admx* - GP ADMX file name: *WindowsRemoteShell.admx*
@ -276,7 +276,7 @@ ADMX Info:
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Specify maximum number of remote shells per user* - GP English name: *Specify maximum number of remote shells per user*
- GP name: *MaxShellsPerUser* - GP name: *MaxShellsPerUser*
- GP path: *Windows Components/Windows Remote Shell* - GP path: *Windows Components/Windows Remote Shell*
- GP ADMX file name: *WindowsRemoteShell.admx* - GP ADMX file name: *WindowsRemoteShell.admx*
@ -320,7 +320,7 @@ ADMX Info:
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Specify Shell Timeout* - GP English name: *Specify Shell Timeout*
- GP name: *ShellTimeOut* - GP name: *ShellTimeOut*
- GP path: *Windows Components/Windows Remote Shell* - GP path: *Windows Components/Windows Remote Shell*
- GP ADMX file name: *WindowsRemoteShell.admx* - GP ADMX file name: *WindowsRemoteShell.admx*

2
windows/client-management/mdm/policy-csp-search.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - Search # Policy CSP - Search

2
windows/client-management/mdm/policy-csp-security.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - Security # Policy CSP - Security

2
windows/client-management/mdm/policy-csp-settings.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - Settings # Policy CSP - Settings

2
windows/client-management/mdm/policy-csp-smartscreen.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - SmartScreen # Policy CSP - SmartScreen

2
windows/client-management/mdm/policy-csp-speech.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - Speech # Policy CSP - Speech

2
windows/client-management/mdm/policy-csp-start.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - Start # Policy CSP - Start

4
windows/client-management/mdm/policy-csp-storage.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - Storage # Policy CSP - Storage
@ -62,7 +62,7 @@ If you disable or do not configure this policy setting, Windows will activate un
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Do not allow Windows to activate Enhanced Storage devices* - GP English name: *Do not allow Windows to activate Enhanced Storage devices*
- GP name: *TCGSecurityActivationDisabled* - GP name: *TCGSecurityActivationDisabled*
- GP path: *System/Enhanced Storage Access* - GP path: *System/Enhanced Storage Access*
- GP ADMX file name: *enhancedstorage.admx* - GP ADMX file name: *enhancedstorage.admx*

4
windows/client-management/mdm/policy-csp-system.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - System # Policy CSP - System
@ -546,7 +546,7 @@ Also, see the "Turn off System Restore configuration" policy setting. If the "Tu
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Turn off System Restore* - GP English name: *Turn off System Restore*
- GP name: *SR_DisableSR* - GP name: *SR_DisableSR*
- GP path: *System/System Restore* - GP path: *System/System Restore*
- GP ADMX file name: *systemrestore.admx* - GP ADMX file name: *systemrestore.admx*

2
windows/client-management/mdm/policy-csp-textinput.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - TextInput # Policy CSP - TextInput

2
windows/client-management/mdm/policy-csp-timelanguagesettings.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - TimeLanguageSettings # Policy CSP - TimeLanguageSettings

22
windows/client-management/mdm/policy-csp-update.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/25/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - Update # Policy CSP - Update
@ -46,8 +46,6 @@ ms.date: 08/25/2017
<!--EndSKU--> <!--EndSKU-->
<!--StartDescription--> <!--StartDescription-->
<p style="margin-left: 20px">Added in Windows 10, version 1607. Allows the IT admin (when used with **Update/ActiveHoursStart**) to manage a range of active hours where update reboots are not scheduled. This value sets the end time. There is a 12 hour maximum from start time. <p style="margin-left: 20px">Added in Windows 10, version 1607. Allows the IT admin (when used with **Update/ActiveHoursStart**) to manage a range of active hours where update reboots are not scheduled. This value sets the end time. There is a 12 hour maximum from start time.
> [!NOTE] > [!NOTE]
@ -86,8 +84,6 @@ ms.date: 08/25/2017
<!--EndSKU--> <!--EndSKU-->
<!--StartDescription--> <!--StartDescription-->
<p style="margin-left: 20px">Added in Windows 10, version 1703. Allows the IT admin to specify the max active hours range. This value sets max number of active hours from start time. <p style="margin-left: 20px">Added in Windows 10, version 1703. Allows the IT admin to specify the max active hours range. This value sets max number of active hours from start time.
<p style="margin-left: 20px">Supported values are 8-18. <p style="margin-left: 20px">Supported values are 8-18.
@ -123,8 +119,6 @@ ms.date: 08/25/2017
<!--EndSKU--> <!--EndSKU-->
<!--StartDescription--> <!--StartDescription-->
<p style="margin-left: 20px">Added in Windows 10, version 1607. Allows the IT admin (when used with **Update/ActiveHoursEnd**) to manage a range of hours where update reboots are not scheduled. This value sets the start time. There is a 12 hour maximum from end time. <p style="margin-left: 20px">Added in Windows 10, version 1607. Allows the IT admin (when used with **Update/ActiveHoursEnd**) to manage a range of hours where update reboots are not scheduled. This value sets the start time. There is a 12 hour maximum from end time.
> [!NOTE] > [!NOTE]
@ -163,7 +157,6 @@ ms.date: 08/25/2017
<!--EndSKU--> <!--EndSKU-->
<!--StartDescription--> <!--StartDescription-->
<p style="margin-left: 20px">Enables the IT admin to manage automatic update behavior to scan, download, and install updates. <p style="margin-left: 20px">Enables the IT admin to manage automatic update behavior to scan, download, and install updates.
<p style="margin-left: 20px">Supported operations are Get and Replace. <p style="margin-left: 20px">Supported operations are Get and Replace.
@ -212,7 +205,6 @@ ms.date: 08/25/2017
<!--EndSKU--> <!--EndSKU-->
<!--StartDescription--> <!--StartDescription-->
<p style="margin-left: 20px">Added in Windows 10, version 1607. Allows the IT admin to manage whether to scan for app updates from Microsoft Update. <p style="margin-left: 20px">Added in Windows 10, version 1607. Allows the IT admin to manage whether to scan for app updates from Microsoft Update.
<p style="margin-left: 20px">The following list shows the supported values: <p style="margin-left: 20px">The following list shows the supported values:
@ -249,7 +241,6 @@ ms.date: 08/25/2017
<!--EndSKU--> <!--EndSKU-->
<!--StartDescription--> <!--StartDescription-->
<p style="margin-left: 20px">Allows the IT admin to manage whether Automatic Updates accepts updates signed by entities other than Microsoft when the update is found at the UpdateServiceUrl location. This policy supports using WSUS for 3rd party software and patch distribution. <p style="margin-left: 20px">Allows the IT admin to manage whether Automatic Updates accepts updates signed by entities other than Microsoft when the update is found at the UpdateServiceUrl location. This policy supports using WSUS for 3rd party software and patch distribution.
<p style="margin-left: 20px">Supported operations are Get and Replace. <p style="margin-left: 20px">Supported operations are Get and Replace.
@ -290,7 +281,6 @@ ms.date: 08/25/2017
<!--EndSKU--> <!--EndSKU-->
<!--StartDescription--> <!--StartDescription-->
<p style="margin-left: 20px">Specifies whether the device could use Microsoft Update, Windows Server Update Services (WSUS), or Windows Store. <p style="margin-left: 20px">Specifies whether the device could use Microsoft Update, Windows Server Update Services (WSUS), or Windows Store.
<p style="margin-left: 20px">Even when Windows Update is configured to receive updates from an intranet update service, it will periodically retrieve information from the public Windows Update service to enable future connections to Windows Update, and other services like Microsoft Update or the Windows Store <p style="margin-left: 20px">Even when Windows Update is configured to receive updates from an intranet update service, it will periodically retrieve information from the public Windows Update service to enable future connections to Windows Update, and other services like Microsoft Update or the Windows Store
@ -369,7 +359,6 @@ ms.date: 08/25/2017
<!--EndSKU--> <!--EndSKU-->
<!--StartDescription--> <!--StartDescription-->
<p style="margin-left: 20px">Added in Windows 10, version 1703. Allows the IT Admin to specify the period for auto-restart reminder notifications. <p style="margin-left: 20px">Added in Windows 10, version 1703. Allows the IT Admin to specify the period for auto-restart reminder notifications.
<p style="margin-left: 20px">Supported values are 15, 30, 60, 120, and 240 (minutes). <p style="margin-left: 20px">Supported values are 15, 30, 60, 120, and 240 (minutes).
@ -405,7 +394,6 @@ ms.date: 08/25/2017
<!--EndSKU--> <!--EndSKU-->
<!--StartDescription--> <!--StartDescription-->
<p style="margin-left: 20px">Added in Windows 10, version 1703. Allows the IT Admin to specify the method by which the auto-restart required notification is dismissed. <p style="margin-left: 20px">Added in Windows 10, version 1703. Allows the IT Admin to specify the method by which the auto-restart required notification is dismissed.
<p style="margin-left: 20px">The following list shows the supported values: <p style="margin-left: 20px">The following list shows the supported values:
@ -442,7 +430,6 @@ ms.date: 08/25/2017
<!--EndSKU--> <!--EndSKU-->
<!--StartDescription--> <!--StartDescription-->
<p style="margin-left: 20px">Added in Windows 10, version 1607. Allows the IT admin to set which branch a device receives their updates from. <p style="margin-left: 20px">Added in Windows 10, version 1607. Allows the IT admin to set which branch a device receives their updates from.
<p style="margin-left: 20px">The following list shows the supported values: <p style="margin-left: 20px">The following list shows the supported values:
@ -479,7 +466,6 @@ ms.date: 08/25/2017
<!--EndSKU--> <!--EndSKU-->
<!--StartDescription--> <!--StartDescription-->
<p style="margin-left: 20px">Since this policy is not blocked, you will not get a failure message when you use it to configure a Windows 10 Mobile device. However, the policy will not take effect. <p style="margin-left: 20px">Since this policy is not blocked, you will not get a failure message when you use it to configure a Windows 10 Mobile device. However, the policy will not take effect.
<p style="margin-left: 20px">Added in Windows 10, version 1607. Defers Feature Updates for the specified number of days. <p style="margin-left: 20px">Added in Windows 10, version 1607. Defers Feature Updates for the specified number of days.
@ -518,7 +504,6 @@ ms.date: 08/25/2017
<!--EndSKU--> <!--EndSKU-->
<!--StartDescription--> <!--StartDescription-->
<p style="margin-left: 20px">Added in Windows 10, version 1607. Defers Quality Updates for the specified number of days. <p style="margin-left: 20px">Added in Windows 10, version 1607. Defers Quality Updates for the specified number of days.
<p style="margin-left: 20px">Supported values are 0-30. <p style="margin-left: 20px">Supported values are 0-30.
@ -763,7 +748,6 @@ If a machine has Microsoft Update enabled, any Microsoft Updates in these catego
<!--EndSKU--> <!--EndSKU-->
<!--StartDescription--> <!--StartDescription-->
<p style="margin-left: 20px">Added in Windows 10, version 1703. Allows the IT Admin to specify the deadline in days before automatically scheduling and executing a pending restart outside of active hours. The deadline can be set between 2 and 30 days from the time the restart becomes pending. If configured, the pending restart will transition from Auto-restart to Engaged restart (pending user schedule) to be automatically executed within the specified period. If no deadline is specified or deadline is set to 0, the restart will not be automatically executed and will remain Engaged restart (pending user scheduling). <p style="margin-left: 20px">Added in Windows 10, version 1703. Allows the IT Admin to specify the deadline in days before automatically scheduling and executing a pending restart outside of active hours. The deadline can be set between 2 and 30 days from the time the restart becomes pending. If configured, the pending restart will transition from Auto-restart to Engaged restart (pending user schedule) to be automatically executed within the specified period. If no deadline is specified or deadline is set to 0, the restart will not be automatically executed and will remain Engaged restart (pending user scheduling).
<p style="margin-left: 20px">Supported values are 2-30 days. <p style="margin-left: 20px">Supported values are 2-30 days.
@ -799,7 +783,6 @@ If a machine has Microsoft Update enabled, any Microsoft Updates in these catego
<!--EndSKU--> <!--EndSKU-->
<!--StartDescription--> <!--StartDescription-->
<p style="margin-left: 20px">Added in Windows 10, version 1703. Allows the IT Admin to control the number of days a user can snooze Engaged restart reminder notifications. <p style="margin-left: 20px">Added in Windows 10, version 1703. Allows the IT Admin to control the number of days a user can snooze Engaged restart reminder notifications.
<p style="margin-left: 20px">Supported values are 1-3 days. <p style="margin-left: 20px">Supported values are 1-3 days.
@ -835,7 +818,6 @@ If a machine has Microsoft Update enabled, any Microsoft Updates in these catego
<!--EndSKU--> <!--EndSKU-->
<!--StartDescription--> <!--StartDescription-->
<p style="margin-left: 20px">Added in Windows 10, version 1703. Allows the IT Admin to control the timing before transitioning from Auto restarts scheduled outside of active hours to Engaged restart, which requires the user to schedule. The period can be set between 2 and 30 days from the time the restart becomes pending. <p style="margin-left: 20px">Added in Windows 10, version 1703. Allows the IT Admin to control the timing before transitioning from Auto restarts scheduled outside of active hours to Engaged restart, which requires the user to schedule. The period can be set between 2 and 30 days from the time the restart becomes pending.
<p style="margin-left: 20px">Supported values are 2-30 days. <p style="margin-left: 20px">Supported values are 2-30 days.
@ -1161,7 +1143,6 @@ If a machine has Microsoft Update enabled, any Microsoft Updates in these catego
<!--EndSKU--> <!--EndSKU-->
<!--StartDescription--> <!--StartDescription-->
<p style="margin-left: 20px">Added in Windows 10, version 1607. Allows IT Admins to pause Quality Updates. <p style="margin-left: 20px">Added in Windows 10, version 1607. Allows IT Admins to pause Quality Updates.
<p style="margin-left: 20px">The following list shows the supported values: <p style="margin-left: 20px">The following list shows the supported values:
@ -1313,7 +1294,6 @@ If a machine has Microsoft Update enabled, any Microsoft Updates in these catego
<!--EndSKU--> <!--EndSKU-->
<!--StartDescription--> <!--StartDescription-->
<p style="margin-left: 20px">Added in Windows 10, version 1703. Allows the IT Admin to specify the period for auto-restart imminent warning notifications. <p style="margin-left: 20px">Added in Windows 10, version 1703. Allows the IT Admin to specify the period for auto-restart imminent warning notifications.
<p style="margin-left: 20px">Supported values are 15, 30, or 60 (minutes). <p style="margin-left: 20px">Supported values are 15, 30, or 60 (minutes).

2
windows/client-management/mdm/policy-csp-wifi.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - Wifi # Policy CSP - Wifi

2
windows/client-management/mdm/policy-csp-windowsdefendersecuritycenter.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - WindowsDefenderSecurityCenter # Policy CSP - WindowsDefenderSecurityCenter

2
windows/client-management/mdm/policy-csp-windowsinkworkspace.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - WindowsInkWorkspace # Policy CSP - WindowsInkWorkspace

6
windows/client-management/mdm/policy-csp-windowslogon.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - WindowsLogon # Policy CSP - WindowsLogon
@ -62,7 +62,7 @@ If you disable or do not configure this policy setting, users can choose which a
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Turn off app notifications on the lock screen* - GP English name: *Turn off app notifications on the lock screen*
- GP name: *DisableLockScreenAppNotifications* - GP name: *DisableLockScreenAppNotifications*
- GP path: *System/Logon* - GP path: *System/Logon*
- GP ADMX file name: *logon.admx* - GP ADMX file name: *logon.admx*
@ -112,7 +112,7 @@ If you disable or don't configure this policy setting, any user can disconnect t
<!--StartADMX--> <!--StartADMX-->
ADMX Info: ADMX Info:
- GP english name: *Do not display network selection UI* - GP English name: *Do not display network selection UI*
- GP name: *DontDisplayNetworkSelectionUI* - GP name: *DontDisplayNetworkSelectionUI*
- GP path: *System/Logon* - GP path: *System/Logon*
- GP ADMX file name: *logon.admx* - GP ADMX file name: *logon.admx*

2
windows/client-management/mdm/policy-csp-wirelessdisplay.md
View File

@ -6,7 +6,7 @@ ms.topic: article
ms.prod: w10 ms.prod: w10
ms.technology: windows ms.technology: windows
author: nickbrower author: nickbrower
ms.date: 08/09/2017 ms.date: 08/30/2017
--- ---
# Policy CSP - WirelessDisplay # Policy CSP - WirelessDisplay

22
windows/deployment/update/device-health-get-started.md
View File

@ -39,37 +39,37 @@ Online Crash Analysis | oca.telemetry.microsoft.com
Device Health is offered as a solution in the Microsoft Operations Management Suite (OMS), a collection of cloud-based servicing for monitoring and automating your on-premise and cloud environments. For more information about OMS, see [Operations Management Suite overview](https://azure.microsoft.com/en-us/documentation/articles/operations-management-suite-overview/). Device Health is offered as a solution in the Microsoft Operations Management Suite (OMS), a collection of cloud-based servicing for monitoring and automating your on-premise and cloud environments. For more information about OMS, see [Operations Management Suite overview](https://azure.microsoft.com/en-us/documentation/articles/operations-management-suite-overview/).
**If you are already using OMS**, you’ll find Device Health in the Solutions Gallery. Select the **Device Health** tile in the gallery and then click **Add** on the solution's details page. Device Health is now visible in your workspace. **If you are already using OMS**, you’ll find Device Health in the Solutions Gallery. Select the **Device Health** tile in the gallery and then click **Add** on the solution's details page. Device Health is now visible in your workspace. While you're in the Solutions Gallery, you should consider installing the [Upgrade Readiness](../upgrade/use-upgrade-readiness-to-manage-windows-upgrades.md) and [Update Compliance](update-compliance-monitor.md) solutions as well, if you haven't already.
**If you are not yet using OMS**, use the following steps to subscribe to OMS Device Health: **If you are not yet using OMS**, use the following steps to subscribe to OMS Device Health:
1. Go to [Operations Management Suite](https://www.microsoft.com/en-us/cloud-platform/operations-management-suite) on Microsoft.com and click **Sign in**. 1. Go to [Operations Management Suite](https://www.microsoft.com/en-us/cloud-platform/operations-management-suite) on Microsoft.com and click **Sign in**.
[![](images/uc-02a.png)](images/uc-02.png) [![Operations Management Suite bar with sign-in button](images/uc-02a.png)](images/uc-02.png)
2. Sign in to Operations Management Suite (OMS). You can use either a Microsoft Account or a Work or School account to create a workspace. If your company is already using Azure Active Directory (Azure AD), use a Work or School account when you sign in to OMS. Using a Work or School account allows you to use identities from your Azure AD to manage permissions in OMS. 2. Sign in to Operations Management Suite (OMS). You can use either a Microsoft Account or a Work or School account to create a workspace. If your company is already using Azure Active Directory (Azure AD), use a Work or School account when you sign in to OMS. Using a Work or School account allows you to use identities from your Azure AD to manage permissions in OMS.
[![](images/uc-03a.png)](images/uc-03.png) [![OMS Sign-in dialog box for account name and password](images/uc-03a.png)](images/uc-03.png)
3. Create a new OMS workspace. 3. Create a new OMS workspace.
[![](images/uc-04a.png)](images/uc-04.png) [![OMS dialog with buttons to create a new OMS workspace or cancel](images/uc-04a.png)](images/uc-04.png)
4. Enter a name for the workspace, select the workspace region, and provide the email address that you want associated with this workspace. Click **Create**. 4. Enter a name for the workspace, select the workspace region, and provide the email address that you want associated with this workspace. Click **Create**.
[![](images/uc-05a.png)](images/uc-05.png) [![OMS Create New Workspace dialog](images/uc-05a.png)](images/uc-05.png)
5. If your organization already has an Azure subscription, you can link it to your workspace. Note that you may need to request access from your organization’s Azure administrator. If your organization does not have an Azure subscription, create a new one or select the default OMS Azure subscription from the list. If you do not yet have an Azure subscription, follow [this guide](https://blogs.technet.microsoft.com/upgradeanalytics/2016/11/08/linking-operations-management-suite-workspaces-to-microsoft-azure/) to create and link an Azure subscription to an OMS workspace. 5. If your organization already has an Azure subscription, you can link it to your workspace. Note that you may need to request access from your organization’s Azure administrator. If your organization does not have an Azure subscription, create a new one or select the default OMS Azure subscription from the list. If you do not yet have an Azure subscription, follow [this guide](https://blogs.technet.microsoft.com/upgradeanalytics/2016/11/08/linking-operations-management-suite-workspaces-to-microsoft-azure/) to create and link an Azure subscription to an OMS workspace.
[![](images/uc-06a.png)](images/uc-06.png) [![OMS dialog to link existing Azure subscription or create a new one](images/uc-06a.png)](images/uc-06.png)
6. To add Device Health to your workspace, go to the Solution Gallery, Select the **Device Health** tile and then select **Add** on the solution's detail page. 6. To add Device Health to your workspace, go to the Solution Gallery, Select the **Device Health** tile and then select **Add** on the solution's detail page. While you have this dialog open, you should also consider adding the [Upgrade Readiness](../upgrade/use-upgrade-readiness-to-manage-windows-upgrades.md) and [Update Compliance](update-compliance-monitor.md) solutions as well, if you haven't already. To do so, just select the check boxes for those solutions.
[![](images/uc-08a.png)](images/uc-08.png) [![Windows Analytics details page in Solutions Gallery](images/solution-bundle.png)](images/solution-bundle.png)
7. Click the **Device Health** tile to configure the solution. The **Settings Dashboard** opens. 7. Click the **Device Health** tile to configure the solution. The **Settings Dashboard** opens. In this example, both Upgrade Readiness and Device Health solutions have been added.
[![](images/uc-09a.png)](images/uc-09.png) [![OMS Settings Dashboard showing Device Health and Upgrade Readiness tiles](images/OMS-after-adding-solution.jpg)](images/OMS-after-adding-solution.jpg)
@ -89,7 +89,7 @@ In order for your devices to show up in Windows Analytics: Device Health, they m
3. In the **Options** box, under **Commercial Id**, type the Commercial ID GUID, and then click **OK**.<P> 3. In the **Options** box, under **Commercial Id**, type the Commercial ID GUID, and then click **OK**.<P>
- Using Microsoft Mobile Device Management (MDM)<BR><BR> - Using Microsoft Mobile Device Management (MDM)<BR><BR>
Microsoft’s Mobile Device Management can be used to deploy your Commercial ID to your organization’s devices. The Commercial ID is listed under **Provider/ProviderID/CommercialID**. More information on deployment using MDM can be found [here](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/dmclient-csp).   Microsoft’s Mobile Device Management can be used to deploy your Commercial ID to your organization’s devices. The Commercial ID is listed under **Provider/ProviderID/CommercialID**. You can find more information on deployment using MDM at the [DMClient Configuration Service Provider topic](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/dmclient-csp).  
## Perform checks to ensure and verify successful deployment ## Perform checks to ensure and verify successful deployment

BIN
windows/deployment/update/images/OMS-after-adding-solution.jpg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 34 KiB

BIN
windows/deployment/update/images/solution-bundle.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 338 KiB

24
windows/deployment/update/update-compliance-get-started.md
View File

@ -6,7 +6,7 @@ ms.prod: w10
ms.mktglfcycl: deploy ms.mktglfcycl: deploy
ms.sitesec: library ms.sitesec: library
ms.pagetype: deploy ms.pagetype: deploy
author: greg-lindsay author: jaimeo
--- ---
# Get started with Update Compliance # Get started with Update Compliance
@ -39,61 +39,61 @@ Online Crash Analysis | oca.telemetry.microsoft.com
Update Compliance is offered as a solution in the Microsoft Operations Management Suite (OMS), a collection of cloud-based servicing for monitoring and automating your on-premise and cloud environments. For more information about OMS, see [Operations Management Suite overview](https://azure.microsoft.com/en-us/documentation/articles/operations-management-suite-overview/). Update Compliance is offered as a solution in the Microsoft Operations Management Suite (OMS), a collection of cloud-based servicing for monitoring and automating your on-premise and cloud environments. For more information about OMS, see [Operations Management Suite overview](https://azure.microsoft.com/en-us/documentation/articles/operations-management-suite-overview/).
If you are already using OMS, you’ll find Update Compliance in the Solutions Gallery. Select the **Update Compliance** tile in the gallery and then click **Add** on the solution's details page. Update Compliance is now visible in your workspace. If you are already using OMS, you’ll find Update Compliance in the Solutions Gallery. Select the **Update Compliance** tile in the gallery and then click **Add** on the solution's details page. Update Compliance is now visible in your workspace. While you're in the Solutions Gallery, you should consider installing the [Upgrade Readiness](../upgrade/use-upgrade-readiness-to-manage-windows-upgrades.md) and [Device Health](device-health-monitor.md) solutions as well, if you haven't already.
If you are not yet using OMS, use the following steps to subscribe to OMS Update Compliance: If you are not yet using OMS, use the following steps to subscribe to OMS Update Compliance:
1. Go to [Operations Management Suite](https://www.microsoft.com/en-us/cloud-platform/operations-management-suite) on Microsoft.com and click **Sign in**. 1. Go to [Operations Management Suite](https://www.microsoft.com/en-us/cloud-platform/operations-management-suite) on Microsoft.com and click **Sign in**.
[![](images/uc-02a.png)](images/uc-02.png) [![Operations Management Suite bar with sign-in button](images/uc-02a.png)](images/uc-02.png)
2. Sign in to Operations Management Suite (OMS). You can use either a Microsoft Account or a Work or School account to create a workspace. If your company is already using Azure Active Directory (Azure AD), use a Work or School account when you sign in to OMS. Using a Work or School account allows you to use identities from your Azure AD to manage permissions in OMS. 2. Sign in to Operations Management Suite (OMS). You can use either a Microsoft Account or a Work or School account to create a workspace. If your company is already using Azure Active Directory (Azure AD), use a Work or School account when you sign in to OMS. Using a Work or School account allows you to use identities from your Azure AD to manage permissions in OMS.
[![](images/uc-03a.png)](images/uc-03.png) [![OMS Sign-in dialog box for account name and password](images/uc-03a.png)](images/uc-03.png)
3. Create a new OMS workspace. 3. Create a new OMS workspace.
[![](images/uc-04a.png)](images/uc-04.png) [![OMS dialog with buttons to create a new OMS workspace or cancel](images/uc-04a.png)](images/uc-04.png)
4. Enter a name for the workspace, select the workspace region, and provide the email address that you want associated with this workspace. Click **Create**. 4. Enter a name for the workspace, select the workspace region, and provide the email address that you want associated with this workspace. Click **Create**.
[![](images/uc-05a.png)](images/uc-05.png) [![OMS Create New Workspace dialog](images/uc-05a.png)](images/uc-05.png)
5. If your organization already has an Azure subscription, you can link it to your workspace. Note that you may need to request access from your organization’s Azure administrator. If your organization does not have an Azure subscription, create a new one or select the default OMS Azure subscription from the list. If you do not yet have an Azure subscription, follow [this guide](https://blogs.technet.microsoft.com/upgradeanalytics/2016/11/08/linking-operations-management-suite-workspaces-to-microsoft-azure/) to create and link an Azure subscription to an OMS workspace. 5. If your organization already has an Azure subscription, you can link it to your workspace. Note that you may need to request access from your organization’s Azure administrator. If your organization does not have an Azure subscription, create a new one or select the default OMS Azure subscription from the list. If you do not yet have an Azure subscription, follow [this guide](https://blogs.technet.microsoft.com/upgradeanalytics/2016/11/08/linking-operations-management-suite-workspaces-to-microsoft-azure/) to create and link an Azure subscription to an OMS workspace.
[![](images/uc-06a.png)](images/uc-06.png) [![OMS dialog to link existing Azure subscription or create a new one](images/uc-06a.png)](images/uc-06.png)
6. To add the Update Compliance solution to your workspace, go to the Solutions Gallery. 6. To add the Update Compliance solution to your workspace, go to the Solutions Gallery. While you have this dialog open, you should also consider adding the [Upgrade Readiness](../upgrade/use-upgrade-readiness-to-manage-windows-upgrades.md) and [Device Health](device-health-monitor.md) solutions as well, if you haven't already. To do so, just select the check boxes for those solutions.
[![](images/uc-07a.png)](images/uc-07.png) [![OMS workspace with Solutions Gallery tile highlighted](images/uc-07a.png)](images/uc-07.png)
7. Select the **Update Compliance** tile in the gallery and then select **Add** on the solution’s details page. You might need to scroll to find **Update Compliance**. The solution is now visible in your workspace. 7. Select the **Update Compliance** tile in the gallery and then select **Add** on the solution’s details page. You might need to scroll to find **Update Compliance**. The solution is now visible in your workspace.
[![](images/uc-08a.png)](images/uc-08.png) [![Workspace showing Solutions Gallery](images/uc-08a.png)](images/uc-08.png)
8. Click the **Update Compliance** tile to configure the solution. The **Settings Dashboard** opens. 8. Click the **Update Compliance** tile to configure the solution. The **Settings Dashboard** opens.
[![](images/uc-09a.png)](images/uc-09.png) [![OMS workspace with new Update Compliance tile on the right side highlighted](images/uc-09a.png)](images/uc-09.png)
9. Click **Subscribe** to subscribe to OMS Update Compliance. You will then need to distribute your Commercial ID across all your organization’s devices. More information on the Commercial ID is provided below. 9. Click **Subscribe** to subscribe to OMS Update Compliance. You will then need to distribute your Commercial ID across all your organization’s devices. More information on the Commercial ID is provided below.
[![](images/uc-10a.png)](images/uc-10.png) [![Series of blades showing Connected Sources, Windows Telemetry, and Upgrade Analytics solution with Subscribe button](images/uc-10a.png)](images/uc-10.png)
After you are subscribed to OMS Update Compliance and your devices have a Commercial ID, you will begin receiving data. It will typically take 24 hours for the first data to begin appearing. The following section explains how to deploy your Commercial ID to your Windows 10 devices. After you are subscribed to OMS Update Compliance and your devices have a Commercial ID, you will begin receiving data. It will typically take 24 hours for the first data to begin appearing. The following section explains how to deploy your Commercial ID to your Windows 10 devices.

10
windows/deployment/upgrade/upgrade-readiness-get-started.md
View File

@ -5,7 +5,7 @@ ms.prod: w10
ms.mktglfcycl: deploy ms.mktglfcycl: deploy
ms.sitesec: library ms.sitesec: library
ms.pagetype: deploy ms.pagetype: deploy
author: greg-lindsay author: jaimeo
--- ---
# Get started with Upgrade Readiness # Get started with Upgrade Readiness
@ -43,7 +43,7 @@ Upgrade Readiness is offered as a solution in the Microsoft Operations Managemen
>[!IMPORTANT] >[!IMPORTANT]
>Upgrade Readiness is a free solution. When configured correctly, all data associated with the Upgrade Readiness solution are exempt from billing in both OMS and Azure. Upgrade Readiness data **do not** count toward OMS daily upload limits. >Upgrade Readiness is a free solution. When configured correctly, all data associated with the Upgrade Readiness solution are exempt from billing in both OMS and Azure. Upgrade Readiness data **do not** count toward OMS daily upload limits.
If you are already using OMS, you’ll find Upgrade Readiness in the Solutions Gallery. Select the **Upgrade Readiness** tile in the gallery and then click **Add** on the solution's details page. Upgrade Readiness is now visible in your workspace. If you are already using OMS, you’ll find Upgrade Readiness in the Solutions Gallery. Select the **Upgrade Readiness** tile in the gallery and then click **Add** on the solution's details page. Upgrade Readiness is now visible in your workspace. While you have this dialog open, you should also consider adding the [Device Health](../update/device-health-monitor.md) and [Update Compliance](../update/update-compliance-monitor.md) solutions as well, if you haven't already. To do so, just select the check boxes for those solutions.
If you are not using OMS: If you are not using OMS:
@ -54,9 +54,9 @@ If you are not using OMS:
> If your organization does not have an Azure subscription, create a new one or select the default OMS Azure subscription from the list. Your workspace opens. > If your organization does not have an Azure subscription, create a new one or select the default OMS Azure subscription from the list. Your workspace opens.
1. To add the Upgrade Readiness solution to your workspace, go to the **Solutions Gallery**. Select the **Upgrade Readiness** tile in the gallery and then select **Add** on the solution’s details page. The solution is now visible on your workspace. Note that you may need to scroll to find Upgrade Readiness. 5. To add the Upgrade Readiness solution to your workspace, go to the **Solutions Gallery**. Select the **Upgrade Readiness** tile in the gallery and then select **Add** on the solution’s details page. The solution is now visible on your workspace. Note that you may need to scroll to find Upgrade Readiness.
2. Click the **Upgrade Readiness** tile to configure the solution. The **Settings Dashboard** opens. 6. Click the **Upgrade Readiness** tile to configure the solution. The **Settings Dashboard** opens.
### Generate your commercial ID key ### Generate your commercial ID key
@ -64,7 +64,7 @@ Microsoft uses a unique commercial ID to map information from user computers to
1. On the Settings Dashboard, navigate to the **Windows telemetry** panel. 1. On the Settings Dashboard, navigate to the **Windows telemetry** panel.
![upgrade-readiness-telemetry](../images/upgrade-analytics-telemetry.png) ![Windows Telemetry dialog showing button for "how to enable telemetry," the current commercial ID key, and a Subsribe button](../images/upgrade-analytics-telemetry.png)
2. On the Windows telemetry panel, copy and save your commercial ID key. You’ll need to insert this key into the Upgrade Readiness deployment script later so it can be deployed to user computers. 2. On the Windows telemetry panel, copy and save your commercial ID key. You’ll need to insert this key into the Upgrade Readiness deployment script later so it can be deployed to user computers.

10
windows/deployment/upgrade/use-upgrade-readiness-to-manage-windows-upgrades.md
View File

@ -2,7 +2,7 @@
title: Use Upgrade Readiness to manage Windows upgrades (Windows 10) title: Use Upgrade Readiness to manage Windows upgrades (Windows 10)
description: Describes how to use Upgrade Readiness to manage Windows upgrades. description: Describes how to use Upgrade Readiness to manage Windows upgrades.
ms.prod: w10 ms.prod: w10
author: greg-lindsay author: jaimeo
--- ---
# Use Upgrade Readiness to manage Windows upgrades # Use Upgrade Readiness to manage Windows upgrades
@ -14,7 +14,7 @@ You can use Upgrade Readiness to prioritize and work through application and dri
When you are ready to begin the upgrade process, a workflow is provided to guide you through critical high-level tasks. When you are ready to begin the upgrade process, a workflow is provided to guide you through critical high-level tasks.
<A HREF="../images/ua-cg-15.png">![Workflow](../images/ua-cg-15.png)</A> <A HREF="../images/ua-cg-15.png">![Series of blades showing Upgrade Overview, Step 1: Identify Important Apps, Prioritize Applications, Step 2: Resolve issues, and Review applications with known issues](../images/ua-cg-15.png)</A>
Each step in the workflow is enumerated using blue tiles. Helpful data is provided on white tiles to help you get started, to monitor your progress, and to complete each step. Each step in the workflow is enumerated using blue tiles. Helpful data is provided on white tiles to help you get started, to monitor your progress, and to complete each step.
@ -35,7 +35,7 @@ Also see the following topic for information about additional items that can be
The target version setting is used to evaluate the number of computers that are already running the default version of Windows 10, or a later version. The target version of Windows 10 is displayed on the upgrade overview tile. See the following example: The target version setting is used to evaluate the number of computers that are already running the default version of Windows 10, or a later version. The target version of Windows 10 is displayed on the upgrade overview tile. See the following example:
![Target version](../images/ur-target-version.png) ![Upgrade overview showing target version](../images/ur-target-version.png)
As mentioned previously, the default target version in Upgrade Readiness is set to the released version of the Current Branch for Business (CBB). CBB can be determined by reviewing [Windows 10 release information](https://technet.microsoft.com/windows/release-info.aspx). The target version setting is used to evaluate the number of computers that are already running this version of Windows, or a later version. As mentioned previously, the default target version in Upgrade Readiness is set to the released version of the Current Branch for Business (CBB). CBB can be determined by reviewing [Windows 10 release information](https://technet.microsoft.com/windows/release-info.aspx). The target version setting is used to evaluate the number of computers that are already running this version of Windows, or a later version.
@ -45,10 +45,10 @@ You now have the ability to change the Windows 10 version you wish to target. Th
To change the target version setting, click on **Solutions Settings**, which appears at the top when you open you Upgrade Readiness solution: To change the target version setting, click on **Solutions Settings**, which appears at the top when you open you Upgrade Readiness solution:
![Target version](../images/ua-cg-08.png) ![Upgrade Readiness dialog showing gear labeled Solution Settings](../images/ua-cg-08.png)
>You must be signed in to Upgrade Readiness as an administrator to view settings. >You must be signed in to Upgrade Readiness as an administrator to view settings.
On the **Upgrade Readiness Settings** page, choose one of the options in the drop down box and click **Save**. The changes in the target version setting are reflected in evaluations when a new snapshot is uploaded to your workspace. On the **Upgrade Readiness Settings** page, choose one of the options in the drop down box and click **Save**. The changes in the target version setting are reflected in evaluations when a new snapshot is uploaded to your workspace.
![Target version](../images/ur-settings.png) ![Upgrade Readiness Settings dialog showing gear labeled Save and arrow labeled Cancel](../images/ur-settings.png)

2
windows/device-security/TOC.md
View File

@ -89,7 +89,7 @@
#### [AppLocker Settings](applocker\applocker-settings.md) #### [AppLocker Settings](applocker\applocker-settings.md)
## [BitLocker](bitlocker\bitlocker-overview.md) ## [BitLocker](bitlocker\bitlocker-overview.md)
### [Overview of BitLocker and device encryption in Windows 10](bitlocker\bitlocker-device-encryption-overview-windows-10.md) ### [Overview of BitLocker Device Encryption in Windows 10](bitlocker\bitlocker-device-encryption-overview-windows-10.md)
### [BitLocker frequently asked questions (FAQ)](bitlocker\bitlocker-frequently-asked-questions.md) ### [BitLocker frequently asked questions (FAQ)](bitlocker\bitlocker-frequently-asked-questions.md)
### [Prepare your organization for BitLocker: Planning and policies](bitlocker\prepare-your-organization-for-bitlocker-planning-and-policies.md) ### [Prepare your organization for BitLocker: Planning and policies](bitlocker\prepare-your-organization-for-bitlocker-planning-and-policies.md)
### [BitLocker basic deployment](bitlocker\bitlocker-basic-deployment.md) ### [BitLocker basic deployment](bitlocker\bitlocker-basic-deployment.md)