mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-18 20:03:40 +00:00
Add text from images 6
This commit is contained in:
@ -484,11 +484,14 @@ Use the following guides to verify each one of these requirements:
|
|||||||
|
|
||||||
For more information, see [Assigning licenses to users](#assign-licenses-to-users).
|
For more information, see [Assigning licenses to users](#assign-licenses-to-users).
|
||||||
|
|
||||||
## Known issues
|
## Recommended practices
|
||||||
|
|
||||||
- When a device has been offline for an extended period of time, the Subscription Activation might not reactivate automatically on the device. To resolve this issue, use Conditional Access policies to control access by excluding one of the following cloud apps from their Conditional Access policies using **Select Excluded Cloud Apps**: \
|
### Adding Conditional Access policy
|
||||||
|
|
||||||
|
When a device has been offline for an extended period of time, the Subscription Activation might not reactivate automatically on the device. To resolve this issue, use Conditional Access policies to control access by excluding one of the following cloud apps from their Conditional Access policies using **Select Excluded Cloud Apps**:
|
||||||
|
|
||||||
- [Universal Store Service APIs and Web Application, AppID 45a330b1-b1ec-4cc1-9161-9f03992aa49f](/troubleshoot/azure/active-directory/verify-first-party-apps-sign-in#application-ids-of-commonly-used-microsoft-applications).
|
- [Universal Store Service APIs and Web Application, AppID 45a330b1-b1ec-4cc1-9161-9f03992aa49f](/troubleshoot/azure/active-directory/verify-first-party-apps-sign-in#application-ids-of-commonly-used-microsoft-applications).
|
||||||
|
|
||||||
- [Windows Store for Business, AppID 45a330b1-b1ec-4cc1-9161-9f03992aa49f](/troubleshoot/azure/active-directory/verify-first-party-apps-sign-in#application-ids-of-commonly-used-microsoft-applications).
|
- [Windows Store for Business, AppID 45a330b1-b1ec-4cc1-9161-9f03992aa49f](/troubleshoot/azure/active-directory/verify-first-party-apps-sign-in#application-ids-of-commonly-used-microsoft-applications).
|
||||||
|
|
||||||
Although the app ID is the same in both instances, the name of the cloud app depends on the tenant.
|
Although the app ID is the same in both instances, the name of the cloud app depends on the tenant.
|
||||||
@ -511,27 +514,29 @@ Use the following guides to verify each one of these requirements:
|
|||||||
|
|
||||||
The prompt for authentication usually occurs when a device has been offline for an extended period of time. This change eliminates the need for an exclusion in the Conditional Access policy for Windows 11, version 23H2 with [KB5034848](https://support.microsoft.com/help/5034848) or later. A Conditional Access policy can still be used with Windows 11, version 23H2 with [KB5034848](https://support.microsoft.com/help/5034848) or later if the prompt for user authentication via a toast notification isn't desired.
|
The prompt for authentication usually occurs when a device has been offline for an extended period of time. This change eliminates the need for an exclusion in the Conditional Access policy for Windows 11, version 23H2 with [KB5034848](https://support.microsoft.com/help/5034848) or later. A Conditional Access policy can still be used with Windows 11, version 23H2 with [KB5034848](https://support.microsoft.com/help/5034848) or later if the prompt for user authentication via a toast notification isn't desired.
|
||||||
|
|
||||||
- If a device isn't able to connect to Windows Update, it can lose activation status or be blocked from upgrading to Windows Enterprise. Make sure that Windows Update isn't blocked on the device:
|
### Make sure Windows Update isn't blocked
|
||||||
|
|
||||||
|
If a device isn't able to connect to Windows Update, it can lose activation status or be blocked from upgrading to Windows Enterprise. Make sure that Windows Update isn't blocked on the device:
|
||||||
|
|
||||||
- Using `gpedit.msc` or group policy editor in the domain, make sure that the following group policy setting is set to **Disabled** or **Not Configured**:
|
- Using `gpedit.msc` or group policy editor in the domain, make sure that the following group policy setting is set to **Disabled** or **Not Configured**:
|
||||||
|
|
||||||
::: zone pivot="windows-11"
|
::: zone pivot="windows-11"
|
||||||
|
|
||||||
**Computer Configuration** > **Administrative Templates** > **Windows Components** > **Windows Update** > **Manage updates offered from Windows Server Update Service** > **Do not connect to any Windows Update Internet locations**
|
> **Computer Configuration** > **Administrative Templates** > **Windows Components** > **Windows Update** > **Manage updates offered from Windows Server Update Service** > **Do not connect to any Windows Update Internet locations**
|
||||||
|
|
||||||
::: zone-end
|
::: zone-end
|
||||||
|
|
||||||
::: zone pivot="windows-10"
|
::: zone pivot="windows-10"
|
||||||
|
|
||||||
**Computer Configuration** > **Administrative Templates** > **Windows Components** > **Windows Update** > **Do not connect to any Windows Update Internet locations**
|
> **Computer Configuration** > **Administrative Templates** > **Windows Components** > **Windows Update** > **Do not connect to any Windows Update Internet locations**
|
||||||
|
|
||||||
::: zone-end
|
::: zone-end
|
||||||
|
|
||||||
If this policy is set to **Enabled**, it must be changed to **Disabled** or **Not Configured**.
|
If this policy is set to **Enabled**, it must be changed to **Disabled** or **Not Configured**.
|
||||||
|
|
||||||
- In the following registry key:
|
- In the following registry key of the registry:
|
||||||
|
|
||||||
`HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate`
|
> `HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate`
|
||||||
|
|
||||||
check if the value `DoNotConnectToWindowsUpdateInternetLocations` exists. If the value does exist, verify that it has a REG_DWORD value of `0`. If the value is instead set to `1`, it must be changed to `0`. The value can be changed by running the following command from an elevated command prompt:
|
check if the value `DoNotConnectToWindowsUpdateInternetLocations` exists. If the value does exist, verify that it has a REG_DWORD value of `0`. If the value is instead set to `1`, it must be changed to `0`. The value can be changed by running the following command from an elevated command prompt:
|
||||||
|
|
||||||
@ -543,7 +548,7 @@ Use the following guides to verify each one of these requirements:
|
|||||||
>
|
>
|
||||||
> 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`.
|
> 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`.
|
||||||
|
|
||||||
- Delay in the activation of Enterprise license of Windows.
|
### Delay in the activation of Enterprise license of Windows
|
||||||
|
|
||||||
There might be a delay in the activation of the Enterprise license in Windows. This delay is by design. Windows uses a built-in cache when determining upgrade eligibility. This behavior includes processing responses that indicate that the device isn't eligible for an upgrade. It can take up to four days after a qualifying purchase before the upgrade eligibility is enabled and the cache expires.
|
There might be a delay in the activation of the Enterprise license in Windows. This delay is by design. Windows uses a built-in cache when determining upgrade eligibility. This behavior includes processing responses that indicate that the device isn't eligible for an upgrade. It can take up to four days after a qualifying purchase before the upgrade eligibility is enabled and the cache expires.
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user