• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 185
  • Last Modified:

Where to install?

Hi Guys,

just got through my windows 2003 server standard CD's and i have come accross a small problem. I current have a server that is very problematic,. so instead of upgrading, i want to completely remove windows 2000 and install a fresh version of 2003 server.

The server has 3 drives:
c: 8 gig (where windows 2000 is currently installed)
e: 17 gig
f: 62 gig

i want to install the 2003 installation on the 17 gig hard drive, but have it as hard drive C:. is this possible?

stupidly, i have already started and installation, and i don't think i've done it properly. I inserted the windows 2003 CD into the machine, and selected to install fresh copy rather than upgrade. once it rebooted, it asked me where i wanted to save the OS, and i selected the 17 gig hard drive, and i deleted the partition and then reformatted it in NTFS. The system will now dual boot won't it? how do i get it so that i remove 2000, and have it boot up in 2003 and have drive C (the windows partition) as the 17 gig hard drive?

Please help!
0
Gavin5511
Asked:
Gavin5511
  • 5
  • 2
1 Solution
 
Jay_Jay70Commented:
Hi Gavin5511,

you will get the option on boot of which partition to load, choose windows 2003

once in the osyou will be able to access any data off the other drives and move to your new install - from there you can format the old drives using computer management and in needed - i doubt it though - you can edit your boot.ini file to ensure it only looks for your 2003 machine
   good luck

Cheers!
0
 
Gavin5511Author Commented:
will i also be able to change format the C: to remove windows 2000, and then swap drive letters so F: now becomes c:? how would i do this?
0
 
MaasdrielCommented:
It is possible. You will have to remove the first C: partition. This way the second disk will have the first recognized partition for windows wich in return will name it C:


So, remove the C: partion of the first disk.
Reinstall Windows 2003 Server
Now the formerly E: drive should be called C:.
After the installation of the OS, partition the first disk and chose a drive letter for it.

This is all on the assumption that your D: is something like a CD/DVDROM if this is a partion this method won't work.

Hope this helps.
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
MaasdrielCommented:
A second method is.

Assuming you are using a SCSI change the SCSI ID on 17 gig disk to ID 0

Assuming you are using IDE make sure the 17 gig disk is Primairy master.

Greetings Maasdriel
0
 
MaasdrielCommented:
Sorry for the tripple post.

The second method includes reinstalling Windows 2003 Server. NOTE SCSI: if the 8gig hard disk uses ID0 currently change this to a free ID if you use ID0 on the 17 gig HD.

There's no method that i know of changing the boot driveletter after install.
0
 
Jay_Jay70Commented:
be careful changing the C: drive letter - windows is not in any way a Fan of changing its system drive letter.......
0
 
MaasdrielCommented:
I agree with Jay Jay this is what i meant with no able to change the boot driveletter after install.
The reason for this is that windows has pointers to critical files and loads of other things still pointing to the old driveletter wich in return Windows will not function properly.

This is why you have to reinstall Windows 2003 Server in both options but with these methods you will give you the chance to install a new Windows 2003 Server on a C: partition on the 17 gig harddisk. With a new installation everything will be working properly.
0
 
MaasdrielCommented:
Gavin Do you have any questions related to the anwsers that were given ?
0

Featured Post

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

  • 5
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now