mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-17 11:23:45 +00:00
Fixing TechNet and MSDN links plus refreshing articles 21
This commit is contained in:
Frank Rojas
@ -139,6 +139,8 @@ The first time the device starts, a Windows Pro device can join Microsoft Entra
|
||||
|
||||
1. In the **Choose privacy settings for your device** screen, configure privacy settings as desired, using the **Next** button to go between settings. Once complete, select the **Accept** button.
|
||||
|
||||
1. Additional screens appear depending on the device and the configuration of organization specific settings. For example, the **Windows Hello** screen might appear.
|
||||
|
||||
::: zone-end
|
||||
|
||||
::: zone pivot="windows-10"
|
||||
@ -165,6 +167,8 @@ The first time the device starts, a Windows Pro device can join Microsoft Entra
|
||||
|
||||
1. In the **Choose privacy settings for your device** screen, configure privacy settings as desired. Once complete, select the **Accept** button.
|
||||
|
||||
1. Additional screens appear depending on the device and the configuration of organization specific settings. For example, the **Windows Hello** screen might appear.
|
||||
|
||||
::: zone-end
|
||||
|
||||
Once Windows Setup finishes, the user is automatically signed in and the device is Microsoft Entra joined to the organization's subscription.
|
||||
@ -177,7 +181,7 @@ Once Windows Setup finishes, the user is automatically signed in and the device
|
||||
|
||||
::: zone pivot="windows-11"
|
||||
|
||||
1. Right-click on the Start menu and select **Settings**.
|
||||
1. Right-click on the **Start** menu and select **Settings**.
|
||||
|
||||
1. In the **Settings** app, select **Accounts** in the left hand pane.
|
||||
|
||||
@ -201,7 +205,7 @@ Once Windows Setup finishes, the user is automatically signed in and the device
|
||||
|
||||
::: zone pivot="windows-10"
|
||||
|
||||
1. Right-click on the Start menu and select **Settings**.
|
||||
1. Right-click on the **Start** menu and select **Settings**.
|
||||
|
||||
1. In the **Settings** app, select **Accounts**.
|
||||
|
||||
@ -237,14 +241,21 @@ Once the device is joined to Microsoft Entra ID, users sign in with their Micros
|
||||
|
||||
To verify the Windows Enterprise E3 or E5 subscription:
|
||||
|
||||
|
||||
|
||||
> [!div class="nextstepaction"]
|
||||
> [Activation](ms-settings:activation)
|
||||
|
||||
1. Right click on the **Start** menu and select **Run**.
|
||||
|
||||
1. In the **Run** window, next to **Open**, enter
|
||||
|
||||
`ms-settings:activation`
|
||||
|
||||
and then select **OK**.
|
||||
|
||||
::: zone pivot="windows-11"
|
||||
|
||||
1. Right-click on the Start menu and select **Settings**.
|
||||
|
||||
1. In the **Settings** app, select **System** in the left hand pane.
|
||||
|
||||
1. In the **System** pane, **Activation**.
|
||||
|
||||
1. In the **System > Activation** pane, expand **Activation state** and **Subscription** to see full details of the activation state and status:
|
||||
|
||||
1. Under **Activation state**, verify that Windows is activated. It should display the message:
|
||||
@ -259,16 +270,18 @@ To verify the Windows Enterprise E3 or E5 subscription:
|
||||
>
|
||||
> If the Windows Enterprise subscription hasn't yet been applied, the **Subscription** pane isn't displayed.
|
||||
|
||||
The **System > Activation** pane can also be navigated to with the following steps:
|
||||
|
||||
1. Right-click on the **Start** menu and select **Settings**.
|
||||
|
||||
1. In the **Settings** app, select **System** in the left hand pane.
|
||||
|
||||
1. In the **System** pane, **Activation**.
|
||||
|
||||
::: zone-end
|
||||
|
||||
::: zone pivot="windows-10"
|
||||
|
||||
1. Right-click on the Start menu and select **Settings**.
|
||||
|
||||
1. In the **Settings** app, select **Update & Security**.
|
||||
|
||||
1. In the left hand pane, select **Activation**.
|
||||
|
||||
1. In the **Activation** pane:
|
||||
|
||||
1. Next to **Subscription**, verify that the Windows 10 Enterprise subscription is active. It should display the message:
|
||||
@ -283,19 +296,49 @@ To verify the Windows Enterprise E3 or E5 subscription:
|
||||
|
||||
`Windows is activated with a digital license`
|
||||
|
||||
The **Activation** pane can also be navigated to with the following steps:
|
||||
|
||||
1. Right-click on the **Start** menu and select **Settings**.
|
||||
|
||||
1. In the **Settings** app, select **Update & Security**.
|
||||
|
||||
1. In the left hand pane, select **Activation**.
|
||||
|
||||
::: zone-end
|
||||
|
||||
or by selecting the following link:
|
||||
|
||||
> [!div class="nextstepaction"]
|
||||
> [Activation](ms-settings:activation)
|
||||
|
||||
A device is healthy when both the subscription and activation are active. If there are any problems with the Windows Enterprise E3 or E5 license or the activation of the license, the **Activation** pane displays the appropriate error message or status. This information can be used to help diagnose the licensing and activation process.
|
||||
|
||||
> [!NOTE]
|
||||
>
|
||||
> If the `slmgr /dli` or `slmgr /dlv` commands are used to get the activation information for the E3 or E5 license, the license information displayed is similar to the following output:
|
||||
>
|
||||
> ```console
|
||||
> Name: Windows(R), Professional edition
|
||||
> Description: Windows(R) Operating System, RETAIL channel
|
||||
> Partial Product Key: 3V66T
|
||||
> ```
|
||||
#### Verify that Enterprise edition is enabled with slmgr
|
||||
|
||||
**Slmgr** can also be used to verify the activation information:
|
||||
|
||||
1. Open a command prompt.
|
||||
|
||||
1. In the command prompt window, to get basic licensing information run the command:
|
||||
|
||||
```cmd
|
||||
slmgr /dli
|
||||
```
|
||||
|
||||
A window with output similar to the following opens:
|
||||
|
||||
```console
|
||||
Name: Windows(R), Professional edition
|
||||
Description: Windows(R) Operating System, RETAIL channel
|
||||
Partial Product Key: 3V66T
|
||||
License Status: Licensed
|
||||
```
|
||||
|
||||
To get detailed licensing information, run the following command instead:
|
||||
|
||||
```cmd
|
||||
slmgr /dlv
|
||||
```
|
||||
|
||||
## Troubleshoot the user experience
|
||||
|
||||
|
||||
@ -78,32 +78,6 @@ Inherited activation allows Windows virtual machines to inherit activation state
|
||||
|
||||
To support inherited activation, both the host computer and the VM must be running a currently supported version of Windows. The hypervisor platform must also be Windows Hyper-V.
|
||||
|
||||
## The evolution of deployment
|
||||
|
||||
The following list illustrates the evolution of deploying Windows client with each release:
|
||||
|
||||
- **Windows 7** required redeploying the operating system using a full wipe-and-load process to change from Windows 7 Professional to Windows 10 Enterprise.
|
||||
|
||||
- **Windows 8.1** added support for a Windows 8.1 Pro to Windows 8.1 Enterprise in-place upgrade. This process was considered a "repair upgrade", because the OS version was the same before and after. This upgrade was a lot easier than wipe-and-load, but it was still time-consuming.
|
||||
|
||||
- **Windows 10, version 1507** added the ability to install a new product key using a provisioning package or using MDM to change the edition. This process required a reboot, which would install the new OS components, and took several minutes to complete. However, it was a lot quicker than in-place upgrade.
|
||||
|
||||
- **Windows 10, version 1607** made a large leap forward. The product key could just be changed and the edition instantly changed from Windows 10 Pro to Windows 10 Enterprise. In addition to provisioning packages and MDM, a key can be injected using `slmgr.vbs`, which injects the key into WMI. It became trivial to do this process using a command line.
|
||||
|
||||
- **Windows 10, version 1703** made the step-up from Windows 10 Pro to Windows 10 Enterprise automatic for devices that subscribed to Windows 10 Enterprise E3 or E5 via the CSP program.
|
||||
|
||||
- **Windows 10, version 1709** added support for Windows 10 subscription activation, similar to the CSP support but for large enterprises. This feature enabled the use of Microsoft Entra ID for assigning licenses to users. When users sign in to a device joined to Active Directory or Microsoft Entra ID, it automatically steps up from Windows 10 Pro to Windows 10 Enterprise.
|
||||
|
||||
- **Windows 10, version 1803** updated Windows 10 subscription activation to enable pulling activation keys directly from firmware for devices that support firmware-embedded keys. It was no longer necessary to run a script to activate Windows 10 Pro before activating Enterprise. For virtual machines and hosts running Windows 10, version 1803, [inherited activation](#inherited-activation) was also enabled.
|
||||
|
||||
- **Windows 10, version 1903** updated Windows 10 subscription activation to enable step-up from Windows 10 Pro Education to Windows 10 Education for devices with a qualifying Windows 10 or Microsoft 365 subscription.
|
||||
|
||||
- **Windows 11, version 21H2** updated subscription activation to work on both Windows 10 and Windows 11 devices.
|
||||
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> Subscription activation doesn't update a device to a newer version of Windows. Only the edition is updated.
|
||||
|
||||
## Requirements
|
||||
|
||||
### Windows Enterprise requirements
|
||||
|
||||
Reference in New Issue
Block a user