mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-17 03:13:44 +00:00
Fixing TechNet and MSDN links plus refreshing articles 20
This commit is contained in:
@ -373,7 +373,7 @@ Use the following procedures to review whether a particular device meets these r
|
|||||||
1. In the command prompt window, enter:
|
1. In the command prompt window, enter:
|
||||||
|
|
||||||
```cmd
|
```cmd
|
||||||
dsregcmd /status
|
dsregcmd.exe /status
|
||||||
```
|
```
|
||||||
|
|
||||||
1. Review the output. Under the first section called **Device State**, verify that the value of **AzureAdJoined** is **YES**. If the value is **YES**, the device is joined to Microsoft Entra ID.
|
1. Review the output. Under the first section called **Device State**, verify that the value of **AzureAdJoined** is **YES**. If the value is **YES**, the device is joined to Microsoft Entra ID.
|
||||||
@ -445,10 +445,14 @@ There might be a delay in the activation of the Enterprise license in Windows. T
|
|||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
>
|
>
|
||||||
> Make sure to first check what the group policy of **Do not connect to any Windows Update Internet locations** is set to. If this policy is **Enabled**, then this registry key will eventually be reset back to `1` even after it's manually set to `0` via `reg.exe`. Setting the policy of **Do not connect to any Windows Update Internet locations** to **Disabled** or **Not Configured** will make sure the registry value remains as `0`.
|
> Make sure to first check the group policy of **Do not connect to any Windows Update Internet locations**. If the policy is **Enabled**, then this registry key will eventually be reset back to `1` even after it's manually set to `0` via `reg.exe`. Setting the policy of **Do not connect to any Windows Update Internet locations** to **Disabled** or **Not Configured** will make sure the registry value remains as `0`.
|
||||||
|
|
||||||
## Virtual Desktop Access (VDA)
|
## Virtual Desktop Access (VDA)
|
||||||
|
|
||||||
Subscriptions to Windows Enterprise are also available for virtualized clients. Enterprise E3 and E5 are available for Virtual Desktop Access (VDA) in Azure or in another qualified multitenant host.
|
Subscriptions to Windows Enterprise are also available for virtualized clients. Enterprise E3 and E5 are available for Virtual Desktop Access (VDA) in Azure or in another qualified multitenant host.
|
||||||
|
|
||||||
Virtual machines (VMs) must be configured to enable Windows Enterprise subscriptions for VDA. Active Directory-joined and Microsoft Entra joined clients are supported. For more information, see [Enable VDA for Enterprise subscription activation](vda-subscription-activation.md).
|
Virtual machines (VMs) must be configured to enable Windows Enterprise subscriptions for VDA. Active Directory-joined and Microsoft Entra joined clients are supported. For more information, see [Enable VDA for Enterprise subscription activation](vda-subscription-activation.md).
|
||||||
|
|
||||||
|
## Related articles
|
||||||
|
|
||||||
|
- [MDM enrollment of Windows devices](/windows/client-management/mdm-enrollment-of-windows-devices).
|
Reference in New Issue
Block a user