Install W2k3 on different system/boot volume

  • Thread starter Thread starter Chris Hall
  • Start date Start date
C

Chris Hall

I'm trying to install Windows server 2003 on a different drive other than
the standard system/boot volume C:. An application that I need to get
installed requires that the C: drive basically does not exist, so that an
individual accesses the server with terminal services and the application
maps a profile for that user on C:. Sounds weird, huh? The application
wasn't originally built for Windows and the client I'm working with doesn't
want to use Linux (it used to exist on a Novell box, then NT 4, which they
were able to install the OS without a C: drive). The vendor of the
application is in the process of writing a newer, friendlier application,
but will take six months. My client wants a solution now. Not sure if I
explained this well...

Thanks for any input.
Chris
 
Sorry doesn't make sense. You can't map a drive to a nonexistant drive.

You can install *system to c: and boot to d: then take away users access
[not OS access] from c:
Might want to ask how they did the NT install.

*confusing but in MSspeak boot is where the windows folder resides and
system is where the boot files reside.
 
Hi Joshua,

I agree. Doesn't quite make sense. From what I understand, a virtual C:
directory is created and then the application maps to that virtual
directory, so if there's already a C: partition, the application sees that
C: is already taken, therefore can't use it and bombs out. Seems like it
wouldn't take that much effort to change that to Z: or whatever....but I'm
not a programmer.
 
Chris said:
I'm trying to install Windows server 2003 on a different drive other than
the standard system/boot volume C:. An application that I need to get
installed requires that the C: drive basically does not exist, so that an
individual accesses the server with terminal services and the application
maps a profile for that user on C:. Sounds weird, huh? The application
wasn't originally built for Windows and the client I'm working with doesn't
want to use Linux (it used to exist on a Novell box, then NT 4, which they
were able to install the OS without a C: drive). The vendor of the
application is in the process of writing a newer, friendlier application,
but will take six months. My client wants a solution now. Not sure if I
explained this well...

Thanks for any input.
Chris
Click to expand...


Two things to try ...

1. Windows places its boot files on the active partition. If that
partition happens to not be the first partition then the boot files
won't be on the first partition. But if you don't have a 3rd party app,
like Partition Magic for example, that can be difficult to prearrange.

2. Two individual installs will get around this problem. Install any
version of Windows to C: and then install server where you want it.
Afterward make the partition with the Server install the active
partition and copy the boot files from C: to there. Edit boot.ini and
delete the C: install (after testing that you got what you need of course).

John
 
Back
Top