Editar

Partilhar via

Cloud PC connection quality report

  • Artigo

The Connection quality report helps Windows 365 administrators identify devices that might be performing below expectations. Connection quality is a subjective concept with many variables defining what is acceptable in any given circumstance. Admins should use the objective data provided by this report, feed it into their own subjective performance criteria, to determine their organization's policies and remediations.

Use the Cloud PC connection quality report

To get to the Cloud PC connection quality report, sign in to Microsoft Intune admin center, select Reports > Cloud PC overview > Connection quality.

Screenshot of getting to the Cloud PC connection quality report

The device list shows the individual Cloud PCs with the following columns:

  • Device name
  • Round Trip Time for the most recent (or current) connection (RTT): The number of milliseconds it takes, at the transport layer only, for communication between the client and the Cloud PC. Lower values indicate better round-trip connectivity.
  • Round Trip Time for the specified date range (P50)
  • Available bandwidth for the most recent (or current) connection
  • Available bandwidth for the specified date range (P50): network bandwidth observed during sessions with the specified CPC sample set.
  • Connection gateway
  • Remoting sign-in time (P50): The number of seconds it took the user to complete the sign-in process.
  • Client IP address
  • Protocol for most recent (or current) connection
  • UDP Utilization average over date range
  • Device type: The type of Cloud PC based on the offering (Enterprise, Frontline dedicated, Frontline shared).

Each row in the report gives links to the specific Cloud PC where you can find greater detail regarding the devices connection history and related performance.

You can use the Columns and Add filter options to customize the report:

  • Choose which columns are displayed.
  • Filter the range for each column.
  • Choose the date range (7 days or 28 days).

You can use these filters to identify connections that don't meet your organization's requirements. Then, you can evaluate potential causes, like:

  • Network, host, or client configurations that limit protocol choice.
  • Geographic distance.
  • Authentication methods and architecture.
  • Appropriateness of the client or host.

Next steps

Remoting connection report