This is the location of the VirtualBox binaries on the Host.
This is the hostname of the Host that the Agent software is installed on.
This is the name of the Host Group that the agent belongs to. Images assigned to this group can be run on this Host.
This is the list of Infinity servers known by the agent. If there are multiple servers configured and the server the Agent is logged into fails to respond, the Agent will automatically attempt to connect to the other servers in the list. The Agent regularly polls its server to detect failure.
This is the location the Agent will write VM backups too. The agent will execute preBackup and postBackup scripts if they exist. The scripts must be located in the backup directory. preBackup is run as "preBackup <backup file name> <VM name>". postBackup is run as "postBackup <backup file name> <VM name> <backup job status>".
Possible backup job status messages are "Completed", "Cancelled" or "Error".
If the Login ID and password are set, on Agent start up, the Agent will use these settings to automatically login.
If the login fails, the Agent will display the login dialog.
This sets the Agents logging Level. INFO is the default level. For debugging purposes, the Agent can be configured to log more details. All logs all messages.
When the Log Level is set to ALL, the VirtualBox configuration for VMs will not be removed as usual when a VM is powered off to allow the use of VirtualBox tools to help debug VM issues.
This is the network card the Infinity server will contact the Agent on.
VMs configured to use Bridged Interfaces will be connected to this NIC
VMs configured with audio support will use this facility on the Host to produce sound.
If the user attempts to make an RDP connection to a remote VM, By default the built in Java RDP client will be used.
You can configure the Agent to use another program instead by entering the command here.
Variables %username, %password, %address and %port are supported.
For example: mstsc /v:%address:%port
Maximum Host RAM used by VMs. A cap of zero means that there is no cap on RAM, VMs can use all RAM available on the Host. Setting it higher than the Hosts actual amount of ram will allow the running of more VMs but could lead to problems if the VMs actively use all the RAM configured to them.
If Headless is enabled, VMs will be started on the host in the background. VM access will be remote only.
VMs will be started in full screen mode.
3D acceleration will be available on all VMs. If the 3D checkbox is greyed out, 3D support is not available on this Host.
To take advantage of 3D support, the VMs must have the VirtualBox utilities installed with 3D support enabled in the VM.
By default the VirtualBox will not cache disk IO between the Host and the Infinity server but this option can be enabled.
In Kiosk mode, VMs will be started in full screen and access the the VirtualBox tools will be disabled. But if the VM is shut down, users will have access to the host system.
By default the Agent configures VirtualBox to use Infinity accounts to control remote RDP access to the VMs running on the Host.
If Host RDP is enabled, the Agent will configure VirtualBox to use accounts on the Host system to authenticate RDP access to VMs.
When enabled, causes the Agent to restart VMs that fail.
The individual windows that are displayed on the desktop of the virtual machine can be mapped on the host's desktop, as if the underlying application was actually running on the host.
In a server environment running several similar VMs (e.g. with identical operating systems) on the same host, lots of memory pages are identical. Page Fusion technology is technique to efficiently identify these identical memory pages and share them between multiple VMs.
Page Fusion supports only on 64-bit hosts, and it is not supported on Mac OS X hosts. Page Fusion currently works only with Windows guests (2000 and later).