Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

FR2 change local drive name

Status
Not open for further replies.

Traver

MIS
Aug 9, 2002
126
DK
I just installed a new server using the cd kit with MFe feature release 2 upon it. When I was finished it struck me that I had not changed the C: drive into M: But I was never given the option. Enyboby know a solution ?
 
It is not recommended to remap server drives after installing MetaFrame (any version). The option is given during the installation process, directly after clicking Install or Update MetaFrame, or you can manually run the program driveremap.exe which is installed as part of MetaFrame so that you can change existing remappings, not create new ones, e.g driveremap /u /drive:M /drive:C.

It should be a straightforward matter of uninstalling MetaFrame then re-installing.

For more information, refer to CTX950520

CitrixEngineer@yahoo.co.uk
 
Just as an additional thought, I have been forced to try this on several occasions because of poor communications within our IT department, and every time I try it, I end up rebuilding the server. I would go so far as to say DO NOT remap drives after installing Citrix (not just it is not recommended). I have had such problems with remapping drives after the fact, that I make it my third step in the process after the OS install and the pagefile setup. I do it before I install any other software of any sort. This may be common knowledge to this forum, but I wanted to reiterate the point.
 
I once faced te problem. I remapped the whole darn thing wrong. After removing Citrix and then reinstalling Citrix didn't give me the option anymore to remap.

Our policy here, by the way, is not to remap drives. When you want to restore a server that has been crashed gives you a lot more problems to get corrected then explaining the users to use v: and w: for their local c: and d: drives. But this is merely a policy we maintain... :)
 
Oops, should have mentioned that driveremap is unique to FR2 - it had a different name in 1.0 and FR1. The ACG (Advanced Concepts Guide) covers in detail why you should not map drives after installation or on imaged servers. Guess that means if you're going to clone MF servers, don't remap the drives...

My users are generally too set in their ways to use drives other than C: and D:, so I always remap the server drives, and only image the server with O/S and Apps pre-installed. It's not too arduous to install MF from a network share via a section in the imaging script - you can include the driveremap command in there :) CitrixEngineer@yahoo.co.uk
 
Well just to spice up the story. I removed MFe SP2 and got several errors. In the end the puter told me to insert my w2k cd, because vital things was missing, and had been replaced by files that was wrong.
I put in the w2k cd, and it goes....no wrong cd. After trying different versions of w2k. I said cancel.
Now I can´t boot the server. It is missing a ntoskrnl.exe file......probaly not the only thing it is missing.

I belive I can start from point 0 again.

I am thinking about mapping the other servers back to c:
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top