| If during the Analysis and Design phase of the project you decided upon you will be installing Microsoft Office 2003 then you will be required to use the MST file during installation. This will give you the ability to customize the features you will install and allow you to configure the Outlook profile with a user specific profile. Customizing Office 2003 for a Terminal Services environment installation is possible, but you need to first understand the differences between how Office runs with a Terminal Services environment versus one that is not enabled as such. By default, almost all features in Office 2003 are enabled and installed as part of the installation. This helps reduce the number of subsequent application or feature installations an administrator might need to perform for users. Because Office, by default, is installed in a locked-down configuration, users cannot perform installations (like adding a feature), because they cannot write to the registry or application and system folders. Therefore, it is recommended to install all the applications and available features to minimize the need for further installations by the administrator. As part of an installation to a Terminal Services environment, some specific features are disabled by default because of their high bandwidth requirements for network and dial-up users. For instance, animations, sounds, and high-resolution graphics are disabled; or, in the case of high-resolution graphics, substituted with lower-resolution graphics. In a Terminal Services environment any features you set to Install on Demand will be ignored and installed as Run from My Computer. Also, by default, installations to Terminal Services environment will always install the low-resolution graphics for splash screens. When creating transforms for use with Terminal Services environment, it is highly recommended that you not enable features that are disabled or set to Not Available. The Office installation will be broken down in to three sections. Install Microsoft Office 2003 Resource Kit. Create a custom Terminal Services Transform (MST) file. Execute the Microsoft Office 2003 installation program to install Microsoft Office 2003. (If you will be using Installation Manger you will then be required to add the package to the Management Console for MetaFrame XP In the following section we learn how to install and configure Microsoft Office 2003 on a MetaFrame XP server.
You will need to install the Microsoft Office 2003 Resource Kit Tools on one workstation in order to create a custom transforms file (MST). The MST will allow you to configure how Office 2003 will be configured and what components will be installed. System Requirements Supported Operating Systems - Windows 2000 Service Pack 3, Windows Server 2003, Windows XP Processor - Pentium 233 MHz or higher processor; Pentium III recommended. Operating system - Microsoft Windows 2000 Service Pack 3 or later, or Windows XP or later (recommended). Memory - 64 MB RAM (minimum);128 MB RAM (recommended). Monitor - Super VGA (800 x 600) or higher resolution with 256 colors. Disk drive - CD-ROM drive. Pointing device - Microsoft Mouse, Microsoft IntelliMouse, or compatible pointing device. 1. Download and Install the Office 2003 Edition Resource Kit Tools to your MetaFrame XP Server. The ORK can be downloaded from: http://www.microsoft.com/downloads/details.aspx?displaylang=en&familyid=4bb7cb10-a6e5-4334-8925-3bcf308cfbaf 2. Install the Office 2003 Resource Kit Tools by double-clicking on ORK.exe. 3. Click to check the I accept the terms in the License Agreement checkbox and click Next to continue. 
4. Click Next to accept the default application location. 
5. Select the desired components and click Next to contiune. Note: Only the Custom Installation Wizzard is required. 
6. Click Install to accept the install the Office 2003 Resource Kit 
7. Click OK 
Now that you have installed the Office Resource Kit, you are ready to create a custom Terminal Server transform (MST) file with the Custom Installation Wizard for your environment. You will also be able to use this file for all your Office 2003 MetaFrame installations and for deploying via Installation Manger 2.2. The following defines how to create and configure a custom Microsoft Office 2003 Terminal Services Transform file. The following defines how to create a customer transforms file to customize the deployment of Office 2003 in a Terminal Services environment. 1. Click Start click Programs click Microsoft Office click Microsoft Office Tools click Microsoft Office 2003 Resource Kit click Custom Installation Wizard. 2. Click Next. 
3. Click the Browse button to select the Office 2003 default MSI file located in the root of the Office 2003 CDROM. 
4. Click to select the Create a new MST file radio button and click Next to continue. 
5. Enter the location to save to new MST file and click Next to continue. 
6. Specify the Default installation path and the Organization name and click Next 
7. Click Next to accept the default installation behavior 
8. If you will be installing Citrix MetaFrame Conferencing Manager with Microsoft Exchange Server integration then you will be required to install the Collaboration Data Objects. Expand the Microsoft Outlook for Windows key, right click on Collaboration Data Objects and click Run from My Computer. 
9. To remove the dreaded Office Assistant expand the Office Shared Features key, right on Office Assistant and click Not Available. Click Next when finished 
10. Click to select Do not configure local installation source radio button and click Next to continue. 
11. Click Next to continue. 
12. Click Next to continue. 
13. Click Next to continue 
14. Click Next to continue 
15. Click Next to continue 
16. Click Next to continue. 
17. Click Next to continue. 
18. Click the Add button 
19. Click the New Profile radio button and enter a unique Profile name in the Profile name text box. Click Next to continue 
20. Click the Configure an Exchange Server connection radio button and enter the Exchange Server name. Click Next to continue 
21. Click Next to continue 
22. Click Next to continue. 
23. Select the how Outlook drafts and formats messages and click Next to continue.. 
24. Verify settings and click Next to continue. 
25. Click Next to continue 
26. Click Finish 
27. Click Exit. 
You are now ready to install the Office 2003 application. 1. To install Microsoft Office 2003 click Start Run type: setup.exe TRANSFORMS=C:\TERMSRVR.MST Click OK to launch MS Office 2003s installation program. 
2. You will be required to enter a license and select the defaults from then on. You have now successfully installed Microsoft Office 2003 on a MetaFrame XP Server. MetaFrame Conferencing Manager is more than just a single application but it has been developed in several components and services. Two of those components run as published applications on MetaFrame XP server(s) and the other on any member server of the same domain as the MetaFrame XP farm. Having separate components gives you the flexibility for you to install each of the components (Conference Organizer, Conference Room and MetaFrame Conferencing Manager Client) to different servers. If you are deploying Conferencing Manager in a workgroup you are required to install all the components on a single MetaFrame XP server. If you are deploying in a domain, you can install the different components on individual servers. Installing multiple instances of the MetaFrame Conferencing Manager User interface and the Conference Room component allows you to benefit by load balancing the two components that run as published applications. Citrixs best practice suggests that the Conference Room components be installed to dedicated servers (this is where the conferences are hosted). Conference Organizer may be installed on any one of the Conference Room servers. The User Interface component may be installed on the servers hosting your other productivity applications. Citrix MetaFrame Conferencing Manager consists of the following three components in more detail:
|