ProLiant Deployment and Provisioning
1823062 Members
3157 Online
109645 Solutions
New Discussion юеВ

Re: PXE Boot problem install Guest OS using VMware ESX 2.1

 
Mayur Patel_1
New Member

PXE Boot problem install Guest OS using VMware ESX 2.1

I am trying to use eXpress Deployment Server 5.5 (RDP) running in a Guest Win2K Virtual machines configured with DHCP server.

When I start a new blank guest virtual machine configured as a PXE boot which is VMware PXE Network boot (AMD Am79C970A).

The DHCP server issues a IP address to the PXE boot (all works fine)
I receive the below screen messages:

Auto-select:
Altiris Bootworks (Initial Deployment)

BOOT SERVER IP: 169.254.33.91 (this is the Ip address of the RDP Win2K server running as a Virtual Machine)

Altiris PXE-2.0E Remote Boot (build 071)
UD 169.254.33.91 .
Requesting more DHCP options....
(downloading dos image.....appears for a few seconds)

Transferring control to DOS boot diskette image.....

The VM just sits there waiting and nothing happens.

I have also tried recreating the PXE boot files, I am using the Universal PXE driver.

Could someone please advice what is it that I haven't configured is stopping the machine from booting up and mapping a drive to the eXpress share?

Has anyone managed to get it working in a VMware ESX environment.

Please help.

Thanks.
3 REPLIES 3
Robert Hearn
Frequent Advisor

Re: PXE Boot problem install Guest OS using VMware ESX 2.1

I have seen this issue to be caused by corrupt DOS files. Go into Boot Disk Creator and select Tools > Configure Boot OS and reinstall the DOS files.

Robert Hearn
http://www.RDPGuru.com/
www.deploymentguru.com
Michael Gorden
New Member

Re: PXE Boot problem install Guest OS using VMware ESX 2.1

Good question,

I am trying the same install and having the same problem.

HELP>>>>>

Please.

Mohamed_28
New Member

Re: PXE Boot problem install Guest OS using VMware ESX 2.1

I believe it has nothing to do with the VMware environment, Since i'm having the same problem with Production proliant servers DL, ML and BL !!!
I even re-installed a new RDP with another DOS image from different source, and the problem remains.