To get 'USB passthrough' in a Hyper-V VM you have two options: Enable Enhanced Session mode on both the VM settings and the Hyper-V Server settings and use the VM Console application (the OS version in the VM is important as the version of the RDP Server service in the VM is important) This works with Server 2012 R2 Hyper-V / 8.1 Connect directly to the RDP server service of the VM - this works on older OSes. And depending on the version of the VM OS, may have driver dependencies for the device. Brian Ehlert Learn. Thank you for your reply Brian. Enhanced Session Mode is already enabled at the Policy and User Levels: I am wondering if I am missing an important driver. The reason that I say that is that after I uninstalled VirtualBox, Hyper-V would work, but the Hyper-V Manager would not open. I could only administer Hyper-V using PowerShell.

• Proxmox Windows Drivers
• Proxmox Default Port

Example Assigning Host USB device to a Guest VM. This example is based on qemu-kvm (0.15.0) as installed in Fedora 15. Will first show how to do this manually, and. Hi guys Any one that can help me with this How to redirect a serial com to a KVM machine on Proxmox. How to redirect a serial. The serial port. Proxmox KVM usb passthrough. Open KVM monitor for your KVM machine in Proxmox GUI or in the command line with the. Port 1, Speed 12 Mb/s Class 00.

Whenever I tried to open the Hyper-V Manager, a DLL error was displayed. I figured that some.NET Framework component was corrupted.

I had to upgrade the OS from Pro to Enterprise to get the Hyper-V Manager to work again. I am thinking that something else is missing which was not picked up during the upgrade. I am trying to avoid performing a Repair Install of the OS. Expand system devices and see if you have the following. The com3 device that is usb would show under com & LPT devices.

The symbol might be under human input devices, just depends on what kind of device it is. Like a bar-code scanner is a keyboard. Do you see them under those area's in your device manager? (USB pass-through requires the device drivers to be installed in the guest.) Also are you trying to use a RS232 serial device only? You can forward COM devices in the hyper-v config from the host machine to guest from the guest VM settings. Just depends on what you need to accomplish.

Thank you for your reply. On the Host, in the Device Manager, Remote Desktop USB Hub is displayed. Is that entry also supposed to be in the Guest? I ask because I don't see it there: This is not a Wedge Scanner which connects to the keyboard. It is a Motorola PDA that also scans barcodes. It has its own cradle which connects to a USB port on the computer.

The drivers for the Symbol USB Cradle are installed with Windows Mobile Device Center. The RS232 Serial Device (COM3) is connected to the same type of scanner. It also would be nice to forward the COM3 to the Guest. Here is what is currently displayed for devices in the Guest.

They have weird rules for Remotefx USB redirection. The biggest thing for Server 2012 USB enhanced session host redirection is that it only applies if the server is setup as a RD Session Host.

So, for testing you could role the feature and use the 120 day trial. If you need it in production you will need a licensing server.

Beautiful tables that make it easy to see. Also I tested this via the enhanced session console in Server 2012 R2 and it indeed only works with the RDSSH role installed.

Hopefully this gets fixed. That is the only thing i like about the VMWARE console.

That is when the redirect works. Most of the time it doesn't work for me in VMWARE either. But that is a VMWARE problem. Correct, but you want to focus on the RemoteFX features on remote computers table.

Notice how the 'Other supported RemoteFx USB device is the selection before you enhance session console into your VM. If you follow that table for USB redirection via the Hyper-V enhanced session it will work. I've tested rolling the Remote desktop Session host role to my 2012 R2 server and it worked without fail. Without that role installed i get the same results as you. If you compare the features between enhanced session and RDP 8.0 they are the same.

Further initially you had to enable RDP in the guest to make it work. The only difference was you would use the vmbus to out of band connect to the VM. So, In theory its glorified RDP via the VMBUS for the network. It would be interesting to get a Hyper-V program managers take on this.

But based on what i can tell this is the only logical way it makes sense. Without remotefx usb redirection it doesn't give you any kind of control to redirect USB. Hi dreisman1, According to the table on Client Computer, when Hyper-V is enabled on Windows 8.1 Enterprise, USB Redirection is supposed to work. I tested in hyper-v 2012R2 host, in hyper-v manager when you connect to your VM the enhanced session mode will prompt for setting it, after I checked 'drives that I plug in later' and 'other supported plug and play devices' then connected the VM I could see the USB disk drive (it seems that it is a share) after I unplugged the usb disk and plugged it again.

Best Regards Elton Ji. Interesting, I wonder if its missing a prereq of some kind that server edition might not have out of box. Is the.net 3.5 feature installed on the server? If not install it and then run WMDC from the start screen manually and then connect the device. If that doesn't work try you could try and add the desktop experience to see what that does. To install the desktop experience in Server 2012 do the following.

Open Server manager Click on Manage then do Add Roles and Features. Next through the wizard until you get to features. In the features list go to user interfaces and infrastructure.

Check the Desktop Experience box and press next then install. Usually this requires a reboot. Once that has been added try WMDC again. I don't understand: 'unplug the usb device from the guest'. The usb device is plugged into the host Operating System. On the Host, in the Device Manager, the Symbol USB Sync is displayed under Mobile Devices and the name of the Portable Device is displayed under that category.

