Virtual Machine Deployment Support
Article: 20000044
Applies to: Release 6.x
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.
|
VMware ESX 4.x Virtual Machine configuration
| • |
For Windows guests, the disk size must be at least 8GB.
|
| • |
The LSI Logic SAS controller must be selected.
|
| • |
The virtual network adapter must be set to first in the BIOS boot order.
|
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 Into WinPE 2.1 x86/x64 Automation (Article 20000024).
|
| • |
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 Server 2003 scripted installs, in the Run Script - Configure Answer File task, change
if exist "%featuredir%\oem\unattend-storage.txt" ...
to
rem if exist "%featuredir%\oem\unattend-storage.txt" ...
|
|
Printable version
