Previous Upload to Citrix.com Failed on Studio

Navigation

• Change Log
• Upgrade to vii.15.8000 LTSR
• New Install Grooming
• Delivery Controller vii.15.8000 LTSR New Install
  • Create Site / Databases
  • Second Controller
• SSL for Commitment Controller
• Studio – Slow Launch
• Concurrent Logon Hard Limit
• Local Host Cache
• Database Maintenance – Change Database connection strings, read-committed snapshot, Managing director grooming, Logging Database operations, etc.
  • Change Database Connection Strings
• Consign/Import Configuration
• Studio Administrators
• Customer Feel Improvement Programme (CEIP)
• vCenter Connection – vCenter certificate, Hosting Resources
• Citrix Licensing Server
  • Upgrade Licensing Server to 11.17.2.0 build 35000
  • Actuate 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 Picket
• Health Bank check

💡 = Recently Updated

Alter Log

• 2021 Aug 11 – updated article for vii.15.8000 (Cumulative Update 8)
• 2021 February 24 – 7.15 CU7 and newer support vSphere 7.0 Update 1 (source = CTX131239 Supported Hypervisors for Virtual Desktops (XenDesktop) and Provisioning (Provisioning Services))
• 2021 Feb 9 – updated article for vii.xv.7000 (Cumulative Update seven)
• 2020 Jun thirty – updated article for 7.15.6000 (Cumulative Update vi)
• 2020 Mar xiv – added Citrix Studio 7.xv.5000 Hotfix 1
• 2019 October 22 – Updated Install and Upgrade sections for version 7.15.5000 (Cumulative Update v).
• 2019 Jul vii – Upgrade – added link to Utilizing Local Host Cache for Nondisruptive Database Upgrades at Citrix Docs.
• 2019 Apr 23 – Updated Install and Upgrade sections for version 7.15.4000 (Cumulative Update 4).
• 2019 Jan 18 – New Commitment Controller – for LHC, configure four cores per socket
• 2018 December 28 – SSL for Delivery Controller – added info from Michael Shuster at HowTo: Enable SSL on Citrix Delivery Controllers – Easy Method
• 2018 Nov 7 – New Install – added link to Citrix Tech Zone Endpoint Security and Antivirus Best Practices
• 2018 Oct 29 – Updated Install and Upgrade sections for version 7.15.3000 (Cumulative Update 3).
• 2018 Oct 29 – Wellness Check – Pavan900 posted a PowerShell-based Health Check script at Citrix Studi – Colors for Maintenance Mode at Citrix Discussions
• 2018 Oct 16 – Change SQL connectedness strings – added content from CTX140319
• 2018 October 16 – SSL for Delivery Controller – new section to install certificate on Delivery Controller
• 2018 Sep 28 – Broker Service seven.15.2000 Hotfix 1 download was pulled so I removed it from this procedure
• 2018 Sep 3 – added Banker Service 7.15.2000 Hotfix 1 from CTX237283 – LHC fix
• 2018 June 3 – added Studio 7.15.2000 Hotfix i from CTX235169
• 2018 Apr 17 – Updated Install and Upgrade sections for version vii.fifteen.2000 (Cumulative Update 2).
• 2018 Mar 8 – in New Install Preparation section, added link to Patrick van den Born How to: Configure Citrix XenApp/XenDesktop to use Microsoft SQL multi-subnet (Bones) Availability Groups
• 2018 Jan 4 – in Local Host Cache section, added annotation about PowerShell Execution Policy.
• 2017 Dec 4:
  • Updated Install and Upgrade sections for version seven.15.1000 (Cumulative Update ane).
  • Added vCenter Root CA Certificate section equally alternative to importing bodily vCenter certificate.
  • In LHC section, added link to Trentent Tye Citrix XenDesktop/XenApp 7.15 – The local host enshroud in activity.

Upgrade

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

You lot can upgrade directly from any Delivery Controller version five.6 or newer.

During the upgrade of Commitment 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 and so run in SQL Studio.

1. Consider Utilizing Local Host Enshroud for Nondisruptive Database Upgrades at Citrix Docs.
2. Cumulative Updates – 7.fifteen is a Long Term Service Release (LTSR). Citrix periodically releases Cumulative Updates for LTSR versions.
   • Cumulative Updates include bug fixes simply. Cumulative Updates practice not include any new features. If yous want new features, and so you'll have to upgrade to a Current Release (e.m. vii.sixteen), which has a much shorter support lifecycle. See Lifecycle Milestones for Citrix Virtual Apps & Citrix Virtual Apps and Desktops.
3. LTSR compliance – To remain compliant with LTSR (v years of back up), you lot must install the exact versions detailed at XenApp and XenDesktop vii.fifteen LTSR baseline components at Citrix Docs. If yous upgrade a single component across LTSR, and so you should upgrade all components to the latest release.
   • See Citrix CTX205549 XenApp, XenDesktop, and XenServer Servicing Options (LTSR) FAQ.
   • Citrix LTSR Assistant can determine your LTSR compliance.
     
   • Citrix Smart Check can verify some of the LTSR components.
4. Os Upgrade – If you lot are currently take vii.6 LTSR Controllers on Windows Server 2012 R2, and desire to migrate to Windows Server 2016 Controllers, then do the following:
   1. In-identify upgrade your Windows Server 2012 R2 Controllers to 7.15.8000 LTSR.
   2. Build a couple new Windows Server 2016 VMs with vii.fifteen.8000 LTSR Controller and join them to the existing site/farm.
   3. Edit theListOfDDCs registry central 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 Managing director server > IIS > Application Settings > Managing director path >Service.AutoDiscoveryAddresses to signal to the new Win16 Delivery Controllers.
   6. Adapt 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 sometime Controllers.
   7. If other components are installed on the erstwhile 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.
