mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-20 04:43:37 +00:00
Merge branch 'master' into device-control-intune
This commit is contained in:
@ -32,7 +32,7 @@ This topic contains the following information about how to secure Microsoft BitL
|
|||||||
|
|
||||||
## <a href="" id="bkmk-tpm"></a>Configure MBAM to escrow the TPM and store OwnerAuth passwords
|
## <a href="" id="bkmk-tpm"></a>Configure MBAM to escrow the TPM and store OwnerAuth passwords
|
||||||
|
|
||||||
**Note** For Windows 10, version 1607 or later, only Windows can take ownership of the TPM. In addition, Windows will not retain the TPM owner password when provisioning the TPM. See [TPM owner password](https://technet.microsoft.com/itpro/windows/keep-secure/change-the-tpm-owner-password) for further details.
|
**Note** For Windows 10, version 1607 or later, only Windows can take ownership of the TPM. In addition, Windows will not retain the TPM owner password when provisioning the TPM. See [TPM owner password](https://docs.microsoft.com/windows/security/information-protection/tpm/change-the-tpm-owner-password) for further details.
|
||||||
|
|
||||||
Depending on its configuration, the Trusted Platform Module (TPM) will lock itself in certain situations ─ such as when too many incorrect passwords are entered ─ and can remain locked for a period of time. During TPM lockout, BitLocker cannot access the encryption keys to perform unlock or decryption operations, requiring the user to enter their BitLocker recovery key to access the operating system drive. To reset TPM lockout, you must provide the TPM OwnerAuth password.
|
Depending on its configuration, the Trusted Platform Module (TPM) will lock itself in certain situations ─ such as when too many incorrect passwords are entered ─ and can remain locked for a period of time. During TPM lockout, BitLocker cannot access the encryption keys to perform unlock or decryption operations, requiring the user to enter their BitLocker recovery key to access the operating system drive. To reset TPM lockout, you must provide the TPM OwnerAuth password.
|
||||||
|
|
||||||
@ -40,7 +40,7 @@ MBAM can store the TPM OwnerAuth password in the MBAM database if it owns the TP
|
|||||||
|
|
||||||
### Escrowing TPM OwnerAuth in Windows 8 and higher
|
### Escrowing TPM OwnerAuth in Windows 8 and higher
|
||||||
|
|
||||||
**Note** For Windows 10, version 1607 or later, only Windows can take ownership of the TPM. In addiiton, Windows will not retain the TPM owner password when provisioning the TPM. See [TPM owner password](https://technet.microsoft.com/itpro/windows/keep-secure/change-the-tpm-owner-password) for further details.
|
**Note** For Windows 10, version 1607 or later, only Windows can take ownership of the TPM. In addiiton, Windows will not retain the TPM owner password when provisioning the TPM. See [TPM owner password](https://docs.microsoft.com/windows/security/information-protection/tpm/change-the-tpm-owner-password) for further details.
|
||||||
|
|
||||||
In Windows 8 or higher, MBAM no longer must own the TPM to store the OwnerAuth password, as long as the OwnerAuth is available on the local machine.
|
In Windows 8 or higher, MBAM no longer must own the TPM to store the OwnerAuth password, as long as the OwnerAuth is available on the local machine.
|
||||||
|
|
||||||
|
@ -8,7 +8,7 @@ ms.topic: troubleshooting
|
|||||||
author: kaushika-msft
|
author: kaushika-msft
|
||||||
ms.localizationpriority: medium
|
ms.localizationpriority: medium
|
||||||
ms.author: kaushika
|
ms.author: kaushika
|
||||||
ms.date: 11/30/2018
|
ms.date: 12/19/2018
|
||||||
---
|
---
|
||||||
|
|
||||||
# Advanced troubleshooting for Stop error or blue screen error issue
|
# Advanced troubleshooting for Stop error or blue screen error issue
|
||||||
@ -101,8 +101,7 @@ The memory dump file is saved at the following locations.
|
|||||||
|
|
||||||
You can use the Microsoft DumpChk (Crash Dump File Checker) tool to verify that the memory dump files are not corrupted or invalid. For more information, see the following video:
|
You can use the Microsoft DumpChk (Crash Dump File Checker) tool to verify that the memory dump files are not corrupted or invalid. For more information, see the following video:
|
||||||
|
|
||||||
>[!video https://www.youtube.com/watch?v=xN7tOfgNKag&feature=youtu.be]
|
>[!video https://www.youtube.com/embed/xN7tOfgNKag]
|
||||||
|
|
||||||
|
|
||||||
More information on how to use Dumpchk.exe to check your dump files:
|
More information on how to use Dumpchk.exe to check your dump files:
|
||||||
|
|
||||||
|
@ -6,7 +6,7 @@ ms.topic: landing-page
|
|||||||
ms.manager: elizapo
|
ms.manager: elizapo
|
||||||
author: lizap
|
author: lizap
|
||||||
ms.author: elizapo
|
ms.author: elizapo
|
||||||
ms.date: 12/12/2018
|
ms.date: 12/19/2018
|
||||||
ms.localizationpriority: high
|
ms.localizationpriority: high
|
||||||
---
|
---
|
||||||
# Windows as a service
|
# Windows as a service
|
||||||
@ -25,6 +25,8 @@ Windows 10 is the most secure version of Windows yet. Learn what updates we rele
|
|||||||
The latest news:
|
The latest news:
|
||||||
<ul compact style="list-style: none">
|
<ul compact style="list-style: none">
|
||||||
|
|
||||||
|
<li><a href="https://blogs.windows.com/windowsexperience/2018/12/19/driver-quality-in-the-windows-ecosystem/#ktuodfovWAMAkssM.97">Driver quality in the Windows ecosystem</a> - December 19, 2018</li>
|
||||||
|
<li><a href="http://m365mdp.mpsn.libsynpro.com/001-windows-10-monthly-quality-updates">Modern Desktop Podcast - Episode 001 – Windows 10 Monthly Quality Updates</a> - December 18, 2018</li>
|
||||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Measuring-Delivery-Optimization-and-its-impact-to-your-network/ba-p/301809#M409">Measuring Delivery Optimization and its impact to your network</a> - December 13, 2018</li>
|
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Measuring-Delivery-Optimization-and-its-impact-to-your-network/ba-p/301809#M409">Measuring Delivery Optimization and its impact to your network</a> - December 13, 2018</li>
|
||||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/LTSC-What-is-it-and-when-should-it-be-used/ba-p/293181">LTSC: What is it, and when should it be used?</a> - November 29, 2018</li>
|
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/LTSC-What-is-it-and-when-should-it-be-used/ba-p/293181">LTSC: What is it, and when should it be used?</a> - November 29, 2018</li>
|
||||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Local-Experience-Packs-What-are-they-and-when-should-you-use/ba-p/286841">Local Experience Packs: What are they and when should you use them?</a> - November 14, 2018</li>
|
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Local-Experience-Packs-What-are-they-and-when-should-you-use/ba-p/286841">Local Experience Packs: What are they and when should you use them?</a> - November 14, 2018</li>
|
||||||
|
@ -17,6 +17,7 @@ ms.date: 11/29/2018
|
|||||||
**Applies to**
|
**Applies to**
|
||||||
- Windows 10
|
- Windows 10
|
||||||
- Windows Server 2016
|
- Windows Server 2016
|
||||||
|
- Windows Server 2019
|
||||||
|
|
||||||
This topic for the IT professional describes the Trusted Platform Module (TPM) and how Windows uses it for access control and authentication.
|
This topic for the IT professional describes the Trusted Platform Module (TPM) and how Windows uses it for access control and authentication.
|
||||||
|
|
||||||
@ -38,7 +39,7 @@ Different versions of the TPM are defined in specifications by the Trusted Compu
|
|||||||
|
|
||||||
### Automatic initialization of the TPM with Windows 10
|
### Automatic initialization of the TPM with Windows 10
|
||||||
|
|
||||||
Starting with Windows 10, the operating system automatically initializes and takes ownership of the TPM. This means that in most cases, we recommend that you avoid configuring the TPM through the TPM management console, **TPM.msc**. There are a few exceptions, mostly related to resetting or performing a clean installation on a PC. For more information, see [Clear all the keys from the TPM](initialize-and-configure-ownership-of-the-tpm.md#clear-all-the-keys-from-the-tpm).
|
Starting with Windows 10, the operating system automatically initializes and takes ownership of the TPM. This means that in most cases, we recommend that you avoid configuring the TPM through the TPM management console, **TPM.msc**. There are a few exceptions, mostly related to resetting or performing a clean installation on a PC. For more information, see [Clear all the keys from the TPM](initialize-and-configure-ownership-of-the-tpm.md#clear-all-the-keys-from-the-tpm). We're [no longer actively developing the TPM management console](https://docs.microsoft.com/windows-server/get-started-19/removed-features-19#features-were-no-longer-developing) beginning with Windows Server 2019 and Windows 10, version 1809.
|
||||||
|
|
||||||
In certain specific enterprise scenarios limited to Windows 10, versions 1507 and 1511, Group Policy might be used to back up the TPM owner authorization value in Active Directory. Because the TPM state persists across operating system installations, this TPM information is stored in a location in Active Directory that is separate from computer objects.
|
In certain specific enterprise scenarios limited to Windows 10, versions 1507 and 1511, Group Policy might be used to back up the TPM owner authorization value in Active Directory. Because the TPM state persists across operating system installations, this TPM information is stored in a location in Active Directory that is separate from computer objects.
|
||||||
|
|
||||||
@ -69,14 +70,14 @@ Some things that you can check on the device are:
|
|||||||
- Is SecureBoot supported and enabled?
|
- Is SecureBoot supported and enabled?
|
||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> Windows 10 and Windows Server 2016 support Device Health Attestation with TPM 2.0. Support for TPM 1.2 was added beginning with Windows version 1607 (RS1). TPM 2.0 requires UEFI firmware. A computer with legacy BIOS and TPM 2.0 won't work as expected.
|
> Windows 10, Windows Server 2016 and Windows server 2019 support Device Health Attestation with TPM 2.0. Support for TPM 1.2 was added beginning with Windows version 1607 (RS1). TPM 2.0 requires UEFI firmware. A computer with legacy BIOS and TPM 2.0 won't work as expected.
|
||||||
|
|
||||||
## Supported versions for device health attestation
|
## Supported versions for device health attestation
|
||||||
|
|
||||||
| TPM version | Windows 10 | Windows Server 2016 |
|
| TPM version | Windows 10 | Windows Server 2016 | Windows Server 2019 |
|
||||||
|-------------|-------------|---------------------|
|
|-------------|-------------|---------------------|---------------------|
|
||||||
| TPM 1.2 | >= ver 1607 | >= ver 1607 |
|
| TPM 1.2 | >= ver 1607 | >= ver 1607 | Yes |
|
||||||
| TPM 2.0 | X | X |
|
| TPM 2.0 | Yes | Yes | Yes |
|
||||||
|
|
||||||
|
|
||||||
## Related topics
|
## Related topics
|
||||||
|
Reference in New Issue
Block a user