• View Communities
    • Citrix Developer Network
      The place for unfiltered straight talk on Citrix products. Blogs, code downloads, best practices, APIs, and more can all be found here.
    • Citrix Ready Community Verified
      Does it work with Citrix? Application compatibility questions are a thing of the past with the new Citrix Community Verified site.
    • Blogs
      Learn the latest from the Citrix employees who are building application delivery infrastructure technologies.
    • Blogosphere
      The Citrix Blogosphere is a window into the thousands of conversations taking place about Citrix and Application Delivery.
  •  Sign In
The Citrix Blog
Personal Blog
Joseph Nord
Blogs
Profile
Related Tags
xenapp
Version 2 by Joseph Nord
on Jun 05, 2009 15:20.

<< Changes from 1 to 2
compared with
Current by Joseph Nord
on Jun 05, 2009 15:22.

 
Key
These lines were removed. This word was removed.
These lines were added. This word was added.

View page history


There are 4 changes. View first change.

 How do you add FTAs to profiled applications that the installer forgot to install?&nbsp; Answer: There are a few steps.
  
 This has been on my list to Blog about for a while, just haven't gotten around to writing about it, mostly because&nbsp; I hadn't had a chance to verify the solution would actually work.&nbsp; Conveniently, Karl Muller of I-Access took care of the trial for me, and it worked, so here's the solution.&nbsp; Thanks Karl.
  
  
 *Review*
  
 Backup a couple steps... "FTA what\!"
  
 When an application installs, it writes entries to the machine to establish associations between file extensions (multiple) and programs (single).&nbsp; Each file type definition also includes a reference to the ICON that goes with the extension. This is what Windows Explorer uses to show you icons that looks like MS Word for file's that end in .docx. &nbsp;
  
The *Streaming Profiler* runs installer under isolation and blocks the installers attempt to set FTAs on the true machine.&nbsp; As part of post processing, the profiler examinies all the FTA entries that the installation program TRIED to create and for each of these, creates coresponding FTA entries in the streaming profile XML data - you can see them in the .profile file, if copy to .xml and view with web browser.&nbsp; Easier, just look at the properties of applications captured during profiling and ask to see the FTAs.&nbsp; Yes, that's much easier.
  The *Streaming Profiler* runs the installation program under isolation and blocks the installers attempt to set FTAs on the true machine.&nbsp; As part of post processing, the profiler examines all the FTA entries that the installation program TRIED to create and for each of these, creates corresponding FTA entries in the streaming profile XML data - you can see them in the .profile file, if copy to .xml and view with web browser.&nbsp; Easier, just look at the properties of applications captured during profiling and ask to see the FTAs.&nbsp; Yes, that's much easier.
  
The *Access Management Console* (XenApp publishing console) reads the profile information and gets a list of all the captured FTAs.&nbsp; It makes these AVAILABLE for assocation with applications that you publish.&nbsp; The default is that no FTA will be associated with the published application, so as an admin, you have to go to direct action to establish the FTA by clicking on boxes.
  The *Access Management Console* (XenApp publishing console) reads the profile information and gets a list of all the captured FTAs.&nbsp; It makes these AVAILABLE for association with applications that you publish.&nbsp; The default is that no FTA will be associated with the published application, so as an admin, you have to go to direct action to establish the FTA by clicking on boxes.
  
 BUT - There's a catch, you can only establish FTA reference for the FTAs that were captured by the streaming profiler.
  
 Say you know that .DOC9 (.DOC and the number nine), is SUPPOSED to be associated with MS Word, but you note that the installation program seems to have left that one out, or that the streaming profiler seems to have missed this one.&nbsp; Let's focus on the first one.&nbsp; You have an extra FTA that is SUPPOSED to be associated that seems to be missing from the list.&nbsp; How do you add an extra FTA?
  
 Option 1: Streaming Profiler, application properties, FTAs, Add
  
 Option 2: In the Access Management Console, application properties, FTAs, Add&nbsp;
  
 Both options above would be GREAT, if only they worked.&nbsp; They are both READ-ONLY.&nbsp; You can see the FTAs, but you can't add a new one. &nbsp;
 The solution...
  
 *FTA must be captured during profiling*
  
 When profiling, tell the profiler that you want to launch an installer, it will prompt you for the path and name of the installation program, tell it "CMD".&nbsp; When launch the installer, you will get a command prompt running that is running inside of isolation.&nbsp; Two commands are needed at the command prompt to establish an FTA.
 * assoc .doc9=Word.Document.12
 * ftype Word.Document.12
  
 If the ftype is already in place, you're done.&nbsp; If not,
 * ftype Word.Document.12="C:\Program Files\Microsoft Office\Office12\WINWORD.exe" /n /dde
 * exit
  
 Now, let the streaming profiler do it's thing to see what the "installer" did and it will discover a new FTA for the .doc9.&nbsp; Save the profile and return to the Access Management Console.
  
 *Publishing*
  
 In the AMC, publish a new application, point it at the profile and it will see the FTA that you added.&nbsp; *EASY\!*
  
 *There's a catch*
  
 There is always a catch.&nbsp; The catch here is that the FTA will exist only for new application that you publish.&nbsp; Applications that you have already published have already had the FTA data sucked out of the streaming profile and placed into the XenApp publishing infrastructure.&nbsp; The AMC will not "pick up" or automatically update the applications to refect changes to the profile, so the FTAs won't exist.&nbsp; If you need that FTA added to an application that is alread published, it is necessary to delete the application and republish it.&nbsp;
  There is always a catch.&nbsp; The catch here is that the FTA will exist only for new application that you publish.&nbsp; Applications that you have already published have already had the FTA data sucked out of the streaming profile and placed into the XenApp publishing infrastructure.&nbsp; The AMC will not "pick up" or automatically update the applications to reflect changes to the profile, so the FTAs won't exist.&nbsp; If you need that FTA added to an application that is already published, it is necessary to delete the application and republish it.&nbsp;
  
 *The other solution*
  
 Not recommended, but you can accomplish the same thing by hand editing the XML data in the streaming profile and saving.&nbsp; This isn't the RECOMMENDED answer, but just between all of us, it will work.
  
 Joe Nord&nbsp;