Delivery Controller 7.15.3000 LTSR and Licensing

Last Modified: Dec 12, 2018 @ 6:52 am


ūüí° = Recently Updated

Change Log


If you are performing a new install of XenApp/XenDesktop Controller, then skip to the next section.

You can upgrade directly from any Delivery Controller version 5.6 or newer.

  1. Cumulative Updates Р7.15 is a Long Term Service Release (LTSR). Citrix periodically releases Cumulative Updates for LTSR versions.
  2. LTSR compliance¬†‚Äď To remain compliant with LTSR (5 years of support), you must install the exact versions detailed at XenApp and XenDesktop 7.15 LTSR baseline components¬†at Citrix Docs. If you upgrade a single component beyond LTSR, then you should upgrade all¬†components to the latest release.
  3. OS Upgrade – If you are currently have 7.6 LTSR Controllers on Windows Server 2012 R2, and want to migrate to Windows Server 2016 Controllers, then do the following:
    1. In-place upgrade your Windows Server 2012 R2 Controllers to 7.15.3000 LTSR.
    2. Build a couple new Windows Server 2016 VMs with 7.15.3000 LTSR Controller and join them to the existing site/farm.
    3. Edit the ListOfDDCs registry key on each VDA to point to the new Win16 Controllers.
    4. Edit StoreFront Console > MyStore > Manage Delivery Controllers, and point to the new Win16 Controllers.
    5. Reconfigure Director server > IIS > Application Settings > Director path > Service.AutoDiscoveryAddresses to point to the new Win16 Delivery Controllers.
    6. Adjust monitoring tools to point to the new Win16 Controllers. For example, if using Citrix SCOM, deploy the Citrix SCOM Agents to the new Controllers, and remove from the old Controllers.
    7. If other components are installed on the old Controllers, move those components to the new Win16 Controllers.
    8. Remove the Windows Server 2012 R2 Controllers from Citrix Studio (Configuration > Controllers > Remove Controller), which removes them from the database.
    9. Decommission the Windows Server 2012 R2 Controllers.
  4. Licensing Server РBefore upgrading to 7.15.3000, upgrade your Citrix Licensing Server to Build 25000.
  5. Sysadmin permissions РThe person upgrading Delivery Controller needs temporary SQL sysadmin permission so the databases can be automatically upgraded. Or Citrix Studio can generate SQL scripts that a DBA must then run in SQL Studio.
  6. SCOM Agent РIf StoreFront is installed on the Controller, and if the Citrix SCOM Agent for StoreFront is installed, stop the Citrix MPSF Agent service. See CTX220935 Cannot Perform a StoreFront Upgrade if Citrix SCOM Management Pack Agent Service is Running.
  7. Close PowerShell and Consoles. Make sure all Citrix Consoles and PowerShell consoles are closed. StoreFront won’t upgrade if any are running. If StoreFront fails, then the StoreFront configuration is wiped out.
  8. Other Users – Use Task Manager > Users tab to logoff any other user currently logged into the machine.
  9. Snapshot. If StoreFront is installed on the Controller, take a snapshot before attempting the upgrade.
  10. Download the XenApp/XenDesktop 7.15.3000 LTSR ISO.
  11. Before upgrading, open PowerShell and run the following.
    asnp citrix*

    1. If you don’t see a returned value, then you’ll need to run additional commands to fix the Trust Database Connection as detailed at Known Issues at Citrix Docs
      $cs = Get-ConfigDBConnection
      Set-TrustDBConnection ‚ÄďDBConnection $cs
  12. Run AutoSelect.exe from the 7.15.3000 LTSR ISO.
  13. On the top left, under Upgrade, click Studio and Server Components.
  14. In the Licensing Agreement page, select I have read, understand, and accept the terms, and click Next.
  15. In the Ensure Successful Upgrade page, read the steps, check the box next to¬†I’m ready to continue, and click¬†Next.
  16. In the Firewall page, click Next.
  17. In the Summary page, click Upgrade.
  18. If you see a Running Processes window, close the listed programs, and click Continue.
  19. Click OK when asked to start the upgrade.
  20. In the Smart Tools page, make a selection. If participating, click Connect, login with Citrix Cloud or credentials, and then click Next. See Citrix Insight Services at Citrix Docs for more information on these options.
  21. In the Finish page, check the box next to Launch Studio, and click Finish.

Studio – Upgrade Database, Catalogs, and Delivery Groups

  1. After Citrix Studio launches, if you have¬†sysadmin permissions on SQL, then click¬†Start the automatic Site upgrade. If you don’t have full permission, then get a DBA to help you, click¬†Manually upgrade this site, and follow the instructions.

  2. If you choose to Manually upgrade this site, then note that there might not be an upgrade for the Logging Database schema, depending on what version you are upgrading from.

  3. After all Controllers and VDAs are upgraded, right-click the Catalogs, and click¬†Upgrade Catalog. Note: 7.9 is the newest¬†minimum functional level. You won’t see an option for 7.15.3000. If your Catalogs are already set to VDA version 7.9, then there’s no need to upgrade the Catalogs or Delivery Groups.

  4. Then do the same for the Delivery Groups.¬†Note: 7.9 is the newest¬†minimum functional level. You won’t see an option for 7.15.3000. If your Delivery Groups¬†are already set to VDA version 7.9, then no upgrade is needed.

Other XenApp/XenDesktop components can also be in-place upgraded:

New Install Preparation

Cumulative Updates Р7.15 is a Long Term Service Release (LTSR). Citrix periodically releases Cumulative Updates for LTSR versions.

LTSR compliance¬†‚Äď To remain compliant with LTSR (5 years of support), you must install the exact versions detailed at XenApp and XenDesktop 7.15 LTSR baseline components¬†at Citrix Docs. If you upgrade a single component beyond LTSR, then you should upgrade all¬†components to the latest release.

Installation Automation РIf you want to automate the install of Delivery Controllers, see Dennis Span Citrix Delivery Controller unattended installation with PowerShell and SCCM.

Citrix Licensing РIf you are going to use an existing Citrix Licensing Server, upgrade it to Build 25000.

Note: multiple license types (but not multiple editions) are supported in a single farm. See CTX223926 How to Configure Multiple License Types within a Single XenApp and XenDesktop Site.

SQL Databases

  • Citrix CTX209080 Database Sizing Tool for XenDesktop 7
  • Citrix article¬†CTX114501 –¬†Supported Databases for XenApp and XenDesktop Components
  • Three databases¬†‚Äď There are typically three databases: one for the¬†Site¬†(aka farm), one for¬†Logging¬†(audit log) and one for¬†Monitoring¬†(Director).
    • The name of the¬†monitoring¬†database must not have any spaces in it. See¬†CTX200325¬†Database Naming Limitation when Citrix Director Accesses Monitoring Data Using OData APIs
    • If you want Citrix Studio to create the SQL databases automatically, then the person running Studio must be a¬†sysadmin¬†on the SQL instances. No lesser SQL role¬†will work.¬†sysadmin¬†permissions can be granted temporarily and revoked after installation.
    • As an alternative, you can use Citrix Studio to create SQL scripts, and then run those scripts on the SQL server. In that case, the person running the scripts only needs the¬†dbcreator¬†and¬†securityadmin¬†roles.
    • It is possible to create the three databases in advance. However, you must use the non-default¬†Latin1_General_100_CI_AS_KS¬†collation.
  • SQL High Availability Options:
    • Basic Availability Groups¬†‚Äď Build two SQL 2016 (or newer)¬†Standard Edition¬†servers and create three Basic Availability Groups, one for each database. Each Basic Availability Group has its own Listener.
    • Database Mirroring¬†‚Äď Build two SQL 2014 or older Standard Edition servers and configure Database Mirroring.
    • AlwaysOn Availability Group¬†‚Äď Build two SQL¬†Enterprise Edition¬†servers and create one AlwaysOn Availability Group with one Listener.
    • Failover Clustering¬†‚Äď Build two SQL Enterprise Edition servers and configure SQL Database Failover Clustering.
  • Cloud¬†‚Äď Azure SQL and AWS RDS are not supported. You‚Äôll need to build your own SQL Servers on IaaS VMs.

Windows Feature

Installing Group Policy Management on the Delivery Controllers lets you edit Citrix-targeted Group Policy Objects (GPOs) directly from the Controllers. Controllers already have Studio and Citrix Group Policy Management installed, so if GPMC runs from a Controller, then the GPO Editor will automatically have access to the Citrix Policies node. Or you can install Citrix Group Policy Management Plug-in on a different machine that has GPMC installed.


  • Create a role in vSphere Client. Assign a service account to the role at the Datacenter or higher level.

Delivery Controller New Install

  1. A typical size for the Controller VMs is 2-4 vCPU and 8+ GB of RAM. If all components (Delivery Controller, StoreFront, Licensing, Director, SQL Express) are installed on one server, then you might want to bump up memory to 10 GB or 12 GB.
  2. From Local Host Cache sizing and scaling at Citrix Docs:
    1. For LHC LocalDB, assign the Controller VMs a single socket with multiple cores.
    2. Add two cores for LHC.
    3. Add at least three more Gigs of RAM and watch the memory consumption.
    4. Since there’s no control over LHC election, ensure all Controllers have the same specs.
  3. Make sure the User Right Log on as a service includes NT SERVICE\ALL SERVICES or add NT SERVICE\CitrixTelemetryService to the User Right.
  4. Download the XenApp/XenDesktop 7.15.3000 ISO.
  5. On two Delivery Controllers, to install the Delivery Controller software, run AutoSelect.exe from the 7.15.3000 ISO.
  6. Click Start next to either XenApp or XenDesktop. The only difference is the product name displayed in the installation wizard.
  7. On the top left, click Delivery Controller.
  8. In the Licensing Agreement page, select I have read, understand, and accept the terms, and click Next.
  9. In the Core Components page, you can install all components on one server, or on separate servers. Splitting them out is usually recommended for the following reasons: large environments; or if you have multiple farms, and want to share the Licensing, StoreFront, and Director components across those farms. Click Next.
  10. In the Features page, uncheck the box next to Install Microsoft SQL Server 2014 SP2 Express, and click Next.
  11. In the Firewall page, click Next.
  12. In the Summary page, click Install. This will take several minutes.
  13. In the Call Home page, make a selection, click Connect, enter your Citrix Cloud or credentials, and then click Next.

  14. In the Finish page, click Finish. Studio will automatically launch.
  15. Ensure the two Controller VMs do not run on the same hypervisor host. Create an anti-affinity rule.
  16. Citrix Tech Zone¬†Endpoint Security and Antivirus Best Practices:¬†provides guidelines for configuring antivirus software in Citrix Virtual Apps and Desktops environments¬† ūüí°

Citrix Studio 7.15.2000 Hotfix 1

This hotfix is for 7.15 Cumulative Update 2. If you installed Cumulative Update 3 then you don’t need this fix.

Studio 7.15.2000 does not localize Citrix Policies. To fix it, install CTX235169 LIMITED RELEASE РHotfix DStudioWX86_7_15_2001 РFor Citrix Studio 7.15 LTSR CU2.

  1. Download the hotfix from CTX235169 and unzip it.
  2. Run DStudioWX86_7_15_2001.msi.
  3. In the Please read the Citrix Studio License Agreement page, check the box next to I accept the terms in the License Agreement, and click Install.
  4. In the Completed the Citrix Studio Setup Wizard page, click Finish.

Create Site – Create Database

There are several methods of creating the databases for XenApp/XenDesktop:

  • If you have sysadmin permissions to SQL, let Citrix Studio create the databases automatically.
  • If you don‚Äôt have sysadmin permissions to SQL, then use Citrix Studio to generate SQL scripts, and send them to a DBA.

Use Citrix Studio to Create Database Automatically

  1. Launch Citrix Studio. After it loads, click Deliver applications and desktops to your users.
  2. In the Introduction page, select An empty, unconfigured site. This reduces the number of pages in this Setup wizard. The other pages will be configured later.
  3. Enter a Site Name (aka farm name), and click Next. Only administrators see the farm name.
  4. In the Databases page, if you are building two Controllers, click Select near the bottom of the same page.

    1. Click Add.
    2. Enter the FQDN of the second Controller, and click OK. Note: the Delivery Controller software must already be installed on that second machine.
    3. Then click Save.
  5. If the person running Citrix Studio has sysadmin permissions to the SQL Server, then enter the SQL server name/instance in the three Location fields, and click Next.
  6. If you don’t have¬†sysadmin permission, the jump to the SQL Scripts section below.
  7. On the Licensing page, enter the name of the Citrix License Server, and click Connect. If you installed Licensing with your Delivery Controller, then simply enter localhost.
  8. If the Certificate Authentication appears, select Connect me, and click Confirm.T
  9. Then select your license, and click Next. See CTX223926 How to Configure Multiple License Types within a Single XenApp and XenDesktop Site.
  10. In the Summary page, if your databases are mirrored or in an Availability Group, each database will show high availability servers, and the name of the Mirror server. Click Finish.

  11. It will take some time for the site to be created.

Use Studio to create SQL scripts

  1. If you don’t have sysadmin permissions, change the selection to Generate scripts to manually set up databases on the database server.¬†Change the database names if desired, and click¬†Next.
  2. In the Summary page, click Generate scripts.
  3. A folder will open with six scripts. Edit each of the scripts.
  4. Near the top of each script are two lines to create the database. Uncomment both lines (including the go line). Then save and close the file.

  5. Once all of the scripts are edited, you can send them to your DBA.
    1. On the Principal SQL Server, open the file Site_Principal.sql.

    2. Open the Query menu, and click SQLCMD Mode to enable it.
    3. Then execute the script.
    4. If SQLCMD mode was enabled properly, then the output should look something like this:
    5. If you have a mirrored database, run the second script on the mirror SQL instance. Make sure SQLCMD mode is enabled.
    6. Repeat for the Logging_Principal.sql script.
    7. You’ll have to enable SQLCMD Mode for each script you open.

    8. Repeat for the Monitoring_Principal.sql script.
    9. Once again enable SQLCMD Mode.

    10. The person running Citrix Studio must be added to the SQL Server as a SQL Login, and granted the public server role, so that account can enumerate the databases.

  6. Back in Citrix Studio, click the Continue database configuration and Site setup button.
  7. In the Databases page, enter the SQL server name, and instance name, and click Next.

  8. On the Licensing page, enter the name of the Citrix License Server, and click Connect. If you installed Licensing with your Delivery Controller, then simply enter localhost.
  9. If the Certificate Authentication appears, select Connect me, and click Confirm.
  10. Then select your license, and click Next. See CTX223926 How to Configure Multiple License Types within a Single XenApp and XenDesktop Site.
  11. In the Summary page, if your databases are mirrored, each database will show high availability servers, and the name of the Mirror server. Click Finish.

  12. It will take some time for the site to be created.

Verify Database Mirroring

If your database is mirrored, when you run asnp citrix.* and then run get-brokerdbconnection, you’ll see the Failover Partner in the database connection string.

Second Controller

When building the first Delivery Controller, the scripts might have already included the second Delivery Controller. Thus no special SQL permissions are needed. If the second Delivery Controller has not already been added to the SQL databases, then there are several methods of adding a second Controller to the databases for XenApp/XenDesktop:

  • If you have sysadmin permissions to SQL, let Citrix Studio modify the databases automatically.
  • If you don‚Äôt have sysadmin permissions to SQL then use Citrix Studio to generate SQL scripts and send them to a DBA.

To use Citrix Studio to create the SQL Scripts:

  1. On the first Delivery Controller, if StoreFront is installed on the Controller, then delete the default StoreFront store (/Citrix/Store), and recreate it with your desired Store name (e.g. /Citrix/CompanyStore).
  2. On the second Delivery Controller, install XenDesktop as detailed earlier.
  3. After running Studio, click Connect this Delivery Controller to an existing Site.
  4. Enter the name of the first Delivery Controller, and click OK.
  5. If you don’t have full SQL permissions (sysadmin), click No when asked if you want to update the database automatically.
  6. Click Generate scripts.
  7. A folder will open with six scripts. If not mirroring, then the top three scripts need to be sent to a DBA. If mirroring, send all six.
  8. On the SQL Server, open one of the .sql files.

  9. Open the Query menu, and click SQLCMD Mode.
  10. Then execute the XenDesktop script.
  11. If SQLCMD mode was enabled properly, then the output should look something like this:
  12. Repeat for the remaining script files.
  13. Back in Citrix Studio, click OK.
  14. In Citrix Studio, under Configuration > Controllers, you should see both controllers.
  15. You can also test the site again if desired.

SSL for Delivery Controller

SSL certificates should be installed on each Delivery Controller to encrypt the traffic between StoreFront and Delivery Controller. This traffic contains user credentials. The SSL certificate on each Delivery Controller needs to match the FQDN of the Delivery Controller.

  • If StoreFront is installed on the Delivery Controller, then make sure the certificate matches the Delivery Controller FQDN, and not necessarily the StoreFront FQDN. The actual StoreFront certificate is hosted on NetScaler Load Balancing Virtual Server, and not usually on the StoreFront server.

To enable SSL for a Delivery Controller:

  1. Run¬†certlm.msc, go to Personal > Certificates, and create or install a server certificate that matches the Delivery Controller’s FQDN. This can be an internally-signed certificate if the StoreFront server trusts internally-signed certificates.
  2. If IIS is installed on the Delivery Controller, then simply run IIS Manager, go to Default Web Site, click Edit Bindings, and add an https binding using the chosen certificate.

If IIS is not installed on the Delivery Controller:

  1. Open Registry Editor and go to HKEY_CLASSES_ROOT\Installer\Products.
  2. Right-click Products and click Find.
  3. Enter Citrix Broker Service and click Find Next.
  4. On the left, you’ll see the key name in the form of a GUID. Start a Rename operation and copy the GUID. You’ll need this in a bit.
  5. Go to certlm.msc > Personal > Certificates.
  6. Double-click the certificate you want to bind.
  7. On the¬†Details tab, scroll down to¬†Thumbprint and copy the thumbprint. You’ll need this in a bit.
  8. Open a command prompt as administrator.
  9. Enter the following text:
    netsh http add sslcert ipport= certhash=
  10. Right after certhash= paste the certificate thumbprint you copied earlier.
    1. Remove the special character at the beginning of the thumbprint.
    2. Remove the spaces.
  11. Add the following to the command line:
  12. Paste the GUID for Citrix Broker Service that you copied earlier.
    1. Make sure the GUID has curly braces on both sides with no space between appid and the left curly brace.
    2. Add dashes to the GUID.
      1. After the first 8 characters, add a hyphen.
      2. After the next four characters, add a hyphen.
      3. After the next four characters, add a hyphen.
      4. After the next four characters, add a hyphen.
      5. The last group should have 12 characters.
  13. Press <Enter> to run the command.
  14. If you entered everything correctly, then it should say SSL Certificate successfully added.
  15. To confirm the certificate binding, run the following:
    netsh http show sslcert ipport=

Studio ‚Äď Slow Launch

From B.J.M. Groenhout at Citrix Discussions: The following adjustments can be made if Desktop Studio (and other Citrix management Consoles) will start slowly:

  • Within Internet Explorer, go to Tools ‚Äď Internet Options ‚Äď Tab Advanced ‚Äď Section Security, and uncheck the option Check for publisher‚Äôs certificate revocation

After adjustment Desktop Studio (MMC) will be started immediately. Without adjustment it may take some time before Desktop Studio (MMC) is started.

Registry setting (can be deployed using Group Policy Preferences):

  • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing
    • State“=dword:00023e00

Concurrent Logon Hard Limit

From Samuel Legrand XenApp 7.14 ‚Äď (Really) Manage a DR! – Citrix Policies has a setting called¬†Concurrent Logon Tolerance. However, it is not a hard limit, meaning once the limits are reached, it continues to let users connect. You can configure the Controllers to make it a hard limit by setting the following registry value:

  • HKLM\Software\Policies\Citrix\DesktopServer
    • LogonToleranceIsHardLimit (DWORD) = 1

Local Host Cache

If you have 10,000 or fewer VDAs per zone (up to 40,000 VDAs per multi-zone site/farm), you can enable Local Host Cache (LHC) instead of Connection Leasing. LHC allows new sessions to be started even if SQL database is unavailable. VDA limits for LHC are higher in 7.15 than previous versions of XenApp/XenDesktop.

From Local Host Cache sizing and scaling at Citrix Docs:

  1. For LHC LocalDB, assign the Controller VMs a single socket with multiple cores.
  2. Add two cores for LHC.
  3. Add at least three more Gigs of RAM and watch the memory consumption.
  4. Since there’s no control over LHC election, ensure all Controllers have the same specs.
  5. The Docs article has scripts for monitoring LHC performance.

From XenApp 7.12, LHC and a reboot at Citrix Discussions:

  • If the rebooted DDC is the elected one, a different DDC will take over (causing registration storm) and when the DDC gets back, it will take over brokering causing second registration storm. Site will sort itself out and all will work.
  • If the rebooted DDC is not the elected one, it will not impact any functionality.
  • If you turn the DDC down when site is working, and start it during outage, LHC will not trigger on that machine. This DDC will not impact the LHC unless it would become the elected one. In that scenario it will take control, however not start LHC and resources would not be available.

Trentent Tye at¬†Citrix XenDesktop/XenApp 7.15 ‚Äď The local host cache in action¬†has a video showing LHC in action.¬†¬†ūüí°

For Windows Server 2008 R2 Controllers, PowerShell 3, or newer, is required. See LHC XD 7.12 and W2K8SR2 SP1 at Citrix Discussions.

As mentioned by Citrix Docs, make sure PowerShell Execution Policy is set to RemoteSigned, Unrestricted, or Bypass.

If you did a fresh install of 7.15, then Local Host Cache should be enabled by default. You can run Get-BrokerSite to confirm. (run asnp citrix.* first).

If not enabled, you can run some PowerShell commands to enable Local Host Cache:

asnp citrix.*
Set-BrokerSite -ConnectionLeasingEnabled $false
Set-BrokerSite -LocalHostCacheEnabled $true

George Spiers Local Host Cache XenApp & XenDesktop 7.12 shows the Event Log entries when LHC is enabled.

Database Maintenance

Enable Read-Committed Snapshot

The XenDesktop Database can become heavily utilized under load in a large environment. Therefore Citrix recommends enabling the Read_Committed_Snapshot option on the XenDesktop databases to remove contention on the database from read queries. This can improve the interactivity of Studio and Director. It should be noted that this option may increase the load on the tempdb files. See Citrix article CTX137161 How to Enable Read-Committed Snapshot in XenDesktop for configuration instructions.

Change Database Connection Strings

Sometimes the database connection strings need to be modified:

  • When moving the SQL databases to a different SQL server
  • For AlwaysOn Availability Groups, to add MultiSubnetFailover to the SQL connection strings
  • For SQL mirroring, to add Failover Partner to the SQL connection strings

