mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-25 11:47:23 +00:00
- updated headers on hybrid deployments
This commit is contained in:
parent
23f720c609
commit
058d5233d0
@ -17,6 +17,7 @@ ms.date: 08/19/2018
|
|||||||
- Windows 10
|
- Windows 10
|
||||||
- Azure Active Directory joined
|
- Azure Active Directory joined
|
||||||
- Hybrid Deployment
|
- Hybrid Deployment
|
||||||
|
- Certificate trust
|
||||||
|
|
||||||
If you plan to use certificates for on-premises single-sign on, then follow these **addtional** steps to configure the environment to enroll a Windows Hello for Business certificates for Azure AD joined devices.
|
If you plan to use certificates for on-premises single-sign on, then follow these **addtional** steps to configure the environment to enroll a Windows Hello for Business certificates for Azure AD joined devices.
|
||||||
|
|
||||||
|
@ -14,9 +14,10 @@ ms.date: 08/19/2018
|
|||||||
# Windows Hello for Business Certificate Trust New Installation
|
# Windows Hello for Business Certificate Trust New Installation
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
- Windows 10
|
- Windows 10, version 1703 or later
|
||||||
|
- Hybrid deployment
|
||||||
|
- Certificate trust
|
||||||
|
|
||||||
>This guide only applies to Hybrid deployments for Windows 10, version 1703 or higher.
|
|
||||||
|
|
||||||
Windows Hello for Business involves configuring distributed technologies that may or may not exist in your current infrastructure. Hybrid certificate trust deployments of Windows Hello for Business rely on these technologies
|
Windows Hello for Business involves configuring distributed technologies that may or may not exist in your current infrastructure. Hybrid certificate trust deployments of Windows Hello for Business rely on these technologies
|
||||||
|
|
||||||
|
@ -14,9 +14,10 @@ ms.date: 08/18/2018
|
|||||||
# Configure Device Registration for Hybrid Windows Hello for Business
|
# Configure Device Registration for Hybrid Windows Hello for Business
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
- Windows 10
|
- Windows 10, version 1703 or later
|
||||||
|
- Hybrid deployment
|
||||||
|
- Certificate trust
|
||||||
|
|
||||||
>This guide only applies to Hybrid deployments for Windows 10, version 1703 or higher.
|
|
||||||
|
|
||||||
You're environment is federated and you are ready to configure device registration for your hybrid environment. Hybrid Windows Hello for Business deployment needs device registration and device write-back to enable proper device authentication.
|
You're environment is federated and you are ready to configure device registration for your hybrid environment. Hybrid Windows Hello for Business deployment needs device registration and device write-back to enable proper device authentication.
|
||||||
|
|
||||||
|
@ -14,11 +14,11 @@ ms.date: 08/19/2018
|
|||||||
# Hybrid Windows Hello for Business Prerequisites
|
# Hybrid Windows Hello for Business Prerequisites
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
- Windows 10
|
- Windows 10, version 1703 or later
|
||||||
|
- Hybrid deployment
|
||||||
|
- Certificate trust
|
||||||
|
|
||||||
|
|
||||||
>This guide only applies to Hybrid deployments for Windows 10, version 1703 or higher.
|
|
||||||
|
|
||||||
Hybrid environments are distributed systems that enable organizations to use on-premises and Azure-based identities and resources. Windows Hello for Business uses the existing distributed system as a foundation on which organizations can provide two-factor authentication that provides a single sign-in like experience to modern resources.
|
Hybrid environments are distributed systems that enable organizations to use on-premises and Azure-based identities and resources. Windows Hello for Business uses the existing distributed system as a foundation on which organizations can provide two-factor authentication that provides a single sign-in like experience to modern resources.
|
||||||
|
|
||||||
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:
|
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:
|
||||||
|
@ -14,9 +14,9 @@ ms.date: 09/08/2017
|
|||||||
# Hybrid Azure AD joined Certificate Trust Deployment
|
# Hybrid Azure AD joined Certificate Trust Deployment
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
- Windows 10
|
- Windows 10, version 1703 or later
|
||||||
|
- Hybrid deployment
|
||||||
>This guide only applies to Hybrid deployments for Windows 10, version 1703 or higher.
|
- Certificate trust
|
||||||
|
|
||||||
|
|
||||||
Windows Hello for Business replaces username and password sign-in to Windows with strong user authentication based on asymmetric key pair. The following deployment guide provides the information needed to successfully deploy Windows Hello for Business in a hybrid certificate trust scenario.
|
Windows Hello for Business replaces username and password sign-in to Windows with strong user authentication based on asymmetric key pair. The following deployment guide provides the information needed to successfully deploy Windows Hello for Business in a hybrid certificate trust scenario.
|
||||||
|
@ -14,11 +14,11 @@ ms.date: 08/19/2018
|
|||||||
# Hybrid Windows Hello for Business Provisioning
|
# Hybrid Windows Hello for Business Provisioning
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
- Windows 10
|
- Windows 10, version 1703 or later
|
||||||
|
- Hybrid deployment
|
||||||
|
- Certificate trust
|
||||||
|
|
||||||
|
|
||||||
>This guide only applies to Hybrid deployments for Windows 10, version 1703 or higher.
|
|
||||||
|
|
||||||
## Provisioning
|
## Provisioning
|
||||||
The Windows Hello for Business provisioning begins immediately after the user has signed in, after the user profile is loaded, but before the user receives their desktop. Windows only launches the provisioning experience if all the prerequisite checks pass. You can determine the status of the prerequisite checks by viewing the **User Device Registration** in the **Event Viewer** under **Applications and Services Logs\Microsoft\Windows**.
|
The Windows Hello for Business provisioning begins immediately after the user has signed in, after the user profile is loaded, but before the user receives their desktop. Windows only launches the provisioning experience if all the prerequisite checks pass. You can determine the status of the prerequisite checks by viewing the **User Device Registration** in the **Event Viewer** under **Applications and Services Logs\Microsoft\Windows**.
|
||||||
|
|
||||||
|
@ -14,9 +14,10 @@ ms.date: 08/19/2018
|
|||||||
# Configuring Windows Hello for Business: Active Directory
|
# Configuring Windows Hello for Business: Active Directory
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
- Windows 10
|
- Windows 10, version 1703 or later
|
||||||
|
- Hybrid deployment
|
||||||
|
- Certificate trust
|
||||||
|
|
||||||
>This guide only applies to Hybrid deployments for Windows 10, version 1703 or higher.
|
|
||||||
|
|
||||||
The key synchronization process for the hybrid deployment of Windows Hello for Business needs the Windows Server 2016 Active Directory schema.
|
The key synchronization process for the hybrid deployment of Windows Hello for Business needs the Windows Server 2016 Active Directory schema.
|
||||||
|
|
||||||
|
@ -9,17 +9,16 @@ ms.pagetype: security, mobile
|
|||||||
ms.localizationpriority: medium
|
ms.localizationpriority: medium
|
||||||
author: mikestephens-MS
|
author: mikestephens-MS
|
||||||
ms.author: mstephen
|
ms.author: mstephen
|
||||||
ms.date: 08/06/2018
|
ms.date: 08/20/2018
|
||||||
---
|
---
|
||||||
# Configure Windows Hello for Business: Active Directory Federation Services
|
# Configure Windows Hello for Business: Active Directory Federation Services
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
- Windows10
|
- Windows10, version 1703 or later
|
||||||
|
- Hybrid deployment
|
||||||
|
- Certificate trust
|
||||||
|
|
||||||
## Federation Services
|
## Federation Services
|
||||||
|
|
||||||
>This guide only applies to Hybrid deployments for Windows 10, version 1703 or higher.
|
|
||||||
|
|
||||||
The Windows Server 2016 Active Directory Federation Server Certificate Registration Authority (AD FS RA) enrolls for an enrollment agent certificate. Once the registration authority verifies the certificate request, it signs the certificate request using its enrollment agent certificate and sends it to the certificate authority.
|
The Windows Server 2016 Active Directory Federation Server Certificate Registration Authority (AD FS RA) enrolls for an enrollment agent certificate. Once the registration authority verifies the certificate request, it signs the certificate request using its enrollment agent certificate and sends it to the certificate authority.
|
||||||
|
|
||||||
The Windows Hello for Business Authentication certificate template is configured to only issue certificates to certificate requests that have been signed with an enrollment agent certificate.
|
The Windows Hello for Business Authentication certificate template is configured to only issue certificates to certificate requests that have been signed with an enrollment agent certificate.
|
||||||
|
@ -14,9 +14,10 @@ ms.date: 10/23/2017
|
|||||||
# Configure Hybrid Windows Hello for Business: Directory Synchronization
|
# Configure Hybrid Windows Hello for Business: Directory Synchronization
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
- Windows 10
|
- Windows 10, version 1703 or later
|
||||||
|
- Hybrid deployment
|
||||||
|
- Certificate trust
|
||||||
|
|
||||||
>This guide only applies to Hybrid deployments for Windows 10, version 1703 or higher.
|
|
||||||
|
|
||||||
## Directory Synchronization
|
## Directory Synchronization
|
||||||
|
|
||||||
|
@ -15,11 +15,10 @@ ms.date: 08/19/2018
|
|||||||
# Configure Hybrid Windows Hello for Business: Public Key Infrastructure
|
# Configure Hybrid Windows Hello for Business: Public Key Infrastructure
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
- Windows 10
|
- Windows 10, version 1703 or later
|
||||||
- Hybrid Deployment
|
- Hybrid Deployment
|
||||||
- Certificate Trust
|
- Certificate Trust
|
||||||
|
|
||||||
>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 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.
|
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.
|
||||||
|
|
||||||
|
@ -14,9 +14,10 @@ ms.date: 08/19/2018
|
|||||||
# Configure Hybrid Windows Hello for Business: Group Policy
|
# Configure Hybrid Windows Hello for Business: Group Policy
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
- Windows 10
|
- Windows 10, version 1703 or later
|
||||||
|
- Hybrid deployment
|
||||||
|
- Certificate trust
|
||||||
|
|
||||||
>This guide only applies to Hybrid deployments for Windows 10, version 1703 or higher.
|
|
||||||
|
|
||||||
## Policy Configuration
|
## Policy Configuration
|
||||||
|
|
||||||
|
@ -14,9 +14,10 @@ ms.date: 08/19/2018
|
|||||||
# Configure Windows Hello for Business
|
# Configure Windows Hello for Business
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
- Windows 10
|
- Windows 10, version 1703 or later
|
||||||
|
- Hybrid deployment
|
||||||
|
- Certificate trust
|
||||||
|
|
||||||
>This guide only applies to Hybrid deployments for Windows 10, version 1703 or higher.
|
|
||||||
|
|
||||||
You're environment is federated and you are ready to configure your hybrid environment for Windows Hello for business using the certificate trust model.
|
You're environment is federated and you are ready to configure your hybrid environment for Windows Hello for business using the certificate trust model.
|
||||||
> [!IMPORTANT]
|
> [!IMPORTANT]
|
||||||
|
@ -14,11 +14,10 @@ ms.date: 08/19/2018
|
|||||||
# Windows Hello for Business Key Trust New Installation
|
# Windows Hello for Business Key Trust New Installation
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
- Windows 10
|
- Windows 10, version 1703 or later
|
||||||
- Hybrid deployment
|
- Hybrid deployment
|
||||||
- Key trust
|
- Key trust
|
||||||
|
|
||||||
>This guide only applies to Hybrid deployments for Windows 10, version 1703 or higher.
|
|
||||||
|
|
||||||
Windows Hello for Business involves configuring distributed technologies that may or may not exist in your current infrastructure. Hybrid key trust deployments of Windows Hello for Business rely on these technologies
|
Windows Hello for Business involves configuring distributed technologies that may or may not exist in your current infrastructure. Hybrid key trust deployments of Windows Hello for Business rely on these technologies
|
||||||
|
|
||||||
|
@ -14,11 +14,11 @@ ms.date: 08/19/2018
|
|||||||
# Configure Device Registration for Hybrid key trust Windows Hello for Business
|
# Configure Device Registration for Hybrid key trust Windows Hello for Business
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
- Windows 10
|
- Windows 10, version 1703 or later
|
||||||
|
- Hybrid deployment
|
||||||
|
- Key trust
|
||||||
|
|
||||||
|
|
||||||
>This guide only applies to Hybrid deployments for Windows 10, version 1703 or higher.
|
|
||||||
|
|
||||||
You are ready to configure device registration for your hybrid environment. Hybrid Windows Hello for Business deployment needs device registration to enable proper device authentication.
|
You are ready to configure device registration for your hybrid environment. Hybrid Windows Hello for Business deployment needs device registration to enable proper device authentication.
|
||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
|
@ -14,11 +14,10 @@ ms.date: 08/19/2018
|
|||||||
# Configure Directory Synchronization for Hybrid key trust Windows Hello for Business
|
# Configure Directory Synchronization for Hybrid key trust Windows Hello for Business
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
- Windows 10
|
- Windows 10, version 1703 or later
|
||||||
- Hybrid deployment
|
- Hybrid deployment
|
||||||
- Key trust
|
- Key trust
|
||||||
|
|
||||||
>This guide only applies to Hybrid deployments for Windows 10, version 1703 or higher.
|
|
||||||
|
|
||||||
You are ready to configure directory synchronization for your hybrid environment. Hybrid Windows Hello for Business deployment needs both a cloud and an on-premises identity to authenticate and access resources in the cloud or on-premises.
|
You are ready to configure directory synchronization for your hybrid environment. Hybrid Windows Hello for Business deployment needs both a cloud and an on-premises identity to authenticate and access resources in the cloud or on-premises.
|
||||||
|
|
||||||
|
@ -9,16 +9,16 @@ ms.pagetype: security, mobile
|
|||||||
author: mikestephens-MS
|
author: mikestephens-MS
|
||||||
ms.author: mstephen
|
ms.author: mstephen
|
||||||
localizationpriority: high
|
localizationpriority: high
|
||||||
ms.date: 05/05/2018
|
ms.date: 08/20/2018
|
||||||
---
|
---
|
||||||
# Hybrid Key trust Windows Hello for Business Prerequisites
|
# Hybrid Key trust Windows Hello for Business Prerequisites
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
- Windows 10
|
- Windows 10, version 1703 or later
|
||||||
|
- Hybrid deployment
|
||||||
|
- Key trust
|
||||||
|
|
||||||
|
|
||||||
>This guide only applies to Hybrid deployments for Windows 10, version 1703 or higher.
|
|
||||||
|
|
||||||
Hybrid environments are distributed systems that enable organizations to use on-premises and Azure-based identities and resources. Windows Hello for Business uses the existing distributed system as a foundation on which organizations can provide two-factor authentication that provides a single sign-in like experience to modern resources.
|
Hybrid environments are distributed systems that enable organizations to use on-premises and Azure-based identities and resources. Windows Hello for Business uses the existing distributed system as a foundation on which organizations can provide two-factor authentication that provides a single sign-in like experience to modern resources.
|
||||||
|
|
||||||
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:
|
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:
|
||||||
|
@ -9,14 +9,14 @@ ms.pagetype: security, mobile
|
|||||||
author: mikestephens-MS
|
author: mikestephens-MS
|
||||||
ms.author: mstephen
|
ms.author: mstephen
|
||||||
ms.localizationpriority: medium
|
ms.localizationpriority: medium
|
||||||
ms.date: 10/20/2017
|
ms.date: 08/20/2018
|
||||||
---
|
---
|
||||||
# Hybrid Azure AD joined Key Trust Deployment
|
# Hybrid Azure AD joined Key Trust Deployment
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
- Windows 10
|
- Windows 10, version 1703 or later
|
||||||
|
- Hybrid deployment
|
||||||
>This guide only applies to Hybrid deployments for Windows 10, version 1703 or higher.
|
- Key trust
|
||||||
|
|
||||||
|
|
||||||
Windows Hello for Business replaces username and password sign-in to Windows with strong user authentication based on asymmetric key pair. The following deployment guide provides the information needed to successfully deploy Windows Hello for Business in a hybrid key trust scenario.
|
Windows Hello for Business replaces username and password sign-in to Windows with strong user authentication based on asymmetric key pair. The following deployment guide provides the information needed to successfully deploy Windows Hello for Business in a hybrid key trust scenario.
|
||||||
|
@ -9,16 +9,16 @@ ms.pagetype: security, mobile
|
|||||||
author: mikestephens-MS
|
author: mikestephens-MS
|
||||||
ms.author: mstephen
|
ms.author: mstephen
|
||||||
ms.localizationpriority: medium
|
ms.localizationpriority: medium
|
||||||
ms.date: 10/20/2017
|
ms.date: 08/20/2018
|
||||||
---
|
---
|
||||||
# Hybrid Windows Hello for Business Provisioning
|
# Hybrid Windows Hello for Business Provisioning
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
- Windows 10
|
- Windows 10, version 1703 or later
|
||||||
|
- Hybrid deployment
|
||||||
|
- Key trust
|
||||||
|
|
||||||
|
|
||||||
>This guide only applies to Hybrid deployments for Windows 10, version 1703 or higher.
|
|
||||||
|
|
||||||
## Provisioning
|
## Provisioning
|
||||||
The Windows Hello for Business provisioning begins immediately after the user has signed in, after the user profile is loaded, but before the user receives their desktop. Windows only launches the provisioning experience if all the prerequisite checks pass. You can determine the status of the prerequisite checks by viewing the **User Device Registration** in the **Event Viewer** under **Applications and Services Logs\Microsoft\Windows**.
|
The Windows Hello for Business provisioning begins immediately after the user has signed in, after the user profile is loaded, but before the user receives their desktop. Windows only launches the provisioning experience if all the prerequisite checks pass. You can determine the status of the prerequisite checks by viewing the **User Device Registration** in the **Event Viewer** under **Applications and Services Logs\Microsoft\Windows**.
|
||||||
|
|
||||||
|
@ -9,14 +9,15 @@ ms.pagetype: security, mobile
|
|||||||
ms.localizationpriority: medium
|
ms.localizationpriority: medium
|
||||||
author: mikestephens-MS
|
author: mikestephens-MS
|
||||||
ms.author: mstephen
|
ms.author: mstephen
|
||||||
ms.date: 05/05/2018
|
ms.date: 08/20/2018
|
||||||
---
|
---
|
||||||
# Configuring Hybrid key trust Windows Hello for Business: Active Directory
|
# Configuring Hybrid key trust Windows Hello for Business: Active Directory
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
- Windows 10
|
- Windows 10, version 1703 or later
|
||||||
|
- Hybrid deployment
|
||||||
|
- Key trust
|
||||||
|
|
||||||
>This guide only applies to Hybrid deployments for Windows 10, version 1703 or higher.
|
|
||||||
|
|
||||||
Configure the appropriate security groups to efficiently deploy Windows Hello for Business to users.
|
Configure the appropriate security groups to efficiently deploy Windows Hello for Business to users.
|
||||||
|
|
||||||
|
@ -14,9 +14,10 @@ ms.date: 08/19/2018
|
|||||||
# Configure Hybrid Windows Hello for Business: Directory Synchronization
|
# Configure Hybrid Windows Hello for Business: Directory Synchronization
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
- Windows 10
|
- Windows 10, version 1703 or later
|
||||||
|
- Hybrid deployment
|
||||||
|
- Key trust
|
||||||
|
|
||||||
>This guide only applies to Hybrid deployments for Windows 10, version 1703 or higher.
|
|
||||||
|
|
||||||
## Directory Syncrhonization
|
## Directory Syncrhonization
|
||||||
|
|
||||||
|
@ -15,11 +15,10 @@ ms.date: 08/19/2018
|
|||||||
# Configure Hybrid Windows Hello for Business: Public Key Infrastructure
|
# Configure Hybrid Windows Hello for Business: Public Key Infrastructure
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
- Windows 10
|
- Windows 10, version 1703 or later
|
||||||
- Hybrid Deployment
|
- Hybrid Deployment
|
||||||
- Key trust
|
- Key trust
|
||||||
|
|
||||||
>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 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.
|
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.
|
||||||
|
|
||||||
|
@ -9,14 +9,15 @@ ms.pagetype: security, mobile
|
|||||||
localizationpriority: high
|
localizationpriority: high
|
||||||
author: mikestephens-MS
|
author: mikestephens-MS
|
||||||
ms.author: mstephen
|
ms.author: mstephen
|
||||||
ms.date: 05/05/2018
|
ms.date: 08/20/2018
|
||||||
---
|
---
|
||||||
# Configure Hybrid Windows Hello for Business: Group Policy
|
# Configure Hybrid Windows Hello for Business: Group Policy
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
- Windows 10
|
- Windows 10, version 1703 or later
|
||||||
|
- Hybrid deployment
|
||||||
|
- Key trust
|
||||||
|
|
||||||
>This guide only applies to Hybrid deployments for Windows 10, version 1703 or higher.
|
|
||||||
|
|
||||||
## Policy Configuration
|
## Policy Configuration
|
||||||
|
|
||||||
|
@ -14,9 +14,10 @@ ms.date: 08/19/2018
|
|||||||
# Configure Hybrid Windows Hello for Business key trust settings
|
# Configure Hybrid Windows Hello for Business key trust settings
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
- Windows 10
|
- Windows 10, version 1703 or later
|
||||||
|
- Hybrid deployment
|
||||||
|
- Key trust
|
||||||
|
|
||||||
>This guide only applies to Hybrid deployments for Windows 10, version 1703 or higher.
|
|
||||||
|
|
||||||
You are ready to configure your hybrid key trust environment for Windows Hello for Business.
|
You are ready to configure your hybrid key trust environment for Windows Hello for Business.
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user