Install Guide

• Log in to the operating system of the virtual machine and run the VMware tools installer within the OS running on the virtual

machine. For more information on installing VMware tools, see VMware documentation.

The following customization is required for both VMware and Hyper-V virtual machine.

Install the puppet agent on the virtual machine:

• If the virtual machine being used was successfully created by ASM, the puppet agent will already be installed.

• To install the puppet agent on the virtual machine, copy the puppet agent install files to the virtual machine. The puppet agent is

available on the ASM appliance for both Windows and Linux.

in /var/lib/razor/repo-store directory. If the virtual machine being customized has network access to the ASM appliance, you

can connect to this same directory as a network share directory using the address: \\<ASM appliance hostname or IP>\razor

\puppet-agent.

Depending on your operating system, the installer may require extra packages (.rpms) which are dependencies and you must

install it first. If the installer reports such dependencies, use the correct method for your operating system to find and install the

dependencies, and then retry installation of the puppet agent.

NOTE: The puppet agent version should be greater than 3.0.0 and lower than 3.4.

• After you install the puppet agent, make sure that the puppet agent service is enabled to run on system start.

– For Windows virtual machines, this must be done by viewing the services and setting the puppet agent service to

"automatic".

– For Linux virtual machines, verify whether the puppet agent is enabled by running the following command and checking the

value of "enable" is set to true:

Puppet resource service puppet

– If the service is not set to true as noted above, run the following puppet command as administrator:

puppet resource service puppet enable=true

• Time must be synchronized between the ASM appliance and the virtual machine being cloned to ensure proper check-in upon

completion of cloning. Make sure that NTP is configured on the virtual machine. Follow the appropriate instructions for your

operating system to synchronize the virtual machine with an NTP server.

• Make sure the ASM appliance hostname "dellasm" can be resolved by using DNS. Either add the appropriate CNAME record in

DNS* or add the appropriate host entries to "/etc/hosts" in Linux or "C:\windows\system32\driver\etc\hosts" in Windows.

• Configure the puppet.conf file to use "dellasm" as a server. To configure the puppet.conf file, perform the following:

– Identify the location of the puppet.conf file. To do this, run the following command as "administrator" in Windows or "root" in

Linux which displays the directory of the puppet.conf file.

puppet config print config

– Open the puppet.conf file by using a text editor and add the line "server = dellasm" to the [main],[master], and [agent]

section. If any of these sections does not exist, create them. A sample resulting puppet.conf file may look similar to the

following:

[main]

server=dellasm

[master]

server=dellasm

[agent]

server=dellasm

NOTE: Extra lines may be present in the puppet.conf file for your system. It is not necessary to delete any

information from this file. You need to ensure that the previously noted section is present in the file.