Client FAQ

1 post / 0 new
Michael
Client FAQ

VirtualHere Client - Frequently Asked Questions

Can the client be run as a service?

Yes

What are the VirtualHere Client program arguments?

The VirtualHere Client has several command line arguments, described below. To use these in Windows simply call vhui32.exe <argument> or vhui64.exe <argument>, in OSX you need to call the binary directly i.e /Applications/VirtualHere/VirtualHere.app/Contents/MacOS/VirtualHere <argument>. In Linux the binary is called vhuit64, or vhclientx86_64, or similar

-h Command line help

-l=<path> The file to log all messages to (instead of logging to the System Messages window)

-c The configuration file to use instead of the default one.

-a Start the client in Administrator Mode. This allows the client to disconnect other users from devices remotely.

-d Silently install the VirtualHere client drivers and exit. This argument is useful for performing enterprise installation over a network via e.g Microsoft Systems Management Server. Administrator authority is needed when using this argument.

-x Extract the VirtuaHere drivers. This is useful for manually installing the VirtualHere drivers. e.g in Windows XP Embedded

-i Under windows & OSX (Administrator authority is needed when using this argument.) you can install the client as a service then interact with it via the command line

-b Same as the -i argument (above) but install client as service with auto-find off by default, (on windows Bonjour will therefore not be auto-installed by default)

-u Uninstall the client service Administrator authority is needed when using this argument

-y Uninstall all VirtualHere drivers (if any) installed on the system Administrator authority is needed when using this argument

-t Send a command to the running client

-r=<file> When used with the argument t/x/i/u/d, will redirect the output to the file specified after the = argument. This is useful for parsing results in batch files under Windows.

Where are the VirtualHere Client parameters stored?

The Virtualhere Client stores all its parameters in a single text file:

Windows : c:\Users\Username\AppData\Roaming\vhui.ini
OSX : /Users/Username/Library/Preferences/vhui Preferences
Linux: ~/.vhui

This file is updated automatically by the VirtualHere client when it is running and usually does not need to be modified by the end user. The client will generate a default configuration file when it is first started.

Is there a client API?

Yes

How do i setup SSL support on the client

See here for setting up SSL on the client

Can i customize the client menu?

Yes you can hide menu items in the client by:
1. Exiting the client.
2. Editing the file c:\Users\<Username>\AppData\Roaming\vhui.ini (e.g for windows)
3. Under the [General] section add the line HideMenuItems and specify the exact name of the menu items separated by commas, that should be hidden. e.g

[General]
...
HideMenuItems=Specify Hubs...,Install Client as a Service,ServerMenu^Properties,DeviceMenu^Properties
...

Note if the Menu has the same name, it needs to be qualified with either ServerMenu^ or DeviceMenu^

What are the VirtualHere Client Technical Limitations?

The client can connect to any number of VirtualHere USB servers simultaneously (limited only by the client memory). The OSX version of the client will not work with isochronous devices such as speakers,microphones and webcams. The Windows and Linux clients do work with these devices.

Can i use Apple Configurator with VirtualHere to remotely refresh my iPads?

Yes, VirtualHere has been designed to be compatible with Apple Configurator. Before running Apple Configurator right click on the iPad in the Client and select "Auto Connect Port" then run Apple Configurator.

When trying to use the Linux client it says "USBIP client drivers are not available, you will have to compile/install your own from the linux kernel source" ?

Your Linux kernel needs the USB/IP drivers compiled in. If VirtualHere cannot access this driver it will complain. Most versions of Linux have these drivers already compiled in, however some embedded Linuxes and come cloud vendors don't. You would then need to obtain the Linux kernel source then use make menuconfig and select Drivers->USBIP and check those then make the kernel. That will produce vhci_hcd.ko and usbip-common.ko. Copy these to the lib modules directory on your Linux client. then type modprobe vhci_hcd type lsmod | grep vhci to confirm the driver was loaded into the kernel.