|
| 1 | +--- |
| 2 | +title: Troubleshoot User Experience Sync for Windows 365 Frontline in shared mode |
| 3 | +description: Troubleshoot User Experience Sync for Windows 365 Frontline in shared mode |
| 4 | +manager: dcscontentpm |
| 5 | +ms.date: 10/29/2025 |
| 6 | +ms.topic: troubleshooting |
| 7 | +ms.reviewer: msft-jasonparker, stulimat, scottduf |
| 8 | +ms.custom: |
| 9 | +- pcy:WinComm User Experience |
| 10 | +- sap:Configuration and Management\Managing Devices with Intune |
| 11 | +ms.collection: |
| 12 | +- M365-identity-device-management |
| 13 | +- tier2 |
| 14 | +--- |
| 15 | + |
| 16 | +# Troubleshoot User Experience Sync for Windows 365 Frontline in shared mode |
| 17 | + |
| 18 | +This article provides troubleshooting steps for the most common issues related to User Experience Sync in Windows 365 Frontline shared mode environments. |
| 19 | + |
| 20 | +## Users receive a warning about a temporary user experience |
| 21 | + |
| 22 | +When a user signs in, Windows might notify them that they've signed in by using a temporary profile instead of the user's regular profile. Windows also displays another notification that states "We can't sign into your account." As a result, the user has a temporary user experience. |
| 23 | + |
| 24 | +> [!NOTE] |
| 25 | +> A temporary profile is a non-persistent Windows user profile that Windows creates when the system can't load or create the user's regular profile. The temporary profile provides basic functionality, but any changes made during the session (such as changes to settings, changes to files, or customizations) are discarded when the user signs out. Users see a notification that they've signed in by using a temporary profile, and their desktop and Start menu use default Windows settings instead of their personalized configuration. |
| 26 | +
|
| 27 | +To start troubleshooting this issue, check the status of the user's individual user storage as described in the following sections. |
| 28 | + |
| 29 | +### Individual user storage failed to attach to their session |
| 30 | + |
| 31 | +During the Windows sign-in process, users follow one of two flows: |
| 32 | + |
| 33 | +- Create and attach new individual user storage |
| 34 | +- Attach their existing individual user storage |
| 35 | + |
| 36 | +Both processes require the service to attach a disk to the Cloud PC while the user is signing in. Attachment failures are uncommon but might occur when the pooled user storage exceeds the storage limit. |
| 37 | + |
| 38 | +#### Pooled user storage has exceeded the storage limit |
| 39 | + |
| 40 | +User Experience Sync provides a limited amount pooled user storage based on a storage calculation. |
| 41 | + |
| 42 | +##### Understanding pooled storage limits |
| 43 | + |
| 44 | +Each provisioning policy defines a pooled user storage limit calculated using the following formula: |
| 45 | + |
| 46 | +**Total pooled storage** = OS disk size × Number of provisioned Cloud PCs |
| 47 | + |
| 48 | +:::image type="content" source="media/troubleshoot-user-experience-sync/user-experience-sync-user-storage-example.png" alt-text="Figure 1: Storage calculation of pooled user storage based on Cloud PC size and count"::: |
| 49 | + |
| 50 | +<sup>**Figure 1:** Storage calculation of pooled user storage based on Cloud PC size and count</sup> |
| 51 | + |
| 52 | +##### Normal storage consumption |
| 53 | + |
| 54 | +Under normal conditions, the pooled user storage is consumed as users create individual user storages. When the storage reaches capacity: |
| 55 | + |
| 56 | +- **Total size** and **Used size** are equal |
| 57 | +- **Available size** shows **0 GB** |
| 58 | +- The **User Storage** tab displays these metrics in the provisioning policy |
| 59 | + |
| 60 | +:::image type="content" source="media/troubleshoot-user-experience-sync/user-experience-sync-full-storage-limit.png" alt-text="Figure 2: Pooled user storage that is at the policy limit"::: |
| 61 | + |
| 62 | +<sup>**Figure 2:** Pooled user storage that is at the policy limit</sup> |
| 63 | + |
| 64 | +##### Exceeded storage conditions |
| 65 | + |
| 66 | +When pooled user storage is *near* capacity and multiple users sign in simultaneously, all users sign in successfully and create their individual user storage. This process results in an **exceeded** condition that has the following characteristics: |
| 67 | + |
| 68 | +- **Used size** becomes **greater** than the **Total size** |
| 69 | +- **Available size** remains **0 GB** |
| 70 | +- A new **Exceeded** property appears, showing the amount that exceeds the policy limit |
| 71 | + |
| 72 | +:::image type="content" source="media/troubleshoot-user-experience-sync/user-experience-sync-exceeded-storage-limit.png" alt-text="Figure 3: Pooled user storage that has exceeded the policy limit"::: |
| 73 | + |
| 74 | +<sup>**Figure 3:** Pooled user storage that has exceeded the policy limit</sup> |
| 75 | + |
| 76 | +##### Exceeded tolerance period |
| 77 | + |
| 78 | +When pooled user storage exceeds its limit, the provisioning policy enters a tolerance period to prevent further storage growth. During this period: |
| 79 | + |
| 80 | +- **Duration**: The tolerance period lasts for **7 days** from when the exceeded condition first occurs. |
| 81 | +- **User impact**: Existing users who have individual storage can continue to sign in and access their personalized user experience. |
| 82 | +- **New user restrictions**: New users that attempt to sign in receive a temporary user experience until storage is freed up. |
| 83 | +- **Administrator actions**: Manually delete individual user storage or increase the Cloud PC count for the assignment. |
| 84 | +- **Automatic resolution**: If storage usage drops below the limit during the tolerance period, normal operations resume immediately. |
| 85 | + |
| 86 | +After the seven-day tolerance period expires: |
| 87 | + |
| 88 | +- **Service protection**: The service begins deleting individual user storage starting at the oldest (based on the last attach timestamp). The quantity of individual user storage that's deleted is determined by the amount of space that's required for the policy to be under the policy limit. |
| 89 | + |
| 90 | +> [!NOTE] |
| 91 | +> Monitor your storage usage regularly and configure the [Frontline Cloud PC User Experience Sync Storage Limits](/windows-365/enterprise/alerts) alert to avoid reaching the exceeded condition. Consider increasing your storage limit before reaching capacity to ensure uninterrupted user experience. |
| 92 | +
|
| 93 | +## Users experience low or full user storage issues |
| 94 | + |
| 95 | +When individual user storage becomes low or full, users might experience performance issues or be unable to save their work. Use the following solutions to address storage constraints. |
| 96 | + |
| 97 | +- [Free up space in OneDrive](https://support.microsoft.com/office/save-disk-space-with-onedrive-files-on-demand-for-windows-0e6860d3-d9f3-4971-b321-7092438fb38e) |
| 98 | +- Review contents of the Downloads folder and delete files and folders that aren't needed |
| 99 | +- Manually run [Storage Sense](/windows/configuration/storage/storage-sense?tabs=settings) |
| 100 | +- Delete user storage (administrative action) |
| 101 | + |
| 102 | + > [!WARNING] |
| 103 | + > Deleting user storage permanently removes all user data and settings. Before you proceed, make sure that the user backed up important data. |
| 104 | +
|
| 105 | + Administrators can follow these steps to delete user storage by using the Windows 365 management portal: |
| 106 | + |
| 107 | + 1. Sign in to the **Microsoft Intune admin center**. |
| 108 | + 1. Navigate to **Devices** > **Windows 365** > **Provisioning policies**. |
| 109 | + 1. Select the appropriate provisioning policy. |
| 110 | + 1. Go to the **User Storage** tab. |
| 111 | + 1. Locate the user storage to delete. |
| 112 | + 1. Select **Delete** and confirm the action. |
0 commit comments