XenDesktop 7.5/StoreFront 2.5 Upgrade

Felix Leven Senior Systems Engineer Microsoft & Citrix.
All things Microsoft Admin, for 20 years plus, focusing on automation, infrastructure as code, devops, monitoring and reporting lately.
Welcome to my short summary for those of you, preparing to upgrade to XenDeskop 7.5.
Yes, the picture says it all, the brand XenApp is back!
This release also includes "Single sign on for local credentials to the storefront site" and for me it finaly made available all director stats ("logon duration" for example), that were just blank since the first XD7 release.

But, be warned:
warningand be prepared:
Lic_updateI recommend to stick to this flowchart from Citrix to update the componets in the right order:

I will not go through setup screenshot's (google knows too many), because that's all pretty straightforward. Instead I will report on my experince with the update.

1.  License Server Update: I worked with Version 11.11.1 build 13012 since my first XD7 installment and it also worked well with the 7.1/7.5. Update to this version if needed!

2.  SA Check/Update: As the screenshot shows, update your SA to at least SA-Date "2014.0226" !

3.  The Installer try's to do as  much "AUTO" as it can, but I don't like that. Why ?

XD 7.5 rellies on NET 4.5.1 and a lot of us prefer to install Full Releases/Updates through GPO/SCCM/WSUS etc.. The "AUTO" Installer form Citrix try's it's best, but I ran into problems more then once (same with SharePoint, SystemCenter), because by design the .NET installer (or other Software) will work as silent as possible. If it runs into problems installing .NET, it will not give you any information about what went wrong and just stops. I assume it will log the problems somewhere in the Citrix setup logs, but I like to manage and troubleshoot Microsoft stuff in the Microsoft world.

Error example: A manual start of the .NET setup told me, it will need at least 2836 MB of free space on C:\ to install, the "AUTO" installer just failed without a hint, because I really was short on free space on my C: drive.

I strongly advise to push .NET 4.5.1 through your Software Deployment/Patch Management before starting the update.

4.  Backup the Database, explained in detail here: http://support.citrix.com/article/CTX135207

5.  Take "a snapshot of/backup" each and every server you are going to update.

6.  Start updating in order of the flowchart.

7.  Not noted on the chart! A Universal PrintServer update is needed, if you are upgrading from XD 7.0.

8.  Update each and every client/server that has STUDIO installed.

9.  Start up a new version of Studio 7.5, to finally start the Database update.

10. To update your site (DB), Studio will present you two options:

Auto: Should do all the DataBase updating for you

Manual update is separated into 5 steps, creating a script collection:
1. Powershell script to disable XD componets
2. SQL to Update DC
3. SQL to Update Monitor DB
4. SQL to Update Logging DB
5. Powershell script to enable XD componets
To execute the SQLs you'll have to enable SQLCMD-mode in SQL Manager.

In my opinion, this will provide more info about success/errors, and you can tell exactly where you are stuck if you need to open a support case.
AND, truth must be told, I ran into problems with the AUTO update. I tested the Update 3 times and on two tries the automatic procedure failed.

I was able to solve my problems this way:
Start "Manual update". It failed after a while on step 2., but I managed to do steps 3-5 anyway. Then, because "Citrix Studio" (after restarting!) was again demanding an update from me, I chose the "AUTO Update" and that was the way it worked 100%.

When I startet with the "automatic update" option first, the update failed AND I had to restore my database, because Studio was NOT demanding to update the DB and Studio/XD were NOT working anymore.

Powershell told me after 2 lines:
Add-PsSnapin Citrix.Broker.Admin.V2 -ErrorAction SilentlyContinue

Open in new window

That the connection failed with an error:
"DBMissingOptionalFeature", I assume this was because the DB was only partialy updated in Step 2 (I could verify this in the DB tables too).

11. Test all components.

Take your time for carefully executing steps 1-3, this will help preventing issues with other important steps of the whole migration/update process and it will give you more time to focus on the XenDesktop update.