On the Guest, the Mobile Device is displayed but the Portable Device is not. I believe that Windows Mobile Device Center is looking for the Portable Device. Maybe the Portable Device needs to be ported through to the Guest? Sorry for the confusion. From what i mean of 'unplugging the device from the guest' is going to the blue RDP drop down bar in the top middle of your screen and click the removable device icon. From there uncheck the symbol device.

Supposedly other people have had issues with manually installing the WMDC and so the idea is to have the guest install the bits automatically if possible. So, once you have it unplugged from the guest remove WMDC and try a fresh plug in after a reboot and see if windows updates will find the stuff on its own.

To your other question you would want anything associated to be ported over. So if you have extra check boxes for the symbol device in the USB remotefx section add them in. When I unplug the device from the Guest, on the Host, the Application Event Log generates this error: Log Name: Application Source: RapiMgr Date: 8:45:29 AM Event ID: 8 Task Category: None Level: Error Keywords: Classic User: N/A Computer: DTTSW8P64002.us.oneilsoft.com Description: Windows Mobile-based device failed to connect due to communication (0x80072745) failure (see data for failure code). Event Xml: 8 2 0 0x0000 125580 Application DTTSW8P64002.us.oneilsoft.com communication (0x80072745).

Sorry for the long drawn out process on this. The portable device that your seeing is how windows is treating the device. Example of this is the SD card reader, if you put an SD card in and right click the drive you can tell it to mount it as a portable device. This makes it so you can leverage the sync center built into windows to do an import. That being said when it is connected to the guest open up device manager and expand 'universal serial bus controllers' or 'system devices' and watch realtime if it refreshes and add's a device. If it does add a device look at the properties and the hardware ID's and attempt a manual driver update.

I appreciate your patience. As we proceed, we are gaining a better understanding about what is happening, and what needs to happen. Let's just continue to endure. I think I am starting to understand the same point. On the Guest, in the Device Manager, the Portable Device is not appearing.

Also, there are no Universal Serial Bus Controllers. Furthermore, when trying to connect to the Guest, there are no changes to the System Devices. I counted the number of devices before and after making the change. I have 36 devices there.

I'm thinking yes it is an OS problem. I know your doing this through the 'Hyper-V Enhanced Session' Have you attempted remotefxUSB through normal RDP to see if you get similar results?

I have seen a user that once could record audio through the enhanced session but it stopped working, but typical RDP continued to work just fine. So in that scenario something strange with the RDP Hyper-V VMBUS had gotten messed up and treated differently.

Proxmox Windows Drivers

For OS testing I would ask if you by chance do you have a copy of Windows 7 Enterprise handy? For WMDC compatibility that would be the best test to see if it would work, though you would have to do it over normal RDP. If you go that route you will also need to install RDP 8.x and set that local group policy like before for USB. Then from there test Windows 8.1 Enterprise to see what results you get as that one would be similar to 2012 R2. With windows 8.1 you could leverage the Hyper-v enhanced session connection as well.

Thank you for your reply. Our office party got in the way of me realizing that you'd replied. Actually, recently, I have been using RDP. It allows me to plug and unplug the device from the guest. 'Hyper-V Enhanced Session' does not allow for me to plug and unplug the device in the Guest.

Would that be a symptom of a specific problem? I am not sure what you are suggesting in the second paragraph. Currently, the Host OS is Windows 8.1 Enterprise. The Guest OS is Windows Server 2012 R2. I do have a laptop with Window 7 Enterprise installed. I can upgrade the laptop to Windows 8.1 Enterprise, if that is what you are suggesting.

LOL, that party must of been quite the rager:-) Anyways, on the second paragraph I'm thinking you should attempt to install 8.1 enterprise as a guest OS similar to the 2012 R2 server configuration. Trying to rule out client vs. Server operating system differences. If windows 8.1 Enterprise mode works just fine that would show a difference between it and 2012 R2 and something in the server OS must be missing support wise. Then i was saying if you had Windows 7 Enterprise you should try that as well if windows 8 did not work. Just because it was more supported by WMDC than 8. Merry Christmas!

Thanks for asking. Sorry it took so long to reply. I didn't get any email that you'd posted a comment. I just tested Windows 8.1 Enterprise, and USB Pass-through works! Just to let you know, Windows Mobile Device Center sometimes does not connect to the device, but the device is still seen by the Operating System.

Proxmox Default Port

Our application only requires for the Operating System to see the device. I eventually did get Windows Mobile Device Center to connect. Here is what the Device Manager looks like: Now, on to Windows 7.

I wonder if Server 2012 R2 is missing the bits needed for the Media sync stuff. I know the Bluetooth stack is missing though you do not require it. Could you start fresh with a Server 2012 R2 VM to test?

Then install only the.net, desktop experience and RDS terminal session host roles and features? Then after complete enable the USB group policy bits and test it again. Let windows update do the install of the mobile device center as well.

I've seen something else in 2012 R2 not work from MS that was an offline install. Yet the online install worked like a champ. Do the testing with Virtualbox/VMWARE workstation and see what results you get.

I think you should get similar results to Hyper-V/RDP 8.x. From what I can tell something is missing in 2012 R2 that is making the Mobile Device Center not function correctly and or thinking it's corrupt hence the issue after upgrade.The VB/VM testing will help support this idea.Let us know how that testing goes.

If it does indeed work you can possibly get a debugger or a process explorer to see what DLL's possibly didn't load on the Hyper-V setup. Since 8.1 worked I'm thinking it has to be OS related. But, you never know.