How to Force a Streamed to Server Application to do Server to Client Content Redirection

book

Article ID: CTX131567

calendar_today

Updated On:

Description

This article describes how to force a Streamed to Server application to do Server to Client content redirection.

Requirements

Streaming Profiler 6.5

Background

Typically when you stream the application to your server, all the processing and the subsequent application that are called, runs on the server. This is the default behaviour, but if you want to customize your redirection, for example to click a link on an email, or a file and have it open on your local Internet Explorer using streaming to server, it is possible.

Instructions

Warning! Using the Registry Editor incorrectly can cause serious issues with the operating system that might require you to reinstall the operating system. Citrix does not guarantee that the issues resulting from the incorrect use of Registry Editor can be resolved. Use the Registry Editor at your own risk. Ensure that you make a backup of the registry before you edit it.

Publish a streamed to server application.
Note: For our example we are using Adobe Reader X, as displayed in the following screen shot.
On the server with the published version of Adobe Reader, drill down the registry and locate:
HKEY_CLASSES_ROOT\http\shell\open\command key.

Note: This key controls the local applications calling for http.
On the server, with the published version of Adobe Reader, drill down the registry and find:
HKEY_CLASSES_ROOT\http\shell\open\command _backup key.

Note: This key controls the streamed applications calling for http.
To force a streamed Adobe Reader X to do content redirection from server to client, copy the command key data and paste it into the command_backup key, as displayed in the following screen shot.
Prior to testing, this is what the normal behavior, prior to changes looks like. You notice that Internet Explorer is started on the server after selecting a link on the document. You also notice the Internet Explorer looks like the one displayed in the following screen shot from the server.
After making the changes in the registry, notice the differences in the following screen shot.

You notice now that the Internet Explorer is not started from the server. You also notice a difference on the look and feel of Internet Explorer. It is now using the local Internet Explorer from server to client content redirection through Streamed to server.
This can also be done with https links through the https key in the registry: