CTX125158 – Case Study: IMA Startup Error Because of the Data Store – Citrix Knowledge Center

Problem Definition The IMA service running is necessary for the discovery of the XenApp server and proper XenApp functionality. Requirements Basis XenApp Administration Skills Background The Citrix IMA service is required to be running on each XenApp server for the discovery process to work correctly and normal operability of XenApp. Using the registry, you can use the CurrentlyLoadingPlugin string to identify if the issue is related to the data store. Troubleshooting Methodology The steps to complete the task: Check to see if the IMA service is started. Attempt to start IMA service; the error message below might appear. “Windows could […]

Read more

CTX127892 – Disconnected Sessions are Not Logged Off after the Disconnect Session Timer Interval has Passed – Citrix Knowledge Center

Summary XenApp 6.0 disconnected sessions are not logged off after the Disconnect session timer interval has passed. Even with the Session Disconnect Timer and Disconnected Session Timer Interval Policies configured and applied to users The Disconnected Session Timer and Disconnected Session Timer Interval Policies do not apply to XenApp, but only apply to XenDesktop. This document applies to: XenApp 6.0 for Windows Server 2008 R2 Source: CTX127892 – Disconnected Sessions are Not Logged Off after the Disconnect Session Timer Interval has Passed – Citrix Knowledge Center

Read more

CTX127874 – Published Application Does Not Launch for a New User – Citrix Knowledge Center

Symptoms A published application does not start properly. The same application starts in a published desktop session for the same user. This affects new user profiles, when the profile on the Terminal Server (TS) is created by launching a published application. However, if the first time launch when the user profile is created is based on a published desktop session, no problems occur even if you launch the application as a published application thereafter. Cause If wfshell is not loaded, the default.profile is not created correctly. The behavior occurs because when the explorer shell is not loaded with the Run […]

Read more