Connectivity health checks and history reports for Windows 365 Cloud PCs

[Guest Abraham_Pineda]

Connectivity health checks and connectivity history reports are new features that will help you mitigate connectivity issues users may experience with their Cloud PCs.

 

Connectivity health checks are run against individual Cloud PCs and tell you whether a Cloud PC is in a healthy and connectable state. These checks can be accessed through the new Performance (preview) tab under the device overview blade. If any of these checks fail, the user won't be able to connect to their Cloud PC.

 

Additionally, you are able to see a user's connectivity history to determine whether a device failed a connectivity check or experienced a connectivity error in the last 14 days. Connectivity health checks are continually run by the Windows 365 service on the back end, and they help ensure that the Cloud PC is ready for connection. Connectivity errors are the result of unexpected network failures or other conditions that might cause a connection to a Cloud PC to drop—for example, interruption in internet service by an internet service provider (ISP).

 

Connectivity errors can occur even when all connectivity health checks have successfully passed.

 

 

Connectivity health checks

 

 

When a connectivity check fails, you'll see one of the health check names shown below. Review the status pane to see more details. Select Troubleshoot this connection to troubleshoot.

 

 

Health check name	Description
DomainJoin	Checks that the Cloud PC is domain joined. When it fails, the Cloud PC isn't joined to a domain. Run the troubleshooter to rejoin it to the domain. If the problem continues, contact Microsoft Support.
DomainReachable	Checks that the Cloud PC can reach the domain. When it fails, this Cloud PC can't connect to the domain. To check for an issue with your virtual network configuration, review your Azure Network Checks (ANC). If the problem continues, contact Microsoft Support.
DomainTrust	Checks that the Cloud PC is trusted by the domain. When it fails, the domain doesn't trust this Cloud PC. Make sure the local device password matches the device password in the domain. If the passwords match and the problem continues, contact Microsoft Support.
SxSStackListener	Checks that the side-by-side stack listener is working properly in the Cloud PC. When it fails, the side-by-side stack installed on the Cloud PC is malfunctioning or blocked. Run the troubleshooting tool to fix this issue.
UrlsAccesible	Checks that all necessary URLs are reachable by the Cloud PC. When it fails, the Cloud PC is blocking traffic to these URLs. Unblock the URLs this Cloud PC uses to connect to Windows 365.
Unknown	This device might not be running or the network isn't connected to the public internet. Try to run the troubleshooting tool for more information.

User connectivity history report

 

 

The user connectivity history report shows when a user started and finished a connection. There are different ways a connection can start and finish, and these are logged as activities in the report. The report shows the following activities:

 

 

The connectivity history report provides visibility of other activities within a one-hour period of a connectivity error or failed check. For example, if a user attempts to connect to their Cloud PC, and is unable to, the health checks and successful sign-in activity within one hour before or after the error will also show. This allows you to evaluate an error, its possible cause, and if/when the system became healthy again. If the user is able to reconnect to their Cloud PC, the admin can still see if the user experiences many disconnects within a 14-day period. This helps narrow down the root cause of the connection failure and is especially useful if a ticket needs to be opened with Microsoft Support.

 

 

Continue reading...