S
SnorkyTheWeasel
Guest
Windows 2003 Server - Terminal Services - Drive Mapping
Not your usual drive mapping issues.....
Objective:
* Make the server's D: Drive appear to the client as the C: Drive.
* Make the remote terminal's CD-ROM Drive appear to the client as the D:
[/b]Drive.
* The remote terminal's C: drive can be mapped to anything ( except C: D: H:
). We store user data and profiles on the H: Drive, which is mapped to
Current Condition:
* The server's C: Drive is for system files.
* The server's D: Drive is for everything else.
Reason:
Install educational software on the server so that students using TS can
access the software from their TS clients. (Note: the licensing issues are
already resolved)
The problem:
* A lot of old and/or badly designed software assumes that the installation
is occurring on the C: Drive, and allows no deviation from that. I could
simply install the badly-designed software on the server's C: Drive, where
all of the system files are located.
* Likewise, that old and/or badly designed software also assumes that the
installation CD is in the D: Drive, and allows no deviation from that. For
purposes of installation, I need to be able to install software from a remote
desktop, using the remote's local CD Drive.
* Installing software on the system drive is inviting trouble - letting
rogue software work its magic on the system files.
Thoughts, Random But Possibly Relevant
For a couple of years I used "virtual drive" software that functioned as a
sort-of-jukebox for serving up programs. When it worked, it was great.
However, its database was easily corrupted and was a constant administrative
headache.
I haven't been able to find what I need on the 'web, in MS documentation,
and in our library of after-market Windows Server 2003 books. Surely this is
feasible with Terminal Services, given that Citrix had this functionality 10
years ago. MS is usually only a few years behind Citrix when it comes to
features.
Not your usual drive mapping issues.....
Objective:
* Make the server's D: Drive appear to the client as the C: Drive.
* Make the remote terminal's CD-ROM Drive appear to the client as the D:
[/b]Drive.
* The remote terminal's C: drive can be mapped to anything ( except C: D: H:
). We store user data and profiles on the H: Drive, which is mapped to
Current Condition:
* The server's C: Drive is for system files.
* The server's D: Drive is for everything else.
Reason:
Install educational software on the server so that students using TS can
access the software from their TS clients. (Note: the licensing issues are
already resolved)
The problem:
* A lot of old and/or badly designed software assumes that the installation
is occurring on the C: Drive, and allows no deviation from that. I could
simply install the badly-designed software on the server's C: Drive, where
all of the system files are located.
* Likewise, that old and/or badly designed software also assumes that the
installation CD is in the D: Drive, and allows no deviation from that. For
purposes of installation, I need to be able to install software from a remote
desktop, using the remote's local CD Drive.
* Installing software on the system drive is inviting trouble - letting
rogue software work its magic on the system files.
Thoughts, Random But Possibly Relevant
For a couple of years I used "virtual drive" software that functioned as a
sort-of-jukebox for serving up programs. When it worked, it was great.
However, its database was easily corrupted and was a constant administrative
headache.
I haven't been able to find what I need on the 'web, in MS documentation,
and in our library of after-market Windows Server 2003 books. Surely this is
feasible with Terminal Services, given that Citrix had this functionality 10
years ago. MS is usually only a few years behind Citrix when it comes to
features.