FIRST ASK:

  • Have you restarted the physical PC?
  • Is it possible to restart your router/modem?
  • Are other applications working as per usual?
  • Is it possible to try logging in on another PC?
  • Have you tried removing the YubiKey and reinserted it? (GBPO)
  • Have you tried a different adapter for your YubiKey? (GBPO)


Cloud PCs are dedicated, stand-alone, persistent virtual machines. This means that unlike Citrix, each user has their own dedicated VM. They are not sharing it with other users.

Therefore, they are effectively like a physical laptop and can be managed via Intune. They can be rebooted, have changes made such as software installations (though not recommended) etc.


Locating the Cloud PC you need to administer

  1. Navigate to Devices > Device Onboarding > Windows 365 > All Cloud PCs in InTune
  2. From the list select the Cloud PC you need to administer via searching for the device name or user's email address



Restarting a Cloud PC


Users have the ability to restart their own Cloud PC. Either via the start menu, or via the Windows App


But if they need you to do it for them, you can do it remotely via Intune:



Restoring a Cloud PC


Cloud PCs are backed up daily. If a user has an issue and you'd like to restore their PC to a previous day, then you can do this:


Note: The restore process will take about 15 minutes, during which the Cloud PC is inaccessible to the user


Reprovisioing a Cloud PC


If an issue hasn't been resolved by a restore, and you are out of options, then you can reprovision their machine.


IMPORTANT: This is effectively wiping and reloading their VM from scratch. All their customisations will be gone. It's just like giving them a brand-new laptop.



Common Errors for Cloud PC


Error: "Protocol error (code: 0x112f) the remote session will be disconnected. Please try connecting to remote computer again."
This happens due to resolution conflict between monitor and RDP client.

Solution: disconnecting the laptop from the dock, opening cloud pc, then connecting to the dock resolved this for a user. 
Alternative solution suggested is to disable the option "Use all my monitors for the remote session" on the Display tab of the client settings.




Error: "We couldn't connect because there are a currently no resources. Try again later or contact tech support for help if this keeps happening"



Solution: Restart Cloud PC. If still doesn't work. Restart Cloud PC again.