O'Reilly Hacks
oreilly.comO'Reilly NetworkSafari BookshelfConferences Sign In/My Account | View Cart   
Book List Learning Lab PDFs O'Reilly Gear Newsletters Press Room Jobs  


Non C: or D: Drive Windows Install
Many Exploits are pointed to the C: or D: drive. Installing Win2K All Versions Not on a C: or D: Drive add an additional layer of Security

Contributed by:
Jon Hopkins
[10/28/03 | Discuss (1) | Link to this hack]

Around the time of Code Red looking at Web logs, most all attempts to compromise my servers were directed to the C: or D: drive. I set out to Install Windowes 2000 Server on a different drive letter.

We have found this to be a great security procedure and we do not have any OS installed on a C: or D: drive. We run SCSI Drive and have also Installed On IDE drives. Windows has a few requirements for it to install. The first being that it Loads the system files on the first Drive. You have the Option to Load the WINNT Directory any where you which. This c: Drive with the system files and the WINNT Directory on any other Drive letter has drawbacks: The sys files Point to the WINNT Directory. The Drive is for the Most part Lost space as it can not be used to in any type of Raid, extended etc. You are Booting to the C: drive and running the OS off of another drive.

A better Install is the system files on the drive that has the WINNT Directory and there is not any C: or D: Drive on the machine.

I have found all software to run in a normal manner. The only glitch found - some software * Poorly written I may add, will check for a C: drive and then can be installed on any drive. Solution is to make a C: drive with the less than 10 mbs that are left on any drive and delete this partition after the install of the software.

O'Reilly Home | Privacy Policy

© 2007 O'Reilly Media, Inc.
Website: | Customer Service: | Book issues:

All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners.