Merge pull request #291691 from RoseHJM/mdb-troubleshooting-appendix

MDB - troubleshooting appendix

Author: Jill Grant

articles/dev-box/how-to-connect-dev-box-virtual-switch.md

@@ -0,0 +1,68 @@
+---  
+title: Configure virtual switches for dev boxes
+description: Learn to configure virtual switches for dev boxes, enabling communication between dev boxes, VMs, and physical devices.
+author: RoseHJM
+ms.author: rosemalcolm
+ms.service: dev-box
+ms.topic: how-to
+ms.date: 12/05/2024
+
+#customer intent: As a developer, I want to learn how to connect to a Dev Box using a virtual switch, so that my dev boxes, VMs, and physical devices can communicate.
+---
+
+# Configure virtual switches for dev boxes
+
+This article provides guidance on how to set up and use dev box with virtual switches. Virtual switches are used to connect dev boxes and other virtual machines (VMs) to both virtual networks and physical networks. They provide a way for dev boxes to communicate with each other and with external networks. 
+
+Dev box supports nested virtualization. You can create virtual machines inside a dev box and connect them to the default virtual switch *Default Switch*. If you want to create another virtual switch with internet access, set up a NAT network with an internal virtual switch. Use an IP address range that suits your required configuration.
+
+> [!WARNING]
+> Incorrect configuration of virtual switch will cause you to lose the connection to dev box immediately and this is NOT reversable. Please setup with extreme care.
+
+## Prerequisites
+- A dev box with Hyper-V and Virtual Machine Platform installed.
+
+## Create virtual switch with NAT network 
+
+Create a virtual switch with a NAT network to enable internet access for your dev box and its guest VMs.
+    
+1. Create internal virtual switch:
+    ```powershell
+    New-VMSwitch -SwitchName "VM-Internal" -SwitchType Internal
+    ```
+
+1. Create an IP address for the NAT gateway
+    ```powershell
+    New-NetIPAddress -IPAddress 192.168.100.1 -PrefixLength 24 -InterfaceIndex 34
+    ```
+
+    To find the *InterfaceIndex*, run `Get-NetAdapter`. Use the *ifIndex* of the adapter linked to the VM-Internal switch. If you choose a different IP range, ensure the IP address ends with “.1”.
+
+1. Create the NAT network
+    ```powershell
+    New-NetNat -Name VM-Internal-Nat -InternalIPInterfaceAddressPrefix 192.168.100.0/24
+    ```
+
+## Configure guest VMs
+
+Configure guest virtual machines (VMs) to use the virtual switch.
+
+1. Create guest virtual machines (VMs) in your dev box, using the *VM-Internal* virtual switch. At this stage, the guest VM doesn't have internet access because it doesn't have an IP address.
+
+1. Assign IP addresses to the guest VM. 
+
+   1. On the guest VM, set the IP address to an available address in the range, like 192.168.100.10, 192.168.100.11, etc. 
+   1. Use the subnet mask 255.255.255.0, default gateway 192.168.100.1, and your desired DNS (for example, 8.8.8.8 for internet or your dev box's DNS). 
+   1. Open Network Connections, right-click the network adapter, select **Properties** > **Internet Protocol Version 4 (TCP/IPv4)**.
+
+     :::image type="content" source="media/how-to-connect-devices-to-dev-box/tcpip-config.png" alt-text="Screenshot that shows the TCP/IP version 4 configuration dialog.":::
+
+After setting the IP address, the setup is complete. Verify that you have:
+
+- Internet access from the guest VM.
+- Access between guest VMs.
+- Access to guest VMs from the dev box.
+
+## Related content
+
+- [Microsoft Dev Box: Frequently asked questions](dev-box-faq.yml)

articles/dev-box/how-to-connect-devices-to-dev-box.md

@@ -0,0 +1,82 @@
+---  
+title: How to connect Android devices to a dev box
+description: Learn how to connect Android devices to a dev box for efficient testing and debugging, enhancing your app development workflow and productivity.
+author: RoseHJM
+ms.author: rosemalcolm
+ms.service: dev-box
+ms.topic: how-to
+ms.date: 12/11/2024
+
+#customer intent: As a developer, I want to connect Android devices to my dev box so that I can develop apps for Android.
+
+---
+
+# Connect Android devices to a dev box
+
+Connecting Android devices to a dev box enhances your app development process by allowing you to test and debug directly on physical devices. This article provides step-by-step instructions to help you connect your Android devices to a dev box, streamlining your development workflow.
+
+## Prerequisites
+
+- Access to a dev box
+- A client computer to connect to the dev box from
+
+## Prepare your client computer
+
+To connect Android devices to your dev box, you first connect the devices to client computer you use to connect to the dev box.
+
+### Connect Android devices
+
+Connect your Android device to the client computer you'll use to connect to your dev box.
+
+1. To open Device Manager, from the search box on the taskbar, run `devmgmt.msc`.
+1. Check that your device displays like one of the following options:
+    - Device name: Universal Serial Bus / Pixel 6
+    - Android Device / Android Composite Android Debug Bridge (ADB) Interface
+1. Uninstall nonstandard devices and drivers and restart your computer.
+1. In Device manager, verify your Android device displays.
+
+> [!CAUTION]
+> Some devices like Samsung might not connect if the ADB interface device exists on the computer you connect from. To resolve this issue, uninstall the device.
+
+### Configure USB redirection
+
+Configure following Local Group Policy settings to allow USB redirection on your client computer. 
+
+1. To open Local Group Policy Editor, from a cmd window, run `gpedit.msc`.
+1. Navigate to **Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Connection Client\RemoteFX USB Redirection**.
+1. Enable **Allow RDP redirection of other supported RemoteFX USB devices from this computer** for **Administrators and Users**.
+1. To apply the policy changes, from a cmd window, run `gpupdate /force`.
+1. Restart your computer.
+
+## Prepare your dev box
+
+When your Android devices are connected to your client computer, you can configure your dev box to access them by enabling USB redirection.
+
+### Configure USB redirection
+
+Configure following Local Group Policy settings to allow USB redirection on your dev box. 
+
+1. To open Local Group Policy Editor, from a cmd window, run `gpedit.msc`.
+1. Open **Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Device and Resource Redirection**.
+1. Set **Do not allow supported Plug and Play device redirection** to **Disabled**.
+1. Navigate to **Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Connection Client\RemoteFX USB Device Redirection**.
+1. Enable **Allow RDP redirection of other supported RemoteFX USB devices from this computer** for **Administrators and Users**.
+1. To apply the policy changes, from a cmd window, run `gpupdate /force`.
+1. Restart your computer.
+
+## Troubleshoot ADB Connection Issues
+
+If the Android device isn't accessible to ADB, check the latest device drivers are installed and the device displays in Device Manager. 
+
+Perform the following steps on your dev box:
+
+1. To open Device Manager, from the search box on the taskbar, run `devmgmt.msc`.
+1. Ensure the Google USB driver is installed and the device appears as [**Android Device \ Android Composite ADB Interface**](https://developer.android.com/studio/run/win-usb). 
+    - Devices from other manufacturers might not display in Device manager. 
+    - If your device is from another manufacturer, check [Install a USB driver](https://developer.android.com/studio/run/oem-usb#InstallingDriver) for manufacturer specific drivers. The goal is to make the ADB interface device show up in Device Manager. 
+    - The device name can vary from manufacturer to manufacturer, such as "Samsung Android Phone \ Samsung Android ADB Interface" or "Android Device \ Android Composite ADB Interface".  
+1. Restart your computer. 
+
+## Related content
+
+- [Microsoft Dev Box: Frequently asked questions](dev-box-faq.yml)

articles/dev-box/media/how-to-connect-devices-to-dev-box/automatic-drive-redirection.png

@@ -121,6 +121,20 @@ items:
     href: how-to-configure-stop-on-disconnect.md
   - name: Skip or delay an automatic shutdown
     href: how-to-skip-delay-stop.md
+- name: Connect devices to dev boxes
+  items:
+  - name: Connect physical devices to a dev box
+    displayName: USB, devices, connect, physical, peripherals, android
+    href: how-to-connect-devices-to-dev-box.md
+  - name: Configure virtual switch
+    displayName: connect, devices, switch
+    href: how-to-connect-dev-box-virtual-switch.md
+  - name: Drives and storage
+    displayName: drives, storage, connect, physical, peripherals, android, switch
+    href: /azure/virtual-desktop/redirection-configure-drives-storage?tabs=group-policy&pivots=dev-box
+  - name: USB redirection
+    displayName: USB, devices, connect, physical, peripherals, android, switch
+    href: /azure/virtual-desktop/redirection-configure-usb?tabs=intune&pivots=dev-box
 - name: Troubleshooting
   items: 
   - name: Automatically repair connectivity issues