Delivery Controller 7. LTSR and Licensing Carl Stalhood. Navigation Recently Updated. Upgrade. If you are performing a new install of Xen. Certificate Renewal Wizard Windows 7' title='Certificate Renewal Wizard Windows 7' />AppXen. Desktop Controller, then skip to the next section. You can upgrade directly from any Delivery Controller version 5. Before upgrading, if you have a standalone Citrix Licensing Server, upgrade it to 1. Certificate Renewal Wizard Windows 7' title='Certificate Renewal Wizard Windows 7' />During the upgrade of Delivery 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. Frequent updatesupgrades Xen. App and Xen. Desktop 7. Long Term Service Release LTSR. To stay on Current Release CR, youre expected to upgrade to the future 7. LTSR means youre expected to install future Cumulative Updates for 7. See Lifecycle Milestones for Xen. App Xen. Desktop. LTSR compliance  To remain compliant with LTSR 5 years of support, you must install the exact versions detailed at Xen. You cant sign in to Skype for Business Online because the certificate cant be acquired or validated. SURTD6000RMXLP3UFeatures. APC SmartUPS RT 6000VA RM 208V to 208120V. High density, doubleconversion online power protection with scalable runtime. App and Xen. Desktop 7. LTSR baseline components at Citrix Docs. If you upgrade a single component beyond LTSR, then you should upgrade all components to the latest release. OS Upgrade If you are currently have 7. LTSR Controllers on Windows Server 2. R2, and want to migrate to Windows Server 2. Controllers, then do the following. In place upgrade your Windows Server 2. R2 Controllers to 7. LTSR. Build a couple new Windows Server 2. VMs with 7. 1. 5 LTSR Controller and join them to the existing sitefarm. Edit the List. Of. DDCs registry key on each VDA to point to the new Controllers. Edit Store. Front Console My. Store Manage Delivery Controllers, and point to the new Controllers. Reconfigure Director server IIS Application Settings Director path  Service. Auto. Discovery. Addresses to point to the new Delivery Controllers. Adjust monitoring tools to point to the new Controllers. For example, if using Citrix SCOM, deploy the Citrix SCOM Agents to the new Controllers, and remove from the old Controllers. If other components are installed on the old Controllers, move those components to the new Controllers. Remove the Windows Server 2. R2 Controllers from Citrix Studio Configuration Controllers Remove Controller, which removes them from the database. Decommission the Windows Server 2. R2 Controllers. SCOM Agent If Store. Front is installed on the Controller, and if the Citrix SCOM Agent for Store. Front is installed, stop the Citrix MPSF Agent service. See CTX2. 20. 93. Cannot Perform a Store. Front Upgrade if Citrix SCOM Management Pack Agent Service is Running. Close Power. Shell and Consoles. Make sure all Citrix Consoles and Power. Shell consoles are closed. Store. Front wont upgrade if any are running. If Store. Front fails, then the Store. Front configuration is wiped out. Other Users Use Task Manager Users tab to logoff any other user currently logged into the machine. Snapshot. If Store. Front is installed on the Controller, take a snapshot before attempting the upgrade. Another option is to export the Store. Front configuration so you can restore it later if something goes wrong. Download the Xen. AppXen. Desktop 7. LTSR ISO. Before upgrading, open Power. Shell and run the following. Get Trust. DBConnection. 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. Get Config. DBConnection. Set Trust. DBConnection DBConnection cs. Run Auto. Select. LTSR ISO. On the top left, click Studio and Server Components. In the Licensing Agreement page, select I have read, understand, and accept the terms, and click Next. In the Ensure Successful Upgrade page, read the steps, check the box next to Im ready to continue, and click Next. In the Firewall page, click Next. In the Summary page, click Upgrade. If you see a Running Processes window, close the listed programs, and click Continue. Click OK when asked to start the upgrade. In the Smart Tools page, make a selection. If participating, click Connect, login with Citrix Cloud or mycitrix. Next. See Citrix Insight Services at Citrix Docs for more information on these options. In the Finish page, check the box next to Launch Studio, and click Finish. Studio Upgrade Database, Catalogs, and Delivery Groups. After Citrix Studio launches, if you have sysadmin permissions on SQL, then click Start the automatic Site upgrade. If you dont have full permission, then get a DBA to help you, click Manually upgrade this site, and follow the instructions. If you choose to Manually upgrade this site, then note that there might not be an upgrade for the Logging Database schema, depending on what version you are upgrading from. After all Controllers and VDAs are upgraded, right click the Catalogs, and click Upgrade Catalog. Note 7. 9 is the newest minimum functional level. You wont see an option for 7. If your Catalogs are already set to VDA version 7. Catalogs or Delivery Groups. Then do the same for the Delivery Groups. Note 7. You wont see an option for 7. If your Delivery Groups are already set to VDA version 7. Other Xen. AppXen. Desktop components can also be in place upgraded New Install Preparation. Frequent updatesupgrades Xen. App and Xen. Desktop 7. Long Term Service Release LTSR. To stay on Current Release CR, youre expected to upgrade to the future 7. LTSR means youre expected to install future Cumulative Updates for 7. See Lifecycle Milestones for Xen. App Xen. Desktop. LTSR compliance  To remain compliant with LTSR 5 years of support, you must install the exact versions detailed at Xen. App and Xen. Desktop 7. LTSR baseline components at Citrix Docs. If you upgrade a single component beyond LTSR, then you should upgrade all components to the latest release. Automation If you want to automate the install of Delivery Controllers, see Dennis Span Citrix Delivery Controller unattended installation with Power. Shell and SCCM. Citrix Licensing If you are going to use an existing Citrix Licensing Server, upgrade it to 1. Note multiple license types but not multiple editions are supported in a single farm. See CTX2. 23. 92. How to Configure Multiple License Types within a Single Xen. App and Xen. Desktop Site. SQL Databases. Citrix CTX2. Database Sizing Tool for Xen. Desktop 7. Citrix article CTX1. Supported Databases for Xen. App and Xen. Desktop Components. There are typically three databases one for the Site aka farm, one for Logging audit log and one for Monitoring Director. The name of the monitoring database must not have any spaces in it. See CTX2. 00. 32. Database Naming Limitation when Citrix Director Accesses Monitoring Data Using OData APIs. If you want Citrix Studio to create the SQL databases automatically, then the person running Studio must be a sysadmin on the SQL instances. No lesser SQL role will work. 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. Enhanced Security Internet Explorer Windows 2012 Command. It is possible to create the databases in advance. However, you must use the non default Latin. General1. 00CIASKS collation. If SQL 2. 01. 6 Standard Edition or newer, create a Basic Availability Group. Basic Availability Groups BAG only need SQL Standard Edition licensing. You need two SQL Standard Edition servers, plus a file share witness. Xen. AppXen. Desktop 7. Carl Stalhood. Navigation Recently Updated. Hardware. Hypervisor Host Hardware. Citrix Blog Post Citrix Scalability The Rule of 5 and 1. Simply take the number of physical cores in a hypervisor host, multiply it by 5 or 1. Single Server Scalability. Use 5 if youre looking for the number of Xen. Desktop VMs you can host on a box, and use 1. Xen. App user sessions you can host on a box. Virtual Machine Hardware. VDA virtual machine sizing. For virtual desktops, give the virtual machine 2 v. CPU and 2 GB of RAMFor Windows 2. R2 RDSH, give the virtual machine 4 v. CPU and 1. 2 2. 4 GB of RAMFor Windows 2. R2 RDSH, give the virtual machine 8 v. CPU, and 2. 4 4. GB of RAMSee Daniel Feller Sizing Windows 2. Windows 2. 01. 2 And Windows 1. Virtual Machines. If using RAM caching MCSIO or Pv. S, add more RAM for the cache. Remove the floppy drive. Remove any serial or LPT ports. If v. Sphere. To reduce disk space, reserve memory. Memory reservations reduce or eliminate the virtual machine. The NIC should be VMXNET3. If this VDA will boot from Provisioning Services. For v. Sphere, the NIC must be VMXNET3. For v. Sphere, configure the CD ROM to boot from IDE instead of SATA. SATA comes with VM hardware version 1. SATA wont work with Pv. S. For Windows 1. CTX2. 24. 84. 3 Windows 1. Citrix Xen. Desktop . Citrix provides partial support for Semi Annual Channel Targeted aka Current Branch versions of Windows 1. Citrix provides full support for Semi Annual Channel Broad aka Current Branch for Business versions of Windows 1. VDA version released after a Windows 1. Broad typically 4 months and 4 patches after initial release. Windows 1. 0 1. 70. Broad is supported by VDA 7. VDA 7. 1. 5 was released after Windows 1. Broad after four monthly Windows patches. Windows 1. 0 1. 70. Targeted Citrix Product Manager in the comments mentioned that 7. Citrix has a live article about all this CTX2. The Microsoft patches required for 1. Nov 1. 4th Patch Tuesday KB4. VDA already installed, to 1. D patch last week of November via Microsoft Update Catalogue will allow you to do a fresh new VDA install on top of 1. Install the latest version of hypervisor drivers e. VMware Tools. If Windows 7 on v. Sphere, dont install the VMware SVGA driver. For more details, see Citrix CTX2. Intermittent Connection FailuresBlack Screen Issues When Connecting from Multi Monitor Client Machines to Windows 7 VDA with VDA 7. SphereESXi. The v. Sphere Activity Monitoring Feature with NSX Guest Introspection feature uses a TDI driver vnetflt. Connection Interrupted message when users log off of Citrix. See VMware 2. 12. Windows virtual machines using the v. Shield Endpoint TDI Manager or NSX Network Introspection Driver vnetflt. Xen. Desktop 7. 1. Connection interrupted at Citrix Discussions. If v. Sphere, disable NIC Hotplug. Users could use the systray icon to Eject the Ethernet Controller. Obviously this is bad. To disable this functionality, power off the virtual machine. Once powered off, right click the virtual machine, and click Edit. Settings. On the VM Options tab, expand Advanced, and then click Edit Configuration. On the bottom left, enter devices. On the right, enter false. Then click Add. Then click OK a couple times to close the windows. The VM can then be powered on. Windows Preparation. Computer Group Policy Make sure the Master VM is in the same OU as the Linked Clones so the Master VM will get the computer level GPO settings in its registry. Run gpupdate on the master after moving the VM to the correct OU. When Clones are created from the Master, the computer level GPO settings will already be applied, thus eliminating a timing issue. If RDSH Server OS, disable IE Enhanced Security Configuration in Server Manager Local Server. Optionally, go to Action Center Windows 8. R2 or Control Panel  Security and Maintenance Windows 1. User Account Control, and enable Smart. Screen. In Windows 1. Settings app for Change User Account Control settings. Smart. Screen is configured in Windows Defender Security Center App browser control. Run Windows Update. Add your Citrix Administrators group to the local Administrators group on the VDA. Computer Management. The Remote Desktop Services Prompt for Password policy prevents Single Sign on to the Virtual Delivery Agent. Check registry key HKEYLOCALMACHINESOFTWAREPoliciesMicrosoftWindows NTTerminal Services. If f. Prompt. For. Password 1 then you need to fix group policy. The following GPO setting will prevent Single Sign on from working. Computer Configuration Policies Administrative Templates Windows Components Remote Desktop Services Remote Desktop Session Host Security Always prompt for password upon connection. Or set the registry value HKEYLOCALMACHINESOFTWARECitrixPortica. Auto. Logon DWORD 0x. For Windows 72. 00. R2 VDAs that will use Personal v. Disk, or App. Disk, or any other layering technology, install Microsoft hotfix 2. A computer stops responding because of a deadlock situation in the Mountmgr. This hotfix solved a Personal v. Disk Image update issue detailed at Citrix Discussions. If this VDA is Windows Server 2. R2, see http www. To remove the built in apps in Windows 1. Robin Hobo How to remove built in apps in Windows 1. Enterprise. For Remote Assistance in Citrix Director, configure the GPO setting Computer Configuration Policies Administrative Templates System Remote Assistance Offer Remote Assistance. See Jason Samuel How to setup Citrix Director Shadowing with Remote Assistance using Group Policy for more details. If you intend to use Citrixs SCOM Management Packs for Xen. AppXen. Desktop, make sure Win. RM is enabled on the VDA by running winrm quickconfig. Or you can enable Win. RM using Group Policy. Install Virtual Delivery Agent 7. LTSRFor virtual desktops, make sure you are logged into the console. The VDA wont install if you are connected using RDP. Make sure. NET Framework 4. CLI Install Command Line Install Options are detailed at Install using the command line at Citrix Docs. The Citrix Telemetry Service seems to cause problems. You can use the Command Line Installer to exclude Telemetry Service as detailed at VDA upgrade cmdlet at Citrix Discussions. Xen. Desktop. VDASetup. EnableHDXPORTS enableframehawkport EnableREALTIMETRANSPORT optimize controllers xdc. Exclude Citrix Telemetry ServiceGUI Install Mount the downloaded Xen. Desktop 7. 1. 5 LTSR ISO, and and run Auto. Select. exe. Alternatively, you can download the standalone VDA package and run that instead. Go the main Xen. Desktop 7. Expand the section labelled Components that are on the product ISO but also packaged separately to download the Standalone VDA installers. VDA installer called Desktop OS Core Services that is designed for Remote PC deployments. Click Start next to either Xen. App or Xen. Desktop. The only difference is the product name displayed in the installation wizard. On the top right, click Virtual Delivery Agent for Windows Desktop OS, or Windows Server OS, depending on which type of VDA you are building. In the Environment page, select Create a Master Image, and click Next. For virtual desktops, in the HDX 3. D Pro page, click Next. In the Core Components page, if you dont need Citrix Receiver installed on your VDA, then uncheck the box. Receiver is usually only needed for double hop connections connect to first VDA, and then from there, connect to second VDA.