5. License Server – Earlier upgrading to 7.15.8000, upgrade your Citrix Licensing Server to 11.17.two.0 Build 35000.
   
6. Sysadmin permissions – The person upgrading Delivery Controller needs temporary SQLsysadmin permission so the databases can be automatically upgraded. Or Citrix Studio tin can generate SQL scripts that a DBA must then run in SQL Studio.
7. SCOM Amanuensis – If StoreFront is installed on the Controller, and if the Citrix SCOM Agent for StoreFront is installed, end theCitrix MPSF Amanuensis service. See CTX220935 Cannot Perform a StoreFront Upgrade if Citrix SCOM Management Pack Agent Service is Running.
   
8. Close PowerShell and Consoles. Make sure all Citrix Consoles and PowerShell consoles are closed. StoreFront won't upgrade if whatever are running. If StoreFront fails, then the StoreFront configuration is wiped out.
9. Other Users – Utilize Job Managing director > Users tab to logoff any other user currently logged into the machine.
   
10. Snapshot. If StoreFront is installed on the Controller, take a snapshot before attempting the upgrade.
    • Another selection is to export the StoreFront configuration so you can restore it later if something goes wrong.
11. Download the XenApp/XenDesktop vii.15.8000 LTSR ISO.
    
12. RunAutoSelect.exe from the 7.15.8000 LTSR ISO.
    
13. On the peak left, nether Upgrade, clickStudio and Server Components.
    
14. In theLicensing Understanding page, selectI take read, understand, and take the terms, and clickNext.
    
15. In the Ensure Successful Upgrade folio, read the steps, bank check the box side by side toI'm gear up to continue, and clickNext.
    
16. In thePreliminary Site Tests page, click the bluish button labelledFirst Preliminary Tests.
    
    • If any tests fail, then clickView Test Report.
      
17. ClickNext.
    
18. In theFirewall page, clickNext.
    
19. In theSummary page, clickUpgrade.
    
20. If you see a Running Processes window, close the listed programs, and click Continue.
    
21. Click OK when asked to start the upgrade.
    
22. Click Close if you are prompted to restart.
    
23. Later on the reboot, login.
24. If you see aLocate 'XenDesktop LTSR CU8' installation media window:
    
    1. Don't close the Locate window.
    2. Mountain theXenApp_and_XenDesktop_7.15.8000.iso.
       
    3. Go dorsum to theLocate window.
    4. On the bottom left, under This PC, click the mounted bulldoze. So click the Select Folder push.
       
    5. Installation will resume.
25. In the Telephone call Home folio, brand a pick. If participating, clickConnect, login with mycitrix.com credentials, and then click Side by side. Come across Citrix Insight Services at Citrix Docs for more information on these options.
    
26. In theFinish folio, check the box next to Launch Studio and clickCease.
    

Studio – Upgrade Database, Catalogs, and Delivery Groups

1. After Citrix Studio launches, if you havesysadmin permissions on SQL, so clickStart the automatic Site upgrade. If yous don't take full permission, and then get a DBA to aid you, clickManually upgrade this site, and follow the instructions.
   
   
2. If yous cull toManually upgrade this site, then note that at that place 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, correct-click the Catalogs, and clickUpgrade Catalog. Note: vii.9 is the newest minimum functional level. Y'all won't see an option for 7.15.8000. If your Catalogs are already set to VDA version seven.nine, then at that place'southward no demand to upgrade the Catalogs or Delivery Groups.
   
   
   
4. Then practise the same for the Commitment Groups. Notation: seven.ix is the newest minimum functional level. Yous won't run across an selection for 7.15.8000. If your Delivery Groups are already fix to VDA version 7.nine, and so no upgrade is needed.
   
   
   

Other XenApp/XenDesktop components can as well exist in-place upgraded:

• StoreFront 3.12.8000
• Director 7.15.8000
  • Upgrading Managing director overrides modifications to LogOn.aspx (e.g. default domain proper name), so you'll have to reapply them.
• VDAs 7.xv.8000
• Citrix Policy Management Plug-in
• Profile Management 7.15.8000 Grouping Policy Templates
• Citrix Workspace app Group Policy Templates
• Workspace Environment Management 2106
• Provisioning Services 7.fifteen.39
• Session Recording vii.fifteen.8000
• Federated Authentication Service 7.fifteen.8000

New Install Preparation

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

• Cumulative Updates include bug fixes merely. Cumulative Updates exercise not include whatever new features. If you want new features, and so you'll take to upgrade to a Current Release (east.one thousand. seven.16), which has a much shorter support lifecycle. Meet Lifecycle Milestones for Citrix Virtual Apps & Citrix Virtual Apps and Desktops.

LTSR compliance – To remain compliant with LTSR (5 years of back up), y'all must install the exact versions detailed at XenApp and XenDesktop seven.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.

• See Citrix CTX205549 XenApp, XenDesktop, and XenServer Servicing Options (LTSR) FAQ.
• Citrix LTSR Assistant can determine your LTSR compliance. Note: LTSR Banana downloads its configuration from ctxsym.citrix.com, so you lot don't have to update LTSR Assistant subsequently installing a new Cumulative Update.
  
• Citrix Smart Check tin can verify some of the LTSR components.

Installation Automation – If you desire to automate the install of Delivery Controllers, see Dennis Bridge 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 11.17.2.0 Build 35000.

Note: multiple license types (but non 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 3 databases: one for theSite (aka subcontract), one forLogging (inspect log) and 1 forMonitoring (Manager).
  • The proper name of themonitoring database must not have any spaces in information technology. See CTX200325 Database Naming Limitation when Citrix Director Accesses Monitoring Information Using OData APIs
  • If you want Citrix Studio to create the SQL databases automatically, then the person running Studio must be asysadmin on the SQL instances. No lesser SQL role will piece of work.sysadmin permissions can exist granted temporarily and revoked after installation.
  • As an alternative, y'all can use Citrix Studio to create SQL scripts, and and then run those scripts on the SQL server. In that case, the person running the scripts but needs thedbcreator andsecurityadmin roles.
  • It is possible to create the iii databases in advance. Nonetheless, you lot 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 3 Bones Availability Groups, 1 for each database. Each Bones Availability Group has its own Listener.
    • SQL Standard Edition is much cheaper than SQL Enterprise Edition.
    • Run into Patrick van den Born How to: Configure Citrix XenApp/XenDesktop to use Microsoft SQL multi-subnet (Basic) Availability Groups.  💡
  • Database Mirroring – Build two SQL 2014 or older Standard Edition servers and configure Database Mirroring.
  • AlwaysOn Availability Grouping – Build 2 SQLEnterprise Edition servers and create 1 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. Y'all'll need to build your own SQL Servers on IaaS VMs.

Windows Characteristic

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 Grouping Policy Management installed, so if GPMC runs from a Controller, then the GPO Editor will automatically take admission to theCitrix Policies node. Or you lot tin can install Citrix Group Policy Management Plug-in on a different auto that has GPMC installed.

vSphere

• Create a function 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 ii-4 vCPU and 8+ GB of RAM. If all components (Delivery Controller, StoreFront, Licensing, Managing director, SQL Express) are installed on i server, and then you might want to bump upwardly 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 to the lowest degree three more Gigs of RAM and watch the memory consumption.
   4. Since there'due south no control over LHC election, ensure all Controllers take the same specs.
   5. SQL LocalDB uses max four cores on ane socket. Configure the Delivery Controller VM with four cores per socket.
      
3. Make certain the User RightLog on every bit a service includesNT SERVICE\ALL SERVICESor addNT SERVICE\CitrixTelemetryService to the User Right.
   
4. Download the XenApp/XenDesktop 7.15.8000 ISO.
   
5. On two Delivery Controllers, to install the Commitment Controller software, runAutoSelect.exe from the 7.15.8000 ISO.
   
6. Click Outset next to either XenApp or XenDesktop. The only difference is the product proper name displayed in the installation wizard.
   
7. On the top left, click Delivery Controller.
   
8. In theLicensing Agreement folio, selectI take read, understand, and accept the terms, and clickNext.
   
9. In the Core Components page, you tin 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, and Manager components across those farms. In CU6 and afterwards, StoreFront is no longer an option in this metainstaller, but information technology can be installed separately. Click Side by side.
   
10. In the Features folio, uncheck the box next to Install Microsoft SQL Server 2014 SP3 Express, and click Next.
    
11. In theFirewall page, clickSide by side.
    
12. In the Summary page, click Install. This volition take several minutes.
    
13. In the Call Home folio, brand a pick, click Connect, enter your MyCitrix.com credentials, and then click Next.
    
14. In the Finish page, click Finish. Studio will automatically launch.
    
15. Ensure the two Controller VMs do non run on the same hypervisor host. Create an anti-affinity dominion.
    
16. Citrix Tech Zone Endpoint Security and Antivirus Best Practices: provides guidelines for configuring antivirus software in Citrix Virtual Apps and Desktops environments

Create Site – Create Database

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

• If you have sysadmin permissions to SQL, allow Citrix Studio create the databases automatically.
• If you don't have sysadmin permissions to SQL, then use Citrix Studio to generate SQL scripts, and transport them to a DBA.

Employ 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 proper name), and click Next. Only administrators see the farm name.
   
4. In the Databases folio, if you are building two Controllers, click Select near the lesser of the same page.
   
   1. Click Add together.
   2. Enter the FQDN of the 2nd Controller, and click OK. Annotation: the Delivery Controller software must already exist 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 proper name/case in the threeLocation fields, and clickNext.
6. If you don't havesysadmin permission, the spring to the SQL Scripts section beneath.
   
7. On the Licensing folio, enter the name of the Citrix License Server, and click Connect. If you lot installed Licensing with your Delivery Controller, then simply enter localhost.
8. If the Certificate Authentication appears, select Connect me, and click Confirm.
   
9. And then select your license, and click Next. Come across CTX223926 How to Configure Multiple License Types inside a Unmarried XenApp and XenDesktop Site.
   
10. In the Summary page, if your databases are mirrored or in an Availability Group, each database volition show high availability servers, and the proper noun of the Mirror server. Click End.
    
    
11. It volition have some time for the site to be created.

Utilize Studio to create SQL scripts

1. If you don't have sysadmin permissions, alter the selection to Generate scripts to manually ready databases on the database server. Change the database names if desired, and clickNext.
   
2. In the Summary folio, clickGenerate scripts.
   
3. A folder will open with six scripts. Edit each of the scripts.
   
4. Near the meridian of each script are two lines to create the database. Uncomment both lines (including the get line). Then save and close the file.
   
   
5. Once all of the scripts are edited, y'all tin can ship them to your DBA.
   1. On the Primary SQL Server, open the fileSite_Principal.sql.
      
      
   2. Open the Query bill of fare, and click SQLCMD Mode to enable it.
      
   3. Then execute the script.
      
   4. If SQLCMD style was enabled properly, then the output should look something similar this:
      
   5. If you accept a mirrored database, run the 2d script on the mirror SQL example. Make sure SQLCMD way is enabled.
      
   6. Echo for the Logging_Principal. sql script.
      
   7. You'll have to enable SQLCMD Mode for each script y'all open up.
      
      
      
   8. Repeat for the Monitoring_Principal. sql script.
      
   9. Once more enable SQLCMD Mode.
      
      
      
   10. The person running Citrix Studio must exist added to the SQL Server as a SQL Login, and granted the public server role, and so that account can enumerate the databases.
       
       
6. Dorsum in Citrix Studio, click the Go along database configuration and Site setup button.
   
7. In the Databases page, enter the SQL server proper 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, so just enter localhost.
9. If the Certificate Authentication appears, select Connect me, and click Confirm.
   
10. So select your license, and click Adjacent. See CTX223926 How to Configure Multiple License Types within a Unmarried XenApp and XenDesktop Site.
    
11. In the Summary page, if your databases are mirrored, each database will testify high availability servers, and the proper name of the Mirror server. Click End.
    
    
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 rungo-brokerdbconnection, you'll meet the Failover Partner in the database connexion string.

2d Controller

When edifice the first Commitment Controller, the scripts might take already included the second Delivery Controller. Thus no special SQL permissions are needed. If the 2d Delivery Controller has not already been added to the SQL databases, then in that location are several methods of calculation a second Controller to the databases for XenApp/XenDesktop:

• If you lot have sysadmin permissions to SQL, permit Citrix Studio modify the databases automatically.
• If you don't have sysadmin permissions to SQL and then use Citrix Studio to generate SQL scripts and ship them to a DBA.

To utilize Citrix Studio to create the SQL Scripts:

1. On the starting time Delivery Controller, if StoreFront is installed on the Controller, so delete the default StoreFront shop (/Citrix/Store), and recreate information technology with your desired Store name (eastward.one thousand. /Citrix/CompanyStore).
   
2. On the second Delivery Controller, install XenDesktop as detailed earlier.
3. Subsequently 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 yous 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 binder will open with six scripts. If non mirroring, and so the top three scripts need to be sent to a DBA. If mirroring, send all vi.
   
8. On the SQL Server, open up ane 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. Echo for the remaining script files.
13. Dorsum in Citrix Studio, click OK.
    
14. In Citrix Studio, under Configuration > Controllers, yous should encounter both controllers.
    
15. You tin can likewise examination the site over again if desired.
    

SSL for Commitment Controller

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

• If StoreFront is installed on the Delivery Controller, and 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. Runcertlm.msc, become to Personal > Certificates, and create or install a server certificate that matches the Commitment Controller'southward FQDN. This tin 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 runIIS Director, go toDefault Web Site, clickEdit Bindings, and add anhttps binding using the called certificate.
   
   

If IIS is not installed on the Delivery Controller, and so we demand to build a command line to bind the certificate to Citrix Banker Service.

1. Open a command prompt as administrator.
2. Enter the following text but don't printing Enter yet.

   netsh http add together sslcert ipport=0.0.0.0:443 certhash=

3. Right after certhash= paste the certificate thumbprint using the following process:
   1. Go tocertlm.msc >Personal>Certificates.
   2. Double-click the certificate y'all want to bind.
   3. On theDetails tab, curlicue down toThumbprint and copy the thumbprint.
      
   4. Paste the thumbprint into the command line nosotros're building.
   5. Remove the special grapheme at the beginning of the thumbprint.
   6. Remove the spaces.
      
4. Add together the following to the command line:

                   appid=

5. Michael Shuster at HowTo: Enable SSL on Citrix Delivery Controllers – Easy Method says y'all can run the following PowerShell to get the Banker Service GUID.

   Get-WmiObject -Class Win32_Product | Select-String -Pattern "broker service"

6. Paste the GUID for Citrix Broker Service that yous got from the Become-WmiObject. Make certain the GUID has curly braces on both sides with no space betweenappid and the left curly brace.
   
7. Press <Enter> to run the control.
8. If you entered everything correctly, then it should saySSL Certificate successfully added.
   
9. To ostend the certificate bounden, run the post-obit:

   netsh http show sslcert ipport=0.0.0.0:443

   

Studio – Slow Launch

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

• Within Cyberspace Explorer, go to Tools – Net Options – Tab Avant-garde – Department Security, and uncheck the option Check for publisher's certificate revocation

Afterwards 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
  • "Country"=dword:00023e00

Concurrent Logon Hard Limit

From Samuel Legrand XenApp vii.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 permit users connect. You can configure the Controllers to brand it a hard limit past setting the following registry value:

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

Local Host Cache

If yous 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 Connexion 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 Enshroud sizing and scaling at Citrix Docs:

1. For LHC LocalDB, assign the Controller VMs a unmarried 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'due south no control over LHC ballot, 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 volition take over (causing registration tempest) and when the DDC gets back, information technology 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 volition non touch any functionality.
• If you lot plough the DDC down when site is working, and start it during outage, LHC volition not trigger on that machine. This DDC volition non impact the LHC unless it would become the elected one. In that scenario information technology will have control, all the same not start LHC and resource would not be available.

Trentent Tye at Citrix XenDesktop/XenApp 7.fifteen – The local host cache in action has a video showing LHC in action.  💡

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

Every bit mentioned by Citrix Docs, brand certain PowerShell Execution Policy is gear up to RemoteSigned, Unrestricted, or Bypass.

If y'all did a fresh install of 7.xv, and then Local Host Cache should be enabled by default. You can run Get-BrokerSite to confirm. (run asnp citrix.* beginning).

If non enabled, y'all can run some PowerShell commands to enable Local Host Cache:

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

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

Database Maintenance

Enable Read-Committed Snapshot

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

Modify Database Connexion Strings

Sometimes the database connection strings need to exist 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

Hither are general instructions for moving the database and assigning the right permissions:

1. Fill-in 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 calculation 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 3 Citrix databases, add the Delivery Controller reckoner account to the various database roles equally listed below. The Site database has many more roles than the Logging and Monitoring databases.
   • Site database – ADIdentitySchema_ROLE
   • Site database – Analytics_ROLE (7.eight and newer)
   • Site database – AppLibrarySchema_ROLE (seven.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.viii 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 utilize the Citrix Virtual Apps and Desktops PowerShell API, are:

• DBConnectionStringFuncs.ps1: The cadre script that does the bodily 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. Y'all can also use the ClearPartner option to remove a partner.) Practise non gear up 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 sure Citrix services are up and running, and then updates those services in the correct society on all Controllers in the site. Enclose connexion string data for each database in quotes.
• Change_XD_To_MultiSubnetFailover.ps1: Toggles the improver and removal of MultiSubnetFailover=true. If y'all use AlwaysOn Availability Groups, Microsoft recommends that the connectedness 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 selection. Run the script over again to remove it.
• Change_XD_To_Null.ps1: Resets all the connection strings on the localhost considering something has gone incorrect. By resetting the connection strings to zero, this script places the Controller into an "initial" state. If you run Studio after running this script, you'll exist asked if you want to create a site or join an existing site. This is useful if something has gone incorrect and a reset is needed. After the reset, you can endeavour once more to gear up the connection strings.

Here are the DB Connections that must be changed. Brand sure you lot 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 exist set to NULL, and the commencement to be configured with the new connection string. Repeat these instructions on all Delivery Controllers in the farm.

Remove the existing Database connections

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

## Load the Citrix snap-ins asnp Citrix.*  ## Disable configuration logging for the XD site: Set-LogSite -State Disabled  ## ## Clear the electric current Delivery Controller database connections ## Note: AdminDBConnection must be the last control Set-ConfigDBConnection -DBConnection $null Ready-AppLibDBConnection –DBConnection $null    #7.8 and newer Set-OrchDBConnection –DBConnection $nil      #7.11 and newer Set-TrustDBConnection –DBConnection $zip     #7.11 and newer Set-AcctDBConnection -DBConnection $cypher Set-AnalyticsDBConnection -DBConnection $null # seven.6 and newer Set-HypDBConnection -DBConnection $nothing Prepare-ProvDBConnection -DBConnection $null Set-BrokerDBConnection -DBConnection $zilch Ready-EnvTestDBConnection -DBConnection $zip Set-SfDBConnection -DBConnection $null Set-MonitorDBConnection -DataStore Monitor -DBConnection $null   #Monitoring Database Set-MonitorDBConnection -DBConnection $null                      #Site Database Gear up-LogDBConnection -DataStore Logging -DBConnection $cypher       #Logging Database Set-LogDBConnection -DBConnection $nix                          #Site Database Set-AdminDBConnection -DBConnection $null -forcefulness

Specify the new Database connectedness strings

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

## Replace <dbserver> with the SQL server proper noun, and instance if present, e.g "ServerName\SQLInstanceName". If no SQL Instance name is mentioned, this commandlet will effort to connect to the default SQL instance. ## Supersede <dbname> with the proper noun of your restored Database ## Note: AdminDBConnection should be beginning  $ServerName = "<dbserver>" $SiteDBName = "<SiteDbName>" $LogDBName = "<LoggingDbName>" $MonitorDBName = "<MonitorDbName>" $csSite = "Server=$ServerName;Initial Itemize=$SiteDBName;Integrated Security=True;MultiSubnetFailover=True" $csLogging = "Server=$ServerName;Initial Catalog=$LogDBName;Integrated Security=True;MultiSubnetFailover=Truthful" $csMonitoring = "Server=$ServerName;Initial Catalog=$MonitorDBName;Integrated Security=Truthful;MultiSubnetFailover=True"  Set-AdminDBConnection -DBConnection $csSite Set-ConfigDBConnection -DBConnection $csSite Ready-AcctDBConnection -DBConnection $csSite Fix-AnalyticsDBConnection -DBConnection $csSite # 7.6 and newer Fix-HypDBConnection -DBConnection $csSite  Gear up-ProvDBConnection -DBConnection $csSite Set-AppLibDBConnection –DBConnection $csSite # seven.viii and newer Set-OrchDBConnection –DBConnection $csSite # seven.11 and newer Prepare-TrustDBConnection –DBConnection $csSite # 7.11 and newer Set-BrokerDBConnection -DBConnection $csSite Prepare-EnvTestDBConnection -DBConnection $csSite Set up-SfDBConnection -DBConnection $csSite Gear up-LogDBConnection -DBConnection $csSite Ready-LogDBConnection -DataStore Logging -DBConnection $goose egg Fix-LogDBConnection -DBConnection $null Set-LogDBConnection -DBConnection $csSite Set-LogDBConnection -DataStore Logging -DBConnection $csLogging Set-MonitorDBConnection -DBConnection $csSite Ready-MonitorDBConnection -DataStore Monitor -DBConnection $null Set-MonitorDBConnection -DBConnection $null Prepare-MonitorDBConnection -DBConnection $csSite Set-MonitorDBConnection -DataStore Monitor -DBConnection $csMonitoring Set-LogSite -State Enabled

Exam the new Database connectedness strings

Run the following commands to verify connectivity to the database:

asnp citrix.*  ## Copy these variables from the previous step ## If y'all oasis't airtight your PowerShell window, then the variables might still exist 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=Truthful" $csMonitoring = "Server=$ServerName;Initial Itemize=$MonitorDBName;Integrated Security=Truthful"  Examination-AcctDBConnection -DBConnection $csSite Examination-AdminDBConnection -DBConnection $csSite Exam-AnalyticsDBConnection -DBConnection $csSite # seven.half-dozen and newer Test-AppLibDBConnection -DBConnection $csSite # 7.8 and newer Exam-BrokerDBConnection -DBConnection $csSite Test-ConfigDBConnection -DBConnection $csSite Test-EnvTestDBConnection -DBConnection $csSite Test-HypDBConnection -DBConnection $csSite Examination-LogDBConnection -DBConnection $csSite Test-LogDBConnection -DataStore Logging -DBConnection $csLogging Exam-MonitorDBConnection -DBConnection $csSite Exam-MonitorDBConnection -Datastore Monitor -DBConnection $csMonitoring Test-OrchDBConnection -DBConnection $csSite # 7.eleven and newer Examination-ProvDBConnection -DBConnection $csSite Test-SfDBConnection -DBConnection $csSite Test-TrustDBConnection -DBConnection $csSite # vii.11 and newer

Director Preparation

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

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

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

View Logging Database

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

The Logging Database can exist queried usingBecome-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'south queries can be used to decide the number of configuration operation types performed by XenDesktop Administrator, and to clarify the content of the Configuration Logging database when it is considered oversized. A grooming query is likewise provided to delete data older than a specified date.

Consign/Import Configuration

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

Studio Administrators

Total Administrators

1. In the Studio, under Configuration, click the Administrators node. The outset fourth dimension you lot access the node you'll see a Welcome page. Feel costless to check the box to Don't evidence this once more, and then click Close.
2. On the Administrators tab, right-click, and click Create Administrator.
   
3. In the Administrator and Scope folio, Browse to a grouping (east.g. Citrix Admins) that will have permissions to Studio and Director. These groups typically have admission to all objects, so select the All scope. Alternatively, you can create a Telescopic to limit the objects. Click Next.
   
4. On the Role folio, select a role, then click Next. For example:
   • Full Administrator for the Citrix Admins grouping
   • Help Desk-bound Administrator for the Assist Desk group
   • Machine Catalog Ambassador for the desktop team
     
5. In the Summary folio, click Finish.

Assistance 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 Function 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-bound role log into Director, all they see is this.
   
   To jazz it upwards a trivial, add the Assistance Desk group to the read-but role.
6. Right-click the Help Desk-bound Administrator, and click Edit Administrator.
   
7. Click Add.
   
8. In the Telescopic page, select a telescopic, and click Adjacent.
   
9. In the Role folio, select Read Only Administrator, and click Side by side.
   
10. In the Summary page, click Finish.
11. Then click OK. At present Director will display the dashboard.
    

Customer Feel Improvement Programme

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

1. On the left, go to theConfiguration node.
2. On the right, switch to theProduct Back up tab.
   
3. ClickEnd.
   
4. Click Yeah.
   

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

• License Server CEIP
• Virtual Delivery Agent CEIP
• Contour 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 business relationship to log into vCenter. This business relationship 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 exist applied at the datacenter or college level.

7.15 CU7 and newer support vSphere 7.0 Update ii (source = CTX131239 Supported Hypervisors for Virtual Desktops (XenDesktop) and Provisioning (Provisioning Services))

Import vCenter Root Certificate

If the vCenter certificate is valid and trusted, then you tin 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 lesser right, clickDownload trusted root CA certificates.
   
3. Excerpt the downloaded files.
4. Become to\certs\win.
5. Sort the files by date, and double-click the newest.crt file.
   
6. On theFull general tab, clickInstall Certificate.
   
7. In the Welcome to the Certificate Import Wizard folio, change theStore Location selection toLocal Car, and clickNext.
   
8. In theDocument Store page, clickBrowse.
   
9. SelectTrust Root Certification Authorities, and clickOK.
   
10. In theCompleting the Document Import Wizard page, clickEnd.
    
11. If you close your browser and reopen it, and then go to the vCenter URL, at that place should no longer exist any certificate errors.
12. Skip to the Hosting Resource section.

Import vCenter Certificate

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

Alternatively, you tin 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 information technology. Yet, it is hard to update the thumbprint whenever the vCenter document changes. Information technology might instead be more than reliable to use the older method of configuring theTrusted People shop on the Delivery Controllers. Whenever the vCenter certificate is changed, y'all'll demand to echo these steps.

1. Become the vCenter certificate.
   1. Open a browser and point it to the vCenter URL. Notation: this procedure to get the document won't work in Cyberspace Explorer.
      
   2. If Google Chrome, printing <F12> to open up the Developer Tools.
      
   3. On the top right, click the two right arrows to show more tabs, and clickSecurity.
      
   4. On theSecurity tab, clickView document.
      
   5. On theDetails tab, clickCopy to File.
      
   6. In theWelcome to the Certificate Export Wizard folio, clickNext.
      
   7. In theConsign File Format page, either format will work. ClickNext.
      
   8. In theFile to Consign page, browse to a new file, and clickNext.
      
   9. In theCompleting the Document Export Wizard folio, clickFinish.
      
2. If your Delivery Controller is Windows 2012 R2 or newer, so only runcertlm.msc. This opens the MMC panel 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 correct past highlighting it, and clicking Add.
      
   3. Select Computer account, and click Next.
      
   4. Select Local computer, and click End.
      
   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 folio, scan to the document you saved earlier, and click Next.
   
6. In the Document Store page, click Next.
   
7. In the Completing the Certificate Import Magician page, click Finish.
   
8. Click OK to acknowledge that the import was successful.
9. Repeat these steps on the 2nd Controller. It is important that you import the certificate on both Controllers before adding the Hosting Resources.
10. If you lot open up Internet Explorer and browse to the vCenter Server, in that location should exist no certificate errors.
    

Hosting Resource

7.xv CU7 and newer support vSphere 7.0 Update two (source = CTX131239 Supported Hypervisors for Virtual Desktops (XenDesktop) and Provisioning (Provisioning Services))

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

1. In Studio, expand Configuration and click Hosting. Correct-click it, and click Add Connectedness and Resource.
   
2. In the Connection page, for Connectedness type, select VMware vSphere.
3. Notice at that place's a Learn well-nigh user permissions blueish 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 business relationship that tin log into vCenter.
6. In the Connection name field, requite the connection a name. Typically, this matches the name of the vCenter server.
7. If you are not using Machine Cosmos Services, and instead only need the vCenter connection for car ability management, modify the Create virtual machines using selection to Other Tools. If you intend to use MCS, leave it set toStudio Tools.
8. Click Next.
   
9. In the Storage Management page, clickBrowse, and select a vSphere cluster.
   • Note: as detailed at CTX223662, make sure in that location'southward no comma in the datacenter name.
10. SelectUse storage shared by hypervisors.
11. If you have sufficient disk space on each ESXi host, besides selectOptimize temporary information on available local storage. From Mark Syms at XA 7.9 MCS with RAM Caching at Citrix Discussions: "If you lot utilise just MCS caching to local storage then the VM is non active at all and cannot be moved even when powered off as it has a virtual disk permanently associated with a unmarried 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 theStorage Selectionfolio, 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 magician again to create a separate Hosting Resource.
15. If you selected the temporary information on local storage choice, on the bottom, clickSelect, and choose the datastores you desire to apply for disk caching. By default, all local datastores are selected. Click Next when done.
    
16. In the Networkpage, enter a proper name for the hosting resource. Since each hosting resource is a combination of vCenter, Cluster, Network, and Datastores, include those names in this field (eastward.g. vCenter01-Cluster01-Network01-Datastore01).
17. Select a network and click Next.
    
18. In the Summary folio, click Cease.
    
19. If you take multiple datastores for your VDAs, run the wizard again.
    
20. You lot can employ the existing vCenter connectedness.
    
21. This time, select a different datastore.
    
22. Give it a proper name that indicates the chosen datastore.
    
23. When you create a Itemize, select the Hosting Resource for the datastore where you desire the VDAs to be placed. Create boosted Catalogs for each datastore. You can so combine the Catalogs into a single Delivery Grouping.
    
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 "Enshroud in RAM with overflow to deejay".
    
25. If you rename Storage, Network, or Datacenters, come across Citrix CTX225019 XA/XD 7.thirteen: 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 abolish the wizard.
    

Citrix Licensing Server

Upgrade

XenApp/XenDesktop 7.15.8000 comes with xi.17.2.0 Build 35000.

If y'all accept a standalone Licensing Server, upgrade information technology to Citrix Licensing 11.17.ii.0 build 35000, if it isn't already.

1. Go to the downloaded Citrix Licensing eleven.17.2.0 build 35000, and run CitrixLicensing. exe.
   
   
2. If you run across 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 at present show version 11.17.2.0 build 35000.
   
6. Citrix Licensing 11.half dozen.6.0 build 31000 and newer no longer include the License Administration Console (:8082).
7. Afterwards upgrading Citrix Licensing Server, in Citrix Studio, become toConfiguration > Licensing.
8. On the correct, clickAuthenticate Certificate.
   
9. Change the selection toConnect me, and clickConfirm.
   

Citrix Licensing Manager

Newer versions of License Server come up with a new management web site. License Server 11.16.6 and newer no longer include the License Administration Console (:8082).

1. From the Start Carte, runCitrix Licensing Manager. Or go to https://<My_Licensing_Server>:8083
   
2. You might be prompted to login.
   
   • To eliminate this login, add the License Server URL to the Local Intranet zone.
     
3. Licensing Manager might prompt you to register with Citrix Cloud.
   
   1. On theSettings > Usage and Statistics folio, in theShare usage statistics with Citrix section, clickAnnals.
      
   2. Y'all'll see a screen with a registration code. Click theCopy push button and and then click Register to be have to Citrix Cloud.
      
   3. Afterward logging in to Citrix Cloud, on the top left, click the bill of fare (hamburger) icon and so clickLicense & Usage. If you don't run into this link, y'all might have to logout and log back in.
      
   4. In theLicense & Usage service, switch to the Registrations tab.
      
   5. Click the blueRegister button in the heart of the page.
      
   6. Paste in the copied lawmaking and so clickContinue.
      
   7. ClickRegister.
      
   8. Back in the on-premises Licensing Managing director, it will eventually show as Registered.
      
   9. On the same Usage & Statistics folio, curl down, and so clickUpload now. This should cause data to upload to Citrix Cloud and testify up in Citrix Cloud License & Usage.
      
4. Licensing Manager has a new Dashboard page to replace the 1 in the License Assistants Panel.
   
   • Click the pointer side by side to a license to see when it expires and the number of licenses in utilise.
     
5. If you lot click the gear icon on the top correct…
   
6. On the Business relationship tab, you can add together License Server Administrators.
   
7. TheUpdate Licenses tab lets you bank check for license renewals and download them.
   

Activate Citrix License

The easy manner 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 clickTestify. You can find your lawmaking at http://mycitrix.com, clickAll Licensing Tools, and clickView Licenses.
   
3. Then clickAllocate licenses.
   
   1. Another method of allocating licenses is in the Citrix Licensing Manager at https://MyLicenseServer:8083 >Install Licenses tab.
      
4. After licenses are installed, right-click theLicensing node, and clickEdit Product Edition
   
5. Change the edition to friction match your licenses. If you lot encounter both XenDesktop and XenApp licenses, you must select XenDesktop. If y'all see both Concurrent and User/Device, so you must select User/Device. Click OK when done.
   
6. XenDesktop 7.14 and newer support mixed licensing in a unmarried site/farm. Run into the following:
   • Citrix Blog Mail service Introducing Multi-Blazon Licensing in XenApp & XenDesktop 7.14.
   • Multi-type licensing at Citrix Docs.

License Server CEIP

Citrix Licensing Server enables CEIP by default. This can exist disabled:

1. In the Citrix Licensing Manager (https://MyLicenseServer:8083) past clicking the gear icon.
   
2. Switch to the Usage and Statistics tab and brand a selection in the Share usage statistics with Citrix section.
   

Citrix License Management Service

Version 11.xiv.0.one and newer include the Citrix License Management Service. This service helps you lot avoid prohibited practices:

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

Citrix License Server Monitoring

Citrix Licensing Managing director has historical usage reporting:

1. RunCitrix Licensing Director from the Showtime Menu. Or use a browser to connect to https://MyLicenseServer:8083
   
2. On the Historical Use tab, use the drop-down menus to select a license blazon, select dates, and export to a .csv file.
3. At the bottom of this page is a link to change the retentivity menstruation.
   

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

Practise the following on your XenDesktop Controllers:

1. In Server Manager, open the Manage menu, and click Add Roles and Features.
   
2. In theInstallation Blazon page, selectFunction-based or characteristic-based installation.
   
3. Click Next until you get to the Server Roles folio. Check the box adjacent to Remote Desktop Services, and click Next.
   
4. Click Next until y'all get to the Role Services folio. Bank check the box side by side to Remote Desktop Licensing, and click Adjacent.
   
5. Click Add Features if prompted.
   
6. And then stop the magician to install the role service.
   

Actuate Remote Desktop Licensing

1. After RD Licensing is installed, in Server Director, open the Tool carte, expand Terminal Services (or Remote Desktop Services), and click Remote Desktop Licensing Manager.
   
2. The tool should notice the local server. If it does non, right-click All servers, click Connect, and blazon in the name of the local server.
3. One time the local server can be seen in the listing, correct-click the server and click Activate Server.
   
4. In the Welcome to the Activate Server Wizard page, click Next.
   
5. In the Connexion Method page, click Next.
   
6. In the Company Information page, enter the required data, and click Adjacent.
   
7. All of the fields on the Company Information page are optional, so you exercise non have to enter annihilation. Click Next.
   
8. In the Completing the Activate Server Magician page, uncheck the box next to Start Install Licenses Magician 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 take green check marks. If the person installing Remote Desktop Licensing does non have permissions to add the server to the Concluding 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 Keep 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 shut the window.
    

Smart Check

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

• For a list of checks, come across About health checks at Citrix Docs.
• Encounter What'southward new for Citrix Smart Tools at Citrix Docs
• For a comparison of Smart Cheque and Citrix Insight Services, see Citrix Weblog Mail What Data is Smart Cheque Collecting?

To run Smart Check:

1. Become to https://citrix.cloud.com, and login.
2. After logging in, nether My Services, discoverSmart Tools, and clickManage.
   
3. ClickSmart Bank check.
   
4. If you enabled Smart Tools during the installation of XenDesktop 7.15, and so the site should already exist in that location. ClickConsummate Setup.
   
5. If you didn't enable Smart Cheque during XenDesktop installation, and so on the top correct, clickAdd Site.
   
   1. In step 1, clickDownload Agent.
      
   2. Stride ii indicates it is waiting for you to install the Agent.
      
   3. On a Delivery Controller, run the downloadedCitrixLifecycleManagementAgent.exe.
      
   4. Cheque the box side by side toI accept the terms in the License Agreement, and clickInstall.
      
   5. In theCompleted the Citrix Smart Tools Agent Setup Wizard page, clickEnd.
      
   6. Step 2 at present shows that the Agent was installed successfully. ClickNext.
      
6. Enter credentials for your XenDesktop farm, and clickAdd Site, or clickDone.
   
7. Eventually you'll see aGet Started link.
   
8. Or, if the site is already added to your list of sites, clickView Study next to the site.
   
9. StoreFront, Provisioning Services, and Licensing Server cannot be automatically detected. You tin add a Custom Cheque that targets those machines. Run across Perform health checks on Storefront, Licensing, and Provisioning Servers at Citrix Docs.
   
10. At the acme right, if you clickPerform Check, you tin run 1 of the checks.
    
11. If you lot clickConfigure.
    
12. Yous can schedule the checks to automatically run periodically.
    
13. To view the alerts, click one of the alert badges in the component category. Besides see Smart Bank check alerts reference at Citrix Docs.
    
14. Expand a component, and click an alert.
    
15. On the right, there's an option toHide Alert.
    
    
16. To view the hidden alerts, at the pinnacle right, click the carte du jour icon, and clickShow Hidden Alerts.
    
17. The hidden alert is grayed out. If you click the alert, you can restore it.
    
    

Boosted Smart Checks

The Blueprint Catalog has additional checks that you can add to Smart Check. Click Blueprint Catalog in the menu bar. Curlicue downwards to the Citrix Checks department, and click the plus icon side by side to i of them.

When you go back to Smart Bank check, open a site (View Report), and click Perform Check, you'll see the Custom Cheque that you added from the Blueprint Itemize.

Run into Citrix Blog Post VDA Health Bank check Now Available on Smart Cheque.

Citrix Scout

XenDesktop 7.fifteen includes a new Citrix Scout that can be launched from the Start Carte du jour.

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

Links with more information:

• Bas van Kaam With XenDesktop & XenApp 7.14 comes Scout iii.0 – some big changes, read what's new – compares onetime Spotter with new Scout
• Citrix Docs Citrix Scout

XenApp/XenDesktop Health Bank check

Sacha Tomet Finally ane.0 – but never finalized!: XenApp & XenDesktop 7.x Wellness Check script has now Version ane.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 every bit a service (or local to the delivery controller) and periodically checks the wellness of:

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

And if any of these items fall out of bounds, an SMTP warning is sent to the mailbox of your choice for action. The tool volition as well send "All Clear" emails when these items are resolved, ensuring you are enlightened when the service has resumed a healthy state.

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

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

Related Pages

• Configure RDSH VDAs to use Remote Desktop Licensing Server
• Dorsum to XenApp/XenDesktop 7.15

yuranighprehopecon.blogspot.com

Source: https://www.carlstalhood.com/delivery-controller-7-15-ltsr-and-licensing/

Share this post