mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-14 06:17:22 +00:00
Merge remote-tracking branch 'refs/remotes/origin/master' into rs5
This commit is contained in:
commit
e02e55fc19
@ -8,7 +8,7 @@ author: jdeckerms
|
||||
ms.author: jdecker
|
||||
ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 12/20/2017
|
||||
ms.date: 09/11/2018
|
||||
---
|
||||
|
||||
# Install apps on HoloLens
|
||||
@ -55,8 +55,7 @@ The method that you use to install an app from your Microsoft Store for Business
|
||||
|
||||
## Use MDM to deploy apps to HoloLens
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Online-licensed apps cannot be deployed with Microsoft Store for Business on HoloLens via an MDM provider. If attempted, apps will remain in “downloading” state. Instead, you can use your MDM provider to deploy MDM-hosted apps to HoloLens, or deploy offline-licensed apps to HoloLens via Store for Business
|
||||
|
||||
|
||||
|
||||
You can deploy UWP apps to HoloLens using your MDM provider. For Intune instructions, see [Deploy apps in Microsoft Intune](https://docs.microsoft.com/intune/deploy-use/add-apps).
|
||||
@ -64,6 +63,8 @@ You can deploy UWP apps to HoloLens using your MDM provider. For Intune instruct
|
||||
Using Intune, you can also [monitor your app deployment](https://docs.microsoft.com/intune/deploy-use/monitor-apps-in-microsoft-intune).
|
||||
|
||||
|
||||
>[!TIP]
|
||||
>In Windows 10, version 1607, online-licensed apps cannot be deployed with Microsoft Store for Business on HoloLens via an MDM provider. If attempted, apps will remain in “downloading” state. [Update your HoloLens to a later build](https://support.microsoft.com/help/12643/hololens-update-hololens) for this capability.
|
||||
|
||||
## Use the Windows Device Portal to install apps on HoloLens
|
||||
|
||||
|
@ -14,7 +14,7 @@ ms.date: 08/31/2018
|
||||
> [!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.
|
||||
|
||||
The BitLocker configuration service provider (CSP) is used by the enterprise to manage encryption of PCs and devices. This CSP was added in Windows 10, version 1703. Starting in Windows 10, next major version, it is also supported in Windows 10 Pro.
|
||||
The BitLocker configuration service provider (CSP) is used by the enterprise to manage encryption of PCs and devices. This CSP was added in Windows 10, version 1703. Starting in Windows 10, version 1809, it is also supported in Windows 10 Pro.
|
||||
|
||||
> [!Note]
|
||||
> Settings are enforced only at the time encryption is started. Encryption is not restarted with settings changes.
|
||||
|
@ -18,7 +18,7 @@ This topic shows the OMA DM device description framework (DDF) for the **BitLock
|
||||
|
||||
Looking for the DDF XML files? See [CSP DDF files download](configuration-service-provider-reference.md#csp-ddf-files-download).
|
||||
|
||||
The XML below is the current version Windows 10, next major version.
|
||||
The XML below is the current version Windows 10, version 1809.
|
||||
|
||||
``` syntax
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
|
@ -29,7 +29,7 @@ Footnotes:
|
||||
- 2 - Added in Windows 10, version 1703
|
||||
- 3 - Added in Windows 10, version 1709
|
||||
- 4 - Added in Windows 10, version 1803
|
||||
- 5 - Added in Windows 10, next major version
|
||||
- 5 - Added in Windows 10, version 1809
|
||||
|
||||
<!--StartCSPs-->
|
||||
<hr/>
|
||||
@ -2652,7 +2652,7 @@ Footnotes:
|
||||
- 2 - Added in Windows 10, version 1703
|
||||
- 3 - Added in Windows 10, version 1709
|
||||
- 4 - Added in Windows 10, version 1803
|
||||
- 5 - Added in Windows 10, next major version
|
||||
- 5 - Added in Windows 10, version 1809
|
||||
|
||||
## CSP DDF files download
|
||||
|
||||
@ -2700,7 +2700,7 @@ The following list shows the configuration service providers supported in Window
|
||||
- 2 - Added in Windows 10, version 1703
|
||||
- 3 - Added in Windows 10, version 1709
|
||||
- 4 - Added in Windows 10, version 1803
|
||||
- 5 - Added in Windows 10, next major version
|
||||
- 5 - Added in Windows 10, version 1809
|
||||
|
||||
## <a href="" id="surfacehubcspsupport"></a>CSPs supported in Microsoft Surface Hub
|
||||
|
||||
|
@ -179,7 +179,7 @@ An interior node to group information about Windows Defender health status.
|
||||
Supported operation is Get.
|
||||
|
||||
<a href="" id="health-productstatus"></a>**Health/ProductStatus**
|
||||
Added in Windows 10, next major version. Provide the current state of the product. This is a bitmask flag value that can represent one or multiple product states from below list.
|
||||
Added in Windows 10, version 1809. Provide the current state of the product. This is a bitmask flag value that can represent one or multiple product states from below list.
|
||||
|
||||
Data type is integer. Supported operation is Get.
|
||||
|
||||
|
@ -17,7 +17,7 @@ This topic shows the OMA DM device description framework (DDF) for the **Defende
|
||||
|
||||
Looking for the DDF XML files? See [CSP DDF files download](configuration-service-provider-reference.md#csp-ddf-files-download).
|
||||
|
||||
The XML below is for Windows 10, next major version.
|
||||
The XML below is for Windows 10, version 1809.
|
||||
|
||||
``` syntax
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
|
@ -146,7 +146,7 @@ The following diagram shows the DevDetail configuration service provider managem
|
||||
Supported operation is Get.
|
||||
|
||||
<a href="" id="ext-microsoft-smbiosserialnumber"></a>**Ext/Microsoft/SMBIOSSerialNumber**
|
||||
Added in Windows 10, next major version. SMBIOS Serial Number of the device.
|
||||
Added in Windows 10, version 1809. SMBIOS Serial Number of the device.
|
||||
|
||||
Value type is string. Supported operation is Get.
|
||||
|
||||
|
@ -19,7 +19,7 @@ This topic shows the OMA DM device description framework (DDF) for the **DevDeta
|
||||
|
||||
Looking for the DDF XML files? See [CSP DDF files download](configuration-service-provider-reference.md#csp-ddf-files-download).
|
||||
|
||||
The XML below is for Windows 10, next major version.
|
||||
The XML below is for Windows 10, version 1809.
|
||||
|
||||
``` syntax
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
|
@ -164,35 +164,35 @@ Required. Used for managing apps from the Microsoft Store.
|
||||
Supported operations are Get and Delete.
|
||||
|
||||
<a href="" id="appmanagement-releasemanagement"></a>**AppManagement/AppStore/ReleaseManagement**
|
||||
Added in Windows 10, next major version. Interior node for the managing updates through the Microsoft Store. These settings allow the IT admin to specify update channels for apps that they want their users to use for receiving updates. It allows the IT admin to assign a specific release to a smaller group for testing before the large deployment to the rest of the organization.
|
||||
Added in Windows 10, version 1809. Interior node for the managing updates through the Microsoft Store. These settings allow the IT admin to specify update channels for apps that they want their users to use for receiving updates. It allows the IT admin to assign a specific release to a smaller group for testing before the large deployment to the rest of the organization.
|
||||
|
||||
> [!Note]
|
||||
> ReleaseManagement settings only apply to updates through the Microsoft Store.
|
||||
|
||||
<a href="" id="appmanagement-releasemanagement-releasemanagementkey"></a>**AppManagement/AppStore/ReleaseManagement/_ReleaseManagementKey_**
|
||||
Added in Windows 10, next major version. Identifier for the app or set of apps. If there is only one app, it is the PackageFamilyName. If it is for a set of apps, it is the PackageFamilyName of the main app.
|
||||
Added in Windows 10, version 1809. Identifier for the app or set of apps. If there is only one app, it is the PackageFamilyName. If it is for a set of apps, it is the PackageFamilyName of the main app.
|
||||
|
||||
|
||||
<a href="" id="appmanagement-releasemanagement-releasemanagementkey-channelid"></a>**AppManagement/AppStore/ReleaseManagement/_ReleaseManagementKey_/ChannelId**
|
||||
Added in Windows 10, next major version. Specifies the app channel ID.
|
||||
Added in Windows 10, version 1809. Specifies the app channel ID.
|
||||
|
||||
Value type is string. Supported operations are Add, Get, Replace, and Delete.
|
||||
|
||||
<a href="" id="appmanagement-releasemanagement-releasemanagementkey-releasemanagementid"></a>**AppManagement/AppStore/ReleaseManagement/_ReleaseManagementKey_/ReleaseManagementId**
|
||||
Added in Windows 10, next major version. The IT admin can specify a release ID to indicate a specific release they would like the user or device to be on.
|
||||
Added in Windows 10, version 1809. The IT admin can specify a release ID to indicate a specific release they would like the user or device to be on.
|
||||
|
||||
Value type is string. Supported operations are Add, Get, Replace, and Delete.
|
||||
|
||||
<a href="" id="appmanagement-releasemanagement-releasemanagementkey-effectiverelease"></a>**AppManagement/AppStore/ReleaseManagement/_ReleaseManagementKey_/EffectiveRelease**
|
||||
Added in Windows 10, next major version. Interior node used to specify the effective app release to use when multiple user policies are set on the device. The device policy or last user policy is used.
|
||||
Added in Windows 10, version 1809. Interior node used to specify the effective app release to use when multiple user policies are set on the device. The device policy or last user policy is used.
|
||||
|
||||
<a href="" id="appmanagement-releasemanagement-releasemanagementkey-effectiverelease-channelid"></a>**AppManagement/AppStore/ReleaseManagement/_ReleaseManagementKey_/EffectiveRelease/ChannelId**
|
||||
Added in Windows 10, next major version. Returns the last user channel ID on the device.
|
||||
Added in Windows 10, version 1809. Returns the last user channel ID on the device.
|
||||
|
||||
Value type is string. Supported operation is Get.
|
||||
|
||||
<a href="" id="appmanagement-releasemanagement-releasemanagementkey-effectiverelease-releasemanagementid"></a>**AppManagement/AppStore/ReleaseManagement/_ReleaseManagementKey_/EffectiveRelease/ReleaseManagementId**
|
||||
Added in Windows 10, next major version. Returns the last user release ID on the device.
|
||||
Added in Windows 10, version 1809. Returns the last user release ID on the device.
|
||||
|
||||
Value type is string. Supported operation is Get.
|
||||
|
||||
@ -389,7 +389,7 @@ Expected Behavior on an AMD64 machine that has x86 flavor of an app installed (M
|
||||
|False (not set) |Not configured |X64 flavor is picked |
|
||||
|
||||
<a href="" id="----packagefamilyname-nonremovable"></a>**.../_PackageFamilyName_/NonRemovable**
|
||||
Added in Windows 10, next major version. Specifies if an app is nonremovable by the user.
|
||||
Added in Windows 10, version 1809. Specifies if an app is nonremovable by the user.
|
||||
|
||||
This setting allows the IT admin to set an app to be nonremovable, or unable to be uninstalled by a user. This is useful in enterprise and education scenarios, where the IT admin might want to ensure that everyone always has certain apps and they won't be removed accidentally. This is also useful when there are multiple users per device, and you want to ensure that one user doesn’t remove it for all users.
|
||||
|
||||
|
@ -19,7 +19,7 @@ This topic shows the OMA DM device description framework (DDF) for the **Enterpr
|
||||
|
||||
Looking for the DDF XML files? See [CSP DDF files download](configuration-service-provider-reference.md#csp-ddf-files-download).
|
||||
|
||||
The XML below is for Windows 10, next major version.
|
||||
The XML below is for Windows 10, version 1809.
|
||||
|
||||
``` syntax
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
|
@ -27,7 +27,7 @@ For details about Microsoft mobile device management protocols for Windows 10 s
|
||||
- [What's new in Windows 10, version 1703](#whatsnew10)
|
||||
- [What's new in Windows 10, version 1709](#whatsnew1709)
|
||||
- [What's new in Windows 10, version 1803](#whatsnew1803)
|
||||
- [What's new in Windows 10, next major version](#whatsnewnext)
|
||||
- [What's new in Windows 10, version 1809](#whatsnew1809)
|
||||
- [Change history in MDM documentation](#change-history-in-mdm-documentation)
|
||||
- [Breaking changes and known issues](#breaking-changes-and-known-issues)
|
||||
- [Get command inside an atomic command is not supported](#getcommand)
|
||||
@ -1359,7 +1359,7 @@ For details about Microsoft mobile device management protocols for Windows 10 s
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
## <a href="" id="whatsnewnext"></a>What's new in Windows 10, next major version
|
||||
## <a href="" id="whatsnew1809"></a>What's new in Windows 10, version 1809
|
||||
|
||||
<table class="mx-tdBreakAll">
|
||||
<colgroup>
|
||||
@ -1375,7 +1375,7 @@ For details about Microsoft mobile device management protocols for Windows 10 s
|
||||
<tbody>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[Policy CSP](policy-configuration-service-provider.md)</td>
|
||||
<td style="vertical-align:top"><p>Added the following new policies in Windows 10, next major version:</p>
|
||||
<td style="vertical-align:top"><p>Added the following new policies in Windows 10, version 1809:</p>
|
||||
<ul>
|
||||
<li>ApplicationManagement/LaunchAppAfterLogOn</li>
|
||||
<li>ApplicationManagement/ScheduleForceRestartForUpdateFailures </li>
|
||||
@ -1438,55 +1438,55 @@ For details about Microsoft mobile device management protocols for Windows 10 s
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[PassportForWork CSP](passportforwork-csp.md)</td>
|
||||
<td style="vertical-align:top"><p>Added new settings in Windows 10, next major version.</p>
|
||||
<td style="vertical-align:top"><p>Added new settings in Windows 10, version 1809.</p>
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[EnterpriseModernAppManagement CSP](enterprisemodernappmanagement-csp.md)</td>
|
||||
<td style="vertical-align:top"><p>Added NonRemovable setting under AppManagement node in Windows 10, next major version.</p>
|
||||
<td style="vertical-align:top"><p>Added NonRemovable setting under AppManagement node in Windows 10, version 1809.</p>
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[Win32CompatibilityAppraiser CSP](win32compatibilityappraiser-csp.md)</td>
|
||||
<td style="vertical-align:top"><p>Added new configuration service provider in Windows 10, next major version.</p>
|
||||
<td style="vertical-align:top"><p>Added new configuration service provider in Windows 10, version 1809.</p>
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[WindowsLicensing CSP](windowslicensing-csp.md)</td>
|
||||
<td style="vertical-align:top"><p>Added S mode settings and SyncML examples in Windows 10, next major version.</p>
|
||||
<td style="vertical-align:top"><p>Added S mode settings and SyncML examples in Windows 10, version 1809.</p>
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[SUPL CSP](supl-csp.md)</td>
|
||||
<td style="vertical-align:top"><p>Added 3 new certificate nodes in Windows 10, next major version.</p>
|
||||
<td style="vertical-align:top"><p>Added 3 new certificate nodes in Windows 10, version 1809.</p>
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[Defender CSP](defender-csp.md)</td>
|
||||
<td style="vertical-align:top"><p>Added a new node Health/ProductStatus in Windows 10, next major version.</p>
|
||||
<td style="vertical-align:top"><p>Added a new node Health/ProductStatus in Windows 10, version 1809.</p>
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[BitLocker CSP](bitlocker-csp.md)</td>
|
||||
<td style="vertical-align:top"><p>Added a new node AllowStandardUserEncryption in Windows 10, next major version. Added support for Windows 10 Pro.</p>
|
||||
<td style="vertical-align:top"><p>Added a new node AllowStandardUserEncryption in Windows 10, version 1809. Added support for Windows 10 Pro.</p>
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[DevDetail CSP](devdetail-csp.md)</td>
|
||||
<td style="vertical-align:top"><p>Added a new node SMBIOSSerialNumber in Windows 10, next major version.</p>
|
||||
<td style="vertical-align:top"><p>Added a new node SMBIOSSerialNumber in Windows 10, version 1809.</p>
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[Wifi CSP](wifi-csp.md)</td>
|
||||
<td style="vertical-align:top"><p>Added a new node WifiCost in Windows 10, next major version.</p>
|
||||
<td style="vertical-align:top"><p>Added a new node WifiCost in Windows 10, version 1809.</p>
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[WindowsDefenderApplicationGuard CSP](windowsdefenderapplicationguard-csp.md)</td>
|
||||
<td style="vertical-align:top"><p>Added new settings in Windows 10, next major version.</p>
|
||||
<td style="vertical-align:top"><p>Added new settings in Windows 10, version 1809.</p>
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[RemoteWipe CSP](remotewipe-csp.md)</td>
|
||||
<td style="vertical-align:top"><p>Added new settings in Windows 10, next major version.</p>
|
||||
<td style="vertical-align:top"><p>Added new settings in Windows 10, version 1809.</p>
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[TenantLockdown CSP](\tenantlockdown--csp.md)</td>
|
||||
<td style="vertical-align:top"><p>Added new CSP in Windows 10, next major version.</p>
|
||||
<td style="vertical-align:top"><p>Added new CSP in Windows 10, version 1809.</p>
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[Office CSP](office-csp.md)</td>
|
||||
<td style="vertical-align:top"><p>Added FinalStatus setting in Windows 10, next major version.</p>
|
||||
<td style="vertical-align:top"><p>Added FinalStatus setting in Windows 10, version 1809.</p>
|
||||
</td></tr>
|
||||
</tbody>
|
||||
</table>
|
||||
@ -1605,7 +1605,8 @@ The following list describes the prerequisites for a certificate to be used with
|
||||
|
||||
The following XML sample explains the properties for the EAP TLS XML including certificate filtering.
|
||||
|
||||
> **Note** For PEAP or TTLS Profiles the EAP TLS XML is embedded within some PEAP or TTLS specific elements.
|
||||
>[!NOTE]
|
||||
>For PEAP or TTLS Profiles the EAP TLS XML is embedded within some PEAP or TTLS specific elements.
|
||||
|
||||
|
||||
``` syntax
|
||||
@ -1707,7 +1708,8 @@ The following XML sample explains the properties for the EAP TLS XML including c
|
||||
</EapHostConfig>
|
||||
```
|
||||
|
||||
> **Note** The EAP TLS XSD is located at **%systemdrive%\\Windows\\schemas\\EAPMethods\\eaptlsconnectionpropertiesv3.xsd**
|
||||
>[!NOTE]
|
||||
>The EAP TLS XSD is located at **%systemdrive%\\Windows\\schemas\\EAPMethods\\eaptlsconnectionpropertiesv3.xsd**
|
||||
|
||||
|
||||
|
||||
@ -1774,31 +1776,31 @@ The DM agent for [push-button reset](https://msdn.microsoft.com/windows/hardware
|
||||
<tbody>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[BitLocker CSP](bitlocker-csp.md)</td>
|
||||
<td style="vertical-align:top"><p>Added support for Windows 10 Pro starting in the next major version.</p>
|
||||
<td style="vertical-align:top"><p>Added support for Windows 10 Pro starting in the version 1809.</p>
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[Office CSP](office-csp.md)</td>
|
||||
<td style="vertical-align:top"><p>Added FinalStatus setting in Windows 10, next major version.</p>
|
||||
<td style="vertical-align:top"><p>Added FinalStatus setting in Windows 10, version 1809.</p>
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[RemoteWipe CSP](remotewipe-csp.md)</td>
|
||||
<td style="vertical-align:top"><p>Added new settings in Windows 10, next major version.</p>
|
||||
<td style="vertical-align:top"><p>Added new settings in Windows 10, version 1809.</p>
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[TenantLockdown CSP](\tenantlockdown--csp.md)</td>
|
||||
<td style="vertical-align:top"><p>Added new CSP in Windows 10, next major version.</p>
|
||||
<td style="vertical-align:top"><p>Added new CSP in Windows 10, version 1809.</p>
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[WindowsDefenderApplicationGuard CSP](windowsdefenderapplicationguard-csp.md)</td>
|
||||
<td style="vertical-align:top"><p>Added new settings in Windows 10, next major version.</p>
|
||||
<td style="vertical-align:top"><p>Added new settings in Windows 10, version 1809.</p>
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[Policy DDF file](policy-ddf-file.md)</td>
|
||||
<td style="vertical-align:top"><p>Posted an updated version of the Policy DDF for Windows 10, next major version.</p>
|
||||
<td style="vertical-align:top"><p>Posted an updated version of the Policy DDF for Windows 10, version 1809.</p>
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[Policy CSP](policy-configuration-service-provider.md)</td>
|
||||
<td style="vertical-align:top"><p>Added the following new policies in Windows 10, next major version:</p>
|
||||
<td style="vertical-align:top"><p>Added the following new policies in Windows 10, version 1809:</p>
|
||||
<ul>
|
||||
<li>Browser/AllowFullScreenMode</li>
|
||||
<li>Browser/AllowPrelaunch</li>
|
||||
@ -1859,39 +1861,39 @@ The DM agent for [push-button reset](https://msdn.microsoft.com/windows/hardware
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[PassportForWork CSP](passportforwork-csp.md)</td>
|
||||
<td style="vertical-align:top"><p>Added new settings in Windows 10, next major version.</p>
|
||||
<td style="vertical-align:top"><p>Added new settings in Windows 10, version 1809.</p>
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[EnterpriseModernAppManagement CSP](enterprisemodernappmanagement-csp.md)</td>
|
||||
<td style="vertical-align:top"><p>Added NonRemovable setting under AppManagement node in Windows 10, next major version.</p>
|
||||
<td style="vertical-align:top"><p>Added NonRemovable setting under AppManagement node in Windows 10, version 1809.</p>
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[Win32CompatibilityAppraiser CSP](win32compatibilityappraiser-csp.md)</td>
|
||||
<td style="vertical-align:top"><p>Added new configuration service provider in Windows 10, next major version.</p>
|
||||
<td style="vertical-align:top"><p>Added new configuration service provider in Windows 10, version 1809.</p>
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[WindowsLicensing CSP](windowslicensing-csp.md)</td>
|
||||
<td style="vertical-align:top"><p>Added S mode settings and SyncML examples in Windows 10, next major version.</p>
|
||||
<td style="vertical-align:top"><p>Added S mode settings and SyncML examples in Windows 10, version 1809.</p>
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[SUPL CSP](supl-csp.md)</td>
|
||||
<td style="vertical-align:top"><p>Added 3 new certificate nodes in Windows 10, next major version.</p>
|
||||
<td style="vertical-align:top"><p>Added 3 new certificate nodes in Windows 10, version 1809.</p>
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[Defender CSP](defender-csp.md)</td>
|
||||
<td style="vertical-align:top"><p>Added a new node Health/ProductStatus in Windows 10, next major version.</p>
|
||||
<td style="vertical-align:top"><p>Added a new node Health/ProductStatus in Windows 10, version 1809.</p>
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[BitLocker CSP](bitlocker-csp.md)</td>
|
||||
<td style="vertical-align:top"><p>Added a new node AllowStandardUserEncryption in Windows 10, next major version.</p>
|
||||
<td style="vertical-align:top"><p>Added a new node AllowStandardUserEncryption in Windows 10, version 1809.</p>
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[DevDetail CSP](devdetail-csp.md)</td>
|
||||
<td style="vertical-align:top"><p>Added a new node SMBIOSSerialNumber in Windows 10, next major version.</p>
|
||||
<td style="vertical-align:top"><p>Added a new node SMBIOSSerialNumber in Windows 10, version 1809.</p>
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[Policy CSP](policy-configuration-service-provider.md)</td>
|
||||
<td style="vertical-align:top"><p>Added the following new policies in Windows 10, next major version:</p>
|
||||
<td style="vertical-align:top"><p>Added the following new policies in Windows 10, version 1809:</p>
|
||||
<ul>
|
||||
<li>ApplicationManagement/LaunchAppAfterLogOn</li>
|
||||
<li>ApplicationManagement/ScheduleForceRestartForUpdateFailures </li>
|
||||
@ -1920,7 +1922,7 @@ The DM agent for [push-button reset](https://msdn.microsoft.com/windows/hardware
|
||||
</ul>
|
||||
<p>Recent changes:</p>
|
||||
<ul>
|
||||
<li>DataUsage/SetCost3G - deprecated in Windows 10, next major version.</li>
|
||||
<li>DataUsage/SetCost3G - deprecated in Windows 10, version 1809.</li>
|
||||
</ul>
|
||||
</td></tr>
|
||||
</tbody>
|
||||
@ -1942,7 +1944,7 @@ The DM agent for [push-button reset](https://msdn.microsoft.com/windows/hardware
|
||||
<tbody>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[Wifi CSP](wifi-csp.md)</td>
|
||||
<td style="vertical-align:top"><p>Added a new node WifiCost in Windows 10, next major version.</p>
|
||||
<td style="vertical-align:top"><p>Added a new node WifiCost in Windows 10, version 1809.</p>
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[Diagnose MDM failures in Windows 10](diagnose-mdm-failures-in-windows-10.md)</td>
|
||||
@ -1954,7 +1956,7 @@ The DM agent for [push-button reset](https://msdn.microsoft.com/windows/hardware
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[Bitlocker CSP](bitlocker-csp.md)</td>
|
||||
<td style="vertical-align:top"><p>Added new node AllowStandardUserEncryption in Windows 10, next major version.</p>
|
||||
<td style="vertical-align:top"><p>Added new node AllowStandardUserEncryption in Windows 10, version 1809.</p>
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[Policy CSP](policy-configuration-service-provider.md)</td>
|
||||
@ -1969,7 +1971,7 @@ The DM agent for [push-button reset](https://msdn.microsoft.com/windows/hardware
|
||||
<li>Start/StartLayout - added a table of SKU support information.</li>
|
||||
<li>Start/ImportEdgeAssets - added a table of SKU support information.</li>
|
||||
</ul>
|
||||
<p>Added the following new policies in Windows 10, next major version:</p>
|
||||
<p>Added the following new policies in Windows 10, version 1809:</p>
|
||||
<ul>
|
||||
<li>Update/EngagedRestartDeadlineForFeatureUpdates</li>
|
||||
<li>Update/EngagedRestartSnoozeScheduleForFeatureUpdates</li>
|
||||
@ -1980,7 +1982,7 @@ The DM agent for [push-button reset](https://msdn.microsoft.com/windows/hardware
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[WiredNetwork CSP](wirednetwork-csp.md)</td>
|
||||
<td style="vertical-align:top">New CSP added in Windows 10, next major version.
|
||||
<td style="vertical-align:top">New CSP added in Windows 10, version 1809.
|
||||
</td></tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
@ -48,7 +48,7 @@ The Microsoft Office installation status.
|
||||
The only supported operation is Get.
|
||||
|
||||
<a href="" id="finalstatus"></a>**Installation/_id_/FinalStatus**
|
||||
Added in Windows 10, next major version. Indicates the status of the Final Office 365 installation.
|
||||
Added in Windows 10, version 1809. Indicates the status of the Final Office 365 installation.
|
||||
|
||||
The only supported operation is Get.
|
||||
|
||||
|
@ -19,7 +19,7 @@ This topic shows the OMA DM device description framework (DDF) for the **Office*
|
||||
|
||||
Looking for the DDF XML files? See [CSP DDF files download](configuration-service-provider-reference.md#csp-ddf-files-download).
|
||||
|
||||
The XML below is for Windows 10, next major version.
|
||||
The XML below is for Windows 10, version 1809.
|
||||
|
||||
``` syntax
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
|
@ -194,7 +194,7 @@ Supported operations are Add, Get, Delete, and Replace.
|
||||
*Not supported on Windows Holographic and Windows Holographic for Business.*
|
||||
|
||||
<a href="" id="tenantid-policies-usehellocertificatesassmartcardcertificates"></a>***TenantId*/Policies/UseHelloCertificatesAsSmartCardCertificates** (only for ./Device/Vendor/MSFT)
|
||||
Added in Windows 10, next major version. If you enable this policy setting, applications use Windows Hello for Business certificates as smart card certificates. Biometric factors are unavailable when a user is asked to authorize the use of the certificate's private key. This policy setting is designed to allow compatibility with applications that rely exclusively on smart card certificates.
|
||||
Added in Windows 10, version 1809. If you enable this policy setting, applications use Windows Hello for Business certificates as smart card certificates. Biometric factors are unavailable when a user is asked to authorize the use of the certificate's private key. This policy setting is designed to allow compatibility with applications that rely exclusively on smart card certificates.
|
||||
|
||||
If you disable or do not configure this policy setting, applications do not use Windows Hello for Business certificates as smart card certificates, and biometric factors are available when a user is asked to authorize the use of the certificate's private key.
|
||||
|
||||
|
@ -19,7 +19,7 @@ This topic shows the OMA DM device description framework (DDF) for the **Passpor
|
||||
|
||||
Looking for the DDF XML files? See [CSP DDF files download](configuration-service-provider-reference.md#csp-ddf-files-download).
|
||||
|
||||
The XML below is for Windows 10, next major version.
|
||||
The XML below is for Windows 10, version 1809.
|
||||
|
||||
``` syntax
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
|
@ -2333,7 +2333,7 @@ Supported values:
|
||||
If you don't want to send traffic to Microsoft, use the \<about:blank\> value, which honors both domain and non domain-joined devices when it's the only configured URL.
|
||||
|
||||
|
||||
**Next major version**:<br>
|
||||
**version 1809**:<br>
|
||||
When you enable this policy and select an option, and also enter the URLs of the pages you want in HomePages, Microsoft Edge ignores HomePages.
|
||||
|
||||
<!--/Description-->
|
||||
|
@ -68,7 +68,7 @@ Added in Windows 10, version 1803. This policy allows the IT admin to control wh
|
||||
> MDMWinsOverGP only applies to policies in Policy CSP. It does not apply to other MDM settings with equivalent GP settings that are defined on other configuration service providers.
|
||||
|
||||
This policy is used to ensure that MDM policy wins over GP when same setting is set by both GP and MDM channel. The default value is 0. The MDM policies in Policy CSP will behave as described if this policy value is set 1.
|
||||
Note: This policy doesn’t support Delete command. This policy doesn’t support setting the value to be 0 again after it was previously set 1. In Windows 10, next major version, Delete command and setting the value to be 0 again if it was previously set to 1 will be supported.
|
||||
Note: This policy doesn’t support Delete command. This policy doesn’t support setting the value to be 0 again after it was previously set 1. In Windows 10, version 1809, Delete command and setting the value to be 0 again if it was previously set to 1 will be supported.
|
||||
|
||||
The following list shows the supported values:
|
||||
|
||||
|
@ -34,7 +34,7 @@ ms.date: 07/13/2018
|
||||
<a href="" id="datausage-setcost3g"></a>**DataUsage/SetCost3G**
|
||||
|
||||
<!--Description-->
|
||||
This policy is deprecated in Windows 10, next major version.
|
||||
This policy is deprecated in Windows 10, version 1809.
|
||||
|
||||
<!--/Description-->
|
||||
|
||||
|
@ -822,7 +822,7 @@ GP Info:
|
||||
<!--Description-->
|
||||
|
||||
> [!Warning]
|
||||
> Starting in the next major version of Windows, this policy is deprecated.
|
||||
> Starting in the version 1809 of Windows, this policy is deprecated.
|
||||
|
||||
Domain member: Digitally encrypt or sign secure channel data (always)
|
||||
|
||||
@ -892,7 +892,7 @@ GP Info:
|
||||
<!--Description-->
|
||||
|
||||
> [!Warning]
|
||||
> Starting in the next major version of Windows, this policy is deprecated.
|
||||
> Starting in the version 1809 of Windows, this policy is deprecated.
|
||||
|
||||
Domain member: Digitally encrypt secure channel data (when possible)
|
||||
|
||||
@ -959,7 +959,7 @@ GP Info:
|
||||
<!--Description-->
|
||||
|
||||
> [!Warning]
|
||||
> Starting in the next major version of Windows, this policy is deprecated.
|
||||
> Starting in the version 1809 of Windows, this policy is deprecated.
|
||||
|
||||
Domain member: Disable machine account password changes
|
||||
|
||||
|
@ -370,7 +370,7 @@ The following list shows the supported values:
|
||||
|
||||
<!--/Scope-->
|
||||
<!--Description-->
|
||||
Added in Windows 10, next major version. Specifies whether clipboard items roam across devices. When this is allowed, an item copied to the clipboard is uploaded to the cloud so that other devices can access. Also, when this is allowed, a new clipboard item on the cloud is downloaded to a device so that user can paste on the device.
|
||||
Added in Windows 10, version 1809. Specifies whether clipboard items roam across devices. When this is allowed, an item copied to the clipboard is uploaded to the cloud so that other devices can access. Also, when this is allowed, a new clipboard item on the cloud is downloaded to a device so that user can paste on the device.
|
||||
|
||||
Most restricted value is 0.
|
||||
|
||||
@ -430,7 +430,7 @@ The following list shows the supported values:
|
||||
|
||||
<!--/Scope-->
|
||||
<!--Description-->
|
||||
Updated in Windows 10, next major version. This policy specifies whether users on the device have the option to enable online speech recognition. When enabled, users can use their voice for dictation and to talk to Cortana and other apps that use Microsoft cloud-based speech recognition. Microsoft will use voice input to help improve our speech services. If the policy value is set to 0, online speech recognition will be disabled and users cannot enable online speech recognition via settings. If policy value is set to 1 or is not configured, control is deferred to users.
|
||||
Updated in Windows 10, version 1809. This policy specifies whether users on the device have the option to enable online speech recognition. When enabled, users can use their voice for dictation and to talk to Cortana and other apps that use Microsoft cloud-based speech recognition. Microsoft will use voice input to help improve our speech services. If the policy value is set to 0, online speech recognition will be disabled and users cannot enable online speech recognition via settings. If policy value is set to 1 or is not configured, control is deferred to users.
|
||||
|
||||
Most restricted value is 0.
|
||||
|
||||
|
@ -66,7 +66,7 @@ This security setting allows an administrator to define the members of a securit
|
||||
|
||||
Caution: If a Restricted Groups policy is applied, any current member not on the Restricted Groups policy members list is removed. This can include default members, such as administrators. Restricted Groups should be used primarily to configure membership of local groups on workstation or member servers. An empty Members list means that the restricted group has no members.
|
||||
|
||||
Starting in Windows 10, next major version, you can use this schema for retrieval and application of the RestrictedGroups/ConfigureGroupMembership policy. A minimum occurrence of 0 members when applying the policy implies clearing the access group and should be used with caution.
|
||||
Starting in Windows 10, version 1809, you can use this schema for retrieval and application of the RestrictedGroups/ConfigureGroupMembership policy. A minimum occurrence of 0 members when applying the policy implies clearing the access group and should be used with caution.
|
||||
|
||||
``` syntax
|
||||
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" version="1.0">
|
||||
|
@ -530,7 +530,7 @@ The following list shows the supported values:
|
||||
|
||||
<!--/Scope-->
|
||||
<!--Description-->
|
||||
Added in Windows 10, next major version. This policy controls the Admin Authentication requirement in RecoveryEnvironment.
|
||||
Added in Windows 10, version 1809. This policy controls the Admin Authentication requirement in RecoveryEnvironment.
|
||||
|
||||
Supported values:
|
||||
- 0 - Default: Keep using default(current) behavior
|
||||
|
@ -27,7 +27,7 @@ You can download the DDF files from the links below:
|
||||
- [Download the Policy DDF file for Windows 10, version 1607 release 8C](https://download.microsoft.com/download/6/1/C/61C022FD-6F5D-4F73-9047-17F630899DC4/PolicyDDF_all_version1607_8C.xml)
|
||||
- [CSP DDF files download](configuration-service-provider-reference.md#csp-ddf-files-download)
|
||||
|
||||
The XML below is the DDF for Windows 10, next major version.
|
||||
The XML below is the DDF for Windows 10, version 1809.
|
||||
|
||||
``` syntax
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
|
@ -17,7 +17,7 @@ This topic shows the OMA DM device description framework (DDF) for the **RemoteW
|
||||
|
||||
Looking for the DDF XML files? See [CSP DDF files download](configuration-service-provider-reference.md#csp-ddf-files-download).
|
||||
|
||||
The XML below is the DDF for Windows 10, next major version.
|
||||
The XML below is the DDF for Windows 10, version 1809.
|
||||
|
||||
``` syntax
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
|
@ -241,31 +241,31 @@ Specifies the name of the H-SLP root certificate as a string, in the format *nam
|
||||
The base 64 encoded blob of the H-SLP root certificate.
|
||||
|
||||
<a href="" id="rootcertificate"></a>**RootCertificate4**
|
||||
Added in Windows 10, next major version. Specifies the root certificate for the H-SLP server.
|
||||
Added in Windows 10, version 1809. Specifies the root certificate for the H-SLP server.
|
||||
|
||||
<a href="" id="rootcertificate-name"></a>**RootCertificate4/Name**
|
||||
Added in Windows 10, next major version. Specifies the name of the H-SLP root certificate as a string, in the format *name*.cer.
|
||||
Added in Windows 10, version 1809. Specifies the name of the H-SLP root certificate as a string, in the format *name*.cer.
|
||||
|
||||
<a href="" id="rootcertificate-data"></a>**RootCertificate4/Data**
|
||||
Added in Windows 10, next major version. The base 64 encoded blob of the H-SLP root certificate.
|
||||
Added in Windows 10, version 1809. The base 64 encoded blob of the H-SLP root certificate.
|
||||
|
||||
<a href="" id="rootcertificate"></a>**RootCertificate5**
|
||||
Added in Windows 10, next major version. Specifies the root certificate for the H-SLP server.
|
||||
Added in Windows 10, version 1809. Specifies the root certificate for the H-SLP server.
|
||||
|
||||
<a href="" id="rootcertificate2-name"></a>**RootCertificate5/Name**
|
||||
Added in Windows 10, next major version. Specifies the name of the H-SLP root certificate as a string, in the format *name*.cer.
|
||||
Added in Windows 10, version 1809. Specifies the name of the H-SLP root certificate as a string, in the format *name*.cer.
|
||||
|
||||
<a href="" id="rootcertificate2-data"></a>**RootCertificate5/Data**
|
||||
Added in Windows 10, next major version. The base 64 encoded blob of the H-SLP root certificate.
|
||||
Added in Windows 10, version 1809. The base 64 encoded blob of the H-SLP root certificate.
|
||||
|
||||
<a href="" id="rootcertificate"></a>**RootCertificate6**
|
||||
Added in Windows 10, next major version. Specifies the root certificate for the H-SLP server.
|
||||
Added in Windows 10, version 1809. Specifies the root certificate for the H-SLP server.
|
||||
|
||||
<a href="" id="rootcertificate3-name"></a>**RootCertificate6/Name**
|
||||
Added in Windows 10, next major version. Specifies the name of the H-SLP root certificate as a string, in the format *name*.cer.
|
||||
Added in Windows 10, version 1809. Specifies the name of the H-SLP root certificate as a string, in the format *name*.cer.
|
||||
|
||||
<a href="" id="rootcertificate3-data"></a>**RootCertificate6/Data**
|
||||
Added in Windows 10, next major version. The base 64 encoded blob of the H-SLP root certificate.
|
||||
Added in Windows 10, version 1809. The base 64 encoded blob of the H-SLP root certificate.
|
||||
|
||||
<a href="" id="v2upl1"></a>**V2UPL1**
|
||||
Required for V2 UPL for CDMA. Specifies the account settings for user plane location and IS-801 for CDMA. Only one account is supported at a given time.
|
||||
|
@ -19,7 +19,7 @@ This topic shows the OMA DM device description framework (DDF) for the **SUPL**
|
||||
|
||||
Looking for the DDF XML files? See [CSP DDF files download](configuration-service-provider-reference.md#csp-ddf-files-download).
|
||||
|
||||
The XML below is for Windows 10, next major version.
|
||||
The XML below is for Windows 10, version 1809.
|
||||
|
||||
``` syntax
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
|
@ -12,7 +12,7 @@ ms.date: 08/13/2018
|
||||
# TenantLockdown CSP
|
||||
|
||||
> [!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. This CSP was added in Windows 10, next major version.
|
||||
> 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. This CSP was added in Windows 10, version 1809.
|
||||
|
||||
The TenantLockdown configuration service provider is used by the IT admin to lock a device to a tenant, which ensures that the device remains bound to the tenant in case of accidental or intentional resets or wipes.
|
||||
|
||||
|
@ -18,7 +18,7 @@ This topic shows the OMA DM device description framework (DDF) for the **TenantL
|
||||
|
||||
Looking for the DDF XML files? See [CSP DDF files download](configuration-service-provider-reference.md#csp-ddf-files-download).
|
||||
|
||||
The XML below is for Windows 10, next major version.
|
||||
The XML below is for Windows 10, version 1809.
|
||||
|
||||
``` syntax
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
|
@ -97,7 +97,7 @@ Added in Windows 10, version 1607. Optional. When set to true it enables Web Pr
|
||||
Value type is bool.
|
||||
|
||||
<a href="" id="wificost"></a>**WiFiCost**
|
||||
Added in Windows 10, next major version. Optional. This policy sets the cost of WLAN connection for the Wi-Fi profile. Default behaviour: Unrestricted.
|
||||
Added in Windows 10, version 1809. Optional. This policy sets the cost of WLAN connection for the Wi-Fi profile. Default behaviour: Unrestricted.
|
||||
|
||||
Supported values:
|
||||
|
||||
|
@ -17,7 +17,7 @@ ms.date: 06/28/2018
|
||||
|
||||
This topic shows the OMA DM device description framework (DDF) for the **WiFi** configuration service provider. DDF files are used only with OMA DM provisioning XML.
|
||||
|
||||
The XML below is for Windows 10, next major version.
|
||||
The XML below is for Windows 10, version 1809.
|
||||
|
||||
``` syntax
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
|
@ -14,7 +14,7 @@ ms.date: 07/19/2018
|
||||
> [!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.
|
||||
|
||||
The Win32CompatibilityAppraiser configuration service provider enables the IT admin to query the current status of the Appraiser and UTC telementry health. This CSP was added in Windows 10, next major version.
|
||||
The Win32CompatibilityAppraiser configuration service provider enables the IT admin to query the current status of the Appraiser and UTC telementry health. This CSP was added in Windows 10, version 1809.
|
||||
|
||||
The following diagram shows the Win32CompatibilityAppraiser configuration service provider in tree format.
|
||||
|
||||
|
@ -18,7 +18,7 @@ This topic shows the OMA DM device description framework (DDF) for the **Win32Co
|
||||
|
||||
Looking for the DDF XML files? See [CSP DDF files download](configuration-service-provider-reference.md#csp-ddf-files-download).
|
||||
|
||||
The XML below is for Windows 10, next major version.
|
||||
The XML below is for Windows 10, version 1809.
|
||||
|
||||
``` syntax
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
|
@ -107,7 +107,7 @@ Placeholder for future use. Do not use in production code.
|
||||
Placeholder for future use. Do not use in production code.
|
||||
|
||||
<a href="" id="certificatethumbprints"></a>**Settings/CertificateThumbprints**
|
||||
Added in Windows 10, next major version. This policy setting allows certain Root Certificates to be shared with the Windows Defender Application Guard container.
|
||||
Added in Windows 10, version 1809. This policy setting allows certain Root Certificates to be shared with the Windows Defender Application Guard container.
|
||||
|
||||
Value type is string. Supported operations are Add, Get, Replace, and Delete.
|
||||
|
||||
@ -118,7 +118,7 @@ Example: b4e72779a8a362c860c36a6461f31e3aa7e58c14,1b1d49f06d2a697a544a1059bd59a
|
||||
If you disable or don’t configure this setting, certificates are not shared with the Windows Defender Application Guard container.
|
||||
|
||||
<a href="" id="allowcameramicrophoneredirection"></a>**Settings/AllowCameraMicrophoneRedirection**
|
||||
Added in Windows 10, next major version. The policy allows you to determine whether applications inside Windows Defender Application Guard can access the device’s camera and microphone when these settings are enabled on the user’s device.
|
||||
Added in Windows 10, version 1809. The policy allows you to determine whether applications inside Windows Defender Application Guard can access the device’s camera and microphone when these settings are enabled on the user’s device.
|
||||
|
||||
Value type is integer. Supported operations are Add, Get, Replace, and Delete.
|
||||
|
||||
|
@ -18,7 +18,7 @@ This topic shows the OMA DM device description framework (DDF) for the **Windows
|
||||
|
||||
Looking for the DDF XML files? See [CSP DDF files download](configuration-service-provider-reference.md#csp-ddf-files-download).
|
||||
|
||||
This XML is for Windows 10, next major version.
|
||||
This XML is for Windows 10, version 1809.
|
||||
|
||||
```xml
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
|
@ -164,7 +164,7 @@ The supported operation is Get.
|
||||
Interior node for managing S mode.
|
||||
|
||||
<a href="" id="smode-switchingpolicy"></a>**SMode/SwitchingPolicy**
|
||||
Added in Windows 10, next major version. Determines whether a consumer can switch the device out of S mode. This setting is only applicable to devices available in S mode. For examples, see [Add S mode SwitchingPolicy](#smode-switchingpolicy-add), [Get S mode SwitchingPolicy](#smode-switchingpolicy-get), [Replace S mode SwitchingPolicy](#smode-switchingpolicy-replace) and [Delete S mode SwitchingPolicy](#smode-switchingpolicy-delete)
|
||||
Added in Windows 10, version 1809. Determines whether a consumer can switch the device out of S mode. This setting is only applicable to devices available in S mode. For examples, see [Add S mode SwitchingPolicy](#smode-switchingpolicy-add), [Get S mode SwitchingPolicy](#smode-switchingpolicy-get), [Replace S mode SwitchingPolicy](#smode-switchingpolicy-replace) and [Delete S mode SwitchingPolicy](#smode-switchingpolicy-delete)
|
||||
|
||||
Value type is integer. Supported operations are Add, Get, Replace, and Delete.
|
||||
|
||||
@ -173,12 +173,12 @@ Supported values:
|
||||
- 1 - User Blocked: The admin has blocked the user from switching their device out of S mode. Only the admin can switch the device out of S mode through the SMode/SwitchFromSMode node.
|
||||
|
||||
<a href="" id="smode-switchfromsmode"></a>**SMode/SwitchFromSMode**
|
||||
Added in Windows 10, next major version. Switches a device out of S mode if possible. Does not reboot. For an example, see [Execute SwitchFromSMode](#smode-switchfromsmode-execute)
|
||||
Added in Windows 10, version 1809. Switches a device out of S mode if possible. Does not reboot. For an example, see [Execute SwitchFromSMode](#smode-switchfromsmode-execute)
|
||||
|
||||
Supported operation is Execute.
|
||||
|
||||
<a href="" id="smode-status"></a>**SMode/Status**
|
||||
Added in Windows 10, next major version. Returns the status of the latest SwitchFromSMode set request. For an example, see [Get S mode status](#smode-status-example)
|
||||
Added in Windows 10, version 1809. Returns the status of the latest SwitchFromSMode set request. For an example, see [Get S mode status](#smode-status-example)
|
||||
|
||||
Value type is integer. Supported operation is Get.
|
||||
|
||||
|
@ -19,7 +19,7 @@ This topic shows the OMA DM device description framework (DDF) for the **Windows
|
||||
|
||||
Looking for the DDF XML files? See [CSP DDF files download](configuration-service-provider-reference.md#csp-ddf-files-download).
|
||||
|
||||
The XML below is for Windows 10, next major version.
|
||||
The XML below is for Windows 10, version 1809.
|
||||
|
||||
``` syntax
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
|
@ -14,7 +14,7 @@ ms.date: 06/27/2018
|
||||
> [!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.
|
||||
|
||||
The WiredNetwork configuration service provider (CSP) is used by the enterprise to configure wired Internet on devices that do not have GP to enable them to access corporate Internet over ethernet. This CSP was added in Windows 10, next major version.
|
||||
The WiredNetwork configuration service provider (CSP) is used by the enterprise to configure wired Internet on devices that do not have GP to enable them to access corporate Internet over ethernet. This CSP was added in Windows 10, version 1809.
|
||||
|
||||
The following diagram shows the WiredNetwork configuration service provider in tree format.
|
||||
|
||||
|
@ -61,9 +61,6 @@
|
||||
### [How Windows 10 uses the TPM](tpm/how-windows-uses-the-tpm.md)
|
||||
### [TPM Group Policy settings](tpm/trusted-platform-module-services-group-policy-settings.md)
|
||||
### [Back up the TPM recovery information to AD DS](tpm/backup-tpm-recovery-information-to-ad-ds.md)
|
||||
### [Manage TPM commands](tpm/manage-tpm-commands.md)
|
||||
### [Manage TPM lockout](tpm/manage-tpm-lockout.md)
|
||||
### [Change the TPM owner password](tpm/change-the-tpm-owner-password.md)
|
||||
### [View status, clear, or troubleshoot the TPM](tpm/initialize-and-configure-ownership-of-the-tpm.md)
|
||||
### [Understanding PCR banks on TPM 2.0 devices](tpm/switch-pcr-banks-on-tpm-2-0-devices.md)
|
||||
### [TPM recommendations](tpm/tpm-recommendations.md)
|
||||
|
@ -6,7 +6,8 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
author: brianlic-msft
|
||||
author: andreabichsel
|
||||
ms.author: v-anbic
|
||||
ms.date: 04/19/2017
|
||||
---
|
||||
|
||||
|
@ -6,7 +6,8 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
author: brianlic-msft
|
||||
author: andreabichsel
|
||||
ms.author: v-anbic
|
||||
ms.date: 04/19/2017
|
||||
---
|
||||
|
||||
|
@ -7,7 +7,8 @@ ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
author: brianlic-msft
|
||||
author: andreabichsel
|
||||
ms.author: v-anbic
|
||||
ms.date: 10/27/2017
|
||||
---
|
||||
|
||||
|
@ -1,24 +1,23 @@
|
||||
---
|
||||
title: View status, clear, or troubleshoot the TPM (Windows 10)
|
||||
title: Troubleshoot the TPM (Windows 10)
|
||||
description: This topic for the IT professional describes how to view status for, clear, or troubleshoot the Trusted Platform Module (TPM).
|
||||
ms.assetid: 1166efaf-7aa3-4420-9279-435d9c6ac6f8
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
author: brianlic-msft
|
||||
ms.date: 04/19/2017
|
||||
author: andreabichsel
|
||||
ms.author: v-anbic
|
||||
ms.date: 09/11/2018
|
||||
---
|
||||
|
||||
# View status, clear, or troubleshoot the TPM
|
||||
# Troubleshoot the TPM
|
||||
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
- Windows Server 2016
|
||||
|
||||
This topic for the IT professional describes actions you can take through the Trusted Platform Module (TPM) snap-in, **TPM.msc**:
|
||||
|
||||
- [View the status of the TPM](#view-the-status-of-the-tpm)
|
||||
This topic provides information for the IT professional to troubleshoot the Trusted Platform Module (TPM):
|
||||
|
||||
- [Troubleshoot TPM initialization](#troubleshoot-tpm-initialization)
|
||||
|
||||
@ -32,15 +31,7 @@ For information about the TPM cmdlets, see [TPM Cmdlets in Windows PowerShell](h
|
||||
|
||||
## About TPM initialization and ownership
|
||||
|
||||
Starting with Windows 10, the operating system automatically initializes and takes ownership of the TPM. This is a change from previous operating systems, where you would initialize the TPM and create an owner password. Therefore, with Windows 10, in most cases, we recommend that you avoid configuring the TPM through **TPM.msc**. The one exception is that in certain circumstances you might use **TPM.msc** to clear the TPM. For more information, see [Clear all the keys from the TPM](#clear-all-the-keys-from-the-tpm), later in this topic.
|
||||
|
||||
## View the status of the TPM
|
||||
|
||||
To view the status of the TPM, open the TPM Management console (TPM.msc). In the center pane, find the **Status** box.
|
||||
|
||||
In most cases, the status will be **Ready**. If the status is ready but “**with reduced functionality**,” see [Clear all the keys from the TPM](#clear-all-the-keys-from-the-tpm), later in this topic.
|
||||
|
||||
If the status is **Not ready**, you can try the steps in [Clear all the keys from the TPM](#clear-all-the-keys-from-the-tpm), later in this topic. If this does not bring it to a **Ready** state, contact the manufacturer, and see the troubleshooting suggestions in the next section.
|
||||
Starting with Windows 10, the operating system automatically initializes and takes ownership of the TPM. This is a change from previous operating systems, where you would initialize the TPM and create an owner password.
|
||||
|
||||
## Troubleshoot TPM initialization
|
||||
|
||||
@ -72,19 +63,13 @@ For example, toggling TPMs will cause BitLocker to enter recovery mode. We stron
|
||||
|
||||
## Clear all the keys from the TPM
|
||||
|
||||
With Windows 10, in most cases, we recommend that you avoid configuring the TPM through TPM.msc. The one exception is that you can use TPM.msc to clear the TPM, for example, as a troubleshooting step, or as a final preparation before a clean installation of a new operating system. Preparing for a clean installation in this way helps ensure that the new operating system can fully deploy any TPM-based functionality that it includes, for example, attestation. However, even if the TPM is not cleared before a new operating system is installed, most TPM functionality will probably work correctly.
|
||||
You can use the Windows Defender Security Center app to clear the TPM as a troubleshooting step, or as a final preparation before a clean installation of a new operating system. Preparing for a clean installation in this way helps ensure that the new operating system can fully deploy any TPM-based functionality that it includes, such as attestation. However, even if the TPM is not cleared before a new operating system is installed, most TPM functionality will probably work correctly.
|
||||
|
||||
Clearing the TPM resets it to an unowned state. After you clear the TPM, the Windows 10 operating system will automatically re-initialize it and take ownership again.
|
||||
|
||||
> [!WARNING]
|
||||
> Clearing the TPM can result in data loss. For more information, see the next section, “Precautions to take before clearing the TPM.”
|
||||
|
||||
There are several ways to clear the TPM:
|
||||
|
||||
- **Clear the TPM as part of a complete reset of the computer**: You might want to remove all files from the computer and completely reset it, for example, in preparation for a clean installation. To do this, we recommend that you use the **Reset** option in **Settings**. When you perform a reset and use the **Remove everything** option, it will clear the TPM as part of the reset. You might be prompted to press a key before the TPM can be cleared. For more information, see the “Reset this PC” section in [Recovery options in Windows 10](https://support.microsoft.com/en-us/help/12415/windows-10-recovery-options).
|
||||
|
||||
- **Clear the TPM to fix “reduced functionality” or “Not ready” TPM status**: If you open TPM.msc and see that the TPM status is something other than **Ready**, you can try using TPM.msc to clear the TPM and fix the status. However, be sure to review the precautions in the next section.
|
||||
|
||||
### Precautions to take before clearing the TPM
|
||||
|
||||
Clearing the TPM can result in data loss. To protect against such loss, review the following precautions:
|
||||
@ -103,15 +88,19 @@ Membership in the local Administrators group, or equivalent, is the minimum requ
|
||||
|
||||
**To clear the TPM**
|
||||
|
||||
1. Open the TPM MMC (tpm.msc).
|
||||
1. Open the Windows Defender Security Center app.
|
||||
|
||||
2. If the **User Account Control** dialog box appears, confirm that the action it displays is what you want, and then click **Yes**.
|
||||
2. Click **Device security**.
|
||||
|
||||
3. Under **Actions**, click **Clear TPM**.
|
||||
3. Click **Security processor details**.
|
||||
|
||||
4. You will be prompted to restart the computer. During the restart, you might be prompted by the UEFI to press a button to confirm that you wish to clear the TPM.
|
||||
4. Click **Security processor troubleshooting**.
|
||||
|
||||
5. After the PC restarts, your TPM will be automatically prepared for use by Windows 10.
|
||||
5. Click **Clear TPM**.
|
||||
|
||||
6. You will be prompted to restart the computer. During the restart, you might be prompted by the UEFI to press a button to confirm that you wish to clear the TPM.
|
||||
|
||||
7. After the PC restarts, your TPM will be automatically prepared for use by Windows 10.
|
||||
|
||||
## <a href="" id="turn-on-or-turn-off"></a>Turn on or turn off the TPM (available only with TPM 1.2 with Windows 10, version 1507 or 1511)
|
||||
|
||||
@ -149,20 +138,6 @@ If you want to stop using the services that are provided by the TPM, you can use
|
||||
|
||||
- If you did not save your TPM owner password or no longer know it, click **I do not have the TPM owner password**, and follow the instructions that are provided in the dialog box and subsequent UEFI screens to turn off the TPM without entering the password.
|
||||
|
||||
### Change the TPM Owner Password (available only with Windows 10, version 1607 and earlier versions)
|
||||
|
||||
If you have the [owner password](https://technet.microsoft.com/itpro/windows/keep-secure/change-the-tpm-owner-password) available, you can use TPM.msc to change the TPM Owner Password.
|
||||
|
||||
1. Open the TPM MMC (tpm.msc).
|
||||
|
||||
2. In the **Action** pane, click **Change the Owner Password**
|
||||
|
||||
- If you saved your TPM owner password on a removable storage device, insert it, and then click **I have the owner password file**. In the **Select backup file with the TPM owner password** dialog box, click **Browse** to locate the .tpm file that is saved on your removable storage device, click **Open**, and then click **Turn TPM Off**.
|
||||
|
||||
- If you do not have the removable storage device with your saved TPM owner password, click **I want to enter the password**. In the **Type your TPM owner password** dialog box, type your password (including hyphens), and then click **Turn TPM Off**.
|
||||
|
||||
This capability was fully removed from TPM.msc in later versions of Windows.
|
||||
|
||||
## Use the TPM cmdlets
|
||||
|
||||
You can manage the TPM using Windows PowerShell. For details, see [TPM Cmdlets in Windows PowerShell](https://docs.microsoft.com/powershell/module/trustedplatformmodule/?view=win10-ps).
|
||||
|
@ -20,12 +20,6 @@ This topic for the IT professional describes how to manage which Trusted Platfor
|
||||
|
||||
After a computer user takes ownership of the TPM, the TPM owner can limit which TPM commands can be run by creating a list of blocked TPM commands. The list can be created and applied to all computers in a domain by using Group Policy, or a list can be created for individual computers by using the TPM MMC. Because some hardware vendors might provide additional commands or the Trusted Computing Group may decide to add commands in the future, the TPM MMC also supports the ability to block new commands.
|
||||
|
||||
Domain administrators can configure a list of blocked TPM commands by using Group Policy. Local administrators cannot allow TPM commands that are blocked through Group Policy. For more information about this Group Policy setting, see [TPM Group Policy settings](trusted-platform-module-services-group-policy-settings.md#configure-the-list-of-blocked-tpm-commands).
|
||||
|
||||
Local administrators can block commands by using the TPM MMC, and commands on the default block list are also blocked unless the Group Policy settings are changed from the default settings.
|
||||
|
||||
Two policy settings control the enforcement which allows TPM commands to run. For more information about these policy settings, see [TPM Group Policy settings](trusted-platform-module-services-group-policy-settings.md#ignore-the-default-list-of-blocked-tpm-commands).
|
||||
|
||||
The following procedures describe how to manage the TPM command lists. You must be a member of the local Administrators group.
|
||||
|
||||
**To block TPM commands by using the Local Group Policy Editor**
|
||||
|
@ -6,7 +6,8 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
author: brianlic-msft
|
||||
author: andreabichsel
|
||||
ms.author: v-anbic
|
||||
ms.date: 04/19/2017
|
||||
---
|
||||
|
||||
|
@ -6,7 +6,8 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
author: brianlic-msft
|
||||
author: andreabichsel
|
||||
ms.author: v-anbic
|
||||
ms.date: 08/16/2017
|
||||
---
|
||||
|
||||
|
@ -7,7 +7,8 @@ ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
author: brianlic-msft
|
||||
author: andreabichsel
|
||||
ms.author: v-anbic
|
||||
ms.date: 05/16/2018
|
||||
---
|
||||
|
||||
|
@ -7,7 +7,8 @@ ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
author: brianlic-msft
|
||||
author: andreabichsel
|
||||
ms-author: v-anbic
|
||||
ms.date: 08/21/2018
|
||||
---
|
||||
|
||||
|
@ -6,8 +6,9 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
author: brianlic-msft
|
||||
ms.date: 06/29/2018
|
||||
author: andreabichsel
|
||||
ms.author: v-anbic
|
||||
ms.date: 09/11/2018
|
||||
---
|
||||
|
||||
# TPM Group Policy settings
|
||||
@ -24,37 +25,7 @@ The Group Policy settings for TPM services are located at:
|
||||
|
||||
The following Group Policy settings were introduced in Window 10.
|
||||
|
||||
## Configure the list of blocked TPM commands
|
||||
|
||||
This policy setting allows you to manage the Group Policy list of Trusted Platform Module (TPM) commands that are blocked by Windows.
|
||||
|
||||
If you enable this policy setting, Windows will block the specified commands from being sent to the TPM on the computer. TPM commands are referenced by a command number. For example, command number 129 is **TPM\_OwnerReadInternalPub**, and command number 170 is **TPM\_FieldUpgrade**. To find the command number that is associated with each TPM command, at the command prompt, type **tpm.msc** to open the TPM Management Console and navigate to the **Command Management** section.
|
||||
|
||||
If you disable or do not configure this policy setting, only those TPM commands that are specified through the default or local lists can be blocked by Windows. The default list of blocked TPM commands is preconfigured by Windows.
|
||||
|
||||
- You can view the default list by typing **tpm.msc** at the command prompt, navigating to the **Command Management** section, and exposing the **On Default Block List** column.
|
||||
|
||||
- The local list of blocked TPM commands is configured outside of Group Policy by running the TPM Management Console or scripting using the **Win32\_Tpm** interface.
|
||||
|
||||
## Ignore the default list of blocked TPM commands
|
||||
|
||||
This policy setting allows you to enforce or ignore the computer's default list of blocked Trusted Platform Module (TPM) commands.
|
||||
|
||||
The default list of blocked TPM commands is preconfigured by Windows. You can view the default list by typing **tpm.msc** at the command prompt to open the TPM Management Console, navigating to the **Command Management** section, and exposing the **On Default Block List** column.
|
||||
|
||||
If you enable this policy setting, the Windows operating system will ignore the computer's default list of blocked TPM commands, and it will block only those TPM commands that are specified by Group Policy or the local list.
|
||||
|
||||
If you disable or do not configure this policy setting, Windows will block the TPM commands in the default list, in addition to the commands that are specified by Group Policy and the local list of blocked TPM commands.
|
||||
|
||||
## Ignore the local list of blocked TPM commands
|
||||
|
||||
This policy setting allows you to enforce or ignore the computer's local list of blocked Trusted Platform Module (TPM) commands.
|
||||
|
||||
The local list of blocked TPM commands is configured outside of Group Policy by typing **tpm.msc** at the command prompt to open the TPM Management Console, or scripting using the **Win32\_Tpm** interface. (The default list of blocked TPM commands is preconfigured by Windows.)
|
||||
|
||||
If you enable this policy setting, the Windows operating system will ignore the computer's local list of blocked TPM commands, and it will block only those TPM commands that are specified by Group Policy or the default list.
|
||||
|
||||
If you disable or do not configure this policy setting, Windows will block the TPM commands in the local list, in addition to the commands that are specified in Group Policy and the default list of blocked TPM commands.
|
||||
|
||||
## Configure the level of TPM owner authorization information available to the operating system
|
||||
|
||||
@ -115,7 +86,7 @@ For each standard user, two thresholds apply. Exceeding either threshold prevent
|
||||
|
||||
- [Standard User Total Lockout Threshold](#standard-user-total-lockout-threshold) This value is the maximum total number of authorization failures that all standard users can have before all standard users are not allowed to send commands that require authorization to the TPM.
|
||||
|
||||
An administrator with the TPM owner password can fully reset the TPM's hardware lockout logic by using the TPM Management Console (tpm.msc). Each time an administrator resets the TPM's hardware lockout logic, all prior standard user TPM authorization failures are ignored. This allows standard users to immediately use the TPM normally.
|
||||
An administrator with the TPM owner password can fully reset the TPM's hardware lockout logic by using the Windows Defender Security Center. Each time an administrator resets the TPM's hardware lockout logic, all prior standard user TPM authorization failures are ignored. This allows standard users to immediately use the TPM normally.
|
||||
|
||||
If you do not configure this policy setting, a default value of 480 minutes (8 hours) is used.
|
||||
|
||||
@ -127,7 +98,7 @@ This setting helps administrators prevent the TPM hardware from entering a locko
|
||||
|
||||
An authorization failure occurs each time a standard user sends a command to the TPM and receives an error response indicating an authorization failure occurred. Authorization failures older than the duration are ignored.
|
||||
|
||||
An administrator with the TPM owner password can fully reset the TPM's hardware lockout logic by using the TPM Management Console (tpm.msc). Each time an administrator resets the TPM's hardware lockout logic, all prior standard user TPM authorization failures are ignored. This allows standard users to immediately use the TPM normally.
|
||||
An administrator with the TPM owner password can fully reset the TPM's hardware lockout logic by using the Windows Defender Security Center. Each time an administrator resets the TPM's hardware lockout logic, all prior standard user TPM authorization failures are ignored. This allows standard users to immediately use the TPM normally.
|
||||
|
||||
If you do not configure this policy setting, a default value of 4 is used. A value of zero means that the operating system will not allow standard users to send commands to the TPM, which might cause an authorization failure.
|
||||
|
||||
@ -139,7 +110,7 @@ This setting helps administrators prevent the TPM hardware from entering a locko
|
||||
|
||||
An authorization failure occurs each time a standard user sends a command to the TPM and receives an error response indicating an authorization failure occurred. Authorization failures older than the duration are ignored.
|
||||
|
||||
An administrator with the TPM owner password can fully reset the TPM's hardware lockout logic by using the TPM Management Console (tpm.msc). Each time an administrator resets the TPM's hardware lockout logic, all prior standard user TPM authorization failures are ignored. This allows standard users to immediately use the TPM normally.
|
||||
An administrator with the TPM owner password can fully reset the TPM's hardware lockout logic by using the Windows Defender Security Center. Each time an administrator resets the TPM's hardware lockout logic, all prior standard user TPM authorization failures are ignored. This allows standard users to immediately use the TPM normally.
|
||||
|
||||
If you do not configure this policy setting, a default value of 9 is used. A value of zero means that the operating system will not allow standard users to send commands to the TPM, which might cause an authorization failure.
|
||||
|
||||
|
@ -6,8 +6,9 @@ ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
author: brianlic-msft
|
||||
ms.date: 07/27/2017
|
||||
author: andreabichsel
|
||||
ms.author: v-anbic
|
||||
ms.date: 09/11/2018
|
||||
---
|
||||
|
||||
# Trusted Platform Module
|
||||
@ -26,9 +27,6 @@ Trusted Platform Module (TPM) technology is designed to provide hardware-based,
|
||||
| [TPM fundamentals](tpm-fundamentals.md) | Provides background about how a TPM can work with cryptographic keys. Also describes technologies that work with the TPM, such as TPM-based virtual smart cards. |
|
||||
| [TPM Group Policy settings](trusted-platform-module-services-group-policy-settings.md) | Describes TPM services that can be controlled centrally by using Group Policy settings. |
|
||||
| [Back up the TPM recovery information to AD DS](backup-tpm-recovery-information-to-ad-ds.md) | For Windows 10, version 1511 and Windows 10, version 1507 only, describes how to back up a computer’s TPM information to Active Directory Domain Services. |
|
||||
| [Manage TPM commands](manage-tpm-commands.md) | Describes methods by which a local or domain administrator can block or allow specific TPM commands. |
|
||||
| [Manage TPM lockout](manage-tpm-lockout.md) | Describes how TPM lockout works (to help prevent tampering or malicious attacks), and outlines ways to work with TPM lockout settings. |
|
||||
| [Change the TPM owner password](change-the-tpm-owner-password.md) | In most cases, applies to Windows 10, version 1511 and Windows 10, version 1507 only. Tells how to change the TPM owner password. |
|
||||
| [View status, clear, or troubleshoot the TPM](initialize-and-configure-ownership-of-the-tpm.md) | Describes actions you can take through the TPM snap-in, TPM.msc: view TPM status, troubleshoot TPM initialization, and clear keys from the TPM. Also, for TPM 1.2 and Windows 10, version 1507 or 1511, describes how to turn the TPM on or off. |
|
||||
| [Troubleshoot the TPM](initialize-and-configure-ownership-of-the-tpm.md) | Describes actions you can take through the TPM snap-in, TPM.msc: view TPM status, troubleshoot TPM initialization, and clear keys from the TPM. Also, for TPM 1.2 and Windows 10, version 1507 or 1511, describes how to turn the TPM on or off. |
|
||||
| [Understanding PCR banks on TPM 2.0 devices](switch-pcr-banks-on-tpm-2-0-devices.md) | Provides background about what happens when you switch PCR banks on TPM 2.0 devices. |
|
||||
| [TPM recommendations](tpm-recommendations.md) | Discusses aspects of TPMs such as the difference between TPM 1.2 and 2.0, and the Windows 10 features for which a TPM is required or recommended. |
|
||||
|
@ -8,7 +8,7 @@ ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
author: brianlic-msft
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 08/27/2018
|
||||
---
|
||||
|
||||
# Interactive logon: Number of previous logons to cache (in case domain controller is not available)
|
||||
@ -42,7 +42,7 @@ encrypting the information and keeping the cached credentials in the system's re
|
||||
|
||||
### Best practices
|
||||
|
||||
It is advisable to set **Interactive logon: Number of previous logons to cache (in case domain controller is not available)** to 0. Setting this value to 0 disables the local caching of logon information. Additional countermeasures include enforcing strong password policies and physically securing the computers. If the value is set to 0, users will be unable to log on to any computers if there is no domain controller available to authenticate them. Organizations might want to set **Interactive logon: Number of previous logons to cache (in case domain controller is not available)** to 2 for end-user systems, especially for mobile users. Setting this value to 2 means that the user's logon information will still be in the cache even if a member of the IT department has recently logged on to their device to perform system maintenance. This way, those users will be able to log on to their devices when they are not connected to the corporate network.
|
||||
The [Windows security baselines](https://docs.microsoft.com/windows/security/threat-protection/windows-security-baselines) do not recommend configuring this setting.
|
||||
|
||||
### Location
|
||||
|
||||
@ -57,7 +57,7 @@ The following table lists the actual and effective default values for this polic
|
||||
| Default Domain Policy| Not defined|
|
||||
| Default Domain Controller Policy | Not defined|
|
||||
| Stand-Alone Server Default Settings | 10 logons|
|
||||
| DC Effective Default Settings | 10 logons|
|
||||
| DC Effective Default Settings | No effect|
|
||||
| Member Server Effective Default Settings | 10 logons|
|
||||
| Client Computer Effective Default Settings| 10 logons|
|
||||
|
||||
|
@ -11,7 +11,7 @@ ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
author: andreabichsel
|
||||
ms.author: v-anbic
|
||||
ms.date: 09/03/2018
|
||||
ms.date: 09/11/2018
|
||||
---
|
||||
|
||||
# Review event logs and error codes to troubleshoot issues with Windows Defender Antivirus
|
||||
@ -1417,10 +1417,10 @@ Antivirus client health report.
|
||||
<dt>Antispyware signature creation time: ?<Antispyware signature creation time></dt>
|
||||
<dt>Last quick scan start time: ?<Last quick scan start time></dt>
|
||||
<dt>Last quick scan end time: ?<Last quick scan end time></dt>
|
||||
<dt>Last quick scan source: <Last quick scan source> (1 = scheduled, 2 = on demand)</dt>
|
||||
<dt>Last quick scan source: <Last quick scan source> (0 = scan didn't run, 1 = user initiated, 2 = system initiated)</dt>
|
||||
<dt>Last full scan start time: ?<Last full scan start time></dt>
|
||||
<dt>Last full scan end time: ?<Last full scan end time></dt>
|
||||
<dt>Last full scan source: <Last full scan source> (1 = scheduled, 2 = on demand)</dt>
|
||||
<dt>Last full scan source: <Last full scan source> (0 = scan didn't run, 1 = user initiated, 2 = system initiated)</dt>
|
||||
<dt>Product status: For internal troubleshooting
|
||||
</dl>
|
||||
</td>
|
||||
|
@ -58,8 +58,8 @@ Use advanced protection against ransomware | c1db55ab-c21a-4637-bb3f-a12568109d3
|
||||
Block credential stealing from the Windows local security authority subsystem (lsass.exe) | 9e6c4e1f-7d60-472f-ba1a-a39ef669e4b2
|
||||
Block process creations originating from PSExec and WMI commands | d1e49aac-8f56-4280-b9ba-993a6d77406c
|
||||
Block untrusted and unsigned processes that run from USB | b2b3f03d-6a65-4f7b-a9c7-1c7ef74a9ba4
|
||||
Block only Office communication applications from creating child processes (available for beta testing) | 26190899-1602-49e8-8b27-eb1d0a1ce869
|
||||
Block Adobe Reader from creating child processes (available for beta testing) | 7674ba52-37eb-4a4f-a9a1-f0f9a1619a2c
|
||||
Block only Office communication applications from creating child processes | 26190899-1602-49e8-8b27-eb1d0a1ce869
|
||||
Block Adobe Reader from creating child processes | 7674ba52-37eb-4a4f-a9a1-f0f9a1619a2c
|
||||
|
||||
The rules apply to the following Office apps:
|
||||
|
||||
|
@ -62,8 +62,8 @@ Use advanced protection against ransomware | [!include[Check mark yes](images/sv
|
||||
Block credential stealing from the Windows local security authority subsystem (lsass.exe) | [!include[Check mark no](images/svg/check-no.svg)] | 9e6c4e1f-7d60-472f-ba1a-a39ef669e4b2
|
||||
Block process creations originating from PSExec and WMI commands | [!include[Check mark yes](images/svg/check-yes.svg)] | d1e49aac-8f56-4280-b9ba-993a6d77406c
|
||||
Block untrusted and unsigned processes that run from USB | [!include[Check mark yes](images/svg/check-yes.svg)] | b2b3f03d-6a65-4f7b-a9c7-1c7ef74a9ba4
|
||||
Block only Office communication applications from creating child processes (available for beta testing) | [!include[Check mark yes](images/svg/check-yes.svg)] | 26190899-1602-49e8-8b27-eb1d0a1ce869
|
||||
Block Adobe Reader from creating child processes (available for beta testing) | [!include[Check mark yes](images/svg/check-yes.svg)] | 7674ba52-37eb-4a4f-a9a1-f0f9a1619a2c
|
||||
Block only Office communication applications from creating child processes | [!include[Check mark yes](images/svg/check-yes.svg)] | 26190899-1602-49e8-8b27-eb1d0a1ce869
|
||||
Block Adobe Reader from creating child processes | [!include[Check mark yes](images/svg/check-yes.svg)] | 7674ba52-37eb-4a4f-a9a1-f0f9a1619a2c
|
||||
|
||||
|
||||
See the [Attack surface reduction](attack-surface-reduction-exploit-guard.md) topic for details on each rule.
|
||||
|
@ -63,8 +63,8 @@ Use advanced protection against ransomware | c1db55ab-c21a-4637-bb3f-a12568109d3
|
||||
Block credential stealing from the Windows local security authority subsystem (lsass.exe) | 9e6c4e1f-7d60-472f-ba1a-a39ef669e4b2
|
||||
Block process creations originating from PSExec and WMI commands | d1e49aac-8f56-4280-b9ba-993a6d77406c
|
||||
Block untrusted and unsigned processes that run from USB | b2b3f03d-6a65-4f7b-a9c7-1c7ef74a9ba4
|
||||
Block only Office communication applications from creating child processes (available for beta testing) | 26190899-1602-49e8-8b27-eb1d0a1ce869
|
||||
Block Adobe Reader from creating child processes (available for beta testing) | 7674ba52-37eb-4a4f-a9a1-f0f9a1619a2c
|
||||
Block only Office communication applications from creating child processes | 26190899-1602-49e8-8b27-eb1d0a1ce869
|
||||
Block Adobe Reader from creating child processes | 7674ba52-37eb-4a4f-a9a1-f0f9a1619a2c
|
||||
|
||||
See the [Attack surface reduction](attack-surface-reduction-exploit-guard.md) topic for details on each rule.
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user