Next Topic

Previous Topic

Book Contents

Remote ISO Boot

The Remote ISO Boot page boots VPro machines from an ISO image. An agent machine on the same LAN as the target vPro machine is used to mount a virtual disk on the VPro machine. The virtual disk points to a UNC share on the LAN containing an ISO image. The agent machine then boots the VPro machine from the virtual disk. A Remote ISO Boot cannot be scheduled. The boot occurs immediately.

Warning: Kaseya does not provide ISO images and is not responsible for 100% automation of the boot. A boot may require a user to hit any key to boot from ISO image, else the boot might occur from the hard drive.

VPro Configuration Requirements

  • The agent cannot be on the vPro machine. It has to be on a different machine in the same LAN.
  • The VPro machine being booted must be VPro 3.0 or greater.
  • SOL/IDE-R must be enabled in the Intel AMT BIOS extension. This cannot be done remotely.
  • The agent machine used to boot the vPro machine, the VPro machines being booted and the UNC must all be on the same LAN.
  • Only UNC shares can be specified. Mapped drives are not allowed.
  • Credentials must be defined in advance, providing access to:
    • The agent machine - Use Agent > Set Credential if necessary.
    • The UNC share on the LAN - The network credentials and UNC are both specified when the ISO boot icon is clicked in the Remote ISO Boot grid.
    • The vPro machine - vPro credentials are configured either during LAN Watch scan or by clicking on the credentials icon in the Remote ISO Boot or Power Management grid.

Host Name

The name for the vPro-enabled machine set by vPro configuration.

Proxy Agent

The machine ID of another managed machine used to execute power on, power off or reboot this vPro-enabled machine. The Proxy Agent must be on the same LAN as the vPro machine.

Machine.Group ID

The machine ID of this vPro-enabled machine, if an agent is installed. Blank, if no agent is installed.


The vPro credentials are typically collected during a LAN Watch scan. The credentials are required by the vPro machine to respond to both Power Management and Remote ISO Boot requests. If none are defined or they need to be changed you can click this cell to define a new credential.

Remote ISO Boot

Click the Remote ISO Boot icon to specify the UNC File Path, User Name and Password. Then click the Go button.

  • The UNC File Path must include the filename of the ISO image.
  • The User Name and Password is required to access to the ISO image file on the LAN.


ISO boot is implemented via the following components:

  • VProProxy.dll - This dll is used by the agent on the agent machine to communicate with the VPro machine.
  • Redirect.exe - This process is run with the passed in network credentials and manages the virtual drive.


The following are switches sent to VProProxy.dll when doing an ISO boot.

  • -redirect - We're going to do a redirect operation. Possible values - command
  • -username - The VPro user name (like admin)
  • -password - The password for the VPro user
  • -ip - The ip address of the target machine
  • -iso - The UNC path to the ISO image
  • -redirectPath - The path to redirect.exe
  • -o - The full name and path of the out file for VProProxy.dll
  • -redirectOut - The full name and path of the out file for redirect.exe
  • -netUsername - The name of the network user with authority to access iso image. Name must be in the form of name@domain.
  • -newPassword - The password for the network user


The following is an example of a command line using the switches above.

C:\temp\VProProxy.dll -redirect command -username admin -password Pass=W0rd
-ip -iso "\\\ISOImages\EN_WINDOWS_XP_PRO_WITH_SP2.ISO"
-redirectPath C:\temp\redirect.exe -o C:\temp\ProxyOut.txt
-netUsername -netPassword SomePassword
-redirectOut c:\temp\RedirectInfo.txt