After realizing that I had to dig deep into my notes and search for registry settings on the web that I’ve used multiple times over the years, I thought I’d write a post to serve
Environment Citrix XenApp Server Operating System: Windows 2008 R2 Citrix XenApp Version: 6.5 Citrix XenApp Hotfix: Rollup 1 Citrix Profile Management Version: 4.1 Problem You’ve received complaints from various users that when they launch applications
Problem You attempt to launch a Citrix XenApp 6.5 application published through a Citrix Access Gateway but the Citrix Receiver throws the error: Unable to launch your application. Contact your help desk with the following
Problem You’ve received complaints from users that they are unable to successfully launch Citrix XenApp 6.5 published applications because while the Citrix Receiver launches and attempts to connect to the XenApp server, it hangs at
Problem You’ve successfully installed the Lync 2013 client on your Citrix XenApp 6.5 servers but noticed that when you launch the published application through the Web Interface portal, it crashes with the following output: Microsoft
A common problem that many Citrix administrators come across is when an Active Directory GPO is configured to present a security banner to users who log onto domain joined servers or workstations. The problem this
Problem Ran into an issue the other day where I would have no problems logging into a Citrix XenApp 6.5 environment published with a Citrix Access Gateway VPX 50 (NS10.0: Build 73.5.nc) but noticed that
Problem I was recently asked by a client to look into an issue where he had a specific user who would receive the following error when launching any Citrix XenApp 6.5 published applications: The Group
Problem You attempt to publish an application with a working directory that is configured to a mapped drive: You’ve included the following in your batch file: net use K: /delete /yesnet use K: “\someFileServersoftware” K:BARSQLVFPEXEv9ball.exe
Problem You attempt to connect to a XenApp 6.5 server with a regular user account without administrative privileges via RDP: … but receive the following error: Connection Error The desktop you are trying to open
