From 5709b58045c1298cf2c95ee7d1f49acb219a1dbf Mon Sep 17 00:00:00 2001 From: Kevin Deamandel Date: Sun, 28 Jul 2024 14:55:53 +0200 Subject: [PATCH 1/2] Update troubleshoot-windows-365-boot.md added an additional troubleshooting step - when user has multiple cloud pcs and has no default cloud pc set "something went wrong" will be also displayed on login --- .../enterprise/troubleshoot-windows-365-boot.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/windows-365/enterprise/troubleshoot-windows-365-boot.md b/windows-365/enterprise/troubleshoot-windows-365-boot.md index 190ad92c96d..bcc46c462f4 100644 --- a/windows-365/enterprise/troubleshoot-windows-365-boot.md +++ b/windows-365/enterprise/troubleshoot-windows-365-boot.md @@ -40,8 +40,14 @@ If the user can't access the Cloud PC from the Windows 365 Boot physical device, 1. Check to see if you can sign in to the Cloud PC from either: - The browser at windows365.microsoft.com. - The Windows 365 app on another (non-Windows 365 Boot) device. -2. If you can log into the Cloud PC from either method, then there's an issue with the Windows 365 Boot physical device. In this case, confirm that the physical device is correctly configured and has the requisite software versions. For more information, see [Windows 365 Boot physical device requirements](windows-365-boot-physical-device-requirements.md). -3. Admins can try to manually click on **Device sync** to get the policies delivered faster on the device. Users can try to restart the device. +2. If a user has more than one Cloud PC, make sure they have selected a default Cloud PC to use each time they sign in. To set this default: + - Navigate to https://windows365.microsoft.com. + - In the card for the Cloud PC you want to set as default, select the ellipses (...) > Settings. + -In the Integrated experiences tab, under Boot to this Cloud PC, select Connect while signed into device. + -Select Update. +3. If you can log into the Cloud PC from either method, and a default cloud PC has been set then there's an issue with the Windows 365 Boot physical device. In this case, confirm that the physical device is correctly configured and has the requisite software versions. For more information, see [Windows 365 Boot physical device requirements](windows-365-boot-physical-device-requirements.md). +4. Admins can try to manually click on **Device sync** to get the policies delivered faster on the device. Users can try to restart the device. + ## Physical device registry key configuration From 3b4822455ebbdcb363ee7d8bf989ff51c3f88f4b Mon Sep 17 00:00:00 2001 From: Erik Kjerland Date: Mon, 16 Sep 2024 10:22:49 -0700 Subject: [PATCH 2/2] Update troubleshoot-windows-365-boot.md --- windows-365/enterprise/troubleshoot-windows-365-boot.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/windows-365/enterprise/troubleshoot-windows-365-boot.md b/windows-365/enterprise/troubleshoot-windows-365-boot.md index bcc46c462f4..f405eac5ab6 100644 --- a/windows-365/enterprise/troubleshoot-windows-365-boot.md +++ b/windows-365/enterprise/troubleshoot-windows-365-boot.md @@ -43,9 +43,9 @@ If the user can't access the Cloud PC from the Windows 365 Boot physical device, 2. If a user has more than one Cloud PC, make sure they have selected a default Cloud PC to use each time they sign in. To set this default: - Navigate to https://windows365.microsoft.com. - In the card for the Cloud PC you want to set as default, select the ellipses (...) > Settings. - -In the Integrated experiences tab, under Boot to this Cloud PC, select Connect while signed into device. - -Select Update. -3. If you can log into the Cloud PC from either method, and a default cloud PC has been set then there's an issue with the Windows 365 Boot physical device. In this case, confirm that the physical device is correctly configured and has the requisite software versions. For more information, see [Windows 365 Boot physical device requirements](windows-365-boot-physical-device-requirements.md). + - In the **Integrated experiences** tab, under **Boot to this Cloud PC**, select **Connect while signed into device**. + - Select **Save**. +3. If you can sign into the Cloud PC from the app or web, and a default Cloud PC has been set, then there's an issue with the Windows 365 Boot physical device. In this case, confirm that the physical device is correctly configured and has the requisite software versions. For more information, see [Windows 365 Boot physical device requirements](windows-365-boot-physical-device-requirements.md). 4. Admins can try to manually click on **Device sync** to get the policies delivered faster on the device. Users can try to restart the device.