Here are general instructions for moving the database and assigning the correct permissions:

  1. Backup the three Citrix databases on the original SQL server, and restore them on the new SQL server. See Microsoft’s documentation for details.
  2. In SQL Management Studio > Security > Logins, add the Delivery Controller computer accounts (e.g. CORP\DDC01$)
  3. When adding the SQL Login, on the User Mapping page, select the three Citrix databases (Site database, Monitoring database, and Logging database)
  4. For each of the three Citrix databases, add the Delivery Controller computer account to the various database roles as listed below. The Site database has many more roles than the Logging and Monitoring databases.
    • Site database – ADIdentitySchema_ROLE
    • Site database – Analytics_ROLE (7.8 and newer)
    • Site database – AppLibrarySchema_ROLE (7.8 and newer)
    • Site database – chr_Broker
    • Site database – chr_Controller
    • Site database – ConfigLoggingSchema_ROLE
    • Site database – ConfigLoggingSiteSchema_ROLE
    • Site database – ConfigurationSchema_ROLE
    • Site database – DAS_ROLE
    • Site database – DesktopUpdateManagerSchema_ROLE
    • Site database – EnvTestServiceSchema_ROLE
    • Site database – HostingUnitServiceSchema_ROLE
    • Site database – Monitor_ROLE
    • Site database – MonitorData_ROLE
    • Site database – OrchestrationSchema_ROLE (7.11 and newer)
    • Site database – public
    • Site database – StorefrontSchema_ROLE (7.8 and newer)
    • Site database – TrustSchema_ROLE (7.11 and newer)
    • Monitoring database – Monitor_ROLE
    • Monitoring database – public
    • Logging database – ConfigLoggingSchema_ROLE
    • Logging database – public

From Citrix Docs Update database connection strings when using SQL Server high availability solutions: Citrix offers several PowerShell scripts that update Delivery Controller database connection strings when you are using SQL Server high availability database solutions such as AlwaysOn and mirroring. The scripts, which use the Citrix Virtual Apps and Desktops PowerShell API, are:

  • DBConnectionStringFuncs.ps1: The core script that does the actual work. This script contains common functions that the other scripts use.
  • Change_XD_Failover_Partner_v1.ps1: Updates (adds, changes, or removes) the failover partner. This script prompts for the failover partner location (FQDN) for each database. (Providing a blank failover partner removes the failover partner. You can also use the ClearPartner option to remove a partner.) Do not set the failover partner to the same location as the principal database server.
  • Change_XD_To_ConnectionString.ps1: Uses the provided connection strings to update the connection strings to the databases. This script ensures that certain Citrix services are up and running, and then updates those services in the correct order on all Controllers in the site. Enclose connection string information for each database in quotes.
  • Change_XD_To_MultiSubnetFailover.ps1: Toggles the addition and removal of MultiSubnetFailover=true. If you use AlwaysOn Availability Groups, Microsoft recommends that the connection string include MultiSubnetFailover=true. This option speeds up recovery when a high availability event occurs, and is recommended for both single and multi-subnet environments. Run this script once to add the option. Run the script again to remove it.
  • Change_XD_To_Null.ps1: Resets all the connection strings on the localhost because something has gone wrong. By resetting the connection strings to null, this script places the Controller into an ‚Äúinitial‚ÄĚ state. If you run Studio after running this script, you’ll be asked if you want to create a site or join an existing site. This is useful if something has gone wrong and a reset is needed. After the reset, you can try again to set the connection strings.

Here are the DB Connections that must be changed. Make sure you include all of the DB Connections shown below. You can get the full list of database commands by running Get-Command Set-*DBConnection. When changing the DB connections, AdminDBConnection must be the last to be set to NULL, and the first to be configured with the new connection string.

Remove the existing Database connections

At the Delivery Controller, open PowerShell as Administrator and run the following commands to clear the existing database connections.

## Load the Citrix snap-ins
asnp Citrix.*

Disable configuration logging for the XD site:
Set-LogSite -State Disabled

## ## Clear the current Delivery Controller database connections
## Note: AdminDBConnection must be the last command
Set-ConfigDBConnection -DBConnection $null
Set-AppLibDBConnection ‚ÄďDBConnection $null ¬† ¬†#7.8 and newer
Set-OrchDBConnection ‚ÄďDBConnection $null ¬† ¬†  #7.11 and newer
Set-TrustDBConnection ‚ÄďDBConnection $null     #7.11 and newer
Set-AcctDBConnection -DBConnection $null
Set-AnalyticsDBConnection -DBConnection $null # 7.6 and newer
Set-HypDBConnection -DBConnection $null
Set-ProvDBConnection -DBConnection $null
Set-BrokerDBConnection -DBConnection $null
Set-EnvTestDBConnection -DBConnection $null
Set-SfDBConnection -DBConnection $null
Set-MonitorDBConnection -DataStore Monitor -DBConnection $null   #Monitoring Database
Set-MonitorDBConnection -DBConnection $null                      #Site Database
Set-LogDBConnection -DataStore Logging -DBConnection $null       #Logging Database
Set-LogDBConnection -DBConnection $null                          #Site Database
Set-AdminDBConnection -DBConnection $null -force

Specify the new Database connection strings

Run the following commands to set the new connection strings.¬†Adjust the variables to match your desired connection string. For example, if you wish to add “;MultiSubnetFailover=True” to the connection strings, then set the $csSite variable to "Server=$ServerName;Initial Catalog=$SiteDBName;Integrated Security=True;MultiSubnetFailover=True".¬†Repeat this for the $csLogging and $csMonitoring variables.

## Replace <dbserver> with the SQL server name, and instance if present, e.g "ServerName\SQLInstanceName". If no SQL Instance name is mentioned, this commandlet will try to connect to the default SQL instance.
## Replace <dbname> with the name of your restored Database
## Note: AdminDBConnection should be first

$ServerName = "<dbserver>"
$SiteDBName = "<SiteDbName>"
$LogDBName = "<LoggingDbName>"
$MonitorDBName = "<MonitorDbName>"
$csSite = "Server=$ServerName;Initial Catalog=$SiteDBName;Integrated Security=True"
$csLogging = "Server=$ServerName;Initial Catalog=$LogDBName;Integrated Security=True"
$csMonitoring = "Server=$ServerName;Initial Catalog=$MonitorDBName;Integrated Security=True"

Set-AdminDBConnection -DBConnection $csSite
Set-ConfigDBConnection -DBConnection $csSite
Set-AcctDBConnection -DBConnection $csSite
Set-AnalyticsDBConnection -DBConnection $csSite # 7.6 and newer
Set-HypDBConnection -DBConnection $csSite 
Set-ProvDBConnection -DBConnection $csSite
Set-AppLibDBConnection ‚ÄďDBConnection $csSite # 7.8 and newer
Set-OrchDBConnection ‚ÄďDBConnection $csSite # 7.11 and newer
Set-TrustDBConnection ‚ÄďDBConnection $csSite # 7.11 and newer
Set-BrokerDBConnection -DBConnection $csSite
Set-EnvTestDBConnection -DBConnection $csSite
Set-SfDBConnection -DBConnection $csSite
Set-LogDBConnection -DBConnection $csSite
Set-LogDBConnection -DataStore Logging -DBConnection $null
Set-LogDBConnection -DBConnection $null
Set-LogDBConnection -DBConnection $csSite
Set-LogDBConnection -DataStore Logging -DBConnection $csLogging
Set-MonitorDBConnection -DBConnection $csSite
Set-MonitorDBConnection -DataStore Monitor -DBConnection $null
Set-MonitorDBConnection -DBConnection $null
Set-MonitorDBConnection -DBConnection $csSite
Set-MonitorDBConnection -DataStore Monitor -DBConnection $csMonitoring
Set-LogSite -State Enabled

