User`s guide
Table Of Contents
- VCM Installation and Getting Started Guide
- Updated Information
- About This Book
- Preparing for Installation
- Installing VCM
- Using Installation Manager
- Installing and Configuring the OS Provisioning Server and Components
- Installing the Operating System Provisioning Server
- Preparing Boot Images for Windows Provisioning
- Copy the VCM Certificate to the OS Provisioning Server for Linux Provisioning
- Importing Distributions into the OS Provisioning Server Repository
- Configuring the OS Provisioning Server Integration with the VCM Collector
- Maintaining Operating System Provisioning Servers
- Upgrading or Migrating vCenter Configuration Manager
- Upgrade and Migration Scenarios
- Prerequisites
- Back up Your Databases
- Back up Your Files
- Back up Your Certificates
- Software Supported by the VCM Collector
- Migration Process
- Prerequisites
- Foundation Checker Must Run Successfully
- Use the SQL Migration Helper Tool
- Migrate Only Your Database
- Replace your existing 32-Bit Environment with the Supported 64-bit Environment
- How to Recover Your Machine if the Migration is not Successful
- Migrate a 32-bit environment running VCM 5.3 or earlier to VCM 5.4
- Migrate a 64-bit environment running VCM 5.3 or earlier to VCM 5.4
- Migrate a split installation of VCM 5.3 or earlier to a single-server install...
- After You Migrate VCM
- Upgrade Process
- Upgrading Existing Windows Agents
- Upgrading Existing Remote Clients
- Upgrading Existing UNIX Agents
- Upgrading VCM for Virtualization
- Getting Started with VCM Components and Tools
- Getting Started with VCM
- Discover, License, and Install Windows Machines
- Verifying Available Domains
- Checking the Network Authority
- Assigning Network Authority Accounts
- Discovering Windows Machines
- Licensing Windows Machines
- Installing the VCM Windows Agent on your Windows Machines
- Performing an Initial Collection
- Exploring Windows Collection Results
- Getting Started Collecting Windows Custom Information
- Discover, License, and Install UNIX/Linux Machines
- Discover, License, and Install Mac OS X Machines
- Discover, License, and Collect Oracle Data from UNIX Machines
- Customize VCM for your Environment
- How to Set Up and Use VCM Auditing
- Discover, License, and Install Windows Machines
- Getting Started with VCM for Virtualization
- Getting Started with VCM Remote
- Getting Started with VCM Patching
- Getting Started with Operating System Provisioning
- Getting Started with Software Provisioning
- Getting Started with VCM Management Extensions for Assets
- Getting Started with VCM Service Desk Integration
- Getting Started with VCM for Active Directory
- Accessing Additional Compliance Content
- Installing and Getting Started with VCM Tools
- Maintaining VCM After Installation
- Troubleshooting Problems with VCM
- Index
8. The script runs as follows with a specific example:
Importing data into repository...
Importing source data...
No recipes are accessible.
Adding new recipe WINSERVER2003_std_r2_sp2BasicRecipe-2
Creating UCI WINSERVER2003_std_r2_sp2-BasicUCI.
Attaching UCI WINSERVER2003_std_r2_sp2-BasicUCI to recipe 2.
UCI WINSERVER2003_std_r2_sp2-BasicUCI is attached to recipe 2.
Updating the Summary data...
Import Linux/ESX Distributions
Distributions are the operating system installation files. You must import each OS distribution into the OS
Provisioning repository before you can use VCM to install it on target machines.
NOTE Importing distributions with spaces in the file name is not supported. Before importing, remove
the spaces or replace the spaces with underscores.
Linux, or ESX distributions use the following procedure. The SUSE distribution is issued on multiple DVDs;
however, only the first disk is required and must be imported using the following procedure.
Procedure
1. On the OS Provisioning Server, log in as vcmuser.
2. For your first import, type the command:
# basicimport -i <distribution name>.iso -l <OS Provisioning Server IP
address>
NOTE Changing the OS Provisioning Server IP address at a later time is not currently supported. 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 related DHCP and TFTP
configurations, before you import any OS distributions.
For subsequent imports, the -l option is not necessary:
# basicimport -i <distribution name>.iso
Where the <distribution name> is the iso file name. For example, ESX-4.0.0-update01-208167.
3. Type the Family Name.
For example, ESX. You must provide a unique family name to perform the basicimport of different
operating systems in the same family. No other family can exist with the same combination of name,
version, and architecture values.
4. Type the Family Version.
For example, 4.0ul.
5. Type the Family Architecture, either i386 or x86_64.
6. Type the Provenance.
For example, CD, hotfix, or SP.
Installing and Configuring the OS Provisioning Server and Components
VMware, Inc. 31