| Client to Server Content Redirection allow users running the Program Neighborhood Agent to associate local file types to MetaFrame XP published applications. This allows a user to work with any type of file 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 MetaFrame XPs content redirection capability in conjunction with the Program Neighborhood Agent to redirect client side files to be launched with remote published applications of MetaFrame XP servers. For example, when users double-click attachments encountered in an email application running locally, the attachment opens in an application that is published on the MetaFrame XP server. 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 MetaFrame XP 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. This can be done from the local registry of the server where the new application was installed or per server. a. Farm Level To do this right click on the farm name in the left pane and click Update File Types from Registry before publishing the application or updating a published applications content redirection properties. 
b. Per Server - 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 or updating a published applications content redirection properties. 
3. You can configure client to server redirection in two ways; one, during the publishing of the application you will be prompted with the following screen to select the file type associations you would like to configure with the published applications. 
4. 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 3 Server CD in the \support\debug\i386 folder. 
|