topic RDP PXE Boot Problem in ProLiant Deployment and Provisioning

RDP PXE Boot Problem

Nabil_11 — Thu, 04 Dec 2008 23:03:17 GMT

Hi all,

I have RDP 3.9 shipped with blade enclosure
I try to install it on windows 2003 x64
BUT its stuck at PXE Sync.

then I install RDP RDP381.iso form hp site
burn it at nero.

and install it on windows 2003 32bit.
installation done successfully

MY DS configured as DHCP and PXE Server.
when I try to deploy my blade server
its get an IP address from DHCP
and boot to linux pre boot then
install some files then stop at # prompt

if I hit F12 then F8 and I choose winPE
it gives TFTP error

any help appreciated
is there is clear steps to configure the PXE configuration utility

pleaaaaaaaaaaaase advice

BR

Nabil

Re: RDP PXE Boot Problem

Gordon Leonard — Mon, 08 Dec 2008 13:21:02 GMT

Make sure you have licenses so the client can check in. (You can check this in the help and about screen)

Re: RDP PXE Boot Problem

Nabil_11 — Fri, 12 Dec 2008 12:22:39 GMT

Thanks for your interest,

I add the DHCP option 066
now I'm able to boot via pxe with winPE

I'm new user to RDP !!!

I have another question.

I capture disk image from running windows 2008 OS, Then I try to deploy it.
when the target restarted it fail asking to repair the windows OS.

all what I need to take image from running OS
on c7000 blade and deploy it to another machine.
I try to install Aclint agent on one server
it installed successfully but still the information at RDP server for this client not updated ( such teaming, IP address )
RDP version is 3.82 SP1
target OS windows 2008

Regards

Nabil

Re: RDP PXE Boot Problem

Gordon Leonard — Fri, 12 Dec 2008 14:23:37 GMT

Just for clarification.

When you install RDP and the PXE service and the MS DHCP service are on the same server it *should* automatically add option 60 to the DHCP service. Based on your information your target server and deployment server [DS] are on two different networks. Generally this means you need to configure a helper address on your router (must of the time it's two addresses one for the DHCP and one for the PXE {bootp}) that is servicing the target server. So your saying to only set option 66? This is interesting because you tend to need option 66 and 67. I'll have to try this.

Ok in regards to you image question...I'm not a fan of imaging so I'm not very deep in this topic. When you captured the image did you ensure the NICs where not teamed before capturing the image. Also on the server your capturing how did you land the OS? If you didn't use the RDP scripted install try landing a scripted install on a blade then do an image capture (without making any changes to the script or the OS that has landed).