| Now that you have successfully installed MetaFrame XP Server with Feature Release 3, 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 3 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 3 licenses. 1. Being this is the first time you will be launching the Management Console for MetaFrame XP after the install of Feature Release 3 you will notice a new feature, Pass-Through Authentication. When you enable pass-through authentication, Management Console for MetaFrame XP 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 XP 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 MetaFrame XP or Citrix MetaFrame Conferencing Manager serial number. Remember you will need both a server and connection license for both MetaFrame 1.0 and Feature Release 3. FR3 will automaticly load Feature Release 1 and 2 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. You are now ready to install the applications that were specified as image application during the Applications section of the Design phase. In order to install an application on a Terminal Services server you need to configure the server for install mode. Terminal Services uses a special installation mode for installing applications for multi-user use. This mode is activated by installing an application through the Control Panel Add/Remove Programs applet or by using the command "Change User /Install" prior to installing an application. Once you have finished installing the application you are required to return to normal execution mode by using the command "Change User /Execute". The default Terminal Services mode is Execution mode. The server starts in Execution mode when you start the system. The system is not operating in a global fashion when it is in Execution Mode. That is, the system expects many concurrent user sessions. This requires that the system keep sessions completely separate from each other, including the user at the system console. For instance, every user has a Windows and Windows\System directory that no one else uses. If an application requests the location of the system root, the system will point the application to the user's Windows directory rather than the actual Terminal Services system root. The following is the command switch available for the change user command. | Y:\>change user /? Change Install Mode. CHANGE USER {/EXECUTE | /INSTALL | /QUERY} /EXECUTE Enable execute mode (default). /INSTALL Enable install mode. /QUERY Display current settings. | Important! If you will be implementing client to server content redirection and you install an application(s) that you would like to take advantage of client to server redirection with then you will need to update the IMA data store with the latest file types from the local registry. To do this right click on the server that the application(s) were installed on and click Update File Types from Registry or right click on the Farm node and click Update File Types from Registry. Rapid deployment of MetaFrame XP Servers gives you the following benefits. The ability to deploy a MetaFrame XP Server in minutes rather than hours The ability to guarantee consistency amongst MetaFrame XP Servers You can accomplish this through server cloning or scripted unattended installations as documented below. Note: With the release of MetaFrame XP with Feature Release 3, the installation application is a Microsoft Installer package that gives us the ability to create .mst files for rapid deployment. I will be documenting this for the next release.
|