Support

Running server on a pi3, client on Windows 10 64bit. Recently stopped working seems like after a MS update. the client connects and shows the connection, but I cannot use the usb ports on the pi or Windows doesn't recognize them. Here is the logs:
2020-11-15 17:53:31 INFO :VirtualHere Client 5.1.1 starting (Compiled: Nov 14 2020 20:33:06)
2020-11-15 17:53:31 INFO :Client OS is Windows 10 (build 19041), 64-bit edition
2020-11-15 17:53:31 INFO :Using config at C:\Users\weirp\AppData\Roaming\vhui.ini
2020-11-15 17:53:31 INFO :IPC available at \\.\pipe\vhclient

I've got a windows server with a license and a linux client where the can be run manually using the -n option and everything works fine. What i'd like to do now is setup the linux server so that i don't have to ssh in and start the client each time it needs to be rebooted. To do that it needs to be installed as a daemon which is a supported configuration and there's a near guide about it at https://virtualhere.com/client_service but i can't work out what to do with the script provided.

is it possible to access one usb port by two users at the same time, e.g. insert a flash drive and make it available for clients who can use it by two users, now when the device is used by the first user, the second user receives information that the port is busy and can't use it

We have a large number of raspberry pi's setup as thin clients for end users to use to connect to terminal servers. The users need to be able to use a webcam and Mic (USB) and join meetings. I'm able to get the webcam to work with VirtualHere but the mic (built in to the webcam) only shows up on my admin profile on the terminal server, the end users are not able to see the microphone device at all on any profile. When I was testing VirtualHere I did the initial test under my profile so all the drives installed under my admin profile.

I'm on the edge of buying one or more licenses, so started with downloading the USB server for Raspberry, and that works fine with my Windows client.
However I also wanted to use some USB devices on Debian 10.6.0, but the vhclientarmhf does not start and gives an error;

This is a connection between a Synology DS1819+ (DSM 6.2.3-25426 Update 2) and a Win10 machine. This happened prior to updating to the new vhui64 client and then again after updating to the client. Note: The program IS still running on the Synology, and the USB devices ARE still able to connect to the Win10 machine with client. Thx

System Messages info (removed repeating lines...):

Hi,
I have set steam link on my raspberry pi 3+ on two installations and bought virtual here on steam:
1) standalone steamlink on raspbian, here virtualhere connects to PC client, but it crashes immediately after stream starts and steamlink then restarts
2) libreelec 9.2.4 kodi 18, where there is no crash, but VH client is not showing any connections (message connect to USB hub...)

I bought a license a while ago but reset my device. Now when I enter the license on the client or the server, the application does nothing and says my license has expired.

Hi there,

I can not install virtualhere for DSM 7.0.

Here is the result:

https://help.synology.com/developer-guide/privilege/preface.html

Thank you.

Hi Michael,
VH has been working nicely for a couple weeks, all of a sudden (POSSIBLY after QNAP firmware update?), the connected devices are not being found. I was using a Belkin F5U234 4-port hub, but even connected direct to unit, they're not visible.
Is there some command I can SSH into my NAS to see what devices it's seeing? At this point I can't tell if it's a NAS problem or VH.

Also, the client app never starts minimised, even though the option is enabled. (Win 8.1x64)

All the best,
Dax.