Test the new Database connection strings

Run the following commands to verify connectivity to the database:

asnp citrix.*

## Copy these variables from the previous step
## If you haven’t closed your PowerShell window, then the variables might still be defined. In that case, just run the Test commands
$ServerName = "<dbserver>"
$SiteDBName = "<SiteDbName>"
$LogDBName = "<LoggingDbName>"
$MonitorDBName = "<MonitorDbName>"
$csSite = "Server=$ServerName;Initial Catalog=$SiteDBName;Integrated Security=True"
$csLogging = "Server=$ServerName;Initial Catalog=$LogDBName;Integrated Security=True"
$csMonitoring = "Server=$ServerName;Initial Catalog=$MonitorDBName;Integrated Security=True"

Test-AcctDBConnection -DBConnection $csSite
Test-AdminDBConnection -DBConnection $csSite
Test-AnalyticsDBConnection -DBConnection $csSite # 7.6 and newer
Test-AppLibDBConnection -DBConnection $csSite # 7.8 and newer
Test-BrokerDBConnection -DBConnection $csSite
Test-ConfigDBConnection -DBConnection $csSite
Test-EnvTestDBConnection -DBConnection $csSite
Test-HypDBConnection -DBConnection $csSite
Test-LogDBConnection -DBConnection $csSite
Test-LogDBConnection -DataStore Logging -DBConnection $csLogging
Test-MonitorDBConnection -DBConnection $csSite
Test-MonitorDBConnection -Datastore Monitor -DBConnection $csMonitoring
Test-OrchDBConnection -DBConnection $csSite # 7.11 and newer
Test-ProvDBConnection -DBConnection $csSite
Test-SfDBConnection -DBConnection $csSite
Test-TrustDBConnection -DBConnection $csSite # 7.11 and newer

Director Grooming

If XenDesktop is not Platinum Edition, then all historical Director data is groomed at 30 days.

For XenDesktop/XenApp Platinum Edition, by default, most of the historical Director data is groomed at 90 days. This can be adjusted up to 367 days by running a PowerShell cmdlet.

  1. On a Delivery Controller, run PowerShell elevated (as administrator), and run asnp Citrix.*
  2. Run Get-MonitorConfiguration to see the current grooming settings.
  3. Run Set-MonitorConfiguration to change the grooming settings.

View Logging Database

To view the contents of the Logging Database, in Studio, click the Logging node. On the right is Create Custom Report. See Citrix article CTX138132 Viewing Configuration Logging Data Not Shown for more info.

The Logging Database can be queried using Get-LogLowLevelOperation. See Stefan Beckmann Get user who set maintenance mode for a server or client for an example script that uses this PowerShell cmdlet.

Maintain Logging Database

Citrix¬†CTX215069¬†Troubleshooting and managing Oversized Configuration Logging database:¬†The article’s¬†queries can be used to determine the number of configuration operation types performed by XenDesktop Administrator, and to analyze the content of the Configuration Logging database when it is considered oversized.¬†A grooming query is also provided to delete data older than a specified date.

Export/Import Configuration

Ryan Butler has a PowerShell script that can export configuration from one XenDesktop farm and import it to another.

Studio Administrators

Full Administrators

  1. In the Studio, under Configuration, click the Administrators node. The first time you access the node you‚Äôll see a Welcome¬†page. Feel free to check the box to Don’t show this again, and then click Close.
  2. On the Administrators tab, right-click, and click Create Administrator.
  3. In the Administrator and Scope page, Browse to a group (e.g. Citrix Admins) that will have permissions to Studio and Director. These groups typically have access to all objects, so select the All scope. Alternatively, you can create a Scope to limit the objects. Click Next.
  4. On the Role page, select a role, and then click Next. For example:
    • Full Administrator for the Citrix Admins group
    • Help Desk Administrator for the Help Desk group
    • Machine Catalog Administrator for the desktop team
  5. In the Summary page, click Finish.

Help Desk

  1. In the Studio, under Configuration, click the Administrators node. On the Administrators tab, right-click, and click Create Administrator.
  2. In the Administrator and Scope page, Browse to a Help Desk group that will have permissions to Studio and Director. Select the All scope. And click Next.
  3. On the Role page, select the Help Desk Administrator role, and then click Next.
  4. In the Summary page, click Finish.
  5. When administrators in the Help Desk role log into Director, all they see is this.

    To jazz it up a little, add the Help Desk group to the read-only role.
  6. Right-click the Help Desk Administrator, and click Edit Administrator.
  7. Click Add.
  8. In the Scope page, select a scope, and click Next.
  9. In the Role page, select Read Only Administrator, and click Next.
  10. In the Summary page, click Finish.
  11. Then click OK. Now Director will display the dashboard.

Customer Experience Improvement Program

XenApp/XenDesktop 7.15 enables CEIP by default. If desired, you can disable it in Citrix Studio:

  1. On the left, go to the Configuration node.
  2. On the right, switch to the Product Support tab.
  3. Click End.
  4. Click Yes.

Each XenApp/XenDesktop component has a separate configuration for disabling Customer Experience Improvement Program:

vCenter Connection

XenDesktop uses an Active Directory service account to log into vCenter. This account needs specific permissions in vCenter. To facilitate assigning these permissions, create a new vCenter role and assign it to the XenDesktop service account. The permissions should be applied at the datacenter or higher level.

Import vCenter Root Certificate

If the vCenter certificate is valid and trusted, then you can skip to the Hosting Resource section.

For newer versions of vCenter, you can import the root certificate that signed the vCenter Server/Appliance certificate.

  1. Point your browser to the root path of the vCenter Server URL.
  2. On the bottom right, click Download trusted root CA certificates.
  3. Extract the downloaded files.
  4. Go to \certs\win.
  5. Sort the files by date, and double-click the newest .crt file.
  6. On the General tab, click Install Certificate.
  7. In the Welcome to the Certificate Import Wizard page, change the Store Location selection to Local Machine, and click Next.
  8. In the Certificate Store page, click Browse.
  9. Select Trust Root Certification Authorities, and click OK.
  10. In the Completing the Certificate Import Wizard page, click Finish.
  11. If you close your browser and reopen it, and then go to the vCenter URL, there should no longer be any certificate errors.
  12. Skip to the Hosting Resource section.

Import vCenter Certificate

If the vCenter certificate is valid and trusted, then you can skip to the Hosting Resource section.

Alternatively, you can import the actual vCenter Server certificate (instead of the root). This is the only option for older self-signed vCenter certificates.

Newer versions of XenDesktop have the ability to import the vCenter certificate thumbprint into the database so every Controller trusts it. However, it is difficult to update the thumbprint whenever the vCenter certificate changes. It might instead be more reliable to use the older method of configuring the¬†Trusted People store on the Delivery Controllers. Whenever the vCenter certificate is changed, you’ll need to repeat these steps.

  1. Get the vCenter certificate.
    1. Open a browser and point it to the vCenter URL. Note: this procedure to get the certificate won’t work in Internet Explorer.
    2. If Google Chrome, press <F12> to open the Developer Tools.
    3. On the top right, click the two right arrows to show more tabs, and click Security.
    4. On the Security tab, click View certificate.
    5. On the Details tab, click Copy to File.
    6. In the Welcome to the Certificate Export Wizard page, click Next.
    7. In the Export File Format page, either format will work. Click Next.
    8. In the File to Export page, browse to a new file, and click Next.
    9. In the Completing the Certificate Export Wizard page, click Finish.
  2. If your Delivery Controller is Windows 2012 R2 or newer, then simply run certlm.msc. This opens the MMC console with Certificates snap-in already added and pointing to Local computer.
    1. For Windows 2008 R2, run mmc.exe, open the File menu, and click Add/Remove Snap-in.
    2. Move the Certificates snap-in to the right by highlighting it, and clicking Add.
    3. Select Computer account, and click Next.
    4. Select Local computer, and click Finish.
    5. Click OK.
  3. On the left, right-click the Trusted People node, expand All Tasks, and click Import.
  4. In the Welcome to the Certificate Import Wizard page, click Next.
  5. In the File to Import page, browse to the certificate you saved earlier, and click Next.
  6. In the Certificate Store page, click Next.
  7. In the Completing the Certificate Import Wizard page, click Finish.
  8. Click OK to acknowledge that the import was successful.
  9. Repeat these steps on the second Controller. It is important that you import the certificate on both Controllers before adding the Hosting Resource.
  10. If you open Internet Explorer and browse to the vCenter Server, there should be no certificate errors.

