| Now that we have prepared the network, installed and configured the data store, upgraded the Installer Service and remapped the drives, if required, we are ready to install MetaFrame XP Server with Feature Release 3. If you have decided to install FR3 on a Microsoft Windows Server 2003 then perform the following installation instructions. The following defines how to perform a clean install of Citrix MetaFrame XP with Feature Release 3 to act as the data store server or a regular member server, if you will be using Microsoft SQL Server, Oracle or IBM DB2 and the data store, on Microsoft Windows Server 2003. Note: These procedures are almost identical to installing MetaFrame on a Windows 2000 Server. For screen shots please refer to the How to Create a New MetaFrame with Feature Release 3 Farm section, found above. 1. Insert the MetaFrame XP for Windows, Feature Release 3 Server CD and when the following screen pops up click the Install or update MetaFrame button. 2. Click the MetaFrame XP Feature Release 3 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 MetaFrame XP 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. 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. 12. 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. 13. 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. 14. With the release of Windows Server 2003, Microsoft has locked the system down to where you are required to add users to the Remote Desktop Users group. Select the appropriate settings and click Next to continue.  15. Verify the farm and installation settings are correct and click Finish. 16. Uncheck the View the Readme File checkbox and select the Launch the ICA Client Distribution wizard and click Close to continue 17. The ICA Client Distribution wizard opens. Click Next to continue. 18. Click Next 19. You are now prompted to select the ICA client ICA installation type. Click the Typical radio button and then click Next. 20. Click Finish. 21. Reinsert the Citrix MetaFrame XP Feature Release 3 Server CD and click OK. 22. Click Yes to restart the server and complete the installation of MetaFrame XP with Feature Release 3 You have now successfully installed Citrix MetaFrame XP Server with Feature Release 3 on a Microsoft Windows Server 2003. You are ready to move forward with tuning the server and installing applications. The following details how to add additional MetaFrame XP servers to an existing Farm. 1. Insert the MetaFrame XP for Windows, Feature Release 3 Server CD and when the following screen pops up click the Install or update MetaFrame button. 2. Click the MetaFrame XP Feature Release 3 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. Click Next when you are finished selecting components 8. Click to select the Yes radio button to give the end-user the ability for Pass-Through Authentication. Click Next to continue. 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 the farm you want to join is using and select the zone you will be joining. If you will be connecting to a Microsoft SQL Server then click Connect Directly to the database using ODBC. 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. 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. Verify the TCP/IP radio button is selected. If not then click to select it and click OK. 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. Click Finish Click the Test Data Source button. Verify it reads TESTS COMPLETED SUCCESSFULLY and click OK. If you will be connecting to a Microsoft Access or Microsoft SQL Server Desktop Engine (MSDE) data store then click to select the Connect to a database on this MetaFrame XP server radio button and enter the name of the MetaFrame XP server hosting the data store. Click Next when finished. 11. 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. 12. 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. 13. With the release of Windows Server 2003, Microsoft has locked the system down to where you are required to add users to the Remote Desktop Users group. Select the appropriate settings and click Next to continue.  14. If you will be running Web Interface on the same server as MetaFrame and or forgot to remove IIS during install of Windows 2000 Server then Web Interface 2.1 will automatically be installed during setup. This screen asks if you would like your users to be able to browse to the root of your server (http://myserver) instead of being required to add the full path (http://myserver/citrix/metaframexp) Use this is the web server is not being used in any other faction. Click Next to continue. 15. Verify the farm and installation settings are correct and click Finish. 16. Click Close to continue. We will add this server to the central ICA Client database later. 17. Click Yes to reboot the server. You have now successfully added an additional MetaFrame XP Server to the farm. Repeat the above steps until all implementation phase servers are installed. Note: The first time any additional MetaFrame XP Servers are added to a farm it could take a few minutes to log in. This only occurs on the first reboot. Microsoft Windows Server 2003 enables remote connections to the console, thus allowing the equivalent of standing in from of the server with your hands on the keyboard. Being console access, only one user is allowed at a time. The following defines how to configure Administrators console access to Windows Server 2003 servers through the Management Console for MetaFrame XP. 1. Open the Management Console for MetaFrame XP and right click on MetaFrame XP Farm node and select Properties.  2. Click MetaFrame XP Settings in the left pane and click to check the Enable remote connections to the console checkbox to enable console access and uncheck it to disable console access to all MetaFrame XP Servers in the farm.  3. If you prefer to configure remote console access the you can right click on the MetaFrame XP server of choose and click Properties. In the Remote Console Connections box you have the ability to inherit the farm settings, configured above, or you can enable or disable console access by checking or unchecking the Enable remote connections to the console checkbox.  4. If you have enabled console access you can connect to the console by right clicking on the server of choice click Launch ICA Session click Connect to Servers Console.  Windows the release of Microsoft Windows Server 2003 someone had to readdress all the tuning tips and registry changes we have made in the past, that someone was Ron Oglesby. The following procedures are just a starting point, you will to verify these changes work in your environment. For a detailed list, please check out Ron Oglesbys Tuning Tips document (2003OStips.xls ) based off of Rick Dehlingers tuning tips document. The 2003OStips.xls spreadsheet can be downloaded from: http://ron.oglesby.com/downloads.html. | Step | Description | | 1. | Remove / limit one RDP-TCP Connection in Citrix Connection Configuration Utility - Start Programs Citrix MetaFrameXP Citrix Connection Configuration Highlight rdp-tcp and press the delete key to delete the RDP connection
Or (the recommended way) - Start Programs Citrix MetaFrameXP Citrix Connection Configuration Double click RDP-TCP connection uncheck the Unlimited checkbox and enter 1 in the Maximum Connection Count text box Click OK to finish
| | 2. | Enable Auditing in Local Security Policy - Start Settings Control Panel Administrative Tools Local Security Policy applet Local Policies Audit Policies folder Select the Success/Failure events you want to audit.
- Account Logon Events: Success and Failure
- Audit Logon Events: Success and Failure
- Audit System Events: Failure
| | 3. | Clear the last persons name that logged into the server farm, from the username field of the Microsoft Client. [HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows/CurrentVersion/policies/system] DontDisplayLastUserName=1 | Registry File: DontDisplayLastUserName.reg | | | | | 4. | If you will not be using server side audio redirection then you will want to disable Client Audio Mapping [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\ICA-tcp] "fDisableCam"=dword:00000001 | Registry File: disable client audio mapping.reg | | | | | 5. | If you will NOT be using COM Port redirection then you will want to disable Client COM Port Mapping [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\ICA-tcp] "fDisableCcm"=dword:00000001 | Registry File: disable client COM port mapping.reg | | | | | Step | Description | | 6. | Disable Dr Watson [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug] "Debugger"="" | Registry File: Disable Dr Watson.reg | | | | | 7. | Disable Roaming Profile Cache [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "DeleteRoamingCache"=dword:00000001 | Registry File: Disable Roaming Profile Cache.reg | | | | | 8. | Set TcpMaxDataRetransmissions [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters] "TcpMaxDataRetransmissions"=dword:0000000a | Registry File: Increase Performance and Reliability over WAN links and the Internet.reg | | | | | 9. | Enable ErrorMode [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Windows] "ErrorMode"=dword:00000002 | Registry File: Set ErrorMode.reg | | | | | 10. | Set Event Log to overwrite entries as needed with a log size of 2MBs [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application] "MaxSize"=dword:00200000 : "Retention"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Security] "MaxSize"=dword:00200000 : "Retention"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\System] "MaxSize"=dword:00200000 : "Retention"=dword:00000000 | Registry File: Set Event Log Parameters.reg | | | | | 11. | Set User ICA-TCP Overrides [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\ICA-tcp\UserOverride\Control Panel\Desktop] "AutoEndTasks"="1" "MenuShowDelay"="10" "CursorBlinkRate"="-1" "DragFullWindows"="0" "WaitToKillAppTimeout" = "20000" "SmoothScroll" = dword:00000000 "Wallpaper" = "(none)" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\ICA-tcp\UserOverride\Control Panel\Desktop\WindowMetrics] MinAnimate"="0" | Registry File: Set WinStation Overrides.reg | | | | | Step | Description | | 12. | Disable print events from the Event Log [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Providers] "EventLog"=dword:00000000 | Registry File: Disable Logging of Print Events to the System Event Log.reg | | | | | 13. | Disable Spooler errors from being displayed on the server console [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Spooler] "ErrorControl"=dword:00000002 | Registry File: Surpress Spooler Error Messages.reg | | | | | 14. | Disable print spooler notification dialog screen from being displayed on the server console [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Providers] "NetPopup"=dword:00000000 | Registry File: Turn off NetPopup.reg | | | | | 15. | Remove Outlook Express from the Quick Launch bar and Start Menu [HKEY_LOCAL_MACHINE\ | |