Skip to content

Commit cc51d0e

Browse files
author
msft-jasonparker
committed
more feedback updates
1 parent 24de689 commit cc51d0e

1 file changed

Lines changed: 9 additions & 56 deletions

File tree

support/windows-365/troubleshoot-user-experience-sync.md

Lines changed: 9 additions & 56 deletions
Original file line numberDiff line numberDiff line change
@@ -17,43 +17,28 @@ ms.collection:
1717

1818
This article provides troubleshooting steps for the most common issues related to User Experience Sync in Windows 365 Frontline shared mode environments.
1919

20-
## Common support scenarios
21-
22-
This section provides detailed information for common support scenarios.
23-
24-
### Users receive a warning about a temporary user experience
20+
## Users receive a warning about a temporary user experience
2521

2622
Users may be signed in with a temporary profile, resulting in a temporary user experience. Users will receive a notification during the sign in process. Windows displays another notification stating, "We can't sign into your account".
2723

2824
> [!NOTE]
2925
>
3026
> A temporary profile is a non-persistent Windows user profile created when the system cannot load or create the user's regular profile. The temporary profile provides basic functionality but any changes made during the session (settings, files, customizations) are discarded when the user signs out. Users will see a notification that they're signed in with a temporary profile, and their desktop and Start menu will appear with default Windows settings rather than their personalized configuration.
3127
32-
<!--:::image type="content" source="media/troubleshoot-user-experience-sync/user-experience-sync-temp-profile-agent.png" alt-text="Figure 1: Temporary user experience warning":::
33-
34-
<sup>**Figure 1:** Temporary user experience warning</sup>
35-
36-
:::image type="content" source="media/troubleshoot-user-experience-sync/user-experience-sync-temp-profile-windows.png" alt-text="Figure 2: Windows can't sign in warning":::
37-
38-
<sup>**Figure 2:** Windows can't sign in warning</sup>-->
39-
40-
#### Individual user storage failed to attach to their session
28+
### Individual user storage failed to attach to their session
4129

4230
During the Windows sign-in process, users follow one of two flows:
4331

4432
- Create and attach new individual user storage
4533
- Attach their existing individual user storage
4634

47-
Both processes require the service to attach a disk to the device while the user is signing in. Attachment failures are uncommon but may occur due to:
48-
49-
- The pooled user storage has exceeded the total allocated size
50-
- Service error
35+
Both processes require the service to attach a disk to the Cloud PC while the user is signing in. Attachment failures are uncommon but may occur when the pooled user storage has exceeded the storage limit.
5136

52-
##### Pooled user storage has exceeded the total allocated size
37+
#### Pooled user storage has exceeded the storage limit
5338

5439
User Experience Sync provides a limited amount pooled user storage based on a storage calculation.
5540

56-
###### Understanding pooled storage limits
41+
##### Understanding pooled storage limits
5742

5843
Each provisioning policy defines a pooled user storage limit calculated using the following formula:
5944

@@ -63,7 +48,7 @@ Each provisioning policy defines a pooled user storage limit calculated using th
6348

6449
<sup>**Figure 1:** Storage calculation of pooled user storage based on Cloud PC size and count</sup>
6550

66-
###### Normal storage consumption
51+
##### Normal storage consumption
6752

6853
Under normal conditions, the pooled user storage is consumed as users create individual user storages. When the storage reaches capacity:
6954

@@ -75,7 +60,7 @@ Under normal conditions, the pooled user storage is consumed as users create ind
7560

7661
<sup>**Figure 2:** Pooled user storage that is at the policy limit</sup>
7762

78-
###### Exceeded storage conditions
63+
##### Exceeded storage conditions
7964

8065
When pooled user storage is *near* capacity and multiple users sign in simultaneously, all users will sign in successfully and create their individual user storage. This results in an **exceeded** condition with the following characteristics:
8166

@@ -87,7 +72,7 @@ When pooled user storage is *near* capacity and multiple users sign in simultane
8772

8873
<sup>**Figure 3:** Pooled user storage that has exceeded the policy limit</sup>
8974

90-
###### Exceeded tolerance period
75+
##### Exceeded tolerance period
9176

9277
When pooled user storage exceeds its limit, the provisioning policy enters a tolerance period to prevent further storage growth. During this period:
9378

@@ -104,14 +89,7 @@ After the 7 day tolerance period expires:
10489
> [!NOTE]
10590
> 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.
10691
107-
#### User Experience Sync service error
108-
109-
The User Experience Sync service is responsible for creating and attaching individual user storage. During a service issue, failure, or outage, users may experience a temporary user experience. In these scenarios, open a support case so our support engineers can:
110-
111-
- Determine where in the process the issue occurred
112-
- Identify if the issue is transient or requires service engineering work
113-
114-
### Resolve low or full user storage issues
92+
## Resolve low or full user storage issues
11593

11694
When individual user storage becomes low or full, users may experience performance issues or be unable to save their work. Use the following solutions to address storage constraints.
11795

@@ -132,31 +110,6 @@ When individual user storage becomes low or full, users may experience performan
132110
5. Locate the user storage to delete.
133111
6. Select **Delete** and confirm the action.
134112

135-
### Recover from accidental deletions
136-
137-
If individual user storage is accidentally deleted, follow these recovery steps.
138-
139-
#### Open a support case
140-
141-
When user experience data is lost due to accidental deletion:
142-
143-
1. **Document the issue**:
144-
- User affected and their user principal name
145-
- Date and time when the data loss occurred
146-
- Specific data or settings that were lost
147-
- Any error messages received
148-
149-
2. **Open a Microsoft support case**:
150-
- Go to the Microsoft 365 admin center
151-
- Navigate to **Support** > **New service request**
152-
- Provide detailed information about the data loss
153-
- Include the Cloud PC serial number or device ID
154-
155-
3. **Gather diagnostic information**:
156-
- Event logs from the affected Cloud PC
157-
- Screenshots of any error messages
158-
- User storage policy configuration details
159-
160113
## Monitoring and current limitations
161114

162115
### User Experience Sync monitoring

0 commit comments

Comments
 (0)