mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-18 16:27:22 +00:00
Merged PR 13595: 1/07 AM Publish
This commit is contained in:
Huaping Yu (Beyondsoft Consulting Inc)
commit
0d706992fd
@ -70,7 +70,7 @@ Some things that you can check on the device are:
|
||||
- Is SecureBoot supported and enabled?
|
||||
|
||||
> [!NOTE]
|
||||
> 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.
|
||||
> 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
|
||||
|
||||
@ -83,5 +83,5 @@ Some things that you can check on the device are:
|
||||
## Related topics
|
||||
|
||||
- [Trusted Platform Module](trusted-platform-module-top-node.md) (list of topics)
|
||||
- [TPM Cmdlets in Windows PowerShell](https://technet.microsoft.com/library/jj603116.aspx)
|
||||
- [Prepare your organization for BitLocker: Planning and Policies - TPM configurations](https://technet.microsoft.com/itpro/windows/keep-secure/prepare-your-organization-for-bitlocker-planning-and-policies#bkmk-tpmconfigurations)
|
||||
- [TPM Cmdlets in Windows PowerShell](https://docs.microsoft.com/powershell/module/trustedplatformmodule)
|
||||
- [Prepare your organization for BitLocker: Planning and Policies - TPM configurations](https://docs.microsoft.com/windows/security/information-protection/bitlocker/prepare-your-organization-for-bitlocker-planning-and-policies#bkmk-tpmconfigurations)
|
||||
|
||||
@ -0,0 +1,8 @@
|
||||
---
|
||||
author: jasongerend
|
||||
ms.author: jgerend
|
||||
ms.date: 1/4/2019
|
||||
ms.topic: include
|
||||
ms.prod: w10
|
||||
---
|
||||
Using SMB packet signing can degrade performance on file service transactions, depending on the version of SMB and available CPU cycles.
|
||||
@ -8,7 +8,7 @@ ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
author: brianlic-msft
|
||||
ms.date: 06/19/2018
|
||||
ms.date: 01/04/2019
|
||||
---
|
||||
|
||||
# SMBv1 Microsoft network client: Digitally sign communications (always)
|
||||
@ -31,7 +31,7 @@ If server-side SMB signing is required, a client device will not be able to esta
|
||||
|
||||
If server-side SMB signing is enabled, SMB packet signing will be negotiated with client computers that have SMB signing enabled.
|
||||
|
||||
Using SMB packet signing can impose up to a 15 percent performance degradation on file service transactions.
|
||||
[!INCLUDE [smb1-perf-note](includes/smb1-perf-note.md)]
|
||||
|
||||
There are three other policy settings that relate to packet-signing requirements for Server Message Block (SMB) communications:
|
||||
- [Microsoft network server: Digitally sign communications (always)](smbv1-microsoft-network-server-digitally-sign-communications-always.md)
|
||||
|
||||
@ -8,7 +8,7 @@ ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
author: brianlic-msft
|
||||
ms.date: 06/19/2018
|
||||
ms.date: 01/04/2019
|
||||
---
|
||||
# SMBv1 Microsoft network client: Digitally sign communications (if server agrees)
|
||||
|
||||
@ -29,7 +29,7 @@ If server-side SMB signing is required, a client computer will not be able to es
|
||||
|
||||
If server-side SMB signing is enabled, SMB packet signing will be negotiated with client computers that have SMB signing enabled.
|
||||
|
||||
Using SMB packet signing can impose up to a 15 percent performance degradation on file service transactions.
|
||||
[!INCLUDE [smb1-perf-note](includes/smb1-perf-note.md)]
|
||||
|
||||
There are three other policy settings that relate to packet-signing requirements for Server Message Block (SMB) communications:
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
author: brianlic-msft
|
||||
ms.date: 06/19/201
|
||||
ms.date: 01/04/2019
|
||||
---
|
||||
|
||||
# SMB v1 Microsoft network server: Digitally sign communications (always)
|
||||
@ -33,7 +33,7 @@ If server-side SMB signing is required, a client device will not be able to esta
|
||||
|
||||
If server-side SMB signing is enabled, SMB packet signing will be negotiated with client devices that have SMB signing enabled.
|
||||
|
||||
Using SMB packet signing can impose up to a 15 percent performance degradation on file service transactions.
|
||||
[!INCLUDE [smb1-perf-note](includes/smb1-perf-note.md)]
|
||||
|
||||
There are three other policy settings that relate to packet-signing requirements for Server Message Block (SMB) communications:
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
author: brianlic-msft
|
||||
ms.date: 06/19/2018
|
||||
ms.date: 01/04/2019
|
||||
---
|
||||
|
||||
# SMBv1 Microsoft network server: Digitally sign communications (if client agrees)
|
||||
@ -31,7 +31,7 @@ If server-side SMB signing is required, a client device will not be able to esta
|
||||
|
||||
If server-side SMB signing is enabled, SMB packet signing will be negotiated with client computers that have SMB signing enabled.
|
||||
|
||||
Using SMB packet signing can impose up to a 15 percent performance degradation on file service transactions.
|
||||
[!INCLUDE [smb1-perf-note](includes/smb1-perf-note.md)]
|
||||
|
||||
There are three other policy settings that relate to packet-signing requirements for Server Message Block (SMB) communications:
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user