**Please note: You can download the required file from the Citrix downloads website by visiting the following link: https://www.citrix.com/downloads/citrix-tools** **LTSR Assistant****v2.9.0.1** Created Date: Apr 12, 2016 Updated Date: Apr 16, 2025 **What's New in****v2.9.0.1** * Fixed a sporadic issue that prevented the LTSR Assistant tool from launching. **Changes from Previous Versions** * * Fixed an issue that caused compliance checks to fail for Citrix Virtual Apps and Desktops LTSR 2203 CU6 and 1912 CU10. * Added support for Citrix Virtual Apps and Desktops 2402 LTSR. * Changed the minimum supported .Net Framework version to 4.6.2. * Added support for Citrix Virtual Apps and Desktops 2203 LTSR Cumulative Updates. * Fixed a security protocol issue that caused LTSR compliance rule downloads to fail. * Added support for Citrix Virtual Apps and Desktops 2203 LTSR. * Added support for TLS 1.3. * Added support for XenApp and XenDesktop 7.15 LTSR, Citrix Virtual Apps and Desktops 7 1912 LTSR, and their Cumulative Updates. * Addressed an issue that causes failures when you run the LTSR Assistant from the command line. * Addressed an issue where the LTSR Assistant detected components repeatedly. The issue occurred when the hostname of a component was added more than once. * Updated the recommended XenServer LTSR version to 7.1.2. * Added support for the browser content redirection feature as a compatible component of the XenApp and XenDesktop 7.6 and 7.15 Long Term Service Releases (LTSRs). * Added support for TLS 1.2 and TLS 1.1. * Added support for XenApp and XenDesktop 7.6 LTSR and Cumulative Updates. * Added support for XenApp and XenDesktop7.15 LTSR and Cumulative Updates. * For 7.15 LTSR,the following, additional baseline components are supported: * Linux VDA * VDAs for Windows 10 * Profile Management * For 7.15 LTSR,the following, additional compatible components are supported: * Citrix SCOM Management Pack for XenApp and XenDesktop * Citrix SCOM Management Pack for StoreFront * Citrix SCOM Management Pack for License Server * Citrix SCOM Management Pack for Provisioning Services * Citrix SCOM Management Pack for XenServer * Added capability to work with non-default ports for the Delivery Controller. * Added Get-Help instruction for the _XenServerMachine_ parameter. * Enhanced the Get-Help command for PoSH to provide a parameter description. * Introduced support for XenServer LTSR compliance checking. * Added a dialog box to notify of the latest tool version. * Provided Compliance Report .csv files in the upload package. * Made a usability improvement so that restarting the tool is no longer required when rescanning an environment. **Description** ![Web](/servlet/rtaImage?eid=ka67y000000FJoj&feoid=00N0z0000031cRr&refid=0EM4z000000jpiN) The LTSR Assistant scans components of Citrix Virtual Apps and Desktopsto determine whether they are LTSR compliant. The scanned components can reside on virtual or physical machines. A compliance report is generated showing the LTSR compliance status of the installed components. The report also includes recommendations for components that are not in compliance or are not running the latest version. The compliance results can be uploaded to Citrix Insight Services (CIS) for further analysis and acceptance. Note: XenApp and XenDesktop 7.15 LTSR includes new versions of Windows VDAs and new versions of several XenApp and XenDesktop components. For detailed information, see https://docs.citrix.com/en-us/xenapp-and-xendesktop/7-15-ltsr/whats-new.html. **Prerequisites** * Microsoft .NET Framework 3.5 SP1. * Microsoft Windows PowerShell 2.0 or later. * Windows Remote Management must be enabled on target machines * To scan successfully, the user account must meet the following requirements: * Be aCitrix Virtual Apps and Desktopsadministrator with at least the read-only administrator default role and * Be a member of the local administrators group on target machines. * Windows Firewall must allow inbound ICMP Echo Requests on target machines. * Ensure that Internet access requirements are met. * Ensure that required network ports are opened on target machines. **Enabling Windows Remote Management** To scan theCitrix Virtual Apps and Desktopscomponents, the LTSR Assistant requires WinRM to be enabled on target machines.To enable WinRM with the default settings and to enable execution of remote signed scripts: 1\. Open the PowerShell Command Line window as a local administrator on the Delivery Controller and on each target machine. 2\. Type the following commands: winrm qc Set-ExecutionPolicy RemoteSigned For more information about Windows Remote Management, seeMicrosoft MSDN: Installation and Configuration for Windows Remote Management. **Windows Firewall Must Allow Inbound ICMP Echo Requests on Target Machines** Configure Windows Firewall to allow inbound ICMP echo requests on target machines. For detailed instructions, seeWindows Firewall Troubleshooting Situations: Nobody Can Ping My Computer. **Internet Access Requirements** LTSR Assistant uses Internet access to download LTSR compliance data from the Citrix website. The GUI executable, LTSRAssistant.exe, requires Internet access on startup. The CLI PowerShell module, Citrix.LTSRAssistant.Commands.dll, requires Internet access except when the –ScanOnly parameter is specified. **Required Network Ports** Ensure that the following TCP ports are open and that inbound connections to these ports are allowed on the specified machines. Delivery Controller: * XenDesktop PowerShell SDK HTTP: 80 * WinRM HTTP: 5985 Target Machines: * WinRM HTTP: 5985 **Unverified Components** This document sometimes refers to “unverified” or “unvalidated” components. These are components that the tool attempted to scan and check for compliance but was not able to due to insufficient information on the Delivery Controller or due to network connection errors. **Installing LTSR Assistant** To install LTSR Assistant, create a folder with read and execute rights for everyone, for Example, C:\LTSRAssistant\\. Download LTSRAssistant.zip and extract its content to the newly created folder. **Updating LTSR Assistant** The LTSR Assistant checks for updates on startup. When a newer version of the tool is detected, a “Get Latest Tool Version” hyperlink appears in the upper right corner of the tool interface. The link opens a window that recommends that you upgrade to the new version of the LTSR Assistant. Click "Yes" to download the new version of the tool. ![file](/servlet/rtaImage?eid=ka67y000000FJoj&feoid=00N0z0000031cRr&refid=0EM4z000000jpiY) **How to Use LTSR Assistant** Steps to scan and view the compliance report: 1\. Launch the tool by double-clicking _LTSRAssistant.exe._ ![file](/servlet/rtaImage?eid=ka67y000000FJoj&feoid=00N0z0000031cRr&refid=0EM4z000000jpiT) 2\. On the Welcome page, click "Next" to continue. ![file](/servlet/rtaImage?eid=ka67y000000FJoj&feoid=00N0z0000031cRr&refid=0EM4z000000jpiQ) 3.On the "Configuration" page, select "New configuration" to create a configuration, or "Existing configuration" if previously saved configuration files are available. For "Existing configuration," specify a full path to the existing configuration file in the text field shown below, or use the "Browse…" button to select the existing file. ![file](/servlet/rtaImage?eid=ka67y000000FJoj&feoid=00N0z0000031cRr&refid=0EM4z000000jpij) 4.On the "Delivery Controller" page, enter the name of the Delivery Controller you want to scan. In an existing configuration, the Delivery Controller field is prepopulated but can be modified if necessary. Ensure that the name is correct and click "Test Connection" to verify communication. Click "Next". ![file](/servlet/rtaImage?eid=ka67y000000FJoj&feoid=00N0z0000031cRr&refid=0EM4z000000jpiP) 5.On the "Baseline Components" page, click + to enter the machine name where the component is installed and select the component from the list. For the machine name, use a DNS hostname - not “localhost.” For the machine name, use a DNS hostname - not "localhost." If a configuration exists, the list of baseline components is prepopulated but you can modify it if necessary. You can add new entries and edit or remove existing entries. Verify that machine names and components are correct. Click "Next". ![file](/servlet/rtaImage?eid=ka67y000000FJoj&feoid=00N0z0000031cRr&refid=0EM4z000000jpie) 6.On the "Compatible Components" page, click + to enter the machine name where the component is installed and select the component from the list. For the machine name, use a DNS host name - not "localhost." If a configuration exists, the list of compatible components is prepopulated but you can modify it if necessary. You can add new entries and edit or remove existing entries. Verify that machine names and components are correct. Click "Next". ![file](/servlet/rtaImage?eid=ka67y000000FJoj&feoid=00N0z0000031cRr&refid=0EM4z000000jpii) 7.On the "Summary" page, the tool displays a summary of machine names entered for the Delivery Controller, LTSR baseline components, and LTSR compatible components. ![file](/servlet/rtaImage?eid=ka67y000000FJoj&feoid=00N0z0000031cRr&refid=0EM4z000000jpiS) 8\. If this is a new configuration or an existing configuration that has been modified, you can save it by clicking "Save" and following the prompt to specify the configuration file name and location. If you do not want to save the configuration or any changes you made to it, click "Scan" to begin scanning the components for compliance. ![file](/servlet/rtaImage?eid=ka67y000000FJoj&feoid=00N0z0000031cRr&refid=0EM4z000000jpif) 9\. The "Compliance Report" page shows the compliance scan progress. After the scan is completed, a compliance report appears. ![file](/servlet/rtaImage?eid=ka67y000000FJoj&feoid=00N0z0000031cRr&refid=0EM4z000000jpiO) 10.The "Compliance Report" page displays results for scanned components. For detailed results, click the hyperlink under " Compliant Components." If a component is not compliant or not running the latest version of the LTSR, click the hyperlink under "Recommended Updates" to open the webpage that contains all necessary information (including download links for patches) to make the component compliant or to bring it up to the latest version. You can also view the compliance report in a browser by clicking "View Report in Browser". ![file](/servlet/rtaImage?eid=ka67y000000FJoj&feoid=00N0z0000031cRr&refid=0EM4z000000jpiU) _Compliance report of LTSR 7.6_ ![file](/servlet/rtaImage?eid=ka67y000000FJoj&feoid=00N0z0000031cRr&refid=0EM4z000000jpih) 11.You can save the compliance report for later viewing or for proof of compliance. To do so, click "Save" and provide a file name and location. ![file](/servlet/rtaImage?eid=ka67y000000FJoj&feoid=00N0z0000031cRr&refid=0EM4z000000jpik) 12\. On the "Compliance Report" page, results can be uploaded to Citrix Insight Services.To upload the compliance report, click "Upload" and then "OK" to accept the upload notification. ![file](/servlet/rtaImage?eid=ka67y000000FJoj&feoid=00N0z0000031cRr&refid=0EM4z000000jpiR) 13.In the "Upload to Citrix" window, provide the Citrix user name and password. If a service request number has been provided, enter it here along with an optional description. After providing the information, click "Upload" to send the LTSR Compliance Report to Citrix Insight Services. ![file](/servlet/rtaImage?eid=ka67y000000FJoj&feoid=00N0z0000031cRr&refid=0EM4z000000jpig) 14\. After the upload is completed, click "Close" to exit the "Upload to Citrix" window. 15\. Click "Finish" to exit the tool. When asked to confirm, click “OK.” ![file](/servlet/rtaImage?eid=ka67y000000FJoj&feoid=00N0z0000031cRr&refid=0EM4z000000jpiM) **Loading the LTSR Assistant PowerShell Module** To use the command line interface (CLI), load the LTSR Assistant PowerShell module in a PowerShell session. The steps to load the module are as follows: 1\. Launch PowerShell as an administrator. 2\. Change the working directory to C:\LTSRAssistant by typing: cd C:\LTSRAssistant 3\. Import the LTSR Assistant PowerShell module by typing: import-module .\Citrix.LTSRAssistant.Commands.dll **How to Use the LTSR Assistant Command Line Interface** The following command line examples follow the convention used in PowerShell documentation when specifying command line synopses. Optional parameters are enclosed in square brackets, required values are enclosed in angle brackets, and placeholders for sets of parameters such as “Logging Parameters” and “CIS Upload Parameters” are enclosed in angle brackets. **Get command help** Use this command to get detailed information about parameters. Get-Help Invoke-LTSRAssistant **Scanning a Site** Use this command when scanning aCitrix Virtual Apps and DesktopsSite. Invoke-LTSRAssistant [-DeliveryController] [-Machines]