mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 21:37:22 +00:00
Merge branch 'master' into nimishasatapathy-5556913-terminalserver
This commit is contained in:
commit
7f2e5477c5
@ -265,7 +265,7 @@ This policy setting determines which Windows Notification Service endpoint will
|
|||||||
|
|
||||||
If you disable or do not configure this setting, the push notifications will connect to the default endpoint of client.wns.windows.com.
|
If you disable or do not configure this setting, the push notifications will connect to the default endpoint of client.wns.windows.com.
|
||||||
|
|
||||||
Note: Ensure the proper WNS FQDNs, VIPs, IPs and Ports are also whitelisted from your firewall settings.
|
Note: Ensure the proper WNS FQDNs, VIPs, IPs and Ports are also allowlisted from your firewall settings.
|
||||||
|
|
||||||
<!--/Description-->
|
<!--/Description-->
|
||||||
<!--ADMXMapped-->
|
<!--ADMXMapped-->
|
||||||
|
@ -19,6 +19,9 @@ Quick Assist is a Windows application that enables a person to share their devic
|
|||||||
|
|
||||||
All that's required to use Quick Assist is suitable network and internet connectivity. No particular roles, permissions, or policies are involved. Neither party needs to be in a domain. The helper must have a Microsoft account. The sharer doesn’t have to authenticate.
|
All that's required to use Quick Assist is suitable network and internet connectivity. No particular roles, permissions, or policies are involved. Neither party needs to be in a domain. The helper must have a Microsoft account. The sharer doesn’t have to authenticate.
|
||||||
|
|
||||||
|
> [!NOTE]
|
||||||
|
> In case the helper and sharer use different keyboard layouts or mouse settings, the ones from the sharer are used during the session.
|
||||||
|
|
||||||
### Authentication
|
### Authentication
|
||||||
|
|
||||||
The helper can authenticate when they sign in by using a Microsoft Account (MSA) or Azure Active Directory. Local Active Directory authentication is not supported at this time.
|
The helper can authenticate when they sign in by using a Microsoft Account (MSA) or Azure Active Directory. Local Active Directory authentication is not supported at this time.
|
||||||
|
@ -69,7 +69,7 @@ Key trust deployments do not need client issued certificates for on-premises aut
|
|||||||
The minimum required Enterprise certificate authority that can be used with Windows Hello for Business is Windows Server 2012, but you can also use a third-party Enterprise certification authority. The requirements for the domain controller certificate are shown below. For more details, see [Requirements for domain controller certificates from a third-party CA](/troubleshoot/windows-server/windows-security/requirements-domain-controller).
|
The minimum required Enterprise certificate authority that can be used with Windows Hello for Business is Windows Server 2012, but you can also use a third-party Enterprise certification authority. The requirements for the domain controller certificate are shown below. For more details, see [Requirements for domain controller certificates from a third-party CA](/troubleshoot/windows-server/windows-security/requirements-domain-controller).
|
||||||
|
|
||||||
* The certificate must have a Certificate Revocation List (CRL) distribution point extension that points to a valid CRL, or an Authority Information Access (AIA) extension that points to an Online Certificate Status Protocol (OCSP) responder.
|
* The certificate must have a Certificate Revocation List (CRL) distribution point extension that points to a valid CRL, or an Authority Information Access (AIA) extension that points to an Online Certificate Status Protocol (OCSP) responder.
|
||||||
* The certificate Subject section should contain the directory path of the server object (the distinguished name).
|
* Optionally, the certificate Subject section could contain the directory path of the server object (the distinguished name).
|
||||||
* The certificate Key Usage section must contain Digital Signature and Key Encipherment.
|
* The certificate Key Usage section must contain Digital Signature and Key Encipherment.
|
||||||
* Optionally, the certificate Basic Constraints section should contain: [Subject Type=End Entity, Path Length Constraint=None].
|
* Optionally, the certificate Basic Constraints section should contain: [Subject Type=End Entity, Path Length Constraint=None].
|
||||||
* The certificate Enhanced Key Usage section must contain Client Authentication (1.3.6.1.5.5.7.3.2), Server Authentication (1.3.6.1.5.5.7.3.1), and KDC Authentication (1.3.6.1.5.2.3.5).
|
* The certificate Enhanced Key Usage section must contain Client Authentication (1.3.6.1.5.5.7.3.2), Server Authentication (1.3.6.1.5.5.7.3.1), and KDC Authentication (1.3.6.1.5.2.3.5).
|
||||||
|
@ -237,7 +237,7 @@ Microsoft Edge kiosk mode offers two lockdown experiences of the browser so orga
|
|||||||
|
|
||||||
## Windows Subsystem for Linux
|
## Windows Subsystem for Linux
|
||||||
|
|
||||||
Windows Subsystem for Linux (WSL) is be available in-box.
|
Windows Subsystem for Linux (WSL) is available in-box.
|
||||||
|
|
||||||
## Networking
|
## Networking
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user