We are facing issues when in the morning, after servers dailey reboot, users cannot start a published application, before anyone started a full desktop on those servers, using either the Citrix Receiver Desktop or using a Thin Client.
Environment:
XenApp 7.6 LTSR CU1
Workers: Windows 2008 R2 SP1 patched till 12/07/2016.
Director & Storefronts are Windows 2012 R2
Published application does not require the Explorer.exe so seamless is OK.
Workers using MCS, everyday reboot to clean image, could not start app (published app).
I see them come in on the Director connecting to the server but no session starts. When server reboots and you first start a published desktop, there are no problems.
When you start a published app, hosted on that same server you previously started a published desktop on, the published app starts.
As if, when you start a published desktop, some services get initialized which the publish app also uses but does not initializes them?
I've seen a lot of talking about the "RunOnce /alternateShellStartup" command but don't get it to work. I tried it as a startup script in an Machine Policy and also as a logon script in an User Policy
Question
It It1709152289
Hi guys,
We are facing issues when in the morning, after servers dailey reboot, users cannot start a published application, before anyone started a full desktop on those servers, using either the Citrix Receiver Desktop or using a Thin Client.
Environment:
XenApp 7.6 LTSR CU1
Workers: Windows 2008 R2 SP1 patched till 12/07/2016.
Director & Storefronts are Windows 2012 R2
Published application does not require the Explorer.exe so seamless is OK.
Workers using MCS, everyday reboot to clean image, could not start app (published app).
I see them come in on the Director connecting to the server but no session starts.
When server reboots and you first start a published desktop, there are no problems.
When you start a published app, hosted on that same server you previously started a published desktop on, the published app starts.
As if, when you start a published desktop, some services get initialized which the publish app also uses but does not initializes them?
I've seen a lot of talking about the "RunOnce /alternateShellStartup" command but don't get it to work. I tried it as a startup script in an Machine Policy and also as a logon script in an User Policy
Anyone else have any other solutions of fixes?
BR
Jeroen Van Praet
Link to comment
3 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now