You can control more than 20 screens installed on your network
Simply by adding more virtual machines, you can connect any number of screens on your network!
You can control more than 20 screens installed on your network
Simply by adding more virtual machines, you can connect any number of screens on your network!
Security
When using a physical PC, you can’t use the operating system’s capability to lock up the system and you need to use a workaround to lock the workstation. With a virtual machine, the main server can be locked up while the VM keeps on running in the background.
Better stability
With virtual machines there are almost no hardware incompatibilities so fewer issues can occur. Also, a clone machine can be easily created to enable a quick redundancy of the system.
Flexible
If you would like to have 5 screens controlled by one employee in your company and another set of 5 screens controlled by a different employee, it’s very easy to implement. Simply divide the screens into two virtual machines and give each employee an access to his private VM.
Operating systems
Currently the guest virtual machines can be installed only with the following operating systems:
Windows8.1, Windows10/11 or Windows Server 2012 R2, Server 2016, Server 2019
Supported Hypervisors
Our solution can be implemented on VMWARE’s platform, Microsoft’s Hyper-V, Parallels and Oracle’s VirtualBox.
System resources for the guest virtual machine
Planning the system resources assigned to the guest virtual machine is an essential step and we advise that you make use of our System Configuration Guide.
The recommend resources is related to :
– Number of screens that you connect.
– Type of content.
Minimum requirements:
– 4 logical cores
– 8GB RAM
– 128MB RAM for the virtual display adapter
Network Settings
Known issues when using Monitors AnyWhere on VM configuration:
From our customers experience, when the OSBASE driver is installed on the VM it is very difficult to access the machine via the vSphere console. It’s a known issue of VMWARE as it’s related to their Keyboard and Mouse integration when the virtual machine is using the Extended Desktop mode.
On Virtualbox there is no such issue.
Workaround for this issue
Use a remote control application to control the VM properly. The application must be able to remote the console session of the VM (not Remote Desktop Protocol). Tested and working remote control applications: TeamViewer, VNC, Radmin, Netsupport Manager, AnyDesk, Dameware