How to Force a Non-Native File Type Association for a Streamed Application

How to Force a Non-Native File Type Association for a Streamed Application

book

Article ID: CTX131327

calendar_today

Updated On:

Description

This article contains information on how to force a file type association for a non-native file type in a streamed application.

Requirements

Streaming Profiler 6.5

Instructions

Complete the following procedure to force a file type association for a non-native file type in a streamed application:

Note: To associate a non-native file type to an application, you need to make the changes to the profiled package and not to the server.

  1. Open the package in the streaming profiler.

  2. Right-click the OS type and select Update/Install Application as shown in the following screen shot:

Right-click the OS type and select Update/Install Application
  1. Select Advanced Install.
Select Advanced Install
  1. Select Edit Registry.
Select Edit Registry
  1. Select Launch Windows Registry Editor.
Select Launch Windows Registry Editor

Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.

  1. Select HKLM>SOFTWARE>Classes> as displayed in the following screen shot:
    Note: Here you can find the file types for all the applications. In this example, Adobe Reader x is being used, therefore, find the native .pdf class.

Registry Editor - Select HKLM>SOFTWARE>Classes>

  1. You can see the file type association after selecting the .pdf class. The .pdf class  references two string values hives, as displayed in the following screen shot. Copy these strings to the customized file type:
    (Default)    REG_SZ   AcroExch.Document
    Content Type    REG_SZ   Application/pdf
Copy these strings to the customized file type
  1. Create customized file type. In this example, create the .pac file type by selecting New > Key.
Create customized file type
  1. Name the Key as .pac.
Name the Key as .pac

  1. After creating the key, copy the settings from the .pdf file type.

  2. Close the registry editor, and follow the defaults to finish the profile. Ensure to save the profiled package for the settings to take effect.

Close the registry editor, and follow the defaults to finish the profile

  1. To verify if the setting hastaken effect, open Application Properties > Content redirection.

  2. Ensure to select Show all available file types for this application.
    Note: You notice that .pac is now associated with Adobe Reader X.

  3. Ensure to select the .pac option so that it is available for users.

select the .pac option and make it available for the users
  1. On my client machine, after you are logged into Receiver 3.0, you notice that the .pac files are now associated to Adobe Reader X as displayed in the following screen shot:
.pac files are now associated to Adobe Reader X

Environment

Caution! Using Registry Editor incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.

Issue/Introduction

This article contains information on how to force a file type association for a non-native file type in a streamed application.
Powered by Wolken Software