RDP 2.10 imaging/bootworks problem

[Mark Nottingham]

I installed RDP 2.10 on a new server and I'm getting an error message when I try to do any imaging using my previously created images.

I have installed the Altiris agent onto the server which is configured correctly to point to my new RDP server. I create my imaging job using the built-in jobs and select my image in the properties. I then drag the job onto the server I want to image and the server shuts down for imaging. The server boots up, gets an IP address from DHCP and connects to the RDP server. All the network type stuff runs through, and then I get an error message saying "Bad command or file name" and the whole thing stops at an A: dos prompt.

I have uninstalled and reinstalled a number of times now and I am starting to tear my hair out! I have run through the Boot Disk creator wizard to no avail. I have tried to work out at which point in the script it falls over, but the whole thing runs through so fast it is diffcult to stop it, and the script does a cls command just before the error. However, I think it may be in the autoexec.bat file when it tries to run the command:

A:\bootwork.exe -nologin %CONMIP% %CONMPORT% %CONNAME% %CONIP% %CONPORT% %DEBUG%

If I type dir when the process stops, bootwork.exe is not listed in the files in the root of A:

I hope someone can please help as I have run out of ideas and hope!

Many thanks

Mark

[Gopi Sekar · Accepted solution]

The bad command or file name issue arises due to permission or network related problem in DS.

Check KB article number:59
http://h18013.www1.hp.com/products/servers/management/rdp/knowledgebase/00000059.html

Regards,
Gopi

[Tv_3]

Hi how many nic's are there in your RDP Alteris Server.

It only supports 1 nic, you can't use a multihomed server for alteris.

I had the same experience as you but the reason for me was the dual nic...

Hope this helps...

[Mark Nottingham]

Thanks for your help guys. It seems to be a network related problem. I put the RDP server in the lmhosts file in the Boot Disk configuration tool and it kicked into life. Now I've got to work out why it's not getting all the info from DHCP.
Many thanks.
Mark