Merge pull request #284624 from dknappettmsft/avd-usb-redirection-clarify

AVD redirection USB clarity changes

Author: PMEds28

articles/virtual-desktop/TOC.yml

@@ -231,7 +231,7 @@
       - name: Uniform Resource Identifier schemes
         displayName: uri schemes
         href: uri-scheme.md
-    - name: Redirect peripherals and resources
+    - name: Peripheral and resource redirection
       displayName: devices, microphone, audio, usb, drives, clipboard, printers, scanners, cameras, webcams, smart cards, smartcards, webauthn, location, plug and play, mtp, ptp, serial, com, ports,
       href: redirection-remote-desktop-protocol.md
     - name: Multimedia redirection

articles/virtual-desktop/redirection-configure-usb.md

@@ -511,7 +511,7 @@ The `usbdevicestoredirect` RDP property is used to specify which USB devices are
 |:--:|:--:|--|
 | N/A | *No value specified* | Don't redirect any supported USB peripherals using opaque low-level redirection. |
 | 1 | `*` | Redirect all peripherals that aren't using high-level redirection. |
-| 2 | `{<DeviceClassGUID>}` | Redirect all peripherals that are members of the specified device setup class. |
+| 2 | `{<DeviceClassGUID>}` | Redirect all peripherals that are members of the specified device setup class. For a list of device class GUID values, see [System-Defined Device Setup Classes Available to Vendors](/windows-hardware/drivers/install/system-defined-device-setup-classes-available-to-vendors). |
 | 3 | `<USBInstanceID>` | Redirect a USB peripheral specified by the given device instance path. |
 | 4 | `<-USBInstanceID>` | Don't redirect a peripheral specified by the given device instance path. |
 
@@ -529,13 +529,13 @@ Here are some examples of using the `usbdevicestoredirect` RDP property:
    usbdevicestoredirect:s:*
    ```
 
-- To redirect all supported USB peripherals with a device class GUID of `{6bdd1fc6-810f-11d0-bec7-08002be2092f}`, use:
+- To redirect all supported USB peripherals with a device class GUID of `{6bdd1fc6-810f-11d0-bec7-08002be2092f}` (imaging), use:
 
    ```uri
    usbdevicestoredirect:s:{6bdd1fc6-810f-11d0-bec7-08002be2092f}
    ```
 
-- To redirect all supported USB peripherals that high-level redirection doesn't redirect and USB peripherals with a device class GUIDs of `{6bdd1fc6-810f-11d0-bec7-08002be2092f}` and `{4d36e96c-e325-11ce-bfc1-08002be10318}`, use:
+- To redirect all supported USB peripherals that high-level redirection doesn't redirect and USB peripherals with a device class GUIDs of `{6bdd1fc6-810f-11d0-bec7-08002be2092f}` (imaging) and `{4d36e96c-e325-11ce-bfc1-08002be10318}` (multimedia), use:
 
    ```uri
    usbdevicestoredirect:s:*;{6bdd1fc6-810f-11d0-bec7-08002be2092f};{4d36e96c-e325-11ce-bfc1-08002be10318}
@@ -555,7 +555,7 @@ Here are some examples of using the `usbdevicestoredirect` RDP property:
 
 - Use the following syntax to achieve the following scenario:
    - Redirect all supported USB peripherals that high-level redirection doesn't redirect.
-   - Redirect all supported USB peripherals with a device setup class GUID of `{6bdd1fc6-810f-11d0-bec7-08002be2092f}`.
+   - Redirect all supported USB peripherals with a device setup class GUID of `{6bdd1fc6-810f-11d0-bec7-08002be2092f}` (imaging).
    - Redirect a supported a USB peripheral with instance ID `USB\VID_095D&PID_9208\5&23639F31&0&2`.
    - Don't redirect a supported USB peripheral with an instance ID of `USB\VID_045E&PID_076F\5&14D1A39&0&7`.
 

articles/virtual-desktop/redirection-remote-desktop-protocol.md

@@ -1,13 +1,13 @@
 ---
-title: Redirection over the Remote Desktop Protocol
-description: Learn about redirection over the Remote Desktop Protocol, which enables users to share resources between their local device and a remote session. It applies to Azure Virtual Desktop, Windows 365, Microsoft Dev Box, Remote Desktop Services, and Remote PC connections.
+title: Peripheral and resource redirection over the Remote Desktop Protocol
+description: Learn about redirection over the Remote Desktop Protocol, which enables users to share peripherals and resources between their local device and a remote session. It applies to Azure Virtual Desktop, Windows 365, Microsoft Dev Box, Remote Desktop Services, and Remote PC connections.
 ms.topic: concept-article
 author: dknappettmsft
 ms.author: daknappe
 ms.date: 08/06/2024
 ---
 
-# Redirection over the Remote Desktop Protocol
+# Peripheral and resource redirection over the Remote Desktop Protocol
 
 Redirection enables users to share resources and peripherals, such as the clipboard, webcams, USB devices, printers, and more, between their local device (client-side) and a remote session (server-side) over the *Remote Desktop Protocol* (RDP). Redirection aims to provide a seamless remote experience, comparable to the experience using their local device. This experience helps users be more productive and efficient when working remotely. As an administrator, you can configure redirection to help balance between your security requirements and the needs of your users.
 
@@ -48,7 +48,7 @@ The following table compares redirecting a USB peripheral using opaque low-level
 |--|--|
 | Requires the driver for the USB peripheral to be installed in the remote session. Doesn't require the driver to be installed on the local device. | Requires the driver for the peripheral to be installed on the local device. In most cases, it doesn't require the driver to be installed in the remote session. |
 | Uses a single redirection method for many peripheral classes. | Uses a specific redirection method for each peripheral class. |
-| Forwards URB to and from the USB peripheral over the RDP connection. | Exposes high-level peripheral functionality in a remote session by using an optimized protocol for the peripheral class. |
+| Forwards USB request blocks to and from the USB peripheral over the RDP connection. | Exposes high-level peripheral functionality in a remote session by using an optimized protocol for the peripheral class. |
 | The USB peripheral can't be used on the local device while it's being used in a remote session. It can only be used in one remote session at a time. | The peripheral can be used simultaneously on the local device and in a remote session. |
 | Optimized for low latency connections. Variable based on peripheral driver implementation. | Optimized for LAN and WAN connections and is aware of changes in conditions, such as bandwidth and latency. |