RDP / PXE boot Failed/Invalid Drive Specification,Unable to Map Drive

[oliviey]

Upgraded RDP from 2.1 to 2.2 .
After upgrading unable to Deploy on the Target Server,

DL380 Win 2k Sp1 thats the deployement server.
DL360 is the target Server that fails to complete PXE boot.
Getting a Error Message Invalid Password.
Invalid drive Specification
unable to Map drive.

[Ed Cox]

oliviey,
It might be a couple of things:

1. Unable to resolve the RDP Server hostname listed in the PXE Boot file (\\RDPServer\eXpress)- and if so the PXE boot device won't be able to map the drive. Modify the LMHosts file under the \net directory in the PXE boot file to reference the ip address and hostname of the RDP server.

2. The user account and password listed in the PXE Boot file has had a recent password change. If so...the PXE boot file may still be referencing the previous password.

3. After an upgrade you may have lost the Sharing capability of the \eXpress share on the RDP server. Double check to make sure that the Deployment Server folder is still shared as eXpress.

Good luck,
Ed Cox

[nw1927]

Does anyone have any idea how to modify the username and password in the PXE Boot file in version 2.2 please?

[john mills_3]

try this, on the rdp console server fire up
the rdp console, select tools, pxe config.
Select the "DOS managed" option and click edit
(on the right), then clikc "edit boot image".
When the window opens DON'T click next, click
edit then yes. This will take you into the
configuration wizard that previous rdp versions
used for the boot disk creator.

About 5 nexts (plus a yes) you'll get to the
network connection screen - mod what you need
and "next" your way out. OK the shared menu
screen and SAVE :-)

[john mills_3]

try this, on the rdp console server fire up
the rdp console, select tools, pxe config.
Select the "DOS managed" option and click edit
(on the right), then click "edit boot image".
When the window opens DON'T click next, click
edit then yes. This will take you into the
configuration wizard that previous rdp versions
used for the boot disk creator.

About 5 nexts (plus a yes) you'll get to the
network connection screen - mod what you need
and "next" your way out. OK the shared menu
screen and SAVE :-)

[Barthelmy]

Thanks for your post it worked a treat, the logon ID was changed when the server was added to the domain.