On Internet Explorer 11 Endpoint Analysis Plugin Fails to Run on NetScaler Gateway Virtual Server and User is prompted to “Download” or “Skip Check”

The Endpoint Analysis (EPA) plugin fails on NetScaler Gateway virtual server, when using Internet Explorer 11 (IE 11) with Microsoft hotfix KB3025390 installed.

After installation of the Microsoft hotfix, you will be directed to a page where you can either “Download” the plugin or “Skip Check” in some builds. The EPA plugin does not run as expected.

User-added image

Related:

Lifecycle Maintenance Hotfixes – Definitions and Examples

In some instances, hotfixes might be superseded or replaced. This happens only when a subsequent hotfix includes all fixes from the earlier hotfixes, as explained in the following section.

Note: The information in this document applies primarily to the XenApp and the XenDesktop products, but might be extended to other Citrix products as well.

Access to Hotfixes

Hotfixes are available for download from the Citrix Knowledge Center. The access provided to these hotfixes is based on expected customer impact, as mentioned in the following table:

Hotfix Type

Expected Customer Impact

Access

General Release

Affects a wide customer base

All customers

Limited Release

Affects a smaller number of customers

Customers with Priority and/or Priority Plus Offering Level, Technical Relationship Manager,CTPs, and Partners

Hotfix Replacement and Supersedence

Any hotfix that includes all fixes from an earlier hotfix either supersedes or replaces the original hotfix, as mentioned in the following table:

Original Hotfix Type

Subsequent Hotfix Type

Status of Original Hotfix

Rationale

Limited Release

General Release

Superseded hotfix is no longer available

All customers can access the subsequent hotfix

Limited Release

Limited Release

Superseded hotfix is no longer available

Customers with access to the original hotfix can also access the subsequent hotfix

General Release

General Release

Superseded hotfix is no longer available

All customers can access the subsequent hotfix

General Release

Limited Release

Replaced, but remains available for download from the Citrix Knowledge Center

Original hotfix remains available for customers who cannot access the Limited Release hotfix

Note: The terms superseded and replaced, as used in this article and on the Citrix Knowledge Center, are used to illustrate the difference between release types. They are not used in the same manner as Microsoft, Windows Installer, however Citrix hotfix readmes use the same terms.

The following table provides an examples of original hotfixes and their status:

Original Hotfix Subsequent Hotfix Status Rationale
Limited Release Hotfix A is available for download to customers with Subscription Advantage and a My Citrix account General Release Hotfix B is released. It contains all fixes from Hotfix A, plus new fixes Hotfix B supersedes Hotfix A Hotfix A is no longer available for download because Hotfix B is available to all customers
General Release Hotfix C is available for download from the Knowledge Center to all customers Limited Release Hotfix D is released. It contains all fixes from Hotfix C, plus new fixes Hotfix D replaces Hotfix C Both remain available for download because Hotfix D is available only to customers with Subscription Advantage and a My Citrix account
Limited Release Hotfix E is available for download to customers with Subscription Advantage and a My Citrix account Limited Release Hotfix F is released. It contains fixes, but does not contain all fixes from Hotfix E The status of Hotfix E is unchanged; Hotfix F is offered as a separate, additional hotfix Both are available for download because Hotfix F does not contain all of the fixes from Hotfix E

Related:

XenMobile Server 10.11.0 Rolling Patch 3

Package name: xms_10.11.0.10302.bin

For: XenMobile Server 10.11.0

Deployment type: On-premises only

Replaces: xms_10.11.0.10102.bin and xms_10.11.0.10202.bin

Date: December, 2019

Languages supported: English (US)

Readme version: 1.00

Readme Revision History

Version Date Change Description
1.00 December, 2019 Initial release

Important Notes about This Update

As a best practice, Citrix recommends that you install this and other updates only if you are affected by the specific issues they resolve.

Where to Find Documentation

This document describes the issue(s) resolved by this release and includes installation instructions. For additional product information, see XenMobile Server 10.11 on the Citrix Product Documentation site.

What’s new

For information about XenMobile Server 10.11.0 Rolling Patch 1 release, see XenMobile Server 10.11.0 Rolling Patch 1.

For information about XenMobile Server 10.11.0 Rolling Patch 2 release, see XenMobile Server 10.11.0 Rolling Patch 2.

Known Issue(s) in this Release

There are no known issues in this release.

New Fixes in This Update

  1. On devices running Android Q in Device Administrator mode, you are unable to connect to Secure Hub. You get the following error: Secure Hub could not connect.

    [From xms_10.11.0.10302.bin][CXM-75611]

  2. XenMobile Server experiences a communications error with Apple Deployment Programs (formerly DEP). For more information, see https://support.citrix.com/article/CTX267079.

  3. [From xms_10.11.0.10302.bin][CXM-76049]

Fixes From Replaced Releases

  1. On iOS devices, administrators may lose the ability to send an “unlock device” command to passcode protected devices after the device is upgraded to iOS 13.1.x. To resolve this issue, see https://support.citrix.com/article/CTX262076.

    [From xms_10.11.0.10102.bin][CXM-73152]

  2. Some third-party VPP apps fail to auto-update. This occurred due to blocked hostnames. For more information, see https://support.apple.com/en-us/HT201999.

    [From xms_10.11.0.10202.bin][CXM-72543]

  3. After enrolling a new device or re-enrolling an old device, an error message intermittently displays on the Manage tab.

    [From xms_10.11.0.10202.bin][CXM-72545]

  4. MAM devices wipe apps and app data because of a failure to get user domain details causing the device to assume the user is deleted.

    [From xms_10.11.0.10202.bin][CXM-72738]

  5. Unable to get the VPP for app version B2B when the platform parameter is incorrectly set in MDM API contentMetadataLookup

    From xms_10.11.0.10202.bin][CXM-72765]

  6. If the SMTP error “Couldn’t upload report” occurs, Secure Hub for iOS doesn’t send the log information to XenMobile Server.

    [From xms_10.11.0.10202.bin][CXM-74257]

  7. For iOS, location tracking doesn’t work if you do the following: Configure and deploy a location policy, enable tracking from device Security Actions, and then delete the deployed location policy and create a new one.

    [From xms_10.11.0.10202.bin][CXM-74595]

  8. On the XenMobile Server console, when you select the VPP app Standout, you get the following error: “500 Server Internal Error.”

    [From xms_10.11.0.10202.bin][CXM-74694]

Installing This Update

Note: If your system is configured in cluster mode, follow the steps below to update each node, one after the other.

Important: Before installing this update, take a snapshot of the current settings and create a backup of the database.

  1. Log on to your account on the Citrix website and download the XenMobile Server update (.bin) file to an appropriate location.
  2. In the XenMobile Server Console of a node click Settings > Release Management. The Release Management page appears, which displays the currently installed software version, as well as a list of any updates, patches, and upgrades you have already uploaded.
  3. Under Release Management, click Update. The Update dialog box appears.
  4. Click Browse to upload the update (.bin) file you have downloaded from support.citrix.com.
  5. Click Update and then if prompted, restart the XenMobile Server node using command line.

To verify the patch deployment

After installing this patch, log on to the XenMobile Server Console as an administrator, then navigate to Settings > Release Management > Updates. Information about the most recent successful patch installation appears in this section.

Related:

Hotfix XS81E001 – For Citrix Hypervisor 8.1

Who Should Install This Hotfix?

This is a hotfix for customers running Citrix Hypervisor 8.1.

Note: Ensure that you use XenCenter 8.1.2 or later to install this hotfix. The latest version of XenCenter is available from the Citrix Hypervisor Download site.

Information About this Hotfix

Component Details
Prerequisite None
Post-update tasks* Restart Host
Content live patchable** Yes
Baselines for Live Patch Citrix Hypervisor 8.1
Revision History

Published on Feb 13, 2020

** Available to Enterprise Customers.

Issues Resolved In This Hotfix

This hotfix resolves the following issues:

  • When running Reclaim Space on a thinly provisioned LUN with more than 2 TB of free space, the operation fails with an ioctl not supported error.

Installing the Hotfix

Customers should use either XenCenter or the Citrix Hypervisor Command Line Interface (CLI) to apply this hotfix. As with any software update, back up your data before applying this update. Citrix recommends updating all hosts within a pool sequentially. Upgrading of hosts should be scheduled to minimize the amount of time the pool runs in a “mixed state” where some hosts are upgraded and some are not. Running a mixed pool of updated and non-updated hosts for general operation is not supported.

Note: The attachment to this article is a zip file. It contains the hotfix update package only. Click the following link to download the source code for any modified open source components XS81E001-sources.iso. The source code is not necessary for hotfix installation: it is provided to fulfill licensing obligations.

Installing the Hotfix by using XenCenter

Choose an Installation Mechanism

There are three mechanisms to install a hotfix:

  1. Automated Updates
  2. Download update from Citrix
  3. Select update or Supplemental pack from disk

The Automated Updates feature is available for Citrix Hypervisor Premium Edition customers, or to those who have access to XenServer through their Citrix Virtual Apps and Desktops entitlement. For information about installing a hotfix using the Automated Updates feature, see the Applying Automated Updates in the Citrix Hypervisor documentation.

For information about installing a hotfix using the Download update from Citrix option, see Applying an Update to a Pool in the Citrix Hypervisor documentation.

The following section contains instructions on option (3) installing a hotfix that you have downloaded to disk:

  1. Download the hotfix to a known location on a computer that has XenCenter installed.
  2. Unzip the hotfix zip file and extract the .iso file
  3. In XenCenter, on the Tools menu, select Install Update. This displays the Install Update wizard.
  4. Read the information displayed on the Before You Start page and click Next to start the wizard.
  5. Click Browse to locate the iso file, select XS81E001.iso and then click Open.
  6. Click Next.
  7. Select the pool or hosts you wish to apply the hotfix to, and then click Next.
  8. The Install Update wizard performs a number of update prechecks, including the space available on the hosts, to ensure that the pool is in a valid configuration state. The wizard also checks whether the hosts need to be rebooted after the update is applied and displays the result.
  9. Follow the on-screen recommendations to resolve any update prechecks that have failed. If you want XenCenter to automatically resolve all failed prechecks, click Resolve All. When the prechecks have been resolved, click Next.

  10. Choose the Update Mode. Review the information displayed on the screen and select an appropriate mode.
  11. Note: If you click Cancel at this stage, the Install Update wizard reverts the changes and removes the update file from the host.

  12. Click Install update to proceed with the installation. The Install Update wizard shows the progress of the update, displaying the major operations that XenCenter performs while updating each host in the pool.
  13. When the update is applied, click Finish to close the wizard.
  14. If you chose to carry out the post-update tasks, do so now.

Installing the Hotfix by using the xe Command Line Interface

  1. Download the hotfix file to a known location.
  2. Extract the .iso file from the zip.
  3. Upload the .iso file to the Pool Master by entering the following commands:

    (Where -s is the Pool Master’s IP address or DNS name.)

    xe -s <server> -u <username> -pw <password> update-upload file-name=<filename>XS81E001.iso

    Citrix Hypervisor assigns the update file a UUID which this command prints. Note the UUID.

    04ffe352-3f45-4a2d-bc79-e3f2f13b6d79

  4. Apply the update to all hosts in the pool, specifying the UUID of the update:

    xe update-pool-apply uuid=04ffe352-3f45-4a2d-bc79-e3f2f13b6d79

    Alternatively, if you need to update and restart hosts in a rolling manner, you can apply the update file to an individual host by running the following:

    xe update-apply host=<host> uuid=04ffe352-3f45-4a2d-bc79-e3f2f13b6d79

  5. Verify that the update was applied by using the update-list command.

    xe update-list -s <server> -u root -pw <password> name-label=XS81E001

    If the update is successful, the hosts field contains the UUIDs of the hosts to which this update was successfully applied. This should be a complete list of all hosts in the pool.

  6. If the hotfix is applied successfully, restart each host in the pool, starting with the master.
  7. Use the update-pool-clean command to remove the update files from all hosts in the pool. This command frees up space on shared storage and does not uninstall the update.

    xe update-pool-clean uuid=04ffe352-3f45-4a2d-bc79-e3f2f13b6d79

Files

Hotfix File

Component Details
Hotfix Filename XS81E001.iso
Hotfix File sha256 9f1eca3c219c03fd002ebd61ea982e8d826c7e903b07761506f1eac13694188d
Hotfix Source Filename XS81E001-sources.iso
Hotfix Source File sha256 70b055290c0009f069a7eb7329fe084da1958e8e1e56d624cf36fbb7f82cfffa
Hotfix Zip Filename XS81E001.zip
Hotfix Zip File sha256 db7280bd8f791c91d0d2839e1d04f50f2887e2c26f48eb1cbedeb66b930c718f
Size of the Zip file 31.51 MB

Files Updated

kernel-4.19.19-6.0.10.x86_64.rpm
kernel-livepatch_4.19.19_6.0.9-1-1.x86_64.rpm

More Information

For more information, see Citrix Hypervisor Documentation.

If you experience any difficulties, contact Citrix Technical Support.

Related:

Unable to Upgrade SD-WAN WANOP Software Due to Maintenance Expiration Date

When attempting to upgrade SD-WAN WANOP Software the following error message appears:

“Patch File failed verification.

Please correct any errors listed below.

If the problem persists contact customer support.

Patch File verification errors:

Cannot install patch file:

Maintenance Expiration Date ####-##-## of the license must be later than the Release Date ####-##-## of the patch file.”

Related:

Hotfix XS80E003 – For Citrix Hypervisor 8.0

Who Should Install This Hotfix?

This is a hotfix for customers running Citrix Hypervisor 8.0.

Information About this Hotfix

Component Details
Prerequisite None
Post-update tasks* Restart Host
Content live patchable** No
Baselines for Live Patch N/A
Revision History

Published on Jul 24, 2019

** Available to Enterprise Customers.

Issues Resolved In This Hotfix

This hotfix resolves the following issues:

  • After live migration, a Windows VM can hang for over a minute.
  • If you run your Windows VMs with the viridian_reference_tsc flag enabled, the VM might crash during migration.

This hotfix also allows for the following improvement:

  • You can now increase the performance of Windows VMs by enabling the viridian_reference_tsc and viridian_stimer flags.

    Any new VMs created after you install this hotfix have these flags enabled by default and benefit from the performance improvement. To get the benefit of the improved performance in your existing VMs, complete the steps in the After installing this hotfix section of this article.

This hotfix also includes the following previously released hotfixes:

Installing the Hotfix

Customers should use either XenCenter or the Citrix Hypervisor Command Line Interface (CLI) to apply this hotfix. As with any software update, back up your data before applying this update. Citrix recommends updating all hosts within a pool sequentially. Upgrading of hosts should be scheduled to minimize the amount of time the pool runs in a “mixed state” where some hosts are upgraded and some are not. Running a mixed pool of updated and non-updated hosts for general operation is not supported.

Note: The attachment to this article is a zip file. It contains the hotfix update package only. Click the following link to download the source code for any modified open source components XS80E003-sources.iso. The source code is not necessary for hotfix installation: it is provided to fulfill licensing obligations.

Installing the Hotfix by using XenCenter

Choose an Installation Mechanism

There are three mechanisms to install a hotfix:

  1. Automated Updates
  2. Download update from Citrix
  3. Select update or Supplemental pack from disk

The Automated Updates feature is available for Citrix Hypervisor Premium Edition customers, or to those who have access to XenServer through their Citrix Virtual Apps and Desktops entitlement. For information about installing a hotfix using the Automated Updates feature, see the Applying Automated Updates in the Citrix Hypervisor documentation.

For information about installing a hotfix using the Download update from Citrix option, see Applying an Update to a Pool in the Citrix Hypervisor documentation.

The following section contains instructions on option (3) installing a hotfix that you have downloaded to disk:

  1. Download the hotfix to a known location on a computer that has XenCenter installed.
  2. Unzip the hotfix zip file and extract the .iso file
  3. In XenCenter, on the Tools menu, select Install Update. This displays the Install Update wizard.
  4. Read the information displayed on the Before You Start page and click Next to start the wizard.
  5. Click Browse to locate the iso file, select XS80E003.iso and then click Open.
  6. Click Next.
  7. Select the pool or hosts you wish to apply the hotfix to, and then click Next.
  8. The Install Update wizard performs a number of update prechecks, including the space available on the hosts, to ensure that the pool is in a valid configuration state. The wizard also checks whether the hosts need to be rebooted after the update is applied and displays the result.
  9. Follow the on-screen recommendations to resolve any update prechecks that have failed. If you want XenCenter to automatically resolve all failed prechecks, click Resolve All. When the prechecks have been resolved, click Next.

  10. Choose the Update Mode. Review the information displayed on the screen and select an appropriate mode.
  11. Note: If you click Cancel at this stage, the Install Update wizard reverts the changes and removes the update file from the host.

  12. Click Install update to proceed with the installation. The Install Update wizard shows the progress of the update, displaying the major operations that XenCenter performs while updating each host in the pool.
  13. When the update is applied, click Finish to close the wizard.
  14. If you chose to carry out the post-update tasks, do so now.

Installing the Hotfix by using the xe Command Line Interface

  1. Download the hotfix file to a known location.
  2. Extract the .iso file from the zip.
  3. Upload the .iso file to the Pool Master by entering the following commands:

    (Where -s is the Pool Master’s IP address or DNS name.)

    xe -s <server> -u <username> -pw <password> update-upload file-name=<filename>XS80E003.iso

    Citrix Hypervisor assigns the update file a UUID which this command prints. Note the UUID.

    b99a5e83-e335-431a-a1d1-10e222bc4bfa

  4. Apply the update to all hosts in the pool, specifying the UUID of the update:

    xe update-pool-apply uuid=b99a5e83-e335-431a-a1d1-10e222bc4bfa

    Alternatively, if you need to update and restart hosts in a rolling manner, you can apply the update file to an individual host by running the following:

    xe update-apply host=<host> uuid=b99a5e83-e335-431a-a1d1-10e222bc4bfa

  5. Verify that the update was applied by using the update-list command.

    xe update-list -s <server> -u root -pw <password> name-label=XS80E003

    If the update is successful, the hosts field contains the UUIDs of the hosts to which this update was successfully applied. This should be a complete list of all hosts in the pool.

  6. If the hotfix is applied successfully, restart each host in the pool, starting with the master.
  7. Use the update-pool-clean command to remove the update files from all hosts in the pool. This command frees up space on shared storage and does not uninstall the update.

    xe update-pool-clean uuid=b99a5e83-e335-431a-a1d1-10e222bc4bfa

After installing this hotfix

This hotfix includes updates to VM templates. These updates automatically apply to any VMs you create after applying the hotfix. To apply the updates to your existing Windows VMs and benefit from the performance improvements provided in this hotfix, complete the following steps:

  1. List all VMs that use viridian:

    xe vm-list platform:viridian=true –minimal

  2. For each of the VMs that you want to update:
    1. Refer to the viridian flags in the updated template for the VM. For example:

      xe template-list name-label=’Windows 7 (64-bit)’ params=platform

    2. Update the viridian flags in the platform field to match the updated template. For example:

      xe vm-param-set uuid=<vm-uuid> platform:viridian=true platform:viridian_time_ref_count=true platform:viridian_reference_tsc=true platform:viridian_apic_assist=true platform:viridian_crash_ctl=true platform:viridian_stimer=true

      Note: Only the viridian_reference_tsc and viridian_stimer flags are required to benefit from the performance improvements in this hotfix, but we advise that you set all available viridian flags.

    3. Shut down the VM.

      Do not restart the VM. The restart function does not apply these updates. Ensure that you fully shut down your VM.

      If you do not shut down your VM, you can introduce inconsistency in your viridian flags. This inconsistency can prevent you from applying further hotfixes to the Citrix Hypervisor server that hosts this VM or updating the Citrix Hypervisor server that hosts this VM to a later version.

    4. Start the VM.

Note: You can update all VMs that use viridian with a single command:

xe vm-list platform:viridian=true –minimal | tr , ‘n’ | xargs -n 1 -I {} xe vm-param-set uuid={} platform:viridian=true platform:viridian_time_ref_count=true platform:viridian_reference_tsc=true platform:viridian_apic_assist=true platform:viridian_crash_ctl=true platform:viridian_stimer=true

Only use this command if you want to update all of your VMs. You must shut down and start the VMs again for the updates to take effect.

This process does not update the snapshots associated with these VMs. Do not attempt to update existing snapshots. Instead create a new snapshot from your updated VM.

If you use your VMs with Citrix Virtual Apps and Desktops Machine Creation Services or Citrix Provisioning, ensure that you update your golden images.

Files

Hotfix File

Component Details
Hotfix Filename XS80E003.iso
Hotfix File sha256 c0f0454c1b1bfda741d391851d02f28570cbda9498893e0c8767c0e6c4198981
Hotfix Source Filename XS80E003-sources.iso
Hotfix Source File sha256 22a9c553d27ad01acf7efc80266497eae4959d5c99fc80250064516742a1b44a
Hotfix Zip Filename XS80E003.zip
Hotfix Zip File sha256 d14b96615b96ac7aa7ca42e2fc5b98c953d2cffb150910e88ef27da51af8b48f
Size of the Zip file 7.85 MB

Files Updated

guest-templates-json-1.7.21-1.noarch.rpm
guest-templates-json-data-linux-1.7.21-1.noarch.rpm
guest-templates-json-data-other-1.7.21-1.noarch.rpm
guest-templates-json-data-windows-1.7.21-1.noarch.rpm
guest-templates-json-data-xenapp-1.7.21-1.noarch.rpm
microcode_ctl-2.1-26.xs5.x86_64.rpm
xen-dom0-libs-4.11.1-7.4.x86_64.rpm
xen-dom0-tools-4.11.1-7.4.x86_64.rpm
xen-hypervisor-4.11.1-7.4.x86_64.rpm
xen-libs-4.11.1-7.4.x86_64.rpm
xen-tools-4.11.1-7.4.x86_64.rpm

More Information

For more information, see Citrix Hypervisor Documentation.

If you experience any difficulties, contact Citrix Technical Support.

Related: