[THIN] KB: CTX457309 - MetaFrame/Presentation Server Drive Remapping Best Practice
- From: "Jim Kenzig http://Kenzig.com" <jkenzig@xxxxxxxxx>
- To: thin@xxxxxxxxxxxxx
- Date: Sat, 1 Oct 2005 18:27:45 -0700 (PDT)
Old one but recently updated:
JK
CTX457309 - MetaFrame/Presentation Server Drive Remapping Best Practice
This document was published at:
http://support.citrix.com/kb/entry.jspa?externalID=CTX457309
Document ID: CTX457309, Created on: Nov 28, 2000, Updated: Sep 30, 2005
Products: Citrix MetaFrame XP 1.0 for Microsoft Windows 2000, Citrix MetaFrame
XP 1.0 for Microsoft NT 4.0 Server Terminal Server Edition, Citrix MetaFrame
1.8 for Microsoft Windows 2000, Citrix MetaFrame 1.8 for Microsoft NT 4.0
Server Terminal Server Edition, Citrix MetaFrame XP 1.0 for Microsoft Windows
2003, Citrix MetaFrame Presentation Server 3.0 for Microsoft Windows 2000,
Citrix MetaFrame Presentation Server 3.0 for Microsoft Windows 2003, Citrix
Presentation Server 4.0 for Microsoft Windows 2000, Citrix Presentation Server
4.0 for Microsoft Windows 2003
In Windows 2003 and earlier, more and more services use their own databases
rather than the registry to store information. Examples of this are IIS, Active
Directory, File Replication Services, Disk Configuration information, and the
COM+ Catalog.
The Citrix server drive remapping mechanism available with MetaFrame 1.8
Service Pack 2 for Windows 2000 can scan the registry and COM+ Catalog to
change drive letters. See Page 21 of MetaFrame 1.8 Service Pack 2 for Windows
2000 Installation Guide for specifics.
For MetaFrame XP or later, see the Windows Administrator's Guide for the latest
information.
Windows 2000 and 2003 Dynamic Disks
Attempting to remap drives on Dynamic disks will not work. Because the drive
remap utility is run during/before the MetaFrame or Presentation Server
installation, it is currently necessary to convert from Basic disk to Dynamic
disks after remapping the server drives.
Best Method of Installation
1.
Install Windows 2000 or Windows 2003 with no additional configuration, such as
Active Directory, Dynamic Disks, IIS (the IIS localhost page may not be
displayed after drive remapping), File Replication Services, and so on. Run the
driveremap.exe or equivalent utility for your MetaFrame or Presentation Server
product.
2.
Install MetaFrame 1.8 or later for Windows 2000 or 2003 selecting the desired
drive remapping.
3.
Install MetaFrame 1.8 Service Pack 2 (Step 3 is not required for MetaFrame XP
and later) and run the additional drvremap utility options listed below
(excerpt from Page 21 of the Service Pack Installation Guide):
The COM+ Catalog did not get updated if the Drive Remapping option was used
during MetaFrame 1.8 for Windows 2000 installation. To update the COM+ Catalog,
perform the following steps (assuming your original drive is C and your new
drive is M). If that is not the case, substitute the correct drive letters for
C and M. This fix applies only to MetaFrame 1.8 for Windows 2000 servers.
Log off all users and then log on as an administrator on the console.
At a command prompt, map your old drive to your new drive by typing:
subst C: M:\
At a command prompt, update your COM+ Catalog by typing:
drvremap /drive:M /remap /com
At a command prompt, unmap your old drive by typing:
subst C: /d
Reboot the system.
4.
Configure additional Microsoft Services, including Dynamic disk.
Microsoft IIS 5.0 May Not Function Properly after Installing MetaFrame 1.8 for
Windows 2000 and Remapping Drives
Default Web site > Properties > Home Directory > Local Path shows the path is
correct; that is, M:\inetpub\wwwroot, where M is the name of your remapped
drive C.
Default Web site > Properties > Home Directory > Local Path-> Configuration
Button > Application Mappings.
The executable path is correct with the remapped drive letter.
The IIS directory structure is correct but there may be DCOM error 10010 in the
Event Viewer.
Attempt the below resolution on a MetaFrame 1.8 server. Complete the following:
1. Remove IIS 5.0.
2. Install Service Pack 2 for MetaFrame 1.8.
3. Follow the previous steps to repair the COM+ Catalog.
4. Install IIS 5.0.
Reversing the Citrix Server Drives Remapping Process after Installing MetaFrame
1.8 for Windows 2000
During the installation of MetaFrame 1.8 for Windows 2000, there is an option
to remap the server drives. If the need arises to reverse the drive remapping
when installation is complete, use the following command-line utility:
drvremap /unmap /drive:M /iis /physical /registry /Ads /fixlinks /com
where M is the selected drive letter where remapping commences. Change this to
the drive letter you selected during the installation of MetaFrame 1.8 for
Windows 2000.
Note: Use this command for testing purposes only because Citrix cannot test
every possible configuration that a customer may have. Not all drive references
may be removed.
Unable to Log onto Console after MetaFrame Reboots
This usually occurs when drives were remapped during the MetaFrame
installation. For more information about this subject, see Microsoft article:
Q249321.
How to Change Boot Drive Letter after Remapping the Server Drives During a
MetaFrame Installation
This section describes how to change the system or boot drive letter in Windows
NT 4.0 or Windows 2000 after the MetaFrame installation remaps the server
drives. For the most part, this is not recommended, especially if the drive
letter is the same as when Windows NT 4.0 or Windows 2000 was installed. Q223188
Unable to Remap Server Drives in MetaFrame 1.x
Installing Microsoft Terminal Server 4.0 and creating fault tolerant
configurations before installing MetaFrame can cause issues when attempting to
remap the server drives during MetaFrame installation.
Remapping the server drives during MetaFrame installation is comparable to
using Disk Administrator under Windows NT 4.0. Therefore, the concerns
applicable when using Disk Administrator must be considered when configuring
MetaFrame. The best practice is to install Terminal Server, install MetaFrame
with the appropriate drive mappings, and then use Disk Administrator to
configure the disks accordingly.
Reversing Drive Mappings on MetaFrame 1.x and MetaFrame XP for Microsoft
Windows Terminal Server 4.0, after the initial installation, is not supported.
More Information
WARNING! Using Registry Editor incorrectly can cause serious problems that may
require you to reinstall your operating system. Citrix cannot guarantee that
problems resulting from the incorrect use of Registry Editor can be solved. Use
Registry Editor at your own risk.
If you intend to change a server?s drive letters, do it during MetaFrame XP
installation. If you change server drive letters after installing MetaFrame 1.x
or MetaFrame XP, you must do it before installing any applications. If you
change the server?s drive letters, MetaFrame XP searches the following registry
keys and changes all drive references to reflect the new drive letters:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\*
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\*
HKEY_LOCAL_MACHINE\SOFTWARE\Equinox\eqn\CurrentVersion\NetRules
HKEY_LOCAL_MACHINE\SYSTEM\*
HKEY_CLASSES_ROOT\*
HKEY_USERS\*
MetaFrame XP also updates the pagefile entry and the following shortcut files:
%SystemRoot%\Profiles\Default User\*.lnk
%SystemRoot%\Profiles\Administrator\*.lnk
%SystemRoot%\Profiles\All Users\*.lnk
The first time a user logs on to the MetaFrame server after you change the
drive letters, references to the old drive letters in the user?s profile are
updated.
In addition, removing MetaFrame from Microsoft Windows Terminal Server will not
remap the server drives. If you reinstall MetaFrame, you are not prompted to
remap server drives.
Thus, the only supported way to return the server drives to their original
drive letters is to reinstall Microsoft Windows Terminal Server. Once
completed, reinstall MetaFrame
Other related posts:
- » [THIN] KB: CTX457309 - MetaFrame/Presentation Server Drive Remapping Best Practice
