VMware SOFTWARE REPOSITORY FOR WINDOWS 1.1 Manuale Utente Scaricare il pdf (Pagina 22)

Power on the NAS VM, wait for it to boot to the logon prompt

If you watch the console of the NAS VM you may see messages about not having enough

RAM for ZFS, this does not cause any issues and can be ignored

If your PC has an IP address on the VMNet3 network, it is usually 192.168.199.1. Ping

192.168.199.7 which is the NAS, if this succeeds open the window share

\\192.168.199.7\Build. If the ping fails then you can access though the NAS using the

external IP address of the router. In the example above the external address is 192.168.20.118

(it’s on the Waiting for DHCPOFFER on eth0 line) so the share is \\192.168.20.118\Build.

VMware Fusion note: Using Finder, press Command+K to open the “Connect to Server…”

dialog box. Enter smb://192.168.199.7 and connect as Guest. If you connect as a named user

or connect using NFS, your user permissions will write the files in a way that renders them

inaccessible. (This can be fixed with chown & chmod if you’ve already made this mistake.)

Populate the build Share

The build share is the central repository for the installers and scripts that are used inside the

AutoLab, all of the software that will be used must be on this share before the rest of the

builds begin. There are folders for each piece of software; most of these folders need to have

the ISO files extracted into them. The only ISO files that are required are the Windows 2003

and XP install ISOs placed in the root folder; all sub folders should contain files extracted

from ISOs or ZIP files.

Here are the contents of an empty build share:

Core lab requirements:

The ESX and ESXi folders need to have the ESX and ESXi installer ISO extracted into

them.

The VIM folders need to have the vCenter installers extracted into them.

1 2 ... 17 18 19 20 21 22 23 24 25 26 27 ... 67 68

Nessun commento

VMware SOFTWARE REPOSITORY FOR WINDOWS 1.1 Manuale Utente Pagina 22