Stop D: drive becoming CD drive...

[Doswelk]

I am planning on rolling out Windows XP (installing it via RIS) and have created an image of the configuration we wish to use...

The PCs have CD-ROMs they default to the D: drive.

I need to default the CD-ROMs to become the E: drive leaving the D: drive free for a Subst command.

Any ideas ?

Kevin Doswell

 

[wolluf]

Change the CD Rom drive to E: (from Disk Management) before taking the image?

 

[ShackDaddy]

You might suck down a build, which will default to using D: as the CD drive. Then load Regmon and FileMon by Sysinternals.com and with them scanning, use Disk Administrator to reset the drive letter for the CD to E:. Then go through the log, especially on Regmon and see what change was made to the registry when the drive letter was changed. Find those entries in the registry of the changed machine and put them all in a single 'reg' file and run it as part of your 'first time boot' script.

If you dig around some scripting sites you may even be able to find a script that changes drive letters for you, but most scripts only alter the user environment.

Another possible option would be to create a share on the workstation and map the D: drive to it before creating a RIS image. This might not work since shares are stored on the User side of things.

just some ideas

 

[Doswelk]

Unfortunately as RIS does not require exact hardware it creates HKeyLM for each PC and although the image did have the E: drive set the new PC does not.

 

[Doswelk]

Shackdaddy thankyou for your ideas....

I have found using NTRegmon the key I need to change
HKLM\System\MountedDevices\DosDevices\D: but you need to use regedt32 to set the permissions to allow me to change it in regedit!

So unless someone out there is super clever and knows how to write a kixscript to change the permissions on XP registry and then rename \DosDevices\D: to \DosDevices\E: I am stuck.

I am sure there must be another way

 

[ShackDaddy]

Why can't you change the permissions in the original build? Won't registry permissions changes made in the pre-risetup last through the imaging? Maybe not, but I thought that they might.

ShackDaddy