Steps 4-10
BE WARNED, don't do this live on your first try. Try it in a small test environment first! Do a restore of the DB at least once, to get familiar with the task. When you successfully managed to update to 7.5, roll back to your previous version to get familiar with a complete XenDesktop restore!

That's it, not the "piece of cake update" and Citrix is warning you about it on almost every screen, but it will add some nice features to StoreFront/XenDesktop that we all were waiting for.
Felix Leven Senior Systems Engineer Microsoft & Citrix.
All things Microsoft Admin, for 20 years plus, focusing on automation, infrastructure as code, devops, monitoring and reporting lately.

Comments (5)

NEXT ITDirector of IT


When I attempted this update Studio would not open after I upgraded the first controller.  I got an MMC snap-in error.  Citrix came back and said .NET Framework 4.5.1 was not supported and I should be using 4.0 Extended.  This contradicts what you have listed and I'm not sure I believe Citrix because I think they are guessing.  Do you have any insight about this?
Felix Leven Senior Systems Engineer Microsoft & Citrix.



my Server (MMC) works fine with .NET and at the Moment (and it get's all the monthly patches from Windows Update).

My Client (Studio MMC) on win seven works with 4.5.50709 and

Anyway 4.5.1 is on the 7.5 XenApp/XenDesktop DVD and it is not supported ? My article is based on this bersion.

The Version you find in the ISO file:

But your Studio/MMC is also updated to the newest version ?
NEXT ITDirector of IT

Thanks for the reply Felix...

When I upgraded Studio was upgraded to whatever was on the XenDesktop 7.5 ISO.  I didn't check the version number before I rolled everything back.  But I ran through the upgrade once and everything went fine during the upgrade from XenDesktop 5.6, but then when Studio MMC went to open immediately following the upgrade,  the Studio MMC crashed and I couldn't get in to do the DB upgrade or anything else.  I restored the DB and reverted the DDC to snapshot and ran through the processes again with Citrix on the phone, same result so I had to revert again.

Like you my .NET framework 4.5.1 was already on the server prior the the XenDesktop upgrade via Windows Updates.

After reviewing the logs they collected the best Citrix could tell me, was try again and if Studio still wouldn't open uninstall just Studio on the DDC and reinstall.  They think its a corrupt installation...but I question that since it happened twice.  I guess I could try the other DDC first too and see if that produces the same result.

The second Citrix tech said the first guy was wrong because XenDesktop 7.5 actually requires at least .NET 4.5.  

All I'm looking for it a straight answer (which it seem Citrix is unable to provide)  and not working off of guesses in my production environment...  The .NET version issue seemed plausible until the other tech told me .NET 4.5 was actually required.
Felix Leven Senior Systems Engineer Microsoft & Citrix.


Well, I dont' fully understand your concerns about the .NET Version.

Windows Server 2012 R2 Includes the .NET Framework 4.5.1 and if you are not plannning to deploy 2012 R2 Servers (with XenDesktop) anytime soon, I would not upgrade at all.

In case of older OS Versions I recommend in my article to take care of it with WSUS etc. first, because I knew we would face problems like yours soon.
NEXT ITDirector of IT

I guess I lost you.  My concerns over the .NET version came from Citrix support telling me that's why my Studio wouldn't work after upgrade to XenDesktop 7.5.  One Citrix support guy told me that .NET 4.5.1 was too new and that was my problem, and that I should be using .NET 4.0 Extended.  Then, another guy from Citrix told me that that wasn't correct, and in fact XenDesktop 7.5 requires at least .NET 4.5.  I'm running Server 2008 R2 by the way fully patched.

All I'm really trying to figure out is why after my XenDesktop 7.5  upgrade (from 5.6)  would the new Studio MMC crash and not open...and what can I do to resolve this when I attempt the upgrade again?

Have a question about something in this article? You can receive help directly from the article author. Sign up for a free trial to get started.