• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2705
  • Last Modified:

XenApp 6.5 Published Apps not Launching from within Published Desktop - Server 2008 R2

I had to rebuild my XA65 farm because I deployed the Beta version of Rollup Pack 2 on my previous farm. As a result I was unable to upgrade to the Official Rollup Pack 2 when it was eventually released.

My new farm is complete. For the purpose of this question, lets assume I have the following Servers:
* Web Interface Server
* License Server
* Database Server
* Data Collector
* Published Desktop Host
* Published App Host
(All Servers are Win Server 2008 R2)

Users launch their Published Desktop Session. The published Desktop host has the Citrix Receiver Enterprise 3.4 installed. This launches upon startup. Any Role specific Apps are then published to the users Published Desktop.

On this new farm, if a user tries to launch a published app (hosted on the published app server) from within their published desktop session, the app does not launch and the following error is displayed

receiver error
Then obviously the App does not launch.
If I check the event logs on all of the servers listed above, I find absolutely nothing.

I can however launch the app fine if I launch it outside of the Published Desktop (so direct from the client).

I have tested publishing an app and hosting it from the Published Desktop Host (notepad). I launch the Published desktop, then try launch the published Notepad. It launches fine. So I do not think the issue is related to the receiver.

Both hosts are effectively the same setup (same XenApp, same hotfixes & Rollup Packs etc).
  • 7
  • 5
6 Solutions
Ayman BakrSenior ConsultantCommented:
I think this should resolve your issue:

Many reasons ,....IP setting , configuration ...try direct connect in yr citrix server first then drill down next level.
HowzattAuthor Commented:
The registry settings in the article already appear to be correct.

Regarding "Many reasons", I have tested every possible setting I can think of. I have attempted rebuilding the host too. There doesn't seem to be any network connectivity issues. There are no events anywhere that show an error. It doesn't even show any events that show there was an attempt to start a session. Its like it never happened.
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Ayman BakrSenior ConsultantCommented:
How did you check the registry setting?  Was it on the client device logged in with the profile of the user facing the issue?

What was the order of tasks you carried out when you built the server in the new farm - OS, Xenapp, patches, hotfixes etc....?
HowzattAuthor Commented:
Logged in as the user, ran regedit, then visually checked the settings as to what was in the settings in the reg file.

From memory, steps were as follows:
* OS install
* Win Updates/ SP's
* Install applications
* Install XA 65
* Install Citrix Rollup Packs & any post RP hotfixes & components (eg HDX client rendering installer)
* Install latest receiver
* Deploy registry & policies as per the XA65 Server 2008 R2 Optimisation guide
* Configure XA and connect to farm.
HowzattAuthor Commented:
If I make the user account a domain admin, the applications launches correctly.
So in saying that we know it's probably not a networking issue and nothing to do with the receiver in use.

And since we can launch the published applications directly from the client device, we know the application is not the issue.

So only thing I could see that it could be is the permissions between launching it from the users published desktop vs launching the app from the client device.
Ayman BakrSenior ConsultantCommented:
Apologies for the late reply. Just to make sure we are on the same track - when you said you logged as the user and checked the registry, you meant you launched the published desktop as the user and checked the HKCU registry related to that user from the published desktop?

If you put the user back to normal user account (after you have made him a domain admin), does the issue re-ocurr? Is the issue happening to all users or to specific users? If you just made them local admins does this make a difference?
Ayman BakrSenior ConsultantCommented:
Another suggestion: copy the lockdown profiles registry settings of a working account and replace them on the troubled users' accounts.

But, please backup the registry before doing so; at least to have a roll back plan should things go worse.
HowzattAuthor Commented:
Re checking the registry, yes that is correct.
If I change back to normal user, apps become unavailable again.

Just to add, I can log onto the published desktop host as a local account, but when the receiver fires up I enter the domain account I am testing with, and I can launch the apps.

Re copying the reg settings from a working account, I don't have any working accounts that currently use Citrix profile management. I only have working accounts with Windows profiles.
What I have done is copying this profile to the default profile (then blew away the profile for the test account). I can see the new default profile has been used when logging in again, but same issue remains.
HowzattAuthor Commented:
In the end it turned out to be a User group policy setting.
I removed the link to the current user GP and linked the user GP from our other farm instead. I blew away the test profile and logged in again. I was able to launch all apps successfully!

So which GP setting caused the issue? To be honest I am not 100% sure. When I first created this policy, I simply copied the policy from our previous farm, update the redirected folders & policy paths, I added a few other minor adjustments which I cannot remember anymore. I compared the 2 policy settings and (apart from what I mentioned) the only other difference was I had added some registry settings for the users proxy server (as you lose Internet Explorer Maintenance from GP settings when your PDC has IE10 installed).

I deleted the problem policy, re copied policy from the old farm again, updated the redirected folders & Profile paths. As for the proxy address, I have instead added this into the default user profile as an interim solution. I plan to update our PDC from 2008 R2 to 2012 in the next couple months. Once we do this, we will be able to utilize the updated GP settings structure (where I will once again be able to deploy proxy settings via GP again).
Ayman BakrSenior ConsultantCommented:
Good to hear you could resolve your issue!
HowzattAuthor Commented:
Sorry I have not closed this off yet.
I was hoping I could eventually find time to find out exactly what setting in the Group policy caused the issue so others might be able to use this info. However I am struggling to find the time. So lets just say to anyone else with a similar issue, un-link the group policies, blow away the profile for a test user and login again to test.

Thanks to everyone who commented. It all helped me finding the end resolution.
HowzattAuthor Commented:
I need to include the solution.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Train for your Pen Testing Engineer Certification

Enroll today in this bundle of courses to gain experience in the logistics of pen testing, Linux fundamentals, vulnerability assessments, detecting live systems, and more! This series, valued at $3,000, is free for Premium members, Team Accounts, and Qualified Experts.

  • 7
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now