dagent install in unattend.xml help please!!!

[friedheadsandwich]

pulling my hair out on trying to get a 2008 r2 server build complete...nearly there.... so close but so far away....got everything working except the preinstalled section where the dagent is preinstalled as the server boots into windows

followed the steps in http://forums13.itrc.hp.com/service/forums/questionanswer.do?threadId=1342071

but still can't get it to install

help please. i am losing the will to live on this......some assistance is needed before i attack the rdp server with a sledge hammer

[Gerhard Palmetshofer]

Which version of RDP do you have?

As I wrote on Dec, 30th RDP 6.0 delivers new jobs. The old version used a batchfile to copy dagentx64 but it doesn´t work and it will not work - don´t spend more time into it.
Use the jobs delivered with RDP 6.0 and everything is fine.
Also the RDP upgrade to 6.01 worked fine in our environment.

If you don´t want to upgrade your whole RDP environment you can download the install, run the setup and after the setup has uncompressed all files into a tempfolder you can copy the jobs out of this directory and import them into your RDP Server.

Regards,

Gerhard Palmetshofer

[friedheadsandwich]

i have version rdp version 6.9 sp3 this is the latest version no......? would have thought that the job and scripts would just work.... installing the altiris d agent should be easy right?

[Matt Ronsman]

I am having this same issue. The copy OEM files task seemingly runs but for whatever reason the $OEM$ directory does not end up on the server so the Dagent does not install and the job never finishes. I have tried to make a batch file to do it but that does not help. I can copy the files manually while it is still in WinPE doing the first phase of the 2008 R2 install. Seems like a Windows security thing but I am not sure how to get around it?

Someone please advise... I am using RDP 6.2 with a BL460 G7 server.

Thanx,
Matt

[shocko]

Hi,
The reason the OEM folder is not present is because you are over-writing it with during the install. RDP lays down an NTFS image on the first disk it finds and copies over the OEM folder. You have this section in your answer file:

-
-
-
-
1
500
Primary

-
true
2
Primary


-
-
true
NTFS
System
1
1

-
NTFS
Windows
2
2


0
true




Therfore you'ill re-format the exisiting partition and loose your OEM folder :(

Dont do the parittioning in in the answer file. Do it later when the build in complete :)

[Chris m W]

I am having this same issue. I need to be able to partition the drive. If it automatically creates a partition the size of the disk is there a way to automate it after the build to resize the partition to create a second one?

Thanks,

Chris

[shocko]

Yes, you can specify an initial size for the NTFS image as a percentage of the target disk and then add partition commands to your answer file ;)