The Ultimate Citrix Install Guide
 
1 - Preface
2 - Project Management
3 - Analysis Phase
4 - Design Phase
5 - Implementation Phase
  1. Implementation Overview

2. Prepare the Network Environment

3. 3rd Party IMA Data Store Installation & Maintenance.

4. Install Operating System

5. Install MetaFrame XP with Feature Release 2

6. Tweak Windows 2000 / MetaFrame XP

7. How to Install and Configure Microsoft Office 2000

8. Install Image Applications

9. Rapid Server Deployment

10. Install Manual Applications

11. Resource Manager 2.2 Counters Explained

12. How to Setup Automatic Reboot for MetaFrame Servers

13. MetaFrame Delegated Administration.

14. How to Set the MetaFrame Server Preference for Data Collector Elections

15. How to Create a Zone & Move MetaFrame Servers to it

16. Citrix User Policies

17. How to Implement Automatic ICA Client Updates

18. Client Drive Mapping

19. How to Implement Client to Server Content Redirection

20. How to Implement Server to Client Content Redirection

21. Publishing through the Citrix Management Console

22. How to Build a Stable Printing Environment

23. NFuse Integration

24. How to Secure an Internet Information Services (IIS) Server

25. How to Secure ICA Session Traffic with Citrix Secure Gateway (CSG) 1.1

26. MetaFrame XP Remote Administration Tools

27. ICA Clients

28. Microsoft Terminal Services License Server

29. Implement Windows System Policies.

30. Implementation - Checkpoint
6 - Readiness Phase
7 - Rollout Phase
8 - Appendix

19. How to Implement Client to Server Content Redirection

Client to Server Content Redirection allow users running the Program Neighborhood Agent v6.30 and above to associate local file types to MetaFrame published applications. This allows a user to work with any type of file / data without requiring the applications to be installed locally.

For example if you have users who run applications such as email programs locally, you can use MetaFrames content redirection capability in conjunction with the ICA Win32 Program Neighborhood Agent to redirect application launching from client device to MetaFrame server. When users double-click attachments encountered in an email application running locally, the attachment opens in an application that is published on the MetaFrame server.

It works by having the Program Neighborhood Agent change / add a file type association pointing to the published application in the client devices Windows registry. You must enable client drive mapping to use this feature. You can enable client drive mapping for the entire server farm, for specific servers, or for specific users with Citrix policies as described in the previous sections.

Note: Client to Server Content Redirection is only supported by the Program Neighborhood Agent Win32 client. For more information on the Program Neighborhood Agent, please refer to the How to Install the Program Neighborhood Agent section later on in this document.

 

The following details how to configure client to server content redirection.

1.      Verify that the desired users have client drive mapping enabled

2.      In order to take advantage of the current file type associations 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 before publishing the application and or enabling client to server content redirection.

 


3.      You can configure client to server redirection in two ways; one, during publishing an application you will be prompted with the following screen to select the file type associations you would like to configure with the published applications.

 

If you have already published the application with the file type you would like to associate then you can right click on the published application select properties click the Content Redirection tab and then check the Associate check box of the desired file type.

 

 

IMPORTANT! If for any reason you loose connection with the MetaFrame XP Farm and or the Program Neighborhood Agent prematurely closes you might find yourself with the client device pointing to a farm that it cannot detect. If this happens, open and close the PN Agent, if you still experience the problem you will need to run FTACLN.EXE located on the MetaFrame XP with Feature Release 2 Server CD in the \support\debug\i386 folder.

DABCC Site Map | Legal Notice | Privacy Statement | All Rights Reserved for DABCC, Inc.