OS Directories restrictions?

[Johannes Bauer]

Hey there!

I'm working right now with rdp 2.20 and I'm trying to make several templates, which can be deployed on the right servers.

My problem now is, that only the deployments in the directory .\lib\osdist\w52s and ..\w52e are working.
I found a list in a HP Whitepaper, where these directories are listed. Is there no chance to make custom directories. I want to make templates also for x64 systems and with variable partition size, but these templates won't work because the files are in a false directory.

Is there a setting to add directories as "working directories" or soemthing like that???

Has anyone an idea??
thanks
h

[Albert Austin]

Hi,

According to this link
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00524241/c00524241.pdf

Ver 2.2 does not support x64 systems.

But Ver 3.0 does
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00711206/c00711206.pdf

Maybe you should think of upgrading then if you would like this feature.

Albert

[Johannes Bauer]

thank you albert for your comment.

But except of the 64 bit systems. is it possible to make a template, which deploys for example windows 2003 standard or enterprise with a 16 or 30 gig partition in another directory than /w52e or /w52s

i tried it with /w52e16-gb for example, but these tries do not work.

unfortunatley i cannot explain this :-(

[Albert Austin]

HI,

"is it possible to make a template, which deploys for example windows 2003 standard or enterprise with a 16 or 30 gig partition"

I have personally not done this before, take a look at this thread the diskpart was used to assign different size parttions.

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=720377&admit=-682735245+1155113008558+28353475

"in another directory than /w52e or /w52s"

Why would you want to do this?

Also this may be a silly question, but do you also modify the scripts in your tasks?

Albert

[Johannes Bauer]

thank you for your comment.

The problem is, that i shall create templates for a windows server 2003 standard and enterprise edition (this works) and then for each 1 template with 16 gb and 30 gb parition size.

I thought this will work with the option OEMExtendPartition in the unattend.txt...

Anyway i adapted the scripts, but i cannot find any entry which points exactly to the w52s or w52e directory.
So my installations for /w52s-16gb and so on don't work, eventhough I have for every template an extra default.txt

u can see my problem?

[Albert Austin]

OK,

"but i cannot find any entry which points exactly to the w52s or w52e directory. "

Do you mean you cannot find it in the default RDP scripts?
Under JObs->Deployment Tool box->OS installation scripted-> click on your selection and scripts are displayed on your right pane.Choose Run Script "choose distribution file" on clicking modify you should see this path pointing to the w52s/s directory.

Also you could modify the unattend script to pull your txt file instaed of the default.

Albert

[Johannes Bauer]

thanks for your comment.
well, i am aware of this and i adapted this in my version of this script to e.g. /w52s-16gb, and i think, that anywhere in the RDP the directories, which are supported have to be defined. but where?

[Yuichiro Kitamura · Accepted solution]

Hi Johannes Bauer

I do not understand your problem well.
Probably you want to add OS of other editions to RDP??

> Another edition or language
(When you want to add Windows2003 of a Japanese version.)

1. Create the following directories.

\lib\osdist\w52sj
\lib\osconfig\w52sj

2. Copy the file of I386 folder of Windows2003 CD-ROM to the directory.
3. Select the job which you want to perform on RDP, and copy/paste the job.

For example: "Deploy ProLiant ML/DL/BL + Windows 2003 Standard + PSP"

4. Double-click the copied job, Select "Copy Distribution Files"job-step
5. Click "Modify", and change as follows.
before : set dist=w52s
after : set dist=w52sj

6. Copy an unnatend.txt(default.txt) file to an \lib\osconfig\w52sj folder from an \lib\osconfig\w52s folder.
7. Edit the file.
8. Select an "Create Boot Environment" job-step on RDP, Click "Modify", and change as follows.

before : rem replacetokens .\lib\osconfig\w52s\default.txt .\lib\osconfig\w52s\%ID%.txt
before : set unattendfile=w52s\%ID%.txt
after : rem replacetokens .\lib\osconfig\w52sj\default.txt .\lib\osconfig\w52sj\%ID%.txt
after : set unattendfile=w52sj\%ID%.txt
9. run the job.

I wish for this helping you.

Regards, kita

[Johannes Bauer]

thank you for your anwser.

i did it that way and i thought it is completley right, but it doesn't work.

you know i didn't changed the distribution, becuase it should be the same distribution but the unattend file.

i set OEMExtenPartition= 8000 for a 16 gb partition and OEMExtendPartition=22000 for a 30 GB Partition.
But this doesn't work :(

[Johannes Bauer]

oh i forgot!
sometimes he aborts the installation during script exeception because he can't find a txt file withname 5xxxxxx.txt (xxxxxx stands for some numers e.g.: 00006)

best regards hannes

[Yuichiro Kitamura]

Hi Johannes Bauer

When you want to change the size of OS

1. Install Windows which you want to use.
2. Perform defrag on the Windows.
3. Perform Sysprep on the Windows.
(Sysprep is in Deploy.cab of Windows CD-ROM.)
(While you are using Windows2003SP1, please download deploy.cab from the following sites.)
http://www.microsoft.com/downloads/details.aspx?FamilyID=a34edcf2-ebfd-4f99-bbc4-e93154c332d6&DisplayLang=en

4. Imaging the Windows.
4-a. Right-click by the job Window on RDP, and Click "New job".
4-b. Click "Add", and Select "Create disk image"
4-c. Enter path and filename in Name:, and click "Advanced"
4-d. Select "do not boot to windows", and click "OK", and click "Finish"
4-e. Run the job.
5. Change size, when you distribute imaging Windows.
5-a. Right-click by the job Window on RDP, and Click "New job".
5-b. Click "Add", and Select "Distribute disk image"
5-c. Enter path and filename in Name:, and click "Advanced"
5-d. Change the size of a partition, and click "OK", and click "Finish"
5-e. Run the job.

I wish for this helping you.

Regards, kita

[Johannes Bauer]

thank you all!

finally i got it.
I didn't tried your way yet, but it looks also very reasonable.

Unfortunatley I do not know what it exactly was, but i created new jobs from the beginning and they are working now!

Thank you for the great support!

best regards
h

[Gordon Leonard]

A directory called /w52e16-gb should fail since MS-DOS can't read long names (Which is what your running when your in PXE). In fact any names not using 8.3 naming will cause nothing but problems.

[Johannes Bauer]

this can also be, cause i changed the directory name from w52s-16gb to w52s16gb

could that be the solution?

[Gordon Leonard]

Seems mystery solved.
The newest version of RDP [3.0] does not have this problem since you're booting either WinPE or LinuxPE.

[Johannes Bauer]

but it supports x64 systems only in imaged mode isn't it?

[Johannes Bauer]

kita,

i tried your version of making an image as an alternative.

the problem is now, that i get prompted by deploying the image:

"An Ems connection has been detected ............
If you prefer to configure Setup via this local connection ....."

how can i automate this?
tried to make after the distribtion of the image a script, but this doesnt work :-\

[Yuichiro Kitamura]

Hi Johannes Bauer

First, This thread is long enough.
It becomes difficult for a new person to read.
Therefore, I recommend you to make it a new thread.
Then, those who write a reply increase in number.
I recommend you to do so after this.

Next, Though regrettable, I do not have the environment where a Proliant machine is operated now.
Probably I think that the EMS function has faced your machine how.
I expect that BIOS of your machine has set up ESM effectively.

Please see the following URL.
http://support.microsoft.com/default.aspx?scid=kb;en-us;815273
> If you click OK, or the Close button to quit the dialog box, Setup continues as a typical attended Windows Setup.


I wish for this helping you.

Regards, kita

[Yuichiro Kitamura]

Hi Johannes Bauer

> but it supports x64 systems only in imaged mode isn't it?

Please check the followint url.
http://h18013.www1.hp.com/products/servers/management/rdp/documentation.html
â « Rapid Deployment Pack - Windows Edition 3.00 Support Matrix (pdf)

Regards, kita