Virtual Machine Deployment Support
Article: 193
Applies to: Releases 3.10 through 3.83
In order to deploy Windows to virtual machines, the following configuration changes are required.
Deployment Server configuration
| • |
To support Windows deployments, the default PXE boot option
must be set to "WinPE Managed".
|
| • |
To support Windows Server 2003 x86 deployments, the default PXE boot
option for unknown computers must be set to "WinPE Managed
(32-bit)". For all other Windows deployments, this option must
be set to "WinPE Managed (auto-select)".
IMPORTANT: Virtual Machines configured to boot Windows
must only boot to WinPE as the automation environment, otherwise
the virtual BIOS will become corrupted resulting in PXE boot problems.
|
Virtual Machine Host configuration
| • |
To support Windows x64 guests, the Intel Virtual Technology
(Intel VT) or AMD Virtualization (AMD-V) processor options must
be enabled in RBSU. Release 3.80 enables this
option by default during VMware ESX Server 3.x scripted install jobs.
|
VMware ESX 3.x Virtual Machine configuration
| • |
For Windows Server 2003 x64 and Windows Server 2008 guests, the E1000 virtual
network adapter must be selected.
|
| • |
For Windows Server 2003 x86 guests, the Flexible virtual network adapter
must be selected and a driver added to WinPE automation environment.
Refer to Knowledge Base article
How To Add VMware Flexible NIC Driver For WinPE 2.1 x86/x64 Automation
(Article 192).
|
| • |
For Windows guests, the disk size must be at least 8GB.
|
| • |
The LSI Logic SCSI controller must be selected.
|
| • |
The virtual network adapter must be set to first in the BIOS boot order.
|
Virtual Machine Deployment
| • |
For all Windows deployments, it is recommended to use the jobs
located in Server Deployment Toolbox.
|
| • |
For Windows Server 2003 deployments, the Run Script - Copy ProLiant Files task
must be removed from the scripted install jobs.
|
|
Printable version
