Force Desktops to launch in full screen mode in XenDesktop and XenApp 7.5

In earlier versions of XenApp you could make a desktop full screen in the published application settings. In XenApp/XenDesktop 7.5 this setting is no longer available. It’s a little bit of an annoyance to have to click the top menu of Desktop Viewer to make it full screen, but even then it won’t stretch across both screens in a dual monitor setup.

Lal Mohan at Citrixology has a very good post on how to edit StoreFront to launch a desktop in full screen mode.

On your StoreFront server, open the C:inetpubwwwrootCitrix<StoreName>App_Datadefault.ica file in Notepad, and add the line “DesktopViewer-ForceFullScreenStartup=true” under the [Application] section.

XenApp or XenDesktop applications fail to launch

When accessing my StoreWeb URL, I clicked on an application icon and it would never launch, and at the bottom of the icon the circle would spin continuously. Citrix article CTX128009 fixed the issue.

Use the following registry key that allows you to configure the time-out as follows:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCitrixwfshellTWI

Name: ApplicationLaunchWaitTimeoutMS
Type: REG_DWORD
Data: <required additional time-out, in milliseconds>

Note: Specifying a value of less than 10000 reverts to 10000 because 10 seconds is the minimum override.

 

Create the following registry key: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCitrixwfshellTWI
Value Name: LogoffCheckerStartupDelayInSeconds
Type: REG_DWORD
Value: An integer that denotes the time to wait for the application to start (10 Hexadecimal recommended)
Note: Setting this value also increases the time it takes for a user to log off the server.It is more useful as a troubleshooting step to confirm that the issue is due to the length of time required for your application to launch.

Slow XenApp 5 logons on Server 2008

My XenApp 5 farm published desktops running on Windows Server 2008 x86 had logon times averaging 69 seconds. Group Policy Registry items were taking 40 seconds as seen in the event logs.

I found Citrix article CTX128749. I added a new GPO with a scheduled task containing:

rd “C:ProgramDataMicrosoftGroup Policyhistory” /s /q

I ran the above command and restarted all servers and then timed logons and they had decreased from 69 to 33 seconds. I can live with 33 second logons.

Thanks and a shout out to robissimo for pointing the Citrix article out to me.

XenDesktop and XenApp black or frozen screen

This issue affects XenApp 7.5; XenDesktop 7.1 and 7.5 VDA Core Services for Windows Server OS (64-bit). After launching a published desktop or application, the screen may be completely black, or it may freeze.

Since this issues affects the default graphics mode, I’m scratching my head, amazed that Citrix doesn’t include this fix in the ISO download of XenDesktop/XenApp 7.x. To make matters worse, you can’t just visit the Citrix site and download this hotfix, you have to open a support ticket and they must email you a download link.

See CTX139901 for more info.

How to disable Citrix desktop auto launch in StoreFront

I’m not sure why Citrix thought it would be a good idea to automatically launch a published desktop in the Citrix Receiver for Web (StoreWeb) site in StoreFront and assumed that users wouldn’t want to launch an application instead. It seems logical to not auto launch a desktop and have the administrator edit this config file value if they DO want it to auto launch.

To disable desktop auto launch:
Complete the following steps to disable the desktop launch:

  1. Go to C:inetpubwwwrootCitrixStoreWeb directory.
  2. Open the Web.config file with notepad.
  3. Set the autoLaunchDesktop parameter to “false”.
autoLaunchDesktop
  1. Save the web.config file.

First lonely post

Today I’m recovering from a very simple mistake that could have cost me weeks of work if I hadn’t made a backup copy in VMware of my application server I am building for XenApp 7.5. I painstakingly installed and tweaked a long list of applications on Server 2008 R2 to be used for the master image in XenApp 7.5 Machine Creation Serices (MCS).

I hit a wall with an issue connecting my XenApp 7.5 DC to vSphere for the MCS connection. I submitted traces to Citrix support, who eventually called it a VMware issue. While waiting for VMware support, I decided to manually create the servers in VMware instead of using MCS so that I could forge ahead in the Citrix upgrade. I can always go back and integrate MCS after the VMware issue is resolved. I sysprepped my application server and created a vm template. After creating my first server from the template, I realized that I FORGOT TO UNCHECK “User cannot change password” for the administrator account before shutting the server down after running sysprep. Great, now I can’t login since it forces you to set the administrator password on first login, and the password can’t be changed.

What I SHOULD HAVE DONE is to clone my app server, then sysprep the clone and leave the original server intact. Thankfully I had created a backup copy of this server in the lab, so with a few clicks and a short delay I’m making progress again.

Sometimes its the simple things that can cause you the most pain.