User`s guide

Prerequisites
n
Verify that the distributions you are importing do not include spaces in the filenames. Before you
import, remove the spaces or replace them with underscores.
n
Confirm that the current OS Provisioning Server IP address is correct for your production
environment. You cannot change the OS Provisioning Server IP address at a later time. If the initial IP
address of the OS Provisioning Server after install is not the address you intend for it to have when it is
put into production, you must change its address, and change related DHCP and TFTP configurations,
before you import any OS distributions. If you change the OS Provisioning Server IP address after you
imported the distributions, you must re-import the distributions with the new address. You must also
recreate the Windows boot image with the new IP address.
n
Determine whether you are importing a single ISO image or multiple images from a directory. The
basicimport command uses a -i option to specify an ISO file and a -d option to specify the directory.
See "Using the basicimport Command Options" on page 38.
n
If you are importing multidistribution .iso files, create directories and copy the files to the directories.
See "Create Directories for Windows Distributions" on page 34.
Procedure
1. On the OS Provisioning Server, log in as vcmuser.
2. Mount the ISO by attaching to the media image or mounting the image.
For Windows 2008 and Windows 7, use -t udf mount type and do not include any spaces in the path.
For all other Windows operating systems, use loopback. For example, $ sudo mount -o loop
/<iso_file.iso> /<mount point>.
3. Run the sudo basicimport -d /mnt/<directory name> -l <OS Provisioning Server
private IP address or provisioning network IP address> command.
For example, sudo basicimport -d /mnt/Win2k3SE-R2-SP2-i386 -l 10.11.12.1.
If you created a /tmp/ directory for a multi-CD distribution, include the path. For example,
/tmp/<directory name>, or /tmp/Win2003-R2-SP2-Standard.
For subsequent imports, you can run the command without the -l option.
4. Type the Family Name.
For example, Windows. You must provide a unique family name to import different operating systems
in the same family. No other family can exist with the same combination of name, version, and
architecture values.
5. Type the Family Version.
For example, 2008R2.
6. Type the Family Architecture.
For example, either i386 or x86_64.
7. Type the Provenance.
For example, CD, hotfix, or SP.
8. For Windows 2008 R2, Windows 7, and Windows 2003 only, type the Build Type.
For example, either volume or retail.
Installing, Configuring, and Upgrading the OS Provisioning Server and Components
VMware, Inc. 35