mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-20 21:03:42 +00:00
Merge remote-tracking branch 'refs/remotes/origin/rs5' into jd5wcd
This commit is contained in:
Jeanie Decker
@ -7,7 +7,7 @@ author: jdeckerms
|
||||
ms.author: jdecker
|
||||
ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 07/27/2017
|
||||
ms.date: 08/02/2018
|
||||
---
|
||||
|
||||
# Set up HoloLens
|
||||
@ -30,7 +30,12 @@ The HoloLens setup process combines a quick tutorial on using HoloLens with the
|
||||
2. [Turn on HoloLens](https://support.microsoft.com/help/12642). You will be guided through a calibration procedure and how to perform [the gestures](https://support.microsoft.com/help/12644/hololens-use-gestures) that you will use to operate HoloLens.
|
||||
3. Next, you'll be guided through connecting to a Wi-Fi network.
|
||||
4. After HoloLens connects to the Wi-Fi network, you select between **My work or school owns it** and **I own it**.
|
||||
- When you choose **My work or school owns it**, you sign in with an Azure AD account. If your organization uses Azure AD Premium and has configured automatic MDM enrollment, HoloLens will be enrolled in MDM. If your organization does not use Azure AD Premium, automatic MDM enrollment isn't available, so you will need to [enroll HoloLens in device management manually](hololens-enroll-mdm.md#enroll-through-settings-app).
|
||||
- When you choose **My work or school owns it**, you sign in with an Azure AD account.
|
||||
|
||||
>[!NOTE]
|
||||
>[To share your HoloLens device with multiple Azure AD accounts](hololens-multiple-users.md), the HoloLens device must be running Windows 10, version 1803, and be [upgraded to Windows Holographic for Business](hololens-upgrade-enterprise.md).
|
||||
|
||||
If your organization uses Azure AD Premium and has configured automatic MDM enrollment, HoloLens will be enrolled in MDM. If your organization does not use Azure AD Premium, automatic MDM enrollment isn't available, so you will need to [enroll HoloLens in device management manually](hololens-enroll-mdm.md#enroll-through-settings-app).
|
||||
1. Enter your organizational account.
|
||||
2. Accept privacy statement.
|
||||
3. Sign in using your Azure AD credentials. This may redirect to your organization's sign-in page.
|
||||
|
||||
@ -9,7 +9,7 @@ ms.pagetype: devices
|
||||
author: jdeckerms
|
||||
ms.localizationpriority: medium
|
||||
ms.author: jdecker
|
||||
ms.date: 11/28/2017
|
||||
ms.date: 08/02/2018
|
||||
---
|
||||
|
||||
# Connect to remote Azure Active Directory-joined PC
|
||||
@ -45,6 +45,9 @@ From its release, Windows 10 has supported remote connections to PCs that are jo
|
||||
|
||||
4. Enter **Authenticated Users**, then click **Check Names**. If the **Name Not Found** window opens, click **Locations** and select this PC.
|
||||
|
||||
>[!TIP]
|
||||
>When you connect to the remote PC, enter your account name in this format: `AzureADName\YourAccountName`.
|
||||
|
||||
|
||||
## Supported configurations
|
||||
|
||||
|
||||
@ -10,13 +10,19 @@ ms.localizationpriority: medium
|
||||
author: jdeckerms
|
||||
ms.author: jdecker
|
||||
ms.topic: article
|
||||
ms.date: 07/30/2018
|
||||
ms.date: 08/03/2018
|
||||
---
|
||||
|
||||
# Change history for Configure Windows 10
|
||||
|
||||
This topic lists new and updated topics in the [Configure Windows 10](index.md) documentation for Windows 10 and Windows 10 Mobile.
|
||||
|
||||
## August 2018
|
||||
|
||||
New or changed topic | Description
|
||||
--- | ---
|
||||
[Guidelines for choosing an app for assigned access (kiosk mode)](guidelines-for-assigned-access-app.md) | Added instructions for specifying multiple URLs in configuration settings for Kiosk Browser.
|
||||
|
||||
## July 2018
|
||||
|
||||
New or changed topic | Description
|
||||
|
||||
@ -9,7 +9,7 @@ author: jdeckerms
|
||||
ms.localizationpriority: medium
|
||||
ms.author: jdecker
|
||||
ms.topic: article
|
||||
ms.date: 07/30/2018
|
||||
ms.date: 08/03/2018
|
||||
---
|
||||
|
||||
# Guidelines for choosing an app for assigned access (kiosk mode)
|
||||
@ -59,14 +59,25 @@ In Windows 10, version 1803, you can install the **Kiosk Browser** app from Micr
|
||||
|
||||
Kiosk Browser settings | Use this setting to
|
||||
--- | ---
|
||||
Blocked URL Exceptions | Specify URLs that people can navigate to, even though the URL is in your blocked URL list. You can use wildcards. Separate multiple URLs using ``.<br><br>For example, if you want people to be limited to `contoso.com` only, you would add `contoso.com` to blocked URL exception list and then block all other URLs.
|
||||
Blocked URLs | Specify URLs that people can't navigate to. You can use wildcards. Separate multiple URLs using ``.<br><br>If you want to limit people to a specific site, add `https://*` to the blocked URL list, and then specify the site to be allowed in the blocked URL exceptions list.
|
||||
Blocked URL Exceptions | Specify URLs that people can navigate to, even though the URL is in your blocked URL list. You can use wildcards. <br><br>For example, if you want people to be limited to `contoso.com` only, you would add `contoso.com` to blocked URL exception list and then block all other URLs.
|
||||
Blocked URLs | Specify URLs that people can't navigate to. You can use wildcards. <br><br>If you want to limit people to a specific site, add `https://*` to the blocked URL list, and then specify the site to be allowed in the blocked URL exceptions list.
|
||||
Default URL | Specify the URL that Kiosk Browser will open with. **Tip!** Make sure your blocked URLs don't include your default URL.
|
||||
Enable End Session Button | Show a button in Kiosk Browser that people can use to reset the browser. End Session will clear all browsing data and navigate back to the default URL.
|
||||
Enable Home Button | Show a Home button in Kiosk Browser. Home will return the browser to the default URL.
|
||||
Enable Navigation Buttons | Show forward and back buttons in Kiosk Browser.
|
||||
Restart on Idle Time | Specify when Kiosk Browser should restart in a fresh state after an amount of idle time since the last user interaction.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>To configure multiple URLs for **Blocked URL Exceptions** or **Blocked URLs** in Windows Configuration Designer:
|
||||
>
|
||||
> 1. Create the provisioning package. When ready to export, close the project in Windows Configuration Designer.
|
||||
>2. Open the customizations.xml file in the project folder (e.g C:\Users\name\Documents\Windows Imaging and Configuration Designer (WICD)\Project_18).
|
||||
>3. Insert the null character string in between each URL (e.g www.bing.comwww.contoso.com).
|
||||
>4. Save the XML file.
|
||||
>5. Open the project again in Windows Configuration Designer.
|
||||
>6. Export the package. Ensure you do not revisit the created policies under Kiosk Browser or else the null character will be removed.
|
||||
|
||||
|
||||
>[!TIP]
|
||||
>To enable the **End Session** button for Kiosk Browser in Intune, you must [create a custom OMA-URI policy](https://docs.microsoft.com/intune/custom-settings-windows-10) with the following information:
|
||||
>- OMA-URI: ./Vendor/MSFT/Policy/Config/KioskBrowser/EnableEndSessionButton
|
||||
|
||||
@ -8,7 +8,7 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
author: jdeckerms
|
||||
ms.localizationpriority: high
|
||||
ms.date: 07/30/2018
|
||||
ms.date: 08/03/2018
|
||||
---
|
||||
|
||||
# Set up digital signs on Windows 10
|
||||
@ -61,6 +61,10 @@ This procedure explains how to configure digital signage using Kiosk Browser on
|
||||
- In **BlockedUrl**, enter `*`.
|
||||
- In **DefaultUrl**, enter `https://www.contoso.com/menu`.
|
||||
- Set **EnableEndSessionButton**, **EnableHomeButton**, and **EnableNavigationButtons** to **No**.
|
||||
|
||||
>[!TIP]
|
||||
>For more information on kiosk browser settings, see [Guidelines for web browsers](guidelines-for-assigned-access-app.md#guidelines-for-web-browsers).
|
||||
|
||||
13. On the **File** menu, select **Save**, and select **OK** in the **Keep your info secure** dialog box.
|
||||
14. On the **Export** menu, select **Provisioning package**.
|
||||
15. Change the **Owner** to **IT Admin**, and select **Next**.
|
||||
|
||||
@ -8,7 +8,7 @@ author: jdeckerMS
|
||||
ms.localizationpriority: medium
|
||||
ms.author: jdecker
|
||||
ms.topic: article
|
||||
ms.date: 04/30/2018
|
||||
ms.date: 08/03/2018
|
||||
---
|
||||
|
||||
# Policies (Windows Configuration Designer reference)
|
||||
@ -290,13 +290,21 @@ These settings apply to the **Kiosk Browser** app available in Microsoft Store.
|
||||
|
||||
| Setting | Description | Desktop editions | Mobile editions | Surface Hub | HoloLens | IoT Core |
|
||||
| --- | --- | :---: | :---: | :---: | :---: | :---: |
|
||||
[BlockedUrlExceptions](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-kioskbrowser#kioskbrowser-blockedurlexceptions) | List of exceptions to the blocked website URLs (with wildcard support). Separate multiple URLs using ``. This is used to configure URLs kiosk browsers are allowed to navigate to, which are a subset of the blocked URLs. | X | | | | |
|
||||
[BlockedUrls](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-kioskbrowser#kioskbrowser-blockedurls) | List of blocked website URLs (with wildcard support). Separate multiple URLs using ``. This is used to configure blocked URLs kiosk browsers cannot navigate to. | X | | | | |
|
||||
[BlockedUrlExceptions](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-kioskbrowser#kioskbrowser-blockedurlexceptions) | List of exceptions to the blocked website URLs (with wildcard support). This is used to configure URLs kiosk browsers are allowed to navigate to, which are a subset of the blocked URLs. | X | | | | |
|
||||
[BlockedUrls](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-kioskbrowser#kioskbrowser-blockedurls) | List of blocked website URLs (with wildcard support). This is used to configure blocked URLs kiosk browsers cannot navigate to. | X | | | | |
|
||||
[DefaultURL](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-kioskbrowser#kioskbrowser-defaulturl) | Configures the default URL kiosk browsers to navigate on launch and restart. | X | | | | |
|
||||
[EnableHomeButton](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-kioskbrowser#kioskbrowser-enablehomebutton) | Enable/disable kiosk browser's home button. | X | | | | |
|
||||
[EnableNavigationButtons](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-kioskbrowser#kioskbrowser-enablenavigationbuttons) | Enable/disable kiosk browser's navigation buttons (forward/back). | X | | | | |
|
||||
[RestartOnIdleTime](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-kioskbrowser#kioskbrowser-restartonidletime) | Amount of time in minutes the session is idle until the kiosk browser restarts in a fresh state. The value is an int 1-1440 that specifies the amount of minutes the session is idle until the kiosk browser restarts in a fresh state. The default value is empty which means there is no idle timeout within the kiosk browser. | X | | | | |
|
||||
|
||||
To configure multiple URLs for **Blocked URL Exceptions** or **Blocked URLs** in Windows Configuration Designer:
|
||||
|
||||
1. Create the provisioning package. When ready to export, close the project in Windows Configuration Designer.
|
||||
2. Open the customizations.xml file in the project folder (e.g C:\Users\name\Documents\Windows Imaging and Configuration Designer (WICD)\Project_18).
|
||||
3. Insert the null character string in between each URL (e.g www.bing.comwww.contoso.com).
|
||||
4. Save the XML file.
|
||||
5. Open the project again in Windows Configuration Designer.
|
||||
6. Export the package. Ensure you do not revisit the created policies under Kiosk Browser or else the null character will be removed.
|
||||
|
||||
## Location
|
||||
|
||||
|
||||
@ -23,7 +23,7 @@ Hybrid environments are distributed systems that enable organizations to use on-
|
||||
|
||||
The distributed systems on which these technologies were built involved several pieces of on-premises and cloud infrastructure. High-level pieces of the infrastructure include:
|
||||
* [Directories](#directories)
|
||||
* [Public Key Infrastucture](#public-key-infastructure)
|
||||
* [Public Key Infrastructure](#public-key-infrastructure)
|
||||
* [Directory Synchronization](#directory-synchronization)
|
||||
* [Federation](#federation)
|
||||
* [MultiFactor Authetication](#multifactor-authentication)
|
||||
@ -32,7 +32,7 @@ The distributed systems on which these technologies were built involved several
|
||||
## Directories ##
|
||||
Hybrid Windows Hello for Business needs two directories: on-premises Active Directory and a cloud Azure Active Directory. The minimum required domain functional and forest functional levels for Windows Hello for Business deployment is Windows Server 2008 R2. The
|
||||
|
||||
A hybrid Windows Hello for Busines deployment needs an Azure Active Directory subscription. The hybrid key trust deployment, does not need a premium Azure Active Directory subscription.
|
||||
A hybrid Windows Hello for Business deployment needs an Azure Active Directory subscription. The hybrid key trust deployment, does not need a premium Azure Active Directory subscription.
|
||||
|
||||
You can deploy Windows Hello for Business in any environment with Windows Server 2008 R2 or later domain controllers. However, the key trust deployment needs an ***adequate*** number of Windows Server 2016 domain controllers at each site where users authenticate using Windows Hello for Business. Read the [Planning an adequate number of Windows Server 2016 Domain Controllers for Windows Hello for Business deployments](hello-adequate-domain-controllers.md) to learn more.
|
||||
|
||||
@ -52,13 +52,13 @@ Review these requirements and those from the Windows Hello for Business planning
|
||||
## Public Key Infrastructure ##
|
||||
The Windows Hello for Business deployment depends on an enterprise public key infrastructure as trust anchor for authentication. Domain controllers for hybrid deployments need a certificate in order for Windows 10 devices to trust the domain controller.
|
||||
|
||||
Key trust deployments do not need client issued certificates for on-premises authentication. Active Directory user accounts are automatically configured for public key mapping by Azure AD Connect synchronizing the public key of the registered Windows Hello for Business credential to an attribute on the user's Active Diretory object.
|
||||
Key trust deployments do not need client issued certificates for on-premises authentication. Active Directory user accounts are automatically configured for public key mapping by Azure AD Connect synchronizing the public key of the registered Windows Hello for Business credential to an attribute on the user's Active Directory object.
|
||||
|
||||
The minimum required enterprise certificate authority that can be used with Windows Hello for Business is Windows Server 2012.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> For Azure AD joined device to authenticate to and use on-premises resources, ensure you:
|
||||
> * Install the root certificate authority certificate for your organization in the user's trusted root certifcate store.
|
||||
> * Install the root certificate authority certificate for your organization in the user's trusted root certificate store.
|
||||
> * Publish your certificate revocation list to a location that is available to Azure AD joined devices, such as a web-based url.
|
||||
|
||||
### Section Review
|
||||
@ -99,12 +99,12 @@ Hybrid Windows Hello for Business deployments can use Azure’s Multifactor Auth
|
||||
> [!div class="checklist"]
|
||||
> * Azure MFA Service
|
||||
> * Windows Server 2016 AD FS and Azure (optional, if federated)
|
||||
> * Windows Server 2016 AD FS and third party MFA Adapter (optional, if federated)
|
||||
> * Windows Server 2016 AD FS and third-party MFA Adapter (optional, if federated)
|
||||
|
||||
<br>
|
||||
|
||||
## Device Registration ##
|
||||
Organizations wanting to deploy hybrid key trust need thier domain joined devices to register to Azure Active Directory. Just as a computer has an identity in Active Directory, that same computer has an identity in the cloud. This ensures that only approved computers are used with that Azure Active Directory. Each computer registers its identity in Azure Active Directory.
|
||||
Organizations wanting to deploy hybrid key trust need their domain joined devices to register to Azure Active Directory. Just as a computer has an identity in Active Directory, that same computer has an identity in the cloud. This ensures that only approved computers are used with that Azure Active Directory. Each computer registers its identity in Azure Active Directory.
|
||||
|
||||
|
||||
### Section Checklist ###
|
||||
@ -114,11 +114,11 @@ Organizations wanting to deploy hybrid key trust need thier domain joined device
|
||||
<br>
|
||||
|
||||
### Next Steps ###
|
||||
Follow the Windows Hello for Business hybrid key trust deployment guide. For proof-of-concepts, labs, and new installations, choose the **New Installation Basline**.
|
||||
Follow the Windows Hello for Business hybrid key trust deployment guide. For proof-of-concepts, labs, and new installations, choose the **New Installation Baseline**.
|
||||
|
||||
For environments transitioning from on-premises to hybrid, start with **Configure Azure Directory Syncrhonization**.
|
||||
For environments transitioning from on-premises to hybrid, start with **Configure Azure Directory Synchronization**.
|
||||
|
||||
For federerated and non-federated environments, start with **Configure Windows Hello for Business settings**.
|
||||
For federated and non-federated environments, start with **Configure Windows Hello for Business settings**.
|
||||
|
||||
> [!div class="op_single_selector"]
|
||||
> - [New Installation Baseline](hello-hybrid-key-new-install.md)
|
||||
@ -131,7 +131,7 @@ For federerated and non-federated environments, start with **Configure Windows H
|
||||
|
||||
## Follow the Windows Hello for Business hybrid key trust deployment guide
|
||||
1. [Overview](hello-hybrid-key-trust.md)
|
||||
2. Prerequistes (*You are here*)
|
||||
2. Prerequisites (*You are here*)
|
||||
3. [New Installation Baseline](hello-hybrid-key-new-install.md)
|
||||
4. [Configure Directory Synchronization](hello-hybrid-key-trust-dirsync.md)
|
||||
5. [Configure Azure Device Registration](hello-hybrid-key-trust-devreg.md)
|
||||
|
||||
@ -45,11 +45,11 @@ The provisioning flow has all the information it needs to complete the Windows H
|
||||
* A fresh, successful multi-factor authentication
|
||||
* A validated PIN that meets the PIN complexity requirements
|
||||
|
||||
The remainder of the provisioning includes Windows Hello for Business requesting an asymmetric key pair for the user, preferably from the TPM (or required if explicitly set through policy). Once the key pair is acquired, Windows communicates with Azure Active Directory to register the public key. When key registration completes, Windows Hello for Business provisioning informs the user they can use their PIN to sign-in. The user may close the provisiong application and see their desktop. While the user has completed provisioning, Azure AD Connect syncrhonizes the user's key to Active Directory.
|
||||
The remainder of the provisioning includes Windows Hello for Business requesting an asymmetric key pair for the user, preferably from the TPM (or required if explicitly set through policy). Once the key pair is acquired, Windows communicates with Azure Active Directory to register the public key. When key registration completes, Windows Hello for Business provisioning informs the user they can use their PIN to sign-in. The user may close the provisioning application and see their desktop. While the user has completed provisioning, Azure AD Connect synchronizes the user's key to Active Directory.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> The minimum time needed to syncrhonize the user's public key from Azure Active Directory to the on-premises Active Directory is 30 minutes. The Azure AD Connect scheduler controls the synchronization interval.
|
||||
> **This synchronization latency delays the user's ability to authenticate and use on-premises resouces until the user's public key has synchronized to Active Directory.** Once synchronized, the user can authenticate and use on-premises resources.
|
||||
> The minimum time needed to synchronize the user's public key from Azure Active Directory to the on-premises Active Directory is 30 minutes. The Azure AD Connect scheduler controls the synchronization interval.
|
||||
> **This synchronization latency delays the user's ability to authenticate and use on-premises resources until the user's public key has synchronized to Active Directory.** Once synchronized, the user can authenticate and use on-premises resources.
|
||||
> Read [Azure AD Connect sync: Scheduler](https://docs.microsoft.com/en-us/azure/active-directory/connect/active-directory-aadconnectsync-feature-scheduler) to view and adjust the **synchronization cycle** for your organization.
|
||||
|
||||
> [!NOTE]
|
||||
|
||||
@ -18,7 +18,7 @@ ms.date: 10/23/2017
|
||||
|
||||
>This guide only applies to Hybrid deployments for Windows 10, version 1703 or higher.
|
||||
|
||||
Configure the appropriate security groups to effeiciently deploy Windows Hello for Business to users.
|
||||
Configure the appropriate security groups to efficiently deploy Windows Hello for Business to users.
|
||||
|
||||
|
||||
### Creating Security Groups
|
||||
|
||||
@ -19,13 +19,13 @@ ms.date: 10/23/2017
|
||||
|
||||
>This guide only applies to Hybrid deployments for Windows 10, version 1703 or higher.
|
||||
|
||||
Windows Hello for Business deployments rely on certificates. Hybrid deployments uses publicly issued server authentication certifcates to validate the name of the server to which they are connecting and to encyrpt the data that flows them and the client computer.
|
||||
Windows Hello for Business deployments rely on certificates. Hybrid deployments uses publicly issued server authentication certificates to validate the name of the server to which they are connecting and to encrypt the data that flows them and the client computer.
|
||||
|
||||
All deployments use enterprise issued certificates for domain controllers as a root of trust.
|
||||
|
||||
## Certifcate Templates
|
||||
## Certificate Templates
|
||||
|
||||
This section has you configure certificate templates on your Windows Server 2012 or later issuing certificate authtority.
|
||||
This section has you configure certificate templates on your Windows Server 2012 or later issuing certificate authority.
|
||||
|
||||
### Domain Controller certificate template
|
||||
|
||||
@ -49,7 +49,7 @@ Sign-in a certificate authority or management workstations with _Domain Admin_ e
|
||||
7. On the **Cryptography** tab, select **Key Storage Provider** from the **Provider Category** list. Select **RSA** from the **Algorithm name** list. Type **2048** in the **Minimum key size** text box. Select **SHA256** from the **Request hash** list. Click **OK**.
|
||||
8. Close the console.
|
||||
|
||||
#### Configure Certificate Suspeding for the Domain Controller Authentication (Kerberos) Certificate Template
|
||||
#### Configure Certificate Superseding for the Domain Controller Authentication (Kerberos) Certificate Template
|
||||
|
||||
Many domain controllers may have an existing domain controller certificate. The Active Directory Certificate Services provides a default certificate template for domain controllers--the domain controller certificate template. Later releases provided a new certificate template--the domain controller authentication certificate template. These certificate templates were provided prior to update of the Kerberos specification that stated Key Distribution Centers (KDCs) performing certificate authentication needed to include the **KDC Authentication** extension.
|
||||
|
||||
@ -108,7 +108,7 @@ Sign-in to the certificate authority or management workstation with _Enterprise
|
||||
|
||||
## Follow the Windows Hello for Business hybrid key trust deployment guide
|
||||
1. [Overview](hello-hybrid-cert-trust.md)
|
||||
2. [Prerequistes](hello-hybrid-key-trust-prereqs.md)
|
||||
2. [Prerequisites](hello-hybrid-key-trust-prereqs.md)
|
||||
3. [New Installation Baseline](hello-hybrid-key-new-install.md)
|
||||
4. [Configure Directory Synchronization](hello-hybrid-key-trust-dirsync.md)
|
||||
5. [Configure Azure Device Registration](hello-hybrid-key-trust-devreg.md)
|
||||
|
||||
@ -21,7 +21,7 @@ ms.date: 10/23/2017
|
||||
You are ready to configure your hybrid key trust environment for Windows Hello for Business.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Ensure your environment meets all the [prerequistes](hello-hybrid-key-trust-prereqs.md) before proceeding. Review the [New Installation baseline](hello-hybrid-key-new-install.md) section of this deployment document to learn how to prepare your environment for your Windows Hello for Business deployment.
|
||||
> Ensure your environment meets all the [prerequisites](hello-hybrid-key-trust-prereqs.md) before proceeding. Review the [New Installation baseline](hello-hybrid-key-new-install.md) section of this deployment document to learn how to prepare your environment for your Windows Hello for Business deployment.
|
||||
|
||||
The configuration for Windows Hello for Business is grouped in four categories. These categories are:
|
||||
* [Active Directory](hello-hybrid-key-whfb-settings-ad.md)
|
||||
|
||||
@ -366,7 +366,7 @@ The following table details the hardware requirements for both virtualization-ba
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Trusted Platform Module (TPM) </p></td>
|
||||
<td align="left"><p>Required to support health attestation and necessary for additional key protections for virtualization-based security. TPM 2.0 is supported; TPM 1.2 is also supported beginnning with Windows 10, version 1703.</p></td>
|
||||
<td align="left"><p>Required to support health attestation and necessary for additional key protections for virtualization-based security. TPM 2.0 is supported. Support for TPM 1.2 was added beginning in Windows 10, version 1607 (RS1)</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
Reference in New Issue
Block a user