/build/static/layout/Breadcrumb_cap_w.png

Making RIS delete all existing Partitions

Here is the problem.

We are deploying a bunch of new Acer computers, they have disk to disk recovery, it is a PowerQuest technology and is integrated into the BIOS. This creates a 2GB Fat32 partition on the Hard drive. Windows by default will write the Boot.ini to the first partition avaialble, so when i RIS the Drive, it only makes a 38GB (rest of the 40GB), so because of this I get two entries in my Boot.INI one for the original Win XP Pro the other for Windows 2000 SP4 (which we use). I can easily remove teh entry manually, but when you have 500-600 machines to do in 3 months it gets rather time consuming. Is there any way to have RIS kill all partitions on just the first disk (or all if it is all or nothing).

Thanks for any help.

0 Comments   [ + ] Show comments

Answers (2)

Posted by: Michael_W 19 years ago
Yellow Belt
0
The answer file supports a hard disk partitioning section ([RemoteInstall]) that contains the repartition parameter. If this value is not specified or set to “yes”, a RIS install will delete all partitions on the client computer and format that drive with one NTFS partition. If this value is set to no, RIS will use the default parameters in the answer file.



[RemoteInstall]
repartition = no

If this still does not remove the duplicate entry, write a script that removes the entry from the boot.ini and your done.

Michael
Posted by: cdupuis 19 years ago
Third Degree Green Belt
0
Thanks, I will try it and see what happens.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