This commit is contained in:
Paolo Matarazzo
2023-03-31 08:13:55 -04:00
parent 7070f82348
commit dd438c8611
6 changed files with 5 additions and 9 deletions

View File

@ -110,7 +110,6 @@
"✅ <a href=\"https://learn.microsoft.com/windows/release-health/windows-server-release-info\" target=\"_blank\">Windows Server 2016</a>"
]
},
},
"ms.reviewer":{
"identity-protection/hello-for-business/*.md": "erikdau",
"identity-protection/credential-guard/*.md": "zwhittington",

View File

@ -62,7 +62,7 @@ Group Policy can be used to control the use of the local Administrators group au
> [!IMPORTANT]
>
> - Blank passwords are not allowed in the versions designated in the **Applies To** list at the beginning of this topic.
> - Blank passwords are not allowed.
>
> - Even when the Administrator account has been disabled, it can still be used to gain access to a computer by using safe mode. In the Recovery Console or in safe mode, the Administrator account is automatically enabled. When normal operations are resumed, it is disabled.

View File

@ -9,7 +9,7 @@ ms.reviewer: ardenw
This topic for the IT professional describes the behavior of Remote Desktop Services when you implement smart card sign-in.
The content in this topic applies to the versions of Windows that are designated in the **Applies To** list at the beginning of this topic. In these versions, smart card redirection logic and **WinSCard** API are combined to support multiple redirected sessions into a single process.
Smart card redirection logic and **WinSCard** API are combined to support multiple redirected sessions into a single process.
Smart card support is required to enable many Remote Desktop Services scenarios. These include:
@ -83,7 +83,8 @@ Where &lt;*CertFile*&gt; is the root certificate of the KDC certificate issuer.
For information about this option for the command-line tool, see [-addstore](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/cc732443(v=ws.11)#BKMK_addstore).
> **Note**&nbsp;&nbsp;If you use the credential SSP on computers running the supported versions of the operating system that are designated in the **Applies To** list at the beginning of this topic: To sign in with a smart card from a computer that is not joined to a domain, the smart card must contain the root certification of the domain controller. A public key infrastructure (PKI) secure channel cannot be established without the root certification of the domain controller.
> [!NOTE]
> To sign in with a smart card from a computer that is not joined to a domain, the smart card must contain the root certification of the domain controller. A public key infrastructure (PKI) secure channel cannot be established without the root certification of the domain controller.
Sign-in to Remote Desktop Services across a domain works only if the UPN in the certificate uses the following form: <*ClientName*>@<*DomainDNSName*>

View File

@ -308,8 +308,6 @@ Figure 4 shows the Cryptography architecture that is used by the Windows operat
### Base CSP and smart card KSP properties in Windows
The following properties are supported in versions of Windows designated in the **Applies To** list at the beginning of this topic.
> **Note**&nbsp;&nbsp;The API definitions are located in WinCrypt.h and WinSCard.h.
| **Property** | **Description** |

View File

@ -69,7 +69,7 @@ The following table lists the certificate support in older Windows operating sys
Most issues during authentication occur because of session behavior changes. When changes occur, the Local Security Authority (LSA) does not reacquire the session context; it relies instead on the Cryptographic Service Provider to handle the session change.
In the supported versions of Windows designated in the **Applies To** list at the beginning of this topic, client certificates that do not contain a UPN in the **subjectAltName** (SAN) field of the certificate can be enabled for sign-in, which supports a wider variety of certificates and supports multiple sign-in certificates on the same card.
Client certificates that do not contain a UPN in the **subjectAltName** (SAN) field of the certificate can be enabled for sign-in, which supports a wider variety of certificates and supports multiple sign-in certificates on the same card.
Support for multiple certificates on the same card is enabled by default. New certificate types must be enabled through Group Policy.

View File

@ -7,8 +7,6 @@ ms.topic: how-to
# How to configure Diffie Hellman protocol over IKEv2 VPN connections
>Applies To: Windows Server (General Availability Channel), Windows Server 2016, Windows 10, Windows 11
In IKEv2 VPN connections, the default configuration for Diffie Hellman group is Group 2, which is not secure for IKE exchanges.
To secure the connections, update the configuration of VPN servers and clients by running VPN cmdlets.