| With the release of Feature Release 2, Citrix have simplified installation by consolidating all the management tools (RM, IM, NM) on one CDROM and all of them are installed through one MSI based installation application. You also have the ability to install not only Feature Release 2 but also MetaFrame XP 1.0, all the management tools and Feature Release 2. The following are the system requirements for MetaFrame XP with Feature Release 2 Microsoft Windows 2000 Server, Advanced Server or Datacenter with Service Pack 2. 400MB for MetaFrame XPe, 250MB for ICA Client software and 50MB for the Citrix Management Console. If you have the Java Runtime Environment 1.3.1 or later installed on your system, you will need to uninstall it before installing MetaFrame XP or the Citrix Management Console. You must be logged on with local administrator privileges. You will need to know which version of MetaFrame XP you are licensed for MetaFrame XPs, XPa, or XPe. MetaFrame setup is really broken down in to the following three phases. Upgrade the Windows Installer Service Remap Server drives (if required but I dont recommend it) Install MetaFrame XP with Feature Release 2 Note: MetaFrame XP with Feature Release 2 is a cumulative Feature Release containing all the features and bug fixes found in Feature Release 1 and Service Pack 1, when an FR2 license is added is also adds a FR1 license. The following steps detail how to install MetaFrame XP with Feature Release 2
The first thing you will need to do to install MetaFrame XP with the new MSI installation program is to update Windows 2000 to Windows Installer version 2.0. The following details how to install Microsoft Windows Installer Service 2.0. 1. Browse to the \support\msi20\ folder on the MetaFrame XP Feature Release 2 server CD and double click instmsiw.exe. 
2. Setup will update the Windows Installer Service and prompt you to click OK to continue. Note: If you experience any errors, please refer to the Windows Event Log. 3. Click Yes to reboot the server.
Unlike MetaFrame installation prior to MetaFrame Feature Release 1 and below, if you will be remapping server drives on a MetaFrame server you will need to run the DriveRemap.exe utility located on the root of the MetaFrame XP Feature Release 2 Server CDROM. If you will be remapping drives then it is highly recommended to do so before you install MetaFrame XP or upgrade to Feature Release 2. If you remap server drive letters after installing or upgrading, then will need to do so before installing any application or run the risk of server instability. Beware! If the server is a member of a Windows 2000 Active Directory Domain, driveremap.exe will hang. Move the server into a workgroup, remap the drives, and then rejoin the Active Directory domain. Note: In my option, I would be careful remapping drives. As discussed in the Analysis phase of this document, we dont want to plan for today but for tomorrow and with this in mind, I have always taken the mindset that I dont know what applications or system service/devices that might need to be installed in the future who requires the server drives to start with C:. Granted there are a few workarounds, I still tend to believe in training my users once, vs. running the risk of needed to change it in the future which would require end-user re-education. Note: It is not recommended to run the Drive Remap utility after installing MetaFrame XP with Feature Release 2. The following defines how to remap server drive letters. 1. Insert the MetaFrame XP with Feature Release 2 Server CD and open to the root of the CDROM in Windows Explorer and double click on the DriveRemap.exe utility. 
2. Select the the drive letter you want to remap the C: drive to in the New drive letter drop down box and click OK. 
3. The drives with now be remapped and links reconfigured. 
4. Click Yes to restart the server in order for the drive remapping to take page. 
Note: If you intend to change the servers drive letters, it is required to do so before you install MetaFrame XP. If you change server drive letters after installing MetaFrame XP and any application then you run the risk of the applications not functioning properly and a server rebuild would be required to remedy the issue. Important! Cloning MetaFrame servers can be tricky and hence another great reason why I recommend against remapping drives.
You can unmap drives by running the DriveRemap User Interface, or from the command line, to map back to the original drive letters. For example, if you have mapped C: to M:, you can run the utility and map M: back to C: or even to a different available drive letter. To do this from the command line: driveremap /u /drive:M /drive:C Note:: It is recommended to reboot the server in this example. Note: The usage of this utility is currently not present as an option in the MSI packages or when using the Citrix Unattend.exe methods of FR2 installation. However, the /u option is available to allow the usage of the utility in a script or batch file without prompting for input. The following parameters can be used with driveremap.exe at a command line. | Option | Description | | /? | Displays a dialog box with the available command line options.
NOTE: The same dialog is displayed if there is incorrect usage of any of these parameters. | | /drive:M | Specifies the drive letter to use for the first remapped drive.
NOTE: The drive letter must be in Upper case when using the version of this utility that ships with FR2. | | /u | Allows for an Unattended or Silent install where no dialog boxes are displayed and no user input is required.
NOTE: This option must be used in conjunction with the /drive: option. | | /noreboot | Suppresses the "Restart Computer" dialog box and does not restart the system.
NOTE: It is strongly recommended that the system be restarted after running the utility. | | /ime[filename] | For Japanese IME. Changes the drive letter specified in Software\Microsoft\Windows\CurrentVersion\Ime\Japan\IMEJP\Dictionaries for all of loaded hives under HKEY_USERS. | Examples:
The following command will remap the servers drives starting with the first available drive to M: and not display any dialog boxes or require any input. driveremap /u /drive:M /noreboot The following command will remap back the drive letters to start at C: and then prompt for a reboot. driveremap /u /drive:M /drive:C
The drive letter must be in Upper case when using the version of this utility that ships with FR2. A newer version that is not case-sensitive is available from Citrix Support. If the server is a member of an Active Directory Domain, driveremap.exe will hang, during its processing of "Fixing ADS links...", with the version of this utility that ships with FR2. A dialog box may pop up with the error text, "Unknown Window error". The current workaround is to move the server into a workgroup, remap the drives, and then rejoin the ADS domain. A newer version that does not require the use of the workaround is available from Citrix Support. When running driveremap.exe with no parameters, the drive letter choices in the pull down list may be grayed out. This happens because some aspect of being able to remap the existing drive letters cannot be done. Some reasons for this are: Non-contiguous drive letters, for example - C, D, X. the mapped drive letters are spread over the interval [a..z] and no reasonable interval shifting can be performed. Shifting C to M is a shift of 10. Drive letter X would not be able to shift 10 letters and wrap around the alphabet. Even Network Drives are taken into account. Change the drive letters to C:, D:, E: and re-run the utility. At the command prompt, if you silently remap to a letter that is IN USE, such as a mapped network drive, nothing will happen. The process just returns to the prompt. To see if mappings take place, launch Windows Explorer. Citrix Server drive remapping is not supported on Windows 2000 Dynamic Disks. These issues are From the SP2-FR2_readme.txt that can be found in root of the FR2 package and in the list of FR2 Docs after installation. INSTALLATION OF "TURNKEY" NFUSE CLASSIC MAY FAIL IF UPGRADING ON SERVER WITH REMAPPED DRIVES If you are upgrading to MetaFrame XP, Feature Release 2 from MetaFrame 1.8 for Windows 2000 and the server has remapped drives, the installation of NFuse Classic may fail. To fix the problem, you must update the servers COM+ catalog. See article CTX240747 on the online Citrix Knowledge Base at http://www.citrix.com/support for more information. UPGRADING FROM METAFRAME 1.8 ON A SERVER WITH MAPPED DRIVES DOES NOT UPDATE ICA WIN32 PASS-THROUGH CLIENT If you upgrade from MetaFrame 1.8 to MetaFrame XP on a server with changed server drive letters, the ICA Win32 pass-through Client. To avoid this issue, be sure the server is operating in install mode before running Setup. To update the pass-through client, install the "stand-alone" version of the pass-through client.
With the release of MetaFrame XP with Feature Release 2, Citrix not only changed the installation look and feel but they also made it cumulative. I mean, no longer do you need to install each component separately or are you required to install MetaFrame XP 1.0, then Feature Release 1, the MetaFrame for XP for Windows Feature Release 2 installation program will do it for you. The following defines how to install MetaFrame for XP with Feature Release 2. 1. Insert the MetaFrame XP for Windows, Feature Release 2 Server CD and when the following screen pops up click the Install or update MetaFrame button. 
2. Click the MetaFrame XP Feature Release 2 button to launch the setup program. 
3. Click Next to continue. 
4. Click the I accept the license agreement radio button and click Next to continue. 
5. You are now prompted to select the correct MetaFrame family member you have licenses. This is important you select the correct product family member that corresponds to the license number you will be entering in later or you might experience problems later. Click Next when finished. 
6. You are now prompted to select the product type for which you are licensed. Select the proper Product code and click Next. Note: This information will be found on the CD license label. For this example, I am installing a Retail version 
7. You are now prompted to select the components you will be installing. If you will be installing Installation Manager, I highly recommend removing the Packager component. Open the Installation Manager Key and right click on Packager and click X Entire feature will be unavailable. 
8. Click Next when you are finished selecting components 
9. You are now prompted to create or join a server farm. Click the Create a new farm radio button and click Next. 
10. Enter a server farm name in the Farm Name text box and select what type of Data Store that will be used as documented in the Data Farm Design section of the Design Phase Deliverable. You also have the ability to select the Zone the new server will exist. For the first server in a farm I highly recommend using the default zone name. Click Next when finished. 
11. For this example, I have chosen a SQL Server as my Data Store so the next screen will prompt you to create the ODBC connection to the Data Store. Enter a description in the Description text box and select the SQL Server from the Server drop down list. When finished click Next. 
12. You are now prompted to select the authentication method. Click to select the With SQL Server authentication using a login ID and password entered by the user radio button. Enter the username and password that was entered in step 6 of the How to Create a MetaFrame XP Data Store with SQL Server 2000. Click the Client Configuration button. 
13. Verify the TCP/IP radio button is selected. If not, then click to select it and click OK. 
14. Verify the database created above is selected as the default database and click Next. If it is not already selected then click to check the Change the default database to checkbox and select the XP Data Store database and click Next. 
15. Click Finish 
16. Click the Test Data Source button. 
17. Verify it reads TESTS COMPLETED SUCCESSFULLY and click OK. 
18. You are now prompted to enter a user account to assign Farm Administrator access. I recommend accepting the default and adding / editing Farm Administrators later. As documented in the MetaFrame Delegated Administration section. Click Next when finished. 
19. You are now prompted to select how MetaFrame will deal with shadowing. Unless your customer requires disabling Shadowing support I recommend to accept the defaults and click Next to continue. Note: I recommend accepting the default and with the use of policies, you will be able to assign shadowing rights on a user and or group basis. 
20. Enter the TCP/IP port that the Citrix XML Service will listen on and Click Next. Note: The default is port 80 and unless you have a reason for doing so, I recommend that you stick with the default across all servers in the farm. 
21. If you will be running NFuse on the same server as MetaFrame and or neglected to remove IIS during install then NFuse 1.71 will automatically be installed during setup. This screen asks whether you want your users to be able to browse to the root of your server (http://myserver) instead of requiring adding the path. This requires that you will not be presenting other data on this web server via browsing this URL. When finished click Next. 
22. Verify the farm and installation settings are correct and click Finish. 
23. Uncheck the View the Readme File checkbox and select the Launch the ICA Client Distribution wizard and click Close to continue 
24. The ICA Client Distribution wizard opens. Click Next to continue. 
25. Click Next 
26. You are now prompted to select the ICA client ICA installation type. Click the Typical radio button and then click Next. 
27. Click Finish. 
28. Reinsert the Citrix MetaFrame XP Feature Release 2 Server CD and click OK. 29. Click Yes to restart the server and complete the installation of MetaFrame XP with Feature Release 2
The following details how to upgrade an existing MetaFrame server to Feature Release 2. 1. As a best practice, I recommend you disable any virus software that might be running. 2. Inset the Citrix MetaFrame XP with Feature Release 2 CD, the Citrix MetaFrame XP for Windows Feature Release 2 splash screen will appear. Click the Install or update MetaFrame button. 
3. Click the MetaFrame XP Feature Release 2 button. 
4. Click Next to continue. 
5. Click the I accept the license agreement radio button and click Next to continue. 
6. Click Yes to current with the upgrade of the current MetaFrame server. 
7. Click Finish. 
8. Click the Launch the ICA Client Distribution wizard checkbox in order to upgrade the ICA Client update database to the 6.30 version. Insert the MetaFrame XP Components CD and click Close. 
9. Click Next to continue to load the latest ICA Clients. 
10. Click the Typical radio button and click Next to continue. 
11. Click Yes to restart the server and complete the installation of MetaFrame for Windows, Feature Release 2. 
You have now successfully upgraded to MetaFrame with Feature Release 2.
The following details how to add additional MetaFrame XP servers to an existing Farm. 1. Insert the MetaFrame XP for Windows, Feature Release 2 Server CD and when the following screen pops up click the Install or update MetaFrame button. 2. Click the MetaFrame XP Feature Release 2 button to launch the setup program. 3. Click Next to continue. 4. Click the I accept the license agreement radio button and click Next to continue. 5. You are now prompted to select the MetaFrame family member you have the correct license for. This is important you select the correct product family member that corresponds to the license number you will be entering in late or you might experience problems later. Click Next when finished. 6. You are now prompted to select the product type for which you are licensed. Select the proper Product code and click Next. Note: This information will be found on the CD license label. For this example, I am installing MetaFrame XPe. 7. You are now prompted to select the components you will be installing. If you will be installing Installation Manager, I highly recommend removing the Packager component. Open the Installation Manager Key and right click on Packager and click X Entire feature will be unavailable. 8. Click Next when you are finished selecting components 9. You are now prompted to create or join a server farm. Click the Join an existing farm and click Next. 
10. Select the type of Data Store that will be used as documented in the Data Farm Design section of the Design Phase Deliverable. You also have the ability to select the Zone the new server will be a part of. For the first server in a farm I highly recommend using the default zone name. Click Next when finished. 
11. For this example, I have chosen a SQL Server as my Data Store so the next screen will prompt you to create the ODBC connection to the Data Store. Enter a description in the Description text box and select the SQL Server from the Server drop down list. When finished click Next. 12. You are now prompted to select the authentication method. Click to select the With SQL Server authentication using a login ID and password entered by the user radio button. Enter the username and password that was entered in step 6 of the How to Create a MetaFrame XP Data Store with SQL Server 2000. Click the Client Configuration button. 13. Verify the TCP/IP radio button is selected. If not then click to select it and click OK. 14. Verify the database created above is selected as the default database and click Next. If it is not already selected then click to check the Change the default database to checkbox and select the XP Data Store database and click Next. 15. Click Finish 16. Click the Test Data Source button. 17. Verify it reads TESTS COMPLETED SUCCESSFULLY and click OK. 18. You are now prompted to select how MetaFrame will deal with shadowing. Unless your customer requires disabling Shadowing support I recommend to accept the defaults and click Next to continue. 19. Enter the TCP/IP port that the Citrix XML Service will listen on and Click Next. The default is port 80 and unless you have a reason for doing so, I recommend that you stick with the default across all servers in the farm.
20. If you will be running NFuse on the same server as MetaFrame and or forgot to remove IIS during install then NFuse 1.71 will automatically be installed during setup. This screen asks whether you want your users to be able to browse to the root of your server (http://myserver) instead of requiring adding the path. This requires that you will not be presenting other data on this web server via browsing this URL. When finished click Next. 21. Verify the farm and installation settings are correct and click Finish. 22. Click Close to continue You have now successfully added an additional MetaFrame server to the farm. Repeat the above steps until all implementation phase servers are installed. Note: The first time any additional MetaFrame servers are added to a farm it could take a few minutes to log in. This only occurs on the first reboot.
The following defines how to modify the installed MetaFrame XP Components.
1. Click Start click Settings click Control Panel Click Add/Remove Programs you are now prompted with a list all the applications installed on the MetaFrame server, select Citrix MetaFrame XP for Windows, Feature Release 2 and click the Change button. 
2. Click the Modify radio button and click Next. 
3. Click Next when you are finished selecting components. I recommend that you NEVER install the Installation Manager Packager component on a MetaFrame application server in production. This component is meant for a dedicated server. 
4. Verify the selection and click Finish to complete the changes. 
You have now successfully added/removed components of MetaFrame XP with Feature Release 2.
Now that you have successfully installed MetaFrame XP with Feature Release 2, you will need to install the appropriate MetaFrame licenses. MetaFrame XP licensing consists of several licensing codes, which are strings of characters that you use during the licensing process. When you add the licenses to the server farm for the first time, you will need to enter a MetaFrame XP 1.0 server and connection license. If you will be deploying or upgrading to Feature Release 2 then you will also need to install a server and connection license. You will find those licenses on the inside label of the Citrix software package and if you will be upgrading you will be able to retrieve and fulfill the subscription advantage membership through www.mycitrix.com Citrix software generates other strings that you use in connection with Citrix licensing. The following details how to install the necessary MetaFrame XP with Feature Release 2 licenses. 1. Being this is the first time you will be launching the Citrix Management Console after the install of Feature Release 2 you will notice a new feature, Pass-Through Authentication. When you enable pass-through authentication, Citrix Management Console uses your local workstations user credentials and passed it through to the server. You can log on without re-entering credentials. Check the Enable pass-through authentication checkbox and click the appropriate radio button to select the MetaFrame server you will be connecting to. I highly recommend connecting to a data collector to give you the best performance with the least amount of network traffic. Click OK when finished. 
2. Right click Licensing and click Add License. 
3. Enter the Serial Number. Remember you will need both a server and connection license for both MetaFrame 1.0 and Feature Release 2. FR2 will automaticly load Feature Release 1 licenses. 
4. Click No because you will activate the license later. 
You have now successfully added the appropriate licenses. Remember you have 35 days to activate the license or you the server will stop accepting connections. |