Hosting Resources

A Hosting Resource = vCenter + Cluster (Resource Pool) + Storage + Network. When you create a machine catalog, you select a previously defined Hosting Resource, and the Cluster, Storage, and Network defined in the Hosting Resource object are automatically selected. If you need some desktops on a different Cluster+Storage+Network then you’ll need to define more Hosting Resources in Studio.

  1. In Studio, expand Configuration and click Hosting. Right-click it, and click Add Connection and Resources.
  2. In the Connection page, for Connection type, select VMware vSphere.
  3. Notice there’s a Learn about user permissions¬†blue link to an article that describes the necessary permissions.
  4. Enter https://vcenter01.corp.local/sdk as the vCenter URL. The URL must contain the FQDN of the vCenter server.
  5. Enter credentials of a service account that can log into vCenter.
  6. In the Connection name field, give the connection a name. Typically, this matches the name of the vCenter server.
  7. If you are not using Machine Creation Services, and instead only need the vCenter connection for machine power management, change the Create virtual machines using selection to Other Tools. If you intend to use MCS, leave it set to Studio Tools.
  8. Click Next.

  9. In the Storage Management page, click Browse, and select a vSphere cluster.
    • Note: as detailed at CTX223662, make sure there’s no comma in the datacenter name.
  10. Select Use storage shared by hypervisors.
  11. If you have sufficient disk space on each ESXi host, also select¬†Optimize temporary data on available local storage.¬†From Mark Syms at¬†XA 7.9 MCS with RAM Caching¬†at Citrix Discussions: “If you use just MCS caching to local storage then the VM is not agile at all and cannot be moved even when powered off as it has a virtual disk permanently associated with a single host.”
  12. From Martin Rowan at XA 7.9 MCS with RAM Caching¬†at Citrix Discussions: for the temporary cache disk, “Don’t format it, the raw disk is what MCS caching uses.”
  13. Click Next.
  14. In the Storage Selection page, OS and Personal vDisk must be selected on at least one datastore. For maximum flexibility, only select one datastore. To select additional datastores, run this wizard again to create a separate Hosting Resource.
  15. If you selected the temporary data on local storage option, on the bottom, click Select, and choose the datastores you want to use for disk caching. By default, all local datastores are selected. Click Next when done.
  16. In the Network page, enter a name for the hosting resource. Since each hosting resource is a combination of vCenter, Cluster, Network, and Datastores, include those names in this field (e.g. vCenter01-Cluster01-Network01-Datastore01).
  17. Select a network and click Next.
  18. In the Summary page, click Finish.
  19. If you have multiple datastores for your VDAs, run the wizard again.
  20. You can use the existing vCenter connection.
  21. This time, select a different datastore.
  22. Give it a name that indicates the chosen datastore.
  23. When you create a Catalog, select the Hosting Resource for the datastore where you want the VDAs to be placed. Create additional Catalogs for each datastore. You can then combine the Catalogs into a single Delivery Group.
  24. Later in the Catalog wizard, you’re given an option to enable caching and select a cache size. This is similar to Provisioning Services option “Cache in RAM with overflow to disk”.
  25. If you rename Storage, Network, or Datacenters, see Citrix CTX225019 XA/XD 7.13: Renaming Storage, Network or Datacenters When Used With MCS or PVS. Either run Update-HypHypervisorConnection -LiteralPath "XDHyp:\Connections\MyConnection", or right-click the Hosting Resource and click Edit Storage. You can cancel the wizard.

Citrix Licensing Server


XenApp/XenDesktop 7.15.3000 comes with Build 25000.

If you have a standalone Licensing Server, upgrade it to Citrix Licensing build 25000, if it isn’t already.

  1. Go to the downloaded Citrix Licensing Build 25000, and run CitrixLicensing.exe.

  2. If you see the Subscription Advantage Renewal page, make a selection, and click Next.
  3. In the Upgrade page, click Upgrade.
  4. Click Finish.
  5. If you go to Programs and Features, it should now show version build 25000.
  6. If you login to the license server web console, on the Administration tab…
  7. It shows it as version build 25000.

Activate Citrix License

The easy way to install and activate a Citrix license is through Citrix Studio:

  1. In Citrix Studio, expand Configuration, right-click Licensing, and click Allocate Licenses.
  2. Enter the LA- license code, and click Show. You can find your code at, click All Licensing Tools, and click View Licenses.
  3. Then click Allocate licenses.

    1. Another method of allocating licenses is in the new Licensing Manager at https://MyLicenseServer:8083.
  4. After licenses are installed, right-click the Licensing node, and click Edit Product Edition
  5. Change the edition to match your licenses. If you see both XenDesktop and XenApp licenses, you must select XenDesktop. If you see both Concurrent and User/Device, then you must select User/Device. Click OK when done.
  6. XenDesktop 7.14 and newer support mixed licensing in a single site/farm. See the following:

