Summary
This article outlines frequently asked questions (FAQ) for the Application Streaming feature in Citrix Presentation Server 4.5.
Q1: Is Vista supported?
A: Vista is fully functional for Citrix Presentation Server 4.5; however, it is not an officially supported operating system. All officially supported operating systems have been thoroughly tested by Citrix Systems, Inc.
Q2: How often are “heartbeat” messages sent? Over which port are they sent?
A: Program Neighborhood Agent passes the URL
http://WIserver/Citrix/PNAgent/rade.aspx to the streaming client service and the client service sends HTTP packets on port 80 to the Web Interface server every 10 minutes.
Q3: If two Adobe Acrobat Readers are both configured with .PDF file type association enabled, which one launches when a user double-clicks a PDF file?
A: During application enumeration (the determination of the applications available to the user), the list of published applications is not determined in a preset order or sequence. Therefore, you cannot determine which version of two identical applications will assume responsibility for an action.
The last published application returned to the client during enumeration implements the file type association and is launched (by overwriting the file type association registry).
Q4: Can radedeploy.exe be used to pre-cache the online streamed applications? Does it download the whole package?
A: Yes, online applications can be pre-deployed to the client using RADEDEPLOY. Only the CAB file relevant to the client is copied, not all CAB files – this is exactly how the offline process works.
Q5: Why is the radeoffline.mdb on every server in the farm? How do they communicate with each other? How and when does the offline user get written into this database?
A: The Radeoffline.mdb is the persistent record of the license. During license checkout, the Rade session subsystem (RadeSessionSs.dll) in IMA writes the record to the local RadeOffline.mdb. In addition, the Rade session subsystem sends the update to the data collector for farm wide visibility. These records can be viewed using
queryDS /table:Rade_OfflineLicense (case sensitive).
Q6: How do the obsolete sessions get cleared out of the Access Management Console?
A: The Access Management Console collects information about the obsolete sessions from the data collector. If the XML broker does not receive any contact (“heartbeat” or end session request) from the client, it waits 25 minutes before timing out the license, and 2 hours before timing out the session. When the session is timed out, the data collector records are removed. These intervals are defined in the IMA Rade Subsystem and are not configurable.
Source