Setup Guide

Configuring the Active System Manager

Virtual Appliance

You must configure the following settings in the virtual appliance console before you start using Active

System Manager (ASM):

• Configure static IP Address in the virtual appliance. For detailed information, see Configuring Static IP

Address in the Virtual Appliance

• Configure ASM Virtual Appliance as PXE boot responder. For detailed information, see Configuring

ASM Virtual Appliance as PXE Boot Responder

• Import Windows ISO on the virtual appliance. For detailed information, see Importing Windows ISO

on Virtual Appliance

• Deploy the WinPE image file to the virtual appliance Razor. For detailed information, see Deploying

WinPE on the Virtual Appliance Razor

Configuring Static IP Address in the Virtual Appliance

1. In the VMware Sphere, click the Console tab to open the console of the virtual appliance.

2. Log in to the console with the user name root and password linux and press Enter.

3. In the Properties dialog box, click Network Configuration.

4. In the Network Connections dialog box, click Wired → Auto eth0, and then click Edit.

5. In the Editing Auto eth0 dialog box, click IPv4 Settings tab.

6. Select Manual from the Method drop-down list.

7. In the Addresses table, type the static IP address, subnet mask, gateway, and then click Add.

8. Click Apply to set the static IP address of the appliance.

Configuring ASM Virtual Appliance as PXE Boot

Responder

Active System Manager (ASM) requires both PXE and DHCP network services to function. The ASM virtual

appliance contains a PXE service (called Razor) that is used to register resources with ASM so that

workloads can be deployed. The ASM virtual appliance must be deployed directly on the network

configured for the PXE service.

The PXE service requires a DHCP server configured to provide boot server (TFTP PXE server) information

and specific start-up file information. The ASM PXE implementation uses the iPXE specification so that the

configuration details include instructions to allow legacy PXE servers and resources to boot properly to

this iPXE implementation.