License Server CEIP build 19005 and newer enable CEIP by default. This can be disabled in the Citrix Licensing Manager (https://localhost:8083) by clicking the gear icon.

Switch to the Usage and Statistics tab, and make a selection in the Share usage statistics with Citrix section.

Citrix License Management Service

Version and newer include the Citrix License Management Service. This service helps you avoid prohibited practices:

  • Duplication of licenses outside a Disaster Recovery (DR) environment
  • Use of legacy licenses for new product versions
  • Use of rescinded licenses

Citrix License Server Monitoring

Citrix Licensing 11.13.1 and newer has historical usage reporting:

  1. Run Citrix Licensing Manager from the Start Menu. Or use a browser to connect to https://MyLicenseServer:8083
  2. Use the drop-down menus to select a license type, select dates, and export to a .csv file.
  3. The Update Licenses tab lets you check for renewals and download them.
  4. On the top right is a gear icon where you can set the historical retention period and configure SA license auto-renewal.

    1. On the Usage and Statistics tab…
    2. Scroll down and find the Historical Use section.

Jonathan Medd Monitor Citrix License Usage With PowerShell.

Lal Mohan РCitrix License Usage Monitoring Using Powershell

Jaroslaw Sobel ‚Äď Monitoring Citrix Licenses usage ‚Äď Graphs using WMI, Powershell and RRDtool. This script generates a graph similar to the following:

Remote Desktop Licensing Server

Install Remote Desktop Licensing Server

Do the following on your XenDesktop Controllers:

  1. In Server Manager, open the Manage menu, and click Add Roles and Features.
  2. In the Installation Type page, select Role-based or feature-based installation.
  3. Click Next until you get to the Server Roles page. Check the box next to Remote Desktop Services, and click Next.
  4. Click Next until you get to the Role Services page. Check the box next to Remote Desktop Licensing, and click Next.
  5. Click Add Features if prompted.
  6. Then finish the wizard to install the role service.

Activate Remote Desktop Licensing

  1. After RD Licensing is installed, in Server Manager, open the Tool menu, expand Terminal Services (or Remote Desktop Services), and click Remote Desktop Licensing Manager.
  2. The tool should find the local server. If it does not, right-click All servers, click Connect, and type in the name of the local server.
  3. Once the local server can be seen in the list, right-click the server and click Activate Server.
  4. In the Welcome to the Activate Server Wizard page, click Next.
  5. In the Connection Method page, click Next.
  6. In the Company Information page, enter the required information, and click Next.
  7. All of the fields on the Company Information page are optional, so you do not have to enter anything. Click Next.
  8. In the Completing the Activate Server Wizard page, uncheck the box next to Start Install Licenses Wizard now, and click Finish. Since the session hosts will be configured to pull Per User licenses, there is no need to install licenses on the RD Licensing Server.
  9. In RD Licensing Manager, right-click the server, and click Review Configuration.
  10. Ensure you have green check marks. If the person installing Remote Desktop Licensing does not have permissions to add the server to the Terminal Server License Servers group in Active Directory, ask a domain admin to do it manually. If you have the proper permissions, click Add to Group.
  11. Click Continue when prompted that you must have Domain Admins privileges.
  12. Click OK when prompted that the computer account has been added.
  13. Click OK to close the window.

Smart Check

Citrix Cloud offers a Smart Check service that can scan your XenApp/XenDesktop infrastructure for known issues.

To run Smart Check:

  1. Go to, and login.
  2. After logging in, under My Services, find Smart Tools, and click Manage.
  3. Click Smart Check.
  4. If you enabled Smart Tools during the installation of XenDesktop 7.15, then the site should already be there. Click Complete Setup.
  5. If you didn’t enable Smart Check during XenDesktop installation, then on the top right, click¬†Add Site.

    1. In step 1, click Download Agent.
    2. Step 2 indicates it is waiting for you to install the Agent.
    3. On a Delivery Controller, run the downloaded CitrixLifecycleManagementAgent.exe.
    4. Check the box next to I accept the terms in the License Agreement, and click  Install.
    5. In the Completed the Citrix Smart Tools Agent Setup Wizard page, click Finish.
    6. Step 2 now shows that the Agent was installed successfully. Click Next.
  6. Enter credentials for your XenDesktop farm, and click Add Site, or click Done.
  7. Eventually you’ll see a¬†Get Started link.
  8. Or, if the site is already added to your list of sites, click View Report next to the site.
  9. StoreFront, Provisioning Services, and Licensing Server cannot be automatically detected. You can add a Custom Check that targets those machines. See Perform health checks on Storefront, Licensing, and Provisioning Servers at Citrix Docs.
  10. At the top right, if you click Perform Check, you can run one of the checks.
  11. If you click Configure.
  12. You can schedule the checks to automatically run periodically.
  13. To view the alerts, click one of the alert badges in the component category. Also see Smart Check alerts reference at Citrix Docs.
  14. Expand a component, and click an alert.
  15. On the right, there’s an option to¬†Hide Alert.

  16. To view the hidden alerts, at the top right, click the menu icon, and click Show Hidden Alerts.
  17. The hidden alert is grayed out. If you click the alert, you can restore it.

Additional Smart Checks

The Blueprint Catalog has additional checks that you can add to Smart Check. Click Blueprint Catalog in the menu bar. Scroll down to the Citrix Checks section, and click the plus icon next to one of them.

When you go back to Smart Check, open a site (View Report), and click Perform Check, you’ll see the Custom Check that you added from the Blueprint Catalog.

See Citrix Blog Post VDA Health Check Now Available on Smart Check.

Citrix Scout

XenDesktop 7.15 includes a new Citrix Scout that can be launched from the Start Menu.

The tool can run a manual collection, run a trace, or schedule periodic collection. The results are uploaded to Citrix Smart Tools.

Links with more information:

XenApp/XenDesktop Health Check

Sacha Tomet¬†Finally 1.0 ‚Äď but never finalized!:¬†XenApp & XenDesktop 7.x Health Check script has now Version 1.0.

Pavan900 posted a PowerShell-based Health Check script at Citrix Studi РColors for Maintenance Mode at Citrix Discussions.

Andrew Morgan – New Free Tool: Citrix Director Notification Service: The Citrix Director Notification service sits on an edge server as a service (or local to the delivery controller) and periodically checks the health of:

  • Citrix Licensing.
  • Database Connections.
  • Broker Service.
  • Core Services.
  • Hypervisor Connections.

And if any of these items fall out of bounds, an SMTP alert is sent to the mailbox of your choice for action. The tool will also send ‚ÄúAll Clear‚ÄĚ emails when these items are resolved, ensuring you are aware when the service has resumed a healthy state.

Matt Bodholdt XenDesktop 7.x Controller Service Status Script at CUGC – PowerShell script that checks the following:

  • Lists Controllers with boot time
  • Licensing status
  • Service status on each Controller
  • DB Connections
  • Controller Available Memory
  • Hypervisor Connections Status

Related Pages

43 thoughts on “Delivery Controller 7.15.3000 LTSR and Licensing”

  1. I am looking to add a 7.18 DDC into my 7.15 LTSR farm as part of a process to have the DDC, Storefront, Licensing etc on the latest version but run a mixed, 7.15 LTSR and 7.18 VDA’s. When I try to add the 7.18 DDC to the farm it prompts for a database upgrade. I assume there are no issues of this to the functionality of the 7.15 components in the farm?

    1. From Citrix Docs: “Within each Site, Citrix recommends upgrading all components. Although you can use earlier versions of some components, all the features in the latest version might not be available. For example, although you can use current VDAs in deployments containing earlier Controller versions, new features in the current release may not be available. VDA registration issues can also occur when using non-current versions.” I always upgrade all Controllers at the same time. If you need different versions, then you can create separate farms.

  2. I am looking for solution to optimize HDX bandwidth over the MPLS link. We have 256 kpbs MPLS link in which currently 3 users are using outlook application and they are facing application hanging issue while accessing. So hereby i want to know which device I can be use to optimize the HDX bandwidth connections and apart from that what configuration do I have to do at DDC level in case of HDX optimization..

  3. Hello Carl,

    I currently have a 7.12 production platform (License, 2 Controllers, 2 SF, 2 Director) , and building a 7.12 UAT Platform in order to validate a 7.15 upgrade.

    Currently, the 2 platform get licenses from the same Licenses server (7.12).

    Is it possible to upgrate thise licenses server to 7.15, and get UAT platform (7.15) and production platform (7.12) running correctly? this mixed scenario should be running for 3 weeks.

    Thank you for your help



  4. HI Carl

    Do we have any tool for power management for xenapp 7.18 similar to citrix smart scale.

    i have my ddc and vdi in azure and want to use feature similar to smart scale

    From what i have heard you need citrix cloud subscription to use smart scale and is not free.


  5. Citrix Xenapp 7.15 LTSR CU2 upgrade Installation suite doesnt show the core Components Page, i wonder why.
    I’m forced to upgrade all the components at one go.

    I have Storefront/DDC/License Server components installed on the Same server and want to upgrade DDC component before the storefront. i have already upgraded the License server.
    any inputs why i’m not displayed the Core Components page where i can selectively upgrade only few components in my infra?

  6. Hi Carl,
    I am planning for secure xml communication
    Currently its configured as below:
    1. DDCs are LB via VIP
    2.VIP in turn points to DDC on Prt 80
    3.Monitor used is XD DDC one
    4. for the LB VIP,there is no DNS entry
    5. VIP IP has been added as manage del controller on SF console Transport type HTTP with port 80
    6. No IIS installed on DDC.

    Can you please suggest how i can achieve this

    1. Due to Kerberos and WCF, Load Balancing will not work for VDA registration to Controllers.

      Due to STA tickets, load balancing will not work for NetScaler Gateway to Controllers.

      You might be able to put a cert on the load balancer and configure StoreFront to point to the load balanced FQDN using https. But that’s all you can do with load balancing.

  7. What is the reasoning for installing the Remote Desktop Licensing Server on the Controllers and not the Citrix License Server? And if this must be the case, should the RDLS be on every Controller? Thanks.

  8. Carl,

    I am having issues with a couple of my DDC’s. When I look in Studio it shows on 1 DDC under controllers. The other two are not there. Here’s where it gets weird. If I logon to either of the other two server (the ones not showing in Studio) and launch Studio, it launches and presents the Same info as the third DDC. I would expect to get the “Join an existing site, create a new site, etc” screen.

    I am in the process of upgrading to 7.15LTSR, and prior to the upgrade, I removed both DC A and B from the site as we have not upgraded the VDAs yet and did not want to cause issues. Any thought on this?

    I have run the evict scripts in the past for dead DDC’s but even thought server A and B do not show up anywhere in the database, or when running broker commands, they still connect to the DB. Please help, I am not in a position to rebuild the site, as this is a live production environment.

      1. I was not able to remove the other two DCs through studio, as they did not show up in the list of controllers. I set DB connections to null and ran evict scripts to try to get them out entirely but when i launch studio from either DC1 or DC 2 it still opens like they are functional. I guess my roundabout question is why does studio open on DC 1 and 2 if they do not show up in the list of controllers? I have had several sites where this has happened, and Citrix support can’t seem to give me a reason. Hoping you can shed some light on that.

  9. Hi Carl,
    i have a global farm with 2 DDC in USA and 2 in Israel under same DB, when i open the studio it is take long time to launch it, i already did unchecked the option Check for publisher’s certificate revocation on all DDC servers.
    any ideal what can be the reason?

  10. Hi Carl,
    In the “Activating Remote Desktop Licensing” section you state the following:

    “In the Completing the Activate Server Wizard page, uncheck the box next to Start Install Licenses Wizard now, and click Finish. Since the session hosts will be configured to pull Per User licenses, there is no need to install licenses on the RD Licensing Server.”

    If we have a XenApp 7.15 environment only using Server OS to deliver published desktops, don’t we need to purchase Windows Remote Desktop User CALS for connecting to the session host servers? I’m confused that you’re saying there is no need to install licenses.

    1. Yes, RDSH machines require each named user to have an RDS License.

      However, what I’m saying is that Per User RDS Licensing is not technically enforced like Per Device licenses are enforced. But you must still be compliant with licensing requirements.

  11. Studio ‚Äď Slow Launch

    – Despite this registry key being changed per the solution, it still takes 30-45 minutes to launch any Citrix MMC application (Storefront, Studio, etc.) any thoughts on what else could be interfering with the launch? Using 7.15 LTSR


    1. Are you blocking Internet access from the Studio machine? If you run Studio on a machine that has Internet access, is it faster?

  12. Hey Carl, I recently upgraded from 7.15 to CU1. The LTSR Assistant is complaining about the Citrix StoreFront Privilege Service on my storefront servers. When I look at the details of the Citrix.Storefront.PrivilegedService.exe file it does in fact show version 7.6.3000.1. I have a call logged with support, but wanted to know if you or anyone else has seen this before? Appwiz.cpl on both my storefront servers show this: storefront= 3.12.1000.1, XenApp= 7.15.1000.150, so I am confused that this one component did not upgrade.

        1. Never mind. I was looking in the wrong place. My version of the file is

          Have you tried uninstalling StoreFront and reinstalling? If you have a Server Group, you should be able to then replicate the config from the other node.

          1. I think I will wait for support before I take that on. Everything, to my knowledge, is currently working so I am a little gun shy with making too many changes without support on the call. Thanks.

  13. HI Carl i want to upgrade from 7.6 sp3 to 7.15 ltsr, storefront 3.01 to storefront 3.12( if is needed ), and profilemanagement 5.2 admx to 5.8 or whichever is on 7.15, my question is , if i do the inplace automatic upgrade will all those components work with my 2015 netscaler 11.0 instalation and the setttngs from there which i took from youre website or i need to reconfigure the netscaler?

    1. No NetScaler changes needed, unless you want to use the new UDP-based EDT protocol, or if you’re using AppFlow reporting.

  14. Is there a bug with 7.15 published applications? I published a simple notepad and calc and screen is black. A published desktop is working as expected. The published apps are running on a windows 2012 R2 server

    1. I have many 7.15 deployments with no issues with published applications. I’m guessing something environmental. Have you tried a clean 2012 build with just VDA and put it in an OU with no group policies?

  15. Hi Carl,

    thanks for the great tutorial. We are on XenDesktop 7.6 LTSR CU4 at the moment and plan to upgrade to 7.15 LTSR (license server already updated). We use two delivery controllers, the first one contains also the license server.
    Do you see any problems when I upgrade the first delivery controller, database, delivery groups etce during working hours? Are there logins still possible on the secont delivery controller?

    best regards,

    1. In theory, it should continue to allow logins during the upgrade process. Once the database is upgraded, the upgraded Controller will handle logons.

  16. Hi Carl

    We’re presently running 7.13 and waiting for 7.16 to upgrade. But as I just discovered that support for older OS like “Windows 7” would be depreciated in 7.16 and we still have some such, thought 7.15 LTSR would be an alternative.

    However I’m wondering if inplace upgrade from “LTSR” to “Current Release” is supported, when we would no longer required older OS.

    Trying to put all facts together before jumping into “LTSR”.


    1. Was the database offline during a scheduled restart of RDSH? If so, once the database is back online, it might kick off the scheduled restart.

      1. Not during a normal schedule restart and my database wasn’t offline at this time…
        I expect this force restart directly after the database upgrade.
        I can see some event like “the citrix broker service has begun the processing reboot cycle…” but it’s not the right time for schedule reboot.
        I guess it’s directly linked to database upgrade and schedule restart…
        Citrix is testing in a lab right now.

  17. Hi Carl: Thanks, as usual, for the very helpful documentation here on your Site. One question: I have looked everywhere for “yes” or “no” to this: Does the Delivery Controller, or any VDA that will host Apps or Desktops, need some of the “old” preparation steps that 6.5 used to require? Remember how we had to add the Roles of “Application Server” and “COM+” and “Remote Desktop Session Host” prior to installing XenApp on a Server? Along those same lines, do Apps get installed on a XenApp VDA (or any other) using something like that old “Install using Remote Desktop Services mode” or something similar? Thanks very much!

    1. The XenDesktop/XenApp installer automatically installs whatever it needs.

      If you’re installing MSI, or setup.exe, or install.exe, then no need to “change user /install”, since it happens automatically. Other installers might need it. I usually don’t do it, and fix HKCU manually, instead of relying on “install mode”.

  18. Hi Carl,

    In Studio, Configuration, Licensing when you Change Licensing Server on the Certificate Authentication screen, it always shows “This certificate is not trusted” and the expired license server certificate. Is this just getting the initial cert from when it first connected to the license server, nad not the current SSL cert? Is there a way to get it to fetch the current one? Or is it indeed getting the current one and I need to do something on the Licensing server, renew a cert or…? Thanks!

    1. There are two certs on License Server – one for LS, one for WebServices. I’m guessing you need to change the WebServices cert (C:\Program Files (x86)\Citrix\Licensing\WebServicesForLicensing\Apache\conf). Uninstall/reinstall should generate new self-signed cert.

  19. Hi Carl,

    I am going to implement 1000 Citrix XenApp users session and want to know how much bandwidth would be required at datacenter for the same.

Leave a Reply