The Citrix Workspace environment is faster, always available, stable, and extremely user friendly. And the best thing about it is that users say they don’t even notice it because it always works. Office of the Chief Information Officer Office of the Chief Information Officer Remote Access Services Virtual Desktop Infrastructure (VDI) and Citrix Workplace Note: For your PIV card to work, you MUST install your card reader and insert your PIV card before selecting the PIV image.
A typical Citrix environment can be so complex. What might seem like a simple problem in the Citrix Receiver can turn out to be very hard to troubleshoot. For instance, if a user’s Citrix Receiver is not launching applications, you need to consider a number of factors.
A lot of the solutions involve editing the Windows Registry—a high-risk operation that, if done wrong, can have serious consequences.
Citrix Receiver not Launching Applications: Misconfigured LogoffCheckSysModules registry value in HKLM
When published applications don’t launch and the user doesn’t see any error message, then admins don’t see any entry that stands out in the Event Log of your Citrix server. One of the places you’ll want to check is the value of LogoffCheckSysModules. This is found in the registry subkey:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCitrixwfshellTWI
The value of this registry key SHOULD NOT contain the executable for the application the user is attempting to launch. If the name of the executable in question is there, create a backup of the registry key and then remove the executable’s name from the key.
Application launch attempts in a published desktop get disconnected
When you attempt to launch a published application from a published desktop, that action may disconnect the session of the published desktop. That’s because Citrix receiver is configured by default to reconnect all open sessions upon launch.
To make the application launch succeed, you need to change the value of the WSCReconnectMode key from 3 to 0 in one of the following:
- 64-bit system: HKEY_LOCAL_MACHINESOFTWAREWow6432NodeCitrixDazzle
- 32-bit system: HKEY_CURRENT_USERSOFTWARECitrixDazzle
Application not given enough time to launch
Some launch-related issues occur because certain applications need more time to launch. There are two registry key values you can change that might remedy the problem. Both are in the registry key:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCitrixwfshellTWI
The first is LogoffCheckerStartupDelayInSeconds. Try setting this initially to 10 seconds and then increase by 10 seconds until 600 seconds.
The second one is ApplicationLaunchWaitTimeoutMS. Try setting this initially to 10,000 milliseconds and then increase up to 30,000.
Notice that, for these two registry key values alone, much time can be spent trying out different values. And these are just some of the many possible causes why Citrix Receiver is not launching applications.
Citrix Receiver not Launching in Windows 10
Citrix Receiver for Windows 10 has a list of arguably smart features, however there are several issues that constantly pop-up and prevent Citrix Receiver from launching in Windows 10. For instance, launching Citrix with the regular domain user account fails to launch the desktops and applications. If your Citrix Receiver is not launching in Windows 10, mentioned below are the steps you can undertake to fix these errors.
1. Refresh Citrix Receiver applications.
Click on the drop-down next to your name in the upper-right corner of the menu, and click Refresh Apps.
2. Allocate full permissions to the user count being used.
Assign full permissions for the user account under HKEY_USERUSER_SIDSOFTWARECitrix on the client machine.
3. Download the latest available version to prevent compatibility issues.
Navigate to the Citrix Receiver icon >> Advanced Preferences >> About to check the version. Compare it with the latest available version and download a new one if it does not match.
4. Reset the Citrix Receiver if everything else fails. This might cause accounts, apps, and cached files to be removed.
Navigate to Receiver icon >> Advanced Preferences >> Reset Receiver. A prompt appears, asking if you want to reset the receiver. Click Yes, Reset Receiver and type the URL remote.ptlgateway.net in the popup box that appears next. Enter your credentials again.
Applications not launching on Apple Safari 12
Apple has removed the support for NPAPI, hence Citrix applications now fail to launch in Apple Safari 12. This problem can be solved by carrying out some changes in the server side or the client side. You can modify the web config under the Receiver for Web (RfWeb) site in the server. The client-side change includes enabling the Develop tab at the Safari menu, using which the Safari cache and all Safari Windows are closed prior to starting Safari to browse the Storefront’s receiver.
Avoid Citrix receiver not launching applications issues for good with Parallels RAS
To avoid Citrix Receiver application launch issues for good, shift to Parallels® Remote Application Server (RAS). Parallels RAS is a virtual application and desktop delivery solution with a much simpler architecture. Complex issues like those mentioned above are eliminated from the client-side and can usually be addressed by simply reinstalling or restarting the Parallels Client. In addition, users can also switch to the HTML5 Client until any issue is resolved.
Don’t just take our word for it—try it out yourself. Download your 30-day Parallels RAS trial now and say goodbye to all your application launch issues.
References
Geekworldinc | http://geekworldinc.blogspot.com/2014/02/
Lowell Vanderpool [YouTube video]| https://youtu.be/_U78iAem3uo
Emory Vdt Connect
Carl Stalhood | https://www.carlstalhood.com/virtual-delivery-agent-vda-7-15-ltsr/
Work Anywhere | http://www.waw.raidghost.com/index.php/news-it-waw/blogueurs-follow/1363-virtual-delivery-agent-vda-712
Poppelgaard | https://www.poppelgaard.com/author/admin/page/110
Virtual Private Network (VPN) provides off-campus users with secure access to the Emory University's internal network. Emory VPN access uses a standalone client or web browser to establish the remote access connection. It secures traffic by encrypting communications between a remote computer and Emory's network.
Access: Requires a network ID and password. Users must also register with the IT Service Desk to gain access to the VPN. Call 404-727-7777 to complete this process. Update: This requirement is currently being waived for University users due to the Covid-19 situation. Emory Healthcare users should follow the standard process for gaining VPN access to the Emory Healthcare network.
VPN Client: Windows and Mac users should download the latest Standard Client - this is the preferred VPN access mechanism.
Access URL: vpn.emory.edu
Problems? Check out our VPN Troubleshooting Guide.
Emory Citrix Workspace Log
Questions: Call the IT Service Desk at 404-727-7777 (Emory University employees and students) or 404-778-4357 (Emory Healthcare employees).
Connection Instructions
Please reference the following knowledgebase articles for instructions to connect to the Emory VPN from the following platforms:
Emory Healthcare Vdt Access
Emory Citrix Workspace Employee
Usage Guidelines
Emory Citrix Workspace Login
- Only connect to theVPNif you cannot access the Emory network resources that you need without it. If you are unsure, try to access the system without theVPNfirst, and if you can’t get to it, then feel free to use theVPN.
- Disconnect theVPNafter you no longer need it. Following these first two guidelines will help ensure we have plenty ofVPNresources for everyone.
- Unless you have no other choice, please use Emory owned and managed devices when connecting to theVPN.
- Users who need elevatedVPNaccess to one of the University restricted network cores (Admin, DMZ, HIPAA, etc), still need to have their supervisor, sponsor, or local support submit a Service Now Catalog Request on their behalf for this elevated access.