deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-15 10:23:37 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

revise from review

Browse Source
This commit is contained in:
Aaron Czechowski
2022-09-28 14:07:29 -07:00
parent ecfcfebaf0
commit 66b289785e
2 changed files with 24 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

47
windows/deployment/deploy-enterprise-licenses.md
View File

@ -18,23 +18,12 @@ appliesto:
This article describes how to deploy Windows 10 or Windows 11 Enterprise E3 or E5 licenses with [subscription activation](windows-10-subscription-activation.md) or [Enterprise E3 in CSP](windows-10-enterprise-e3-overview.md) and Azure Active Directory (Azure AD).
> [!NOTE]
> These activation features require a supported and licensed version of Windows 10 Pro or Windows 11 Pro.
>
> - Subscription activation with an enterprise agreement (EA) or a Microsoft Products & Services Agreement (MPSA).
> - Enterprise E3 in CSP.
> - Automatic, non-KMS activation also requires a device with a firmware-embedded activation key.
> - Subscription activation requires Enterprise _per user_ licensing. It doesn't work with _per device_ licensing.
These activation features require a supported and licensed version of Windows 10 Pro or Windows 11 Pro:
## Firmware-embedded activation key
To determine if the computer has a firmware-embedded activation key, enter the following command at an elevated Windows PowerShell prompt:
```PowerShell
(Get-CimInstance -query 'select * from SoftwareLicensingService').OA3xOriginalProductKey
```
If the device has a firmware-embedded activation key, it will be displayed in the output. If the output is blank, the device doesn't have a firmware embedded activation key. Most OEM-provided devices designed to run Windows 8 or later will have a firmware-embedded key.
- Subscription activation with an enterprise agreement (EA) or a Microsoft Products & Services Agreement (MPSA).
- Enterprise E3 in CSP.
- Automatic, non-KMS activation also requires a device with a firmware-embedded activation key.
- Subscription activation requires Enterprise _per user_ licensing. It doesn't work with _per device_ licensing.
## Enable subscription activation with an existing EA
@ -71,7 +60,14 @@ If you need to update contact information and resend the activation email, use t
1. Update the contact information, then select **Update Contact Details**. This action will trigger a new email.
## Active Directory synchronization with Azure AD
## Preparing for deployment: reviewing requirements
- Devices must be running a supported version of Windows 10 Pro or Windows 11 Pro
- Azure AD-joined, or hybrid domain joined with Azure AD Connect. Customers who are federated with Azure AD are also eligible.
For more information, see [Review requirements on devices](#review-requirements-on-devices), later in this article.
### Active Directory synchronization with Azure AD
If you have an on-premises Active Directory Domain Services (AD DS) domain, you need to synchronize the identities in the on-premises AD DS domain with Azure AD. This synchronization is required for users to have a _single identity_ that they can use to access their on-premises apps and cloud services that use Azure AD. An example of a cloud service is Windows Enterprise E3 or E5.
@ -86,13 +82,6 @@ For more information about integrating on-premises AD DS domains with Azure AD,
- [What is hybrid identity with Azure Active Directory?](/azure/active-directory/hybrid/whatis-hybrid-identity)
- [Azure AD Connect and Azure AD Connect Health installation roadmap](/azure/active-directory/hybrid/how-to-connect-install-roadmap)
## Preparing for deployment: reviewing requirements
- Devices must be running a supported version of Windows 10 Pro or Windows 11 Pro
- Azure AD-joined, or hybrid domain joined with Azure AD Connect. Customers who are federated with Azure AD are also eligible.
For more information, see [Review requirements on devices](#review-requirements-on-devices), later in this article.
## Assigning licenses to users
After you've ordered the Windows subscription (Windows 10 Business, E3 or E5), you'll receive an email with guidance on how to use Windows as an online service:
@ -258,6 +247,16 @@ Devices must also be joined to Azure AD, or hybrid domain joined with Azure AD C
Use the following procedures to review whether a particular device meets these requirements.
#### Firmware-embedded activation key
To determine if the computer has a firmware-embedded activation key, enter the following command at an elevated Windows PowerShell prompt:
```PowerShell
(Get-CimInstance -query 'select * from SoftwareLicensingService').OA3xOriginalProductKey
```
If the device has a firmware-embedded activation key, it will be displayed in the output. If the output is blank, the device doesn't have a firmware embedded activation key. Most OEM-provided devices designed to run Windows 8 or later will have a firmware-embedded key.
#### Determine if a device is Azure AD-joined
1. Open a command prompt and enter `dsregcmd /status`.

2
windows/deployment/windows-10-subscription-activation.md
View File

@ -216,7 +216,7 @@ $(Get-WmiObject SoftwareLicensingService).OA3xOriginalProductKey | foreach{ if (
If your organization has an Enterprise Agreement (EA) or Software Assurance (SA):
- Organizations with a traditional EA must order a $0 SKU, process e-mails sent to the license administrator for the company, and assign licenses using Azure AD. Ideally, you assign the licenses to groups using the Azure AD Premium feature for group assignment. For more information, see [Enable subscription activation with an existing EA](./deploy-enterprise-licenses.md#enabling-subscription-activation-with-an-existing-ea).
- Organizations with a traditional EA must order a $0 SKU, process e-mails sent to the license administrator for the company, and assign licenses using Azure AD. Ideally, you assign the licenses to groups using the Azure AD Premium feature for group assignment. For more information, see [Enable subscription activation with an existing EA](./deploy-enterprise-licenses.md#enable-subscription-activation-with-an-existing-ea).
- The license administrator can assign seats to Azure AD users with the same process that's used for Microsoft 365 Apps.