ProLiant Deployment and Provisioning
1830165 Members
6083 Online
109999 Solutions
New Discussion

Getting started with the RDP

 
Mike Celone
Frequent Advisor

Getting started with the RDP

I just downloaded a trial of the HP RDP and so far I have been able to complete a scripted install of Windows 2003 R2 to one of my BL460C servers using the default jobs and WinPE environment. Now I would like to configure one of the jobs with a new unattend.txt file with my own settings in it. I copied the job and modified the script that copies the default.txt to unattend.txt on the host machine. Now when it goes to start the Windows install it gives me an error that say

"The specified Setup script file (c:\unattend.txt) is inaccessible or invalid."

I can verify that it is on the C:\ drive of the host and it does look valid. I ahve tried editing the default.txt file on the RDP server and I get the same issue. I have used this unattend file for many Win2k3 installation before so it should work. What is the correct procedure for modifying the unattend.txt file that gets copied to the machine? Any help is greatly appreciated.
Mike
2 REPLIES 2
Kase
Frequent Advisor

Re: Getting started with the RDP

The job step that performs this in one of our scripted installs looks like this:


rem Copy Unattend.txt

rem replacetokens .\lib\osconfig\w52e\default.txt .\lib\osconfig\w52e\%ID%.txt
set unattendfile=w52e\%ID%.txt

call %ALTIRIS_SHARE%\lib\bin32\winpe\osconfig1.cmd


To modify the unattend.txt, we directly edit the default.txt located, in this case, in the .\lib\osconfig\w52e folder.

It, however, sounds like you have done this already and are still having problems. What does the unattend.txt file look like on the failing server? It sounds like unattend.txt is not getting formatted correctly. Could you scrub and post the unattend.txt?
Mike Celone
Frequent Advisor

Re: Getting started with the RDP

I had someone else take a look at the unattend.txt that I created just to make sure. It turns out that I had a semi-colon in front of a required entry and that was causing the problem. It's working great now.
Mike