Skip to content

Commit a1c4603

Browse files
author
msft-jasonparker
committed
deleted frontline known issue doc and merged back to enterprise
updated the toc
1 parent cc51d0e commit a1c4603

3 files changed

Lines changed: 71 additions & 78 deletions

File tree

support/windows-365/known-issues-enterprise.md

Lines changed: 71 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,8 @@ ms.collection:
1212
- M365-identity-device-management
1313
- tier2
1414
---
15-
# Known issues: Windows 365 Enterprise
15+
16+
# Known issues: Windows 365 Enterprise and Frontline
1617

1718
The following items are known issues for Windows 365 Enterprise.
1819

@@ -268,6 +269,74 @@ For newly provisioned Cloud PCs, verify that WebRTC is available. If it's not, y
268269
269270
- To add the WebRTC Redirector Service app to an individual Cloud PC, follow the steps in [Install the Remote Desktop WebRTC Redirector Service](/azure/virtual-desktop/teams-on-avd#install-the-remote-desktop-webrtc-redirector-service). To get the most up-to-date installer, use this link: [https://aka.ms/msrdcwebrtcsvc/msi](https://aka.ms/msrdcwebrtcsvc/msi).
270271
272+
## Windows 365 Frontline issues
273+
274+
The following are issues for Windows 365 Frontline:
275+
276+
### Users can't access Frontline Cloud PCs in shared mode
277+
278+
When Frontline Cloud PCs in shared mode are assigned to a Microsoft Entra ID group with more than 10,000 members, some users might not receive access and won't see the Cloud PC cards in the Windows app client.
279+
280+
#### Solution
281+
282+
Reduce the Microsoft Entra ID group membership to fewer than 10,000 users.
283+
284+
### Can't decrease Cloud PC count when all Cloud PCs fail provisioning
285+
286+
If provisioning fails due to a Windows Autopilot Device Preparation Profile (DPP) failure and all Cloud PCs show no successfully provisioned devices, administrators can't decrease the number of Cloud PCs in the assignment configuration.
287+
288+
#### Solution
289+
290+
Perform a reprovisioning action in the provisioning policy:
291+
292+
1. Navigate to **Microsoft Intune admin center** > **Devices** > **Windows 365**
293+
2. Select **Provisioning policies**
294+
3. Choose the affected provisioning policy
295+
4. Select **Reprovision** to reset the deployment state
296+
5. After reprovisioning completes, you can adjust the Cloud PC count as needed
297+
298+
### Scheduled reprovisioning doesn't recover after license changes
299+
300+
When Frontline Cloud PCs are provisioned in shared mode and licenses expire or are removed from the tenant, the Cloud PCs are deprovisioned until valid licenses are restored. After licenses are added back, Cloud PCs provision according to the policy configurations, but both scheduled reprovisioning and manual reprovisioning functionality remain disabled.
301+
302+
#### Solution
303+
304+
To restore full reprovisioning functionality after license expiration:
305+
306+
1. **Remove the provisioning policy assignment:**
307+
- Navigate to the affected provisioning policy
308+
- Go to the **Assignments** tab
309+
- Remove all group assignments
310+
311+
2. **Re-add the assignment:**
312+
- Wait 5-10 minutes for the removal to process
313+
- Add the group assignments back to the policy
314+
- Verify that reprovisioning options are now available
315+
316+
### Can't decrease Cloud PC count due to pooled user storage limits
317+
318+
The number of Cloud PCs for Frontline Cloud PCs in shared mode can't be decreased when it would cause the pooled user storage limit to be exceeded.
319+
320+
#### Solution
321+
322+
Delete individual user storage to be under the new limit. The new limit can be determined by multiplying the new Cloud PC count by the OS disk size in GB.
323+
324+
### Autopilot Device Preparation (DPP) initially shows as failed if timeout limit is reached
325+
326+
Once you create the provisioning policy and you receive the error code `DevicePreparationProfileTimeout`, then the time-out limit has been reached and the Cloud PCs are provisioned without applying the Autopilot Device Preparation successfully.
327+
328+
#### Solution
329+
330+
Continue to wait as the Autopilot Device Preparation will continue to install in the background after the initial timeout period.
331+
332+
### Cloud PC serial numbers don't show immediately in Windows Autopilot Device Preparation deployment status
333+
334+
When monitoring the status of the Autopilot Device Preparation profile immediately after provisioning, the Cloud PC serial numbers are not available.
335+
336+
#### Solution
337+
338+
Cloud PC serial numbers can take up to 30 minutes.
339+
271340
## Next steps
272341
273-
[Troubleshoot Windows 365 Enterprise Cloud PC](/windows-365/enterprise/troubleshooting)
342+
[Troubleshoot Windows 365 Enterprise Cloud PC](/windows-365/enterprise/troubleshooting)

support/windows-365/known-issues-frontline.md

Lines changed: 0 additions & 70 deletions
This file was deleted.

support/windows-365/toc.yml

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -75,9 +75,3 @@ items:
7575
items:
7676
- name: Windows 365 BCDR known issues
7777
href: windows-365-bcdr-known-issues.md
78-
- name: Windows 365 Frontline
79-
items:
80-
- name: Known issues with Windows 365 Frontline
81-
href: known-issues-frontline.md
82-
- name: Troubleshoot User Experience Sync
83-
href: troubleshoot-user-experience-sync.md

0 commit comments

Comments
 (0)