mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-07 10:07:21 +00:00
Merge branch 'master' of https://github.com/MicrosoftDocs/windows-docs-pr into whfb-cloudtrust
This commit is contained in:
commit
eb57013f4c
@ -55,15 +55,17 @@ Windows Hello for Business must have a public key infrastructure regardless of t
|
||||
|
||||
This guide assumes most enterprises have an existing public key infrastructure. Windows Hello for Business depends on a Windows enterprise public key infrastructure running the Active Directory Certificate Services role from Windows Server 2012 or later.
|
||||
|
||||
For more details about configuring a Windows enterprise public key infrastructure and installing Active Directory Certificate Services, see [Follow the Windows Hello for Business hybrid key trust deployment guide](/windows/security/identity-protection/hello-for-business/hello-hybrid-key-whfb-settings-pki#follow-the-windows-hello-for-business-hybrid-key-trust-deployment-guide) and [Install the Certification Authority](/windows-server/networking/core-network-guide/cncg/server-certs/install-the-certification-authority).
|
||||
|
||||
> [!NOTE]
|
||||
> Never install a certificate authority on a domain controller in a production environment.
|
||||
|
||||
### Lab-based public key infrastructure
|
||||
|
||||
The following instructions may be used to deploy simple public key infrastructure that is suitable for a lab environment.
|
||||
|
||||
Sign-in using _Enterprise Admin_ equivalent credentials on Windows Server 2012 or later server where you want the certificate authority installed.
|
||||
|
||||
>[!NOTE]
|
||||
>Never install a certificate authority on a domain controller in a production environment.
|
||||
|
||||
1. Open an elevated Windows PowerShell prompt.
|
||||
2. Use the following command to install the Active Directory Certificate Services role.
|
||||
```PowerShell
|
||||
|
@ -26,6 +26,9 @@ ms.technology: windows-sec
|
||||
- Windows 11
|
||||
- Windows Server 2016 and above
|
||||
|
||||
> [!IMPORTANT]
|
||||
> The existing web-based mechanism for the Device Guard Signing Service v1 will be retired on June 9, 2021. Please transition to the PowerShell based version of the service [(DGSS v2)](/microsoft-store/device-guard-signing-portal). For more details, see [Sign an MSIX package with Device Guard signing](/windows/msix/package/signing-package-device-guard-signing) and [Device Guard signing](/microsoft-store/device-guard-signing-portal).
|
||||
|
||||
> [!NOTE]
|
||||
> Some capabilities of Windows Defender Application Control are only available on specific Windows versions. Learn more about the [Windows Defender Application Control feature availability](feature-availability.md).
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user