Remote Desktop license issue Citrix

Navigation

• Change Log
• Upgrade to 7.16
• New Install Preparation
• Delivery Controller 7.16 Install
  • Create Site / Databases
  • Second Controller
• Studio Slow Launch
• Concurrent Logon Hard Limit
• Local Host Cache
• Database MaintenanceChange Databaseconnection strings, read-committed snapshot, Director grooming, Logging Database operations, etc.
• Export/Import Configuration
• Studio Administrators
• Customer Experience Improvement Program [CEIP]
• vCenter Connection vCenter certificate, Hosting Resources
• Citrix Licensing Server
  • Upgrade Licensing Server to 11.14.0.1 build 22103
  • Activate Citrix License
  • License Server CEIP
  • Citrix License Management Service
  • Citrix License Server Monitoring
• Remote Desktop Licensing Server
  • Install Remote Desktop Licensing Server
  • Active Remote Desktop Licensing Server
• Smart Check
  • Additional Custom Smart Checks
  • Citrix Scout
• Health Check

= Recently Updated

Change Log

• 2018 Jan 4 in Local Host Cache section, added note about PowerShell Execution Policy.
• 2017 Dec 3:
  • Added vCenter Root CA Certificate section as alternative to importing actual vCenter certificate.
  • In LHC section, added link toTrentent TyeCitrix XenDesktop/XenApp 7.15 The local host cache in action

Upgrade

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

You can in-place upgrade directly from any Delivery Controller version 7.0 or newer. Citrix recommends upgrading Delivery Controller 5.6 to 7.6 LTSR Cumulative Update 4 before upgrading to 7.16.

During the upgrade ofDelivery Controller, be aware that a database upgrade is required. Either get a DBA to grant you temporary sysadmin permission, or use Citrix Studio to generate SQL scripts that a DBA must then run in SQL Studio.

1. License Server Upgrade Before upgrading to Delivery Controller 7.16, if you have a standaloneCitrix Licensing Server, upgradeit to11.14.0.1 build 22103.
   
2. Frequent updates/upgrades XenApp and XenDesktop 7.16 is a Current Release.
   • With Current Release [CR], youre expected to upgrade to the future 7.17 [and 7.18, and 7.19, etc.] to receive bug fixes, and new features, which might include new bugs. Current Releases are only supported for six months from the release date. That means you should plan to perform these upgrades at least twice a year.
   • If you dont want to continuously upgrade to the latest Current Release, then you can stay onLTSR 7.15, which receivesCumulative Updateswith bug fixes, but no new features.SeeLifecycle Milestones for Citrix Virtual Apps & Citrix Virtual Apps and Desktops.
3. VDA OS Compatibility XenDesktop 7.16 Delivery Controller is supported on Windows 2008 R2 and newer. However, Virtual Delivery Agent [VDA] 7.16 is only supported on a limited number of Windows operating system versions, specifically, Windows 10 [1607+], Windows Server 2012 R2, and Windows Server 2016.
   • If you have older VDA machines running Windows 7 or Windows Server 2008 R2, you can leave their VDA software at version 7.15. It is supported for VDA 7.15 to communicate with Delivery Controllers 7.16.
4. SCOM Agent If StoreFront is installed on the Controller, and if the Citrix SCOM Agent for StoreFront is installed, stop theCitrix MPSF Agent service. SeeCTX220935Cannot Perform a StoreFront Upgrade if Citrix SCOM Management Pack Agent Service is Running.
   
5. Close PowerShell and Consoles. Make sure all Citrix Consoles and PowerShell consoles are closed. StoreFront wont upgrade if any are running. If StoreFront fails, then the StoreFront configuration is wiped out.
6. Other Users Use Task Manager > Users tab to logoff any other user currently logged into the machine.
   
7. Snapshot. If StoreFront is installed on the Controller, take a snapshot before attempting the upgrade.
   1. Another option is to export the StoreFront configuration so you can restore it later if something goes wrong.
8. Download the XenApp/XenDesktop 7.16 ISO.
   
9. Before upgrading, open PowerShell and run the following.asnp citrix* Get-TrustDBConnection
   1. If you dont see a returned value, then youll 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
10. RunAutoSelect.exe from the 7.16 ISO.
    
11. On the top left, clickStudio and Server Components.
    
12. In theLicensing Agreementpage, selectI have read, understand, and accept the terms, and clickNext.
    
13. In the Ensure Successful Upgrade page, read the steps, check the box next toIm ready to continue, and clickNext.
    
14. If you see aLicensing Errors page, make sure the errors dont apply to you, check the box next to Let me continue,and clickNext.
    
15. In theFirewall page, clickNext.
    
16. In theSummary page, clickUpgrade.
    
17. If you see a Running Processes window, close the listed programs, and click Continue.
    
18. Click OK when asked to start the upgrade.
    
19. If the upgrade fails:
    1. Look for MetaInstaller log files under %localappdata%\Temp\Citrix\XenDesktop Installer\MSI Log Files.
       
    2. Look for StoreFront log files underC:\Program Files\Citrix\Receiver StoreFront\Admin\logs.
       
    3. Citrix has aMSI Log Analyzer.
       
20. In the Smart Toolspage, make a selection. If participating, clickConnect, login with Citrix Cloud or mycitrix.com credentials, and then clickNext. SeeCitrix Insight Services at Citrix Docs for more information on these options.
    
    
    
21. If the install fails:
    1. Look for MetaInstaller log files under %localappdata%\Temp\Citrix\XenDesktop Installer\MSI Log Files.
       
    2. Look for StoreFront log files underC:\Program Files\Citrix\Receiver StoreFront\Admin\logs.
       
    3. Citrix has aMSI Log Analyzer.
       
22. In theFinish page, check the box next to Launch Studio, andclickFinish.
    

Studio Upgrade Database, Catalogs, and Delivery Groups

1. After Citrix Studio launches, if you havesysadmin permissions on SQL, then clickStart the automatic Site upgrade. If you dont have full permission, then get a DBA to help you, clickManually upgrade this site, and follow the instructions.
   
   
   
2. If you choose toManually 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 clickUpgrade Catalog. Note: 7.9 is the newestminimum functional level. You wont see an option for 7.16. If your Catalogs are already set to VDA version 7.9, then theres no need to upgrade the Catalogs or Delivery Groups.
   
   
   
   
   
4. Then do the same for the Delivery Groups.Note: 7.9 is the newestminimum functional level. You wont see an option for 7.16. If your Delivery Groupsare already set to VDA version 7.9, then no upgrade is needed.
   
   
   
   
   

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

• StoreFront
• Director
  • Upgrading Director overrides modifications to LogOn.aspx [e.g. default domain name], so youll have to reapply them.
• VDAs
• Citrix Policy Management Plug-in
• Profile Management Group Policy Templates
• Receiver Group Policy Templates
• Workspace Environment Management
• AppDNA
• Provisioning Services
• SCOM Management Packs
• Session Recording
• Federated Authentication Service

New Install Preparation

Frequent updates/upgrades

XenApp and XenDesktop 7.16 is a Current Release.

• With Current Release [CR], youre expected to upgrade to the future 7.17 [and 7.18, and 7.19, etc.] to receive bug fixes, and new features, which might include new bugs. Current Releases are only supported for six months from the release date. That means you should plan to perform these upgrades at least twice a year.
• If you dont want to continuously upgrade to the latest Current Release, then you can stay onLTSR 7.15, which receivesCumulative Updateswith bug fixes, but no new features.SeeLifecycle Milestones for Citrix Virtual Apps & Citrix Virtual Apps and Desktops.

VDA OS Compatibility

XenDesktop 7.16 Delivery Controller is supported on Windows 2008 R2 and newer. However, Virtual Delivery Agent [VDA] 7.16 is only supported on a limited number of Windows operating system versions, specifically, Windows 10 [1607+], Windows Server 2012 R2, and Windows Server 2016.

• If you have older VDA machines running Windows 7 or Windows Server 2008 R2, you can install VDA software version 7.15. It is supported for VDA 7.15 to communicate with Delivery Controllers 7.16.

Installation Automation

If you want to automate the install of Delivery Controllers, see Dennis SpanCitrix Delivery Controller unattended installation with PowerShell and SCCM.

Citrix Licensing

If you are going to use an existing Citrix Licensing Server, upgradeit to 11.14.0.1 build 22103.

Multiple License Types Multiple license types [but not multiple editions] are supported in a single farm. SeeCTX223926How to Configure Multiple License Types within a Single XenApp and XenDesktop Site.

SQL Databases for XenDesktop

• Citrix CTX209080 Database Sizing Tool for XenDesktop 7
• Citrix articleCTX114501 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 monitoringdatabase must not have any spaces in it. SeeCTX200325 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 rolewill 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-defaultLatin1_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.
    • SQL Standard Edition is much cheaper than SQL Enterprise Edition.
  • 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. Youll need to build your own SQL Servers on IaaS VMs.

Windows Feature

InstallingGroup 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.

vCenter Service Account

Create a role in vSphere Client. Assign a service account to the role at the Datacenter or higher level. Delivery Controller will use this service account to login to vCenter.

Delivery Controller 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. FromLocal Host Cache sizing and scalingat 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 theres no control over LHC election, ensure all Controllers have the same specs.
3. Make sure the User RightLog on as a service includesNT SERVICE\ALL SERVICES,or addNT SERVICE\CitrixTelemetryService to the User Right.
   
4. Download the XenApp/XenDesktop 7.16 ISO.
   
5. On two Delivery Controllers, to install the Delivery Controller software, runAutoSelect.exe from the 7.16 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 theLicensing Agreementpage, selectI have read, understand, and accept the terms, and clickNext.
   
9. In the Core Components page, you can install all components on one server, or on separate servers. Splitting them out is only necessary in large environments, or if you have multiple farms, and want to share the Licensing, StoreFront, and Director components across thosefarms. ClickNext.
   
10. In the Features page, uncheck the box next to Install Microsoft SQL Server 2014 SP2 Express, and click Next.
    
11. In theFirewall page, clickNext.
    
12. In the Summary page, click Install.
    
13. In the Smart Toolspage, make a selection. If you choose Smart Tools and Call Home, then click Connect, and enter your Citrix Cloud or MyCitrix.com credentials. Click Next.
    
    
    
    
    
14. In the Finishpage, 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 at vSphere Cluster > Manage > Settings > DRS Rules > Add. Set the Type toSeparate Virtual Machines.
    

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 dont have sysadmin permissions to SQL, then use Citrix Studio to generate SQL scripts, and send the scripts to a DBA.

Use 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 hassysadmin permissions to the SQL Server, then enter the SQL server name/instance in the threeLocation fields, and clickNext.
6. If you dont havesysadmin 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. Select your license type, and click Next. If you see both User/Device and Concurrent, then you usually must select User/Device licenses. Also seeCTX223926How 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.
12. Once done, skip to the Second Controller section.

Use Studio to create SQL scripts

1. If you dont have SQLsysadmin permissions, then change the selection to Generate scripts to manually set up databases on the database server.Change the database names if desired, and clickNext.
   
2. In the Summary page,clickGenerate scripts.
   
3. A folder will open with sixscripts. 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 fileSite_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. Youll 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 Databasespage, 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. SeeCTX223926How 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.
    

Second Controller

When building the first Delivery Controller, the SQL scripts might have already included the second Delivery Controller, and 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 dont 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 firstDelivery 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 machine, install Delivery Controller as detailed earlier.
3. After installation, launch Studio on the second controller, and click Connect this Delivery Controller to an existing Site.
   
4. Enter the name of the first Delivery Controller, and click OK.
   
5. If you dont 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 sixscripts. 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 CitrixStudio, under Configuration > Controllers, you should see both controllers.
    

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 publishers 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 calledConcurrent 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.16 than previous versions of XenApp/XenDesktop.

FromLocal Host Cache sizing and scalingat 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 theres no control over LHC election, ensure all Controllers have the same specs.
5. The Docs article has scripts for monitoring LHC performance.

FromXenApp 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 atCitrix XenDesktop/XenApp 7.15 The local host cache in action has a video showing LHC in action.

For Windows Server 2008 R2 Delivery Controllers, PowerShell 3, or newer, is required. SeeLHC XD 7.12 and W2K8SR2 SP1at Citrix Discussions.

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

If you did a fresh install of 7.16, then Local Host Cache should be enabled by default. You can run Get-BrokerSite to confirm. [runasnp 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 SpiersLocal 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. SeeCitrix article CTX137161How to Enable Read-Committed Snapshot in XenDesktopfor 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

From Citrix Docs Update database connection strings when using SQL Server high availability solutions:Citrix offers several PowerShell scripts that update XenApp and XenDesktop database connection strings when you are using SQL Server high availability database solutions such as AlwaysOn and mirroring.The scripts, which use the XenApp and XenDesktop 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, youll 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.

CTX140319How to Migrate XenDesktop Database to New SQL Server has the correctly ordered list of PowerShell commands to change the database connection strings. Make sure PowerShell is running as administrator before running these commands.

Here are the DB Connections that must be changed. This list might be longer than the article. When using the article, make sure you include all of the DB Connections shown below. You can get the full list of database commands by runningGet-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.

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 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

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 isCreate Custom Report. See Citrix articleCTX138132Viewing Configuration Logging Data Not Shownfor more info.

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

Maintain Logging Database

CitrixCTX215069Troubleshooting and managing Oversized Configuration Logging database:The articlesqueries 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 youll see a Welcomepage. Feel free to check the box to Dont 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 toa 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 toa Help Desk group that will have permissions to Studio and Director. Select the Allscope. 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.16 enables CEIP by default. If desired, you can disable it in Citrix Studio:

1. On the left, go to theConfigurationnode.
2. On the right, switch to theProduct Supporttab.
   
3. ClickEnd.
   
4. Click Yes.
   

Citrix Studio 7.16 collects data for Google Analytics. You can disable this in the registry at HKLM\Software\Citrix\DesktopStudio\GAEnabled = 0.

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

• License Server CEIP
• Virtual Delivery Agent CEIP
• Profile Management CEIP
• StoreFront CEIP
• Provisioning Services CEIP
• Receiver CEIP
• Receiver for HTML5 CEIP
• Session Recording CEIP
• AppDNA CEIP
• NetScaler CEIP

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, clickDownload 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 theGeneral tab, clickInstall Certificate.
   
7. In the Welcome to the Certificate Import Wizard page, change theStore Location selection toLocal Machine, and clickNext.
   
8. In theCertificate Store page, clickBrowse.
   
9. SelectTrust Root Certification Authorities, and clickOK.
   
10. In theCompleting the Certificate Import Wizard page, clickFinish.
    
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 theTrusted People store on the Delivery Controllers. Whenever the vCenter certificate is changed, youll 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 wont work in Internet Explorer.
      
   2. If Google Chrome, press to open the Developer Tools.
      
   3. On the top right, click the two right arrows to show more tabs, and clickSecurity.
      
   4. On theSecurity tab, clickView certificate.
      
   5. On theDetails tab, clickCopy to File.
      
   6. In theWelcome to the Certificate Export Wizard page, clickNext.
      
   7. In theExport File Format page, either format will work. ClickNext.
      
   8. In theFile to Export page, browse to a new file, and clickNext.
      
   9. In theCompleting the Certificate Export Wizard page, clickFinish.
      
2. If your Delivery Controller is Windows 2012 R2 or newer, then simply runcertlm.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 youll 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 theres a Learn about user permissionsblue link to an article that describes the necessary permissions.
4. Enter //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 toStudio Tools.
8. Click Next.
   
   • If you see a message about the vCenter certificate, check the box next to Trust certificate, and click OK.
     
   • Note: this vCenter certificate thumbprint is stored in the XenDesktop database, and is not updated when the vCenter certificate changes. SeeCTX217415Cannot connect to the VCenter server due to a certificate errorfor instructions on manually updating the database with the new certificate thumbprint.
     
   • Also seeCTX224551Xendesktop 7.x Steps to perform after certificate change on vCenter.
   • Alternatively, you can import the vCenter certificate to Trusted People on every Controller.
9. In the Storage Managementpage, clickBrowse, and select a vSphere cluster.
   • Note: as detailed at CTX223662, make sure theres no comma in the datacenter name.
10. SelectUse storage shared by hypervisors.
11. If you have sufficient disk space on each ESXi host, also selectOptimize temporary data on available local storage.From Mark Syms atXA 7.9 MCS with RAM Cachingat 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 Cachingat Citrix Discussions: for the temporary cache disk, Dont format it, the raw disk is what MCS caching uses.
13. Click Next.
    
14. In theStorage Selectionpage, 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, clickSelect, 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 Networkpage, 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 indicatesthe chosen datastore.
    
23. When you create a Catalog, select theHostingResource 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, youre 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 CitrixCTX225019XA/XD 7.13: Renaming Storage, Network or Datacenters When Used With MCS or PVS. Either runUpdate-HypHypervisorConnection -LiteralPath "XDHyp:\Connections\MyConnection", or right-click the Hosting Resource and click Edit Storage. You can cancel the wizard.
    

Citrix Licensing Server

Upgrade

XenApp/XenDesktop 7.16 comes with 11.14.1.1 build 22103.

If you have a standalone Licensing Server, upgrade it to Citrix Licensing 11.14.1.1 build 22103, if it isnt already.

1. Go to the downloaded Citrix Licensing 11.14.1.1 build 22103,and run CitrixLicensing.exe.
   
   
   
2. If you see theSubscription 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 11.14.0.1.22103.
   
6. If you login to the license server web console, on the Administration tab
   
7. It shows it as version 11.14.0.1 build 22103.
   
8. You can also view the version in the registry at HKLM\Software\Wow6432Node\Citrix\LicenseServer\Install.
   

Activate Citrix License

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

1. In Citrix Studio, expandConfiguration, right-clickLicensing, and clickAllocate Licenses.
   
2. Enter the LA- license code, and clickShow.
   • You can find your LA- code at //mycitrix.com, clickAll Licensing Tools, and clickView Licenses.
     
3. Then click theAllocate licenses button.
   
   • Another method of allocating licenses is in the new Licensing Manager at //MyLicenseServer:8083.
     
4. After licenses are installed, right-click theLicensing node, and clickEdit 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:
   • Citrix Blog PostIntroducing Multi-Type Licensing in XenApp & XenDesktop 7.14.
   • Multi-type licensing at Citrix Docs.

License Server CEIP

11.14.1.1 build 19005 and newer enables CEIP by default. This can be disabled in the Citrix Licensing Manager [//MyLicenseServer:8083] by clicking the gear icon.

Switch to the Usage and Statistics tab, and make a selection in theShare usage statistics with Citrixsection.

Citrix License Management Service

Version 11.14.0.1 and newer include theCitrix 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. RunCitrix Licensing Manager from the Start Menu. Or use a browser to connect to //MyLicenseServer:8083
   
2. On the Historical Use tab, use the drop-down menus to select a license type, select dates, and export to a .csv file.
   
3. TheUpdate 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.
   
   1. On theUsage and Statistics tab
      
   2. Scroll down and find theHistorical Use section.
      

Jonathan MeddMonitor 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 theInstallation Type page, selectRole-based or feature-based installation.
   
3. Click Next until you get to the Server Rolespage. Check the box next to Remote Desktop Services,and click Next.
   
4. Click Next until you get to the Role Servicespage. 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.

• For a list of checks, seeAbout health checks at Citrix Docs.
• SeeWhats new for Citrix Smart Tools at Citrix Docs
• For a comparison of Smart Check and Citrix Insight Services, see Citrix Blog PostWhat Data is Smart Check Collecting?

To run Smart Check:

1. Go to //citrix.cloud.com, and login.
2. After logging in, under My Services,findSmart Tools, and clickManage.
   
3. ClickSmart Check.
   
4. If you enabled Smart Tools during the installation of XenDesktop 7.16, then the site should already be there. ClickComplete Setup.
   
5. If you didnt enable Smart Check during XenDesktop installation, then on the top right, clickAdd Site.
   
   1. In step 1, clickDownload Agent.
      
   2. Step 2 indicates it is waiting for you to install the Agent.
      
   3. On aDelivery Controller, run the downloadedCitrixLifecycleManagementAgent.exe.
      
   4. Check the box next toI accept the terms in the License Agreement, and click Install.
      
   5. In theCompleted the Citrix Smart Tools Agent Setup Wizard page, clickFinish.
      
   6. Step 2 now shows that the Agent was installed successfully. ClickNext.
      
6. Enter credentials for your XenDesktop farm, and clickAdd Site, or clickDone.
   
7. Eventually youll see aGet Started link.
   
8. Or, if the site is already added to your list of sites, clickView 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. SeePerform health checks on Storefront, Licensing, and Provisioning Servers at Citrix Docs.
   
10. At the top right, if you clickPerform Check, you can run one of the checks.
    
11. If you clickConfigure.
    
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 seeSmart Check alerts reference at Citrix Docs.
    
14. Expand a component, and click an alert.
    
15. On the right, theres an option toHide Alert.
    
    
    
16. To view the hidden alerts, at the top right, click the menu icon, and clickShow 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, youll see the Custom Check that you added from the Blueprint Catalog.

See Citrix Blog PostVDA Health Check Now Available on Smart Check.

Citrix Scout

XenDesktop 7.16 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:

• Bas van KaamWith XenDesktop & XenApp 7.14 comes Scout 3.0 some big changes, read whats new compares old Scout with new Scout
• Citrix Docs Citrix Scout

XenApp/XenDesktop Health Check

Sacha TometFinally 1.0 but never finalized!:XenApp & XenDesktop 7.x Health Check script has now Version 1.0.

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

• Configure RDSH VDAs to use Remote Desktop Licensing Server
• Back to XenApp/XenDesktop 7.16