run -t commands in silent mode?

I am writing a powershell script based upon the 2.9.2 client version. The USB devices that we attach are WiFi adapters (over 240 connected to multiple VH servers in a classroom/lab environment). Because of the nature of the WiFi adapters, there are frequent times where even though there is a VH client-server connection established, the Windows client does not actually see any WiFi networks. I don't know if there is an issue with the WiFi client, or with VirtualHere. Either way, I can restore this WiFI visibility by restarting the vhclient service and then reconnecting the client to the server.

To make life simpler for the student, I created a powershell exe script on the client desktop that when clicked on restarts the service and then reconnects. But when it executes the two vh cli commands, it generates Pop Ups requiring the student acknowledge them. This is ok as a quick workaround, but I would like to have a switch that would suppress these popups because it is easy for a student to not see them and prevent the script from completing.

Specifically, the two commands that I currently use that create these pop ups are:

vhui64.exe -t "manual add hub"
vhui64.exe -t "auto use port"

I understand that there may be cases where explicitly confirming the command executed is desired, but in my case it is a lab environment hinderance, particularly due to the frequency that this needs to be performed.

Or maybe there is a better way to do this?



Hi Kevin,

You can just redirect output from the -t command to a file with the -r argument that will ensure there are no popups.

e.g vhui64-exe -t "manual add hub," -r "dummy.out"

So just use the -r argument all the time with the -t argument and that will solve your issue.

If the network goes down and up all the time, the client should re-find the server after around 15 seconds. I assume you are using ip addresses specified in the client via the manual add hub option. You can take a look in Windows - Event Viewer and it will show messages in there from the virtualhere client about what is going on.

In reply to by Michael


I should have realized that the -r flag would work with this command too. Took care of the issue, thanks for the response.