Recommended Hotfixes for XenServer 7.x

Citrix Hypervisor, formerly XenServer, is powered by the Xen Project hypervisor.

This article contains the complete set of recommended updates/hotfixes for XenServer 7.x .

For List of XenServer Tools/Management Agent/Windows Driver Updates refer toCTX235403-Updates to Management Agent – For XenServer 7.0 and later​

For XenServer 6.x hotfixes, refer to CTX138115 – Recommended Hotfixes for XenServer 6.x

XenServer 7.6 XenServer 7.5 XenServer 7.4 XenServer 7.1 CU2 XenServer 7.1 CU1 XenServer 7.0

For more information, refer to the following Knowledge Center articles

Note: Citrix recommends updating the XenServer Console before updating any new hotfixes. All XenServer hotfixes can be applied at the same time and the hotfixes in the article are not relevant to the installation order

Hotfix XS76E003 –

For XenServer 7.6
All customers who are affected by the issues described in CTX246572 – Citrix XenServer Multiple Security Updates should install this hotfix.

This hotfix also includes the following previously released hotfixes:

Content live patchable** No
Hotfix XS75E003 –

For XenServer 7.5
All customers who are affected by the issues described in CTX236548 – Citrix XenServer Multiple Security Updates should install this hotfix.

Content live patchable** No
Hotfix XS75E005 –

For XenServer 7.5
All customers who are affected by the issues described in CTX236548 – Citrix XenServer Multiple Security Updates should install this hotfix.

Content live patchable** No
Hotfix XS75E008 –

For XenServer 7.5
All customers who are affected by the issues described in CTX246572 – Citrix XenServer Multiple Security Updates should install this hotfix.

This hotfix also includes the following previously released hotfixes:

Content live patchable** No
Hotfix XS74E005 –

For XenServer 7.4
All customers who are affected by the issues described in CTX236548 – Citrix XenServer Multiple Security Updates should install this hotfix.

Content live patchable** No
Hotfix XS74E006 –

For XenServer 7.4
All customers who are affected by the issues described in CTX236548 – Citrix XenServer Multiple Security Updates should install this hotfix..

This hotfix also includes the following previously released hotfixes:

Content live patchable** No
Hotfix XS74E007 –

For XenServer 7.4
All customers who are affected by the issues described in CTX236548 – Citrix XenServer Multiple Security Updates should install this hotfix.

Content live patchable** No
XenCenter 7.1.3

This release of XenCenter is for customers who use XenCenter as the management console for XenServer 7.1 LTSR. XenCenter 7.1 CU2 is released as part of XenServer 7.1 Cumulative Update 2 and is available only to customers on the Customer Success Services program.

We recommend that you install this version of XenCenter before using XenCenter to update XenServer 7.1 CU1 hosts to XenServer 7.1 CU2.

XS71ECU2

XenServer 7.1 Cumulative Update 2 (XS71ECU2) must be installed by customers running XenServer 7.1 LTSR CU1. It includes all previously released XenServer 7.1 CU1 hotfixes. Installation of XS71ECU2 is required for all future functional hotfixes for XenServer 7.1 LTSR.

XenServer 7.1 Cumulative Update 2 and its subsequent hotfixes are available only to customers on the Customer Success Services program.

Citrix will continue to provide security updates to the base XenServer 7.1 CU1 product for a period of three months from the release date of the XenServer 7.1 Cumulative Update 2 (until March 12, 2019). After this three month period elapses, any new hotfixes released will only support XenServer 7.1 with CU2 applied.

For more information about XenServer 7.1 CU2, see the Citrix XenServer 7.1 Cumulative Update 2 Release Notes.

Content live patchable** No
Hotfix XS71ECU2001 – For XenServer 7.1 Cumulative Update 2

This hotfix resolves the following issue:

  • The XenServer host can experience a memory leak in dom0. This memory leak is triggered by invalid responses to FLOGI messages from connected FCoE equipment.
Content live patchable** Yes
Hotfix XS71ECU2002 – For XenServer 7.1 Cumulative Update 2 All customers who are affected by the issues described in CTX246572 – Citrix XenServer Multiple Security Updates should install this hotfix.

This security hotfix addresses the vulnerabilities as described in the Security Bulletin above. In addition, it resolves the following issues:

  • On some systems, the XenServer host fails to boot when 4096 MB or more memory is assigned to dom0.
  • When starting a VM with more than 16 PCI devices assigned, the VM fails to start and the following error appears in the logs: “Error: hit limit of 16 RMRR devices for domain”.
  • If you have not rebooted your XenServer 7.1 host after applying Cumulative Update 2 and you try to start, reboot, or resume a suspended VM on the host, the operation fails. You might also notice coredump files in any server status reports you collect in this state.

XenServer 7.1 Cumulative Update 1 (XS71ECU1) should be installed by customers running XenServer 7.1. It includes all previously released XenServer 7.1 hotfixes. Installation of XS71ECU1 is required for all future functional hotfixes for XenServer 7.1 LTSR. XenServer 7.1 Cumulative Update 1 and its subsequent hotfixes are available only to customers on the Customer Success Services program.

Citrix will continue to provide security updates to the base XenServer 7.1 product for a period of three months from the release date of the XenServer 7.1 Cumulative Update 1 (until December 11, 2017). After this three month period elapses, any new hotfixes released will only support XenServer 7.1 with CU1 applied.

XenCenter 7.1.2

This release of XenCenter is for customers who use XenCenter as the management console for XenServer 7.1.

XenCenter 7.1.2 is available on the Citrix downloads site as a restricted download. You must sign in to the site and have active membership of the Customer Success Services (CSS) program to access these downloads.

Hotfix XS71ECU1006-

For XenServer 7.1CU1
This is a hotfix for customers running XenServer 7.1 Cumulative Update 1. All customers who are affected by the issues described in CTX230138 – Citrix XenServer Multiple Security Updates should install this hotfix.

Content live patchable* No
Hotfix XS71ECU1013-

For XenServer 7.1CU1
This is a hotfix for customers running XenServer 7.1 Cumulative Update 1. All customers who are affected by the issues described in CTX232655 – Citrix XenServer Multiple Security Updates should install this hotfix.

This security hotfix addresses the vulnerabilities as described in the Security Bulletin above. In addition, it resolves the following issue:

  • If SNMP configuration is modified to request interface statistics Object Identifiers (OIDs) and when SNMP service happens to start before Openvswitch service, all further statistics requests to SNMP returns incorrect data.
Content live patchable* No
Hotfix XS71ECU1015-

For XenServer 7.1CU1

This hotfix addresses following issues:

Customers using Active Directory (AD) with XenCenter are unable to log on to XenCenter, or get disconnected intermittently. In some cases, XenCenter displays incorrect AD group membership details. This hotfix resolves this issue.

Content live patchable* No
Hotfix XS71ECU1019-

For XenServer 7.1CU1

This hotfix resolves the following issues:

  • A race condition in XenBus can cause pauses in Windows VM operation, which lead to Timeout Detection and Recovery (TDR) events. The TDR can cause the VM to crash.
  • Under low resource situations, Xennet can consume all of the RAM on a Windows VM. This causes the VM to crash.
  • XenVBD can consume 100% of a vCPU and can block other processes from using that vCPU.
Content live patchable* No

This hotfix also includes the following previously released hotfixes:

Hotfix XS71ECU1026-

For XenServer 7.1CU1
All customers who are affected by the issues described in CTX236548 – Citrix XenServer Multiple Security Updates should install this hotfix.

This hotfix also includes the following previously released hotfixes:

Content live patchable** No
Hotfix XS71ECU1029-

For XenServer 7.1CU1

This hotfix resolves the following issues:

  • After rebooting, a XenServer host can fail to connect to iSCSI targets on Compellent arrays.
  • When you attempt to migrate a VM between resource pools, the migration can fail with the following error: Storage_interface.Internal_error(“Jsonrpc.Parse_error(_)”). This migration failure can cause some versions of XenCenter to fail.
  • If you cancel an ongoing Storage XenMotion, the next attempt to migrate the VM using Storage XenMotion fails with the VDI Mirroring Cannot be performed error. However, any subsequent attempts to migrate the VM will succeed.
  • After taking a disk-only snapshot for a VM running in the pool, users randomly fail to access the Virtual Hard Disk (VHD) when trying to unpause the VM, and the VM stops responding. This is caused by time racing in Linux Logical Volume Manager (LVM).
  • In addition, this hotfix includes minor performance improvements when performing a large number of VM I/O operations.

This hotfix also includes the following previously released hotfixes:

Content live patchable** No
Hotfix XS71ECU1030-

For XenServer 7.1CU1

This hotfix resolves the following issues:

  • An incorrect setting in the I/O scheduler for all blktap devices can cause poor I/O performance in certain scenarios, depending on the server hardware, server configuration, VM configuration, and workload. This hotfix includes the correct setting.
  • Due to incorrect maximum sector size used by Dom0 kernel, users failed to copy VDIs to/from SR targets on certain iSCSI disks.
  • For XenServer pools that use certain storage targets, a race condition in the iSCSI module can cause hosts in the pool to crash.
  • It is not possible to attach storage provided by iSCSI target Server on Windows Server 2016 VMs.

This hotfix also includes the following previously released hotfixes:

Content live patchable** Yes
Hotfix XS71ECU1033-

For XenServer 7.1CU1

This hotfix resolves the following issues:

  • If customers upgrade a host with legacy disk partition from XenServer 6.x to XenServer 7.1 CU1, and then attempt to apply a subsequent Cumulative Update as an update, they may receive an insufficient space error. This hotfix includes a fix to reduce the calculated space required to apply the update. You must apply this hotfix to XenServer 7.1 CU1 before attempting to update to a subsequent Cumulative Update. This hotfix should not be necessary on hosts that have the new host disk partition layout introduced in XenServer 7.0.
  • When customers are attempting to use Jumbo Frames, a VM without PV drivers installed would cause the MTU to drop to 1500 as the MTU was only being set for the paravirtualised VIF device and not for the fully emulated TAP device.

This hotfix also includes the following previously released hotfixes:

Content live patchable** No
Hotfix XS71ECU1035-

For XenServer 7.1CU1
All customers who are affected by the issues described in CTX246572 – Citrix XenServer Multiple Security Updates should install this hotfix.

This security hotfix addresses the vulnerabilities as described in the Security Bulletin above. In addition, it resolves the following issues:

  • On some systems, the XenServer host fails to boot when 4096 MB or more memory is assigned to dom0.
  • When starting a VM with more than 16 PCI devices assigned, the VM fails to start and the following error appears in the logs: ” Error: hit limit of 16 RMRR devices for domain”.

This hotfix also includes the following previously released hotfixes:

Apply the following hotfixes for XenServer 7.0 and restart XenServer when the hotfix installation is complete.

Hotfix XS70E001 –

For XenServer 7.0
This is a XenCenter update (a .exe file) and not a host side Hotfix. This package needs to be installed

on the Windows Machine Running XenCenter
Hotfix XS70E002 – For XenServer 7.0 All customers who are affected by the CVE-2016-2107 issue described in

CTX212736: Citrix XenServer Multiple Security Updates should install this hotfix.
Hotfix XS70E004 – For XenServer 7.0 Important: This is a critical hotfix for customers running XenServer 7.0. All XenServer 7.0

customers must apply this hotfix.
Hotfix XS70E009 – For XenServer 7.0

This hotfix resolves the following issue:

  • In rare circumstances when a XenServer host is enabling HA, or during a host reboot with HA enabled, the host can fail to establish HA communication with the other hosts. This is due to another process on the host using the listening port required by the HA software.
Update XS70EU001 – Management Agent for XenServer 7.0 The Management Agent update resolves the following issues:

  • Installation of Management Agent can fail after installing newer I/O drivers through Windows Update.
  • Failure to reboot a Windows VM after installing XenServer Tools can result in excessive log entries being written to xensource.log and xenstored-access.log until the VM is rebooted. If customers do not reboot the VM, or delay the reboot, excess logs can fill up the XenServer host log partition.
  • The Management Agent can crash and respawn on systems without a terminal services Windows Management Instrumentation (WMI) object causing high CPU usage and excessive logging in /var/log/daemon.
  • If the Management Agent auto update is enabled after installing XenServer Tools, and a new update is available, the initial auto-update can fail due to a race condition that can cause multiple update attempts to occur simultaneously.
Update XS70EU002 – Management Agent for XenServer 7.0 New versions of the I/O drivers, compatible with Microsoft Windows Server 2016 have been released.
Update XS70EU003 – Management Agent for XenServer 7.0
  • The default behavior of the Management Agent has been improved to enable customers to configure whether any I/O driver updates included in the Management Agent should be applied automatically. For more information, see section 4.3.1 Installing XenServer Tools in the XenServer 7.0 Virtual Machine User’s Guide.
  • This version (v7.1.844) of the Management Agent includes new versions of the I/O drivers that are compatible with Microsoft Windows Server 2016. These drivers have been released previously through the Microsoft Windows Server Update Service. For more information, see Update XS70EU002 – Windows I/O Drivers for XenServer 7.0.
Hotfix XS70E018 – For XenServer 7.0 This is a hotfix for customers running XenServer 7.0. All customers who are affected by the issues described in CTX220112: Citrix XenServer Multiple Security Updates should install this hotfix.
  • This is a hotfix for customers running XenServer 7.0. All customers who are affected by the issues described in CTX219378: Citrix XenServer Multiple Security Updates should install this hotfix.
  • This hotfix supports the improvements to XenServer’s Direct Inspect APIs.
Hotfix XS70E024 – For XenServer 7.0
  • When booting a vGPU provisioned Virtual Machine (VM) from network, an interaction between VGA BIOS and VGA emulation code in the vGPU device model can result in the corruption of the VM console in XenCenter.
Hotfix XS70E027 – For XenServer 7.0
  • When Installing XenServer or upgrading XenServer to a newer version, PBIS services get enabled (even when Role-based access control (RBAC) is not used) and display a lot of error messages. Also, this issue consumes a lot of control domain (dom0) resources.
Hotfix XS70E028 – For XenServer 7.0 This hotfix supports the following new guest operating systems.

  • Oracle Linux 6.8
  • Red Hat Enterprise Linux 6.8
  • CentOS 6.8
  • NeoKylin Linux Advanced Server 6.5 ( only 64 bit )
  • NeoKylin Linux Advanced Server 7.2 ( Only 64 bit )
  • SUSE Linux Enterprise Server 11 SP4
Hotfix XS70E037 – For XenServer 7.0

This hotfix addresses the following issue:

  • When attempting to use XenServer Conversion Manager (XCM) Console to connect to an XCM Virtual Appliance that runs on a slave host, the connection fails and the following message is displayed by the console: “There was a failure communicating with the plugin.” This hotfix ensures that the XCM Console can connect to a XCM Virtual Appliance that runs on any XenServer host.
Hotfix XS70E041 – For XenServer 7.0

This hotfix resolves the following issue:

  • When using SSH to connect to XenServer, a user might experience a memory leak in systemd on XenServer.
Hotfix XS70E048 – For XenServer 7.0 This is a hotfix for customers running XenServer 7.0. All customers who are affected by the issues described in CTX230138 – Citrix XenServer Multiple Security Updates should install this hotfix.

This hotfix also includes the following previously released hotfixes:

Hotfix XS70E052 – For XenServer 7.0 This is a hotfix for customers running XenServer 7.0. All customers who are affected by the issues described in CTX232655 – Citrix XenServer Multiple Security Updates should install this hotfix.This security hotfix addresses the vulnerabilities as described in the Security Bulletin above.
Hotfix XS70E061 – For XenServer 7.0

This is a hotfix for customers running XenServer 7.0.

All customers who are affected by the issues described in CTX236548 – Citrix XenServer Multiple Security Updates should install this hotfix.

Hotfix XS70E062 – For XenServer 7.0

This hotfix resolves the following issues:

  • Virtual machines (VMs) configured with in-guest software RAID may fail to cleanly shut down or restart.
  • After taking a disk-only snapshot for a VM running in the pool, users randomly fail to access the Virtual Hard Disk (VHD) when trying to unpause the VM, and the VM stops responding. This is caused by time racing in Linux Logical Volume Manager (LVM).
  • After rebooting, a XenServer host can fail to connect to iSCSI targets on Compellent arrays.
  • When Intellicache mirroring fails due to ENOSPC on shared storage, the VBD image list gets truncated to point to itself. This causes an infinite loop and can lead to the I/O datapath stopping and subsequently VMs freezing.
  • When a pool master node executes multi-step plugins on the pool member nodes after important events such as coalesce, the plugin continues to execute through all its steps even if one of the previous ones have failed. This can lead to complications such that the other VDI operations are permanently blocked with OTHER_OPERATION_IN_PROGRESS.
  • After deleting a snapshot on a pool member that is not the pool master, a coalesce operation may not succeed. In such cases, the coalesce process can constantly retry to complete the operation, resulting in the creation of multiple RefCounts that can consume a lot of space on the pool member.
  • The storage cleanup process initiated after a VDI destroy can conflict with ongoing VDI copy processes (including Storage XenMotion), causing subsequent operations on the SR to fail.

This hotfix also includes the following previously released hotfixes:

Hotfix XS70E063 – For XenServer 7.0

This hotfix resolves the following issues:

  • High Availability (HA) enabled VMs can take longer to restart after a HA failover.
  • In rare cases, when a XenServer host in a pool is restarted, it may not be able to rejoin the pool.
  • In rare cases, attempts to shut down a XenServer host in a pool may not succeed.
  • On HA-enabled pools, when a task is initiated after a XenServer host has failed, VMs running on the host can take longer (about 10 minutes) to restart. This issue occurs when a task is assigned to the host after it has failed, but before XAPI is aware of the host failure. In such cases, the task doesn’t get cancelled even when XAPI is notified about the failure, causing delays in restarting the VMs.
  • When migrating VMs that have Dynamic Memory Control (DMC) enabled, the VMs shutdown operation can unexpectedly fail. This is caused by reducing memory allocation before shutdown and this operation taking longer than expected.
  • On Nutanix hosts, the host’s memory-overhead is miscalculated after first boot. This is because XAPI calculates the available host RAM on startup assuming no domains other than the XenServer Control Domain are running. On first boot this is true but on subsequent boots, the Nutanix Controller VM (CVM) is started before XAPI.

This hotfix also includes the following previously released hotfixes:

Hotfix XS70E065 – For XenServer 7.0

This hotfix resolves the following issues:

  • A race condition caused Windows VMs to hang repeatedly and give an error with Event ID 129: “StorPort detected a SRB timeout, and issued a reset”.
  • XenVBD can consume 100% of a vCPU and can block other processes from using that vCPU.
  • If a restart is performed without clicking on the Yes or No buttons of the restart to complete installation dialog box, the dialog box continues to appear even after restarting the VM.

This hotfix also includes the following previously released hotfixes:

Hotfix XS70E066 – For XenServer 7.0 All customers who are affected by the issues described in CTX246572 – Citrix XenServer Multiple Security Updates should install this hotfix.

This security hotfix addresses the vulnerabilities as described in the Security Bulletin above.

This hotfix also includes the following previously released hotfixes:

Related:

  • No Related Posts

Install and Use Citrix Files for Windows

TIPS! Need Citrix Files for Windows? Download it here: http://dl.sharefile.com/cfwin

Contents

System Requirements

Available Localization

Install and Configuration

Basic Operations

Icon Overlays

Accessing Dashboard

Settings Menu

Group Policy Definitions

Known Issues

Citrix Files allows you to access your files in ShareFile directly through a mapped drive providing a native Windows Explorer experience. Files are downloaded only when accessed and temporarily stored on your computer. Changes made to the files are automatically saved back to ShareFile cloud. You can also access additional functionality through the Windows right-click context menu and perform operations such as Sharing or Requesting of files.



System Requirements

  • Windows 7 or Higher
  • Windows Server 2008 R2
  • Windows Server 2012 R2
  • Windows Server 2016
  • .NET 4.6.2 Framework is required



Available Localization

Citrix Files supports the following languages: English, Spanish, French, German, Japanese, Dutch, Portuguese, Korea, Simplified Chinese and Russian.



Install and Configuration

Download the Citrix Files executable. Launch the executable and follow the prompts to install the application. Note: Administrative permissions are required to install on your workstation.

Installation Note: In some environments, mainly Windows 10, a reboot may be required after installation. This is necessary in order to properly load the file system driver to mount the Citrix Files drive. If the user chooses to skip the reboot, you may need to launch the application through the start menu. Drive Mapper + Citrix Files for Windows are not supported on the same device.
Installation Note 2: To install Citrix Files without creating a desktop shortcut, use the syntax CitrixFilesForWindows.exe SHORTCUT=0

Once installed, log into your Citrix Files account. After login, a new drive volume “Citrix Files” will appear on your machine. By default, this drive is S: but may be a different drive letter if S: is already in use. This drive will display all of your files and folders from your Citrix Files account.

User-added image
User-added image

Basic Operations

Operation Description
Open and Edit Open a file in your S: drive, make some edits and save. Your changes will automatically be saved back to your Citrix Files account.
Upload Drag a file or folder to the S: drive to upload. You may also perform a copy and paste to upload a file or folder.
Download Drag a file or folder from the S: drive to your desktop or any other folder to download. You may also perform a copy and paste of files and folders to download.
Delete Drag a file or folder to the trash. Although you will be warned that the file will be permanently deleted, items will be available in Citrix Files’s Recycle Bin.
New Folder Creates a new folder in your ShareFiles account.

Right Click Context Menu

Citrix Files integrates with the Windows Explorer context menu to give the application access to additional Citrix Files options. Right click on a file or folder inside your S: to view the context menu options:

User-added image

Menu Option Description
Share options

Available when you right click on a file or folder.

  • Copy Link – Copies a download link to your clipboard. Link settings will be determined by the share options in your settings.
  • Email with Citrix Files – Send a share download link through email. Message options may be customized before sending or by modifying the default share options in your settings.
  • Email with Mail App – Send a download link using your default email client. Link settings will be determined by the share options in your settings.
Request Files

Available when you right-click on a folder, or within a folder when no files are selected.

  • Copy Link – Copies a request link to your clipboard. Link settings will be determined by the share options in your settings.
  • Email with Citrix Files – Send a request link through email. Message options may be customized before sending of by modifying the default share options in your settings.
Open in Website

Opens up your default browser to the current folder location on the Citrix Files website.

View Details View advanced details of a file including file properties, previous versions, and notes.
Check Out Check out a file. If the file is already checked-out, the Check-in option will appear.
Upload Upload files or folders directly from your computer. Use this option if uploading a large file or a large number of files.
Download Download files or folder to a specific location on your computer. Use this option if downloading a large file or a large number of files.
Add to Favorites Add a file or folder to your Favorites folder. If a file or folder is already a Favorite, you will have the option to remove from Favorites.
Refresh Content Manually refreshes the contents of a folder. Note: Folder contents should update automatically as remote changes are made, but you can use this function if you need to refresh manually.
Manage Folder Permissions Allows you to manage access permissions for a folder. You can add/remove users to that folder or limit which operations they are allowed to perform. This context menu option is only available on Folders.

Icon Overlays

Files and Folders will have an icon overlay representing the status of that item. The following defines what each icon overlay represents:

User-added image

Online-only files / folders don’t take up space on your computer. You see a cloud icon for each online-only file / folder in File Explorer, but the file / folder doesn’t download to your device until you access it. You can’t open online-only files / folders when your device isn’t connected to the Internet.

User-added image

Mixed state Folder occurs when you have some items within it are mixed across online-only, always offline and/or cached.

When you open an online-only file, it is download to your device and becomes a cached file. You can open cached files anytime, even without internet access. If you need to free up space, you can change the file back to online only. To do so just right-click the file and select ‘to be set’ or go to the Citrix Files dashboard – settings – free up space

User-added image

Only files or folders that you mark as “Make available offline” will have a green circle with the white check mark. These files or folders are downloaded to your device and are available offline. The bring these files or folders back to online-only, you need to right-click on the file or folder and select “Make available online”

User-added image

Sync (upload / download) is in progress

User-added image

The file is currently checked out



Accessing the Dashboard

You can access the dashboard by left clicking on the Citrix Files system tray icon. The dashboard will show you recently uploaded files. You can also access your Settings and other options by clicking the (…) in the top right corner of the dashboard.

User-added image

Settings Menu

Access the Settings menu from the dashboard or by right-clicking on the Citrix Files for Windows System Tray icon.

User-added image
Menu Option Description
Log Out Logs you out of your Citrix Files account. Cached files will be deleted.
Launch on Startup Determines whether the application should launch automatically after logging onto the computer.
Reset App Settings

Restores the app settings such as share options to their original, default values.

Enable beta Features If your admin has enabled Desktop Apps Betas, then this setting will appear to allow you to enable Betas on this device.
Drive Location Uses S: as the default drive letter, but can be changed to other drive letters which are currently not in use.
Drive Space Clicking ‘Free Up Space’ will move any cached files

Cached Files icon


to an online-only

Online Only icon


experience. Note, if using the Offline Access Beta, this setting will not move any files or folders you brought offline to an online only experience
Share Options Configure share options including notifications and security options.

Note:

Cache size default is 5GB. This can be modified by your administrator via GPO.

Free Up Space

In the Citrix Files for Windows Settings UI, end users have the ability to Free Up Space. When clicked, Citrix Files for Windows will move any cached files

Cached files icon
to an online-only

Online-only icon


experience.

Note:

It will not move any files or folders you brought offline to an online only experience

User-added image

Upon clicking, Free Up Space a native notification will inform you how much space was freed.

User-added image

Citrix Files includes policy definitions that can be used to push out settings and configuration via Group Policy (GPO). The .admx, .adml files are located at C:Program FilescitrixCitrix FilesPolicyDefinitions

To install:

  1. Copy the .admx file to c:WindowsPolicyDefinitions and the en-us .adml file to c:WindowsPolicyDefinitionsen-us
  2. Open Group Policy Editor and the policy options will be available under:
    1. Computer Configuration → Administrative Templates → Citrix Files
    2. User Configuration → Administrative Templates → Citrix Files
Setting Purpose
Computer Configuration
Enable Application If unchecked, Citrix Files will exit before mounting any drives or displaying any UI.
Enable On Premise Connectors

If unchecked, Network Share, Sharepoint, and Documentum connectors will not be visible in Citrix Files.

Enable Personal Cloud Connectors

If unchecked, Personal Cloud and Office 365 Connectors will not be visible in Citrix Files.

Enable Auto-update If Enable Auto-Update is unchecked, Citrix Files will not automatically update to the latest version.
Delete Cache on Exit If Delete Cache on Exit is checked, downloaded file contents will be removed when the application exits.
Cache Size This policy controls how much disk space (in megabytes) to use for cached files. The minimum cache size is 0 MB and the maximum is 9999 MB.
Cache Location This policy configures the location of the file content cache. By default, AppDataLocalCitrixCitrix FilesPartCache. If a custom path is set, that folder must already exist.
Cache Mode
  • Default: Citrix Files will choose a cache mode appropriate for the environment where it is executing.
  • Immediate: Citrix Files reads and writes directly to and from its cache. This mode uses the least memory, but may be slow if the application cache is not on the local disk.
  • Queued: Citrix Files retains some data in memory and writes to its cache in the background. This mode is recommended if the application cache is stored on a network location.
Maximum Log Size This policy will control how much disk space (in MB) will be used for application logs.
Disable Tutorial If enabled, Citrix Files will not show the tutorial on the initial login of the user.
Enable Offline Access If Enable Offline Access is unchecked, users will not be able to mark folders or files to be available while not connected to the internet.
Prefetch Metadata If this policy is enabled, Citrix Files will preload its filesystem structure. This will improve responsiveness at the expense of some CPU, memory, disk, and network usage.

By default, this functionality is disabled on Virtual Desktops (VDA), but enabled for non-VDA machines.

User Configuration
Account This policy configures the account to use for Citrix Files.
Enable Application If unchecked, Citrix Files will exit before mounting any drives or displaying any UI.
Excluded from Upload File extensions that will not be saved back to Citrix Files. These files can still be read and edited locally.
Mount Point 1-10

Mount a specific Citrix Files folder as a network drive. See Mount Point section below for more info.


Mount Points

Mount points allow you to specify a Citrix Files folder to mount as a network drive. You can specify up to 10 mount points.

Mount points can be configured through group policy editor. See the Group Policy Definitions section for instructions on how to import the Citrix Files policy definitions.

To create a mount point, specify the Citrix Files folder by the path to that folder, separated by the ” character. In some cases, the top-level folder name may vary across user types or across different end-user languages. In such cases, you can create the mount point using %wildcard% alias as outlined in the examples below.

Folder type Example
Personal Folders Personal Folders<FolderName> or %personal%<FolderName>
Shared Folders Shared Folders<FolderName><FolderName2> or %shared%<FolderName>
Favorites Favorites or %favorites%<FolderName>
Network Shares connector Network Shares<connector name> or %networkshares%<ConnectorName>
SharePoint connector SharePoint<connector name> or %sharepoint%<ConnectorName>
Box connector Personal CloudBox or %personalcloud%Box
Dropbox connector Personal CloudDropbox or %personalcloud%Dropbox
Google Drive connector Personal CloudGoogle Drive or %personalcloud%Google Drive
OneDrive connector Personal CloudOneDrive or %personalcloud%OneDrive
Office365 connectors Office 365<connector name> or %office365%<ConnectorName>
Root of account (default view)

User-added image



Known Issues

Issue Description Fix or Workaround (if available)
Install Uninstalling the Citrix Files App will remove the current logged in user’s local AppData, but will not remove any other user’s Citrix Files AppData on that machine. Remove the C:users<user>AppdataLocalCitrixCitrix Files and C:Users<user>AppDataRoamingCitrixCitrix Files directories for each user.
Login User may see ‘Failed to execute action’ on login dialog. Attempt to clear the folder below and restart the app C:Users<user>AppDataRoamingCitrixCitrix Files
Explorer Integration If creating or renaming a folder and the operation fails, it is possible that a duplicate folder name exists inside that folder but has not been granted access to your user to see. Try to create or rename the folder to a different name.
Explorer Integration Windows explorer performance may be degraded if browsing a folder containing a larger-sized .exe file. You can wait momentarily while Explorer will eventually respond. n/a
Explorer Integration Windows explorer performance may be degraded if browsing a folder containing a large amount of image/video files. Utilize the following article: CTX241253
Explorer Integration Files are not displayed when browsing a long folder path exceeding 260 chars. n/a
Explorer Integration If changing drive letters for Citrix Files, the left navigation pane may not refresh to the new drive letter immediately. If you navigate into “PC” folder and then navigate into your new Drive letter, the pane should update correctly.
Explorer Integration Citrix Files drive fails to mount on Windows 10.

There was a recent Windows update in build 1809 which introduced issues with Drive Mounting.
Please see https://support.microsoft.com/en-us/help/4471218/mapped-network-drives-don-t-work-in-windows-10-version-1809 for more information and workarounds.
File Operations File or folder names starting with the ~ symbol cannot be uploaded. (#566) n/a
File Operations If copying a file to another folder, versions will not be copied over. This only applies to ‘copy’ operations, and not move. n/a
File Operations Renaming a file or folder to the same name with different case is not allowed. n/a
File Operations Citrix Files for Windows fails to mount on Windows 10. A recent Windows update in version 1809 introduced issues with drive mounting. For more information and workarounds on mapped drives and Windows 10 1809, see https://support.microsoft.com/en-us/help/4471218/mapped-network-drives-don-t-work-in-windows-10-version-1809
Open/ Edit Editing a checked-out file may result in errors if the user does not have delete permission. Give the user delete permissions for that particular folder, or do not check out the file and edit.
Open/ Edit Temp office files may be seen in explorer during editing of a file. After refreshing the explorer view, the temp files should be removed from the explorer view.
Connectors Mount point configured for OneDrive for Business sub-folder intermittently doesn’t load (#763) Create the mount point to point to the root of the connector. Ex: Office 365<connector name>
Icon Overlays If Citrix Files is installed on same machine as ShareFile Sync, the overlay for Check-in/Check-out may not appear. n/a
Restricted Zone Context menu does not display when you right-click on the restricted zone folder. Currently, we do not support restricted zones.
Delete If a user does not have delete permissions on a folder, if they attempt to delete a file from Citrix Files, the file will temporarily disappear from the Explorer view, but will re-appear within a few seconds along with a system notification message that the delete operation failed. n/a

Related:

  • No Related Posts

Hotfix XS71ECU2003 – For XenServer 7.1 Cumulative Update 2

Who Should Install This Hotfix?

This is a hotfix for customers running XenServer 7.1 Cumulative Update 2.

Note: Customers must install Hotfix XS71ECU2002 before attempting to apply this hotfix.

Note: This hotfix is available only to customers on the Customer Success Services program.

Information About this Hotfix

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

Published on Mar 18, 2019

** Available to Enterprise Customers.

Issues Resolved In This Hotfix

This hotfix resolves the following issues:

  • Depending on the guest OS and device, devices passed through to a guest might not function correctly due to missed interrupts.

Installing the Hotfix

Customers should use either XenCenter or the XenServer Command Line Interface (CLI) to apply this hotfix. When the installation is complete, see the Post-update tasks in the table Information About this Hotfix for information about any post-update tasks you should perform for the update to take effect. 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 XS71ECU2003-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 XenServer Enterprise Edition customers, or to those who have access to XenServer through their XenApp/XenDesktop entitlement. For information about installing a hotfix using the Automated Updates feature, see the Applying Automated Updates in the XenServer documentation.

For information about installing a hotfix using the Download update from Citrix option, see Applying an Update to a Pool in the XenServer 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 XS71ECU2003.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>XS71ECU2003.iso

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

    63651705-430c-415a-8741-a3e9ade3e465

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

    xe update-pool-apply uuid=63651705-430c-415a-8741-a3e9ade3e465

    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=63651705-430c-415a-8741-a3e9ade3e465

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

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

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

  6. 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=63651705-430c-415a-8741-a3e9ade3e465

Files

Hotfix File

Component Details
Hotfix Filename XS71ECU2003.iso
Hotfix File sha256 55375938078304d9b2596b343fd492fc10ebc18102010e2a5ed731d4c3f20f2a
Hotfix Source Filename XS71ECU2003-sources.iso
Hotfix Source File sha256 de0811ae348ec0376a88a073453cf275be25e48826c13428560dfdbf68ff8122
Hotfix Zip Filename XS71ECU2003.zip
Hotfix Zip File sha256 c562383e1cf8c477eebe2e44f06146b2c724b9bd9c3b1e41eb3eed9ba4347f6a
Size of the Zip file 0.92 MB

Files Updated

xen-device-model-0.10.2.xs-1.4.x86_64.rpm

More Information

For more information, see XenServer Documentation.

If you experience any difficulties, contact Citrix Technical Support.

Related:

  • No Related Posts

Citrix Director Becomes Unresponsive after Submitting the Credentials when IIS X-Frame-Options is enabled

  1. Edit the Citrix Director web.config file:

    <system.serviceModel> <serviceHostingEnvironment multipleSiteBindingsEnabled="true" aspNetCompatibilityEnabled="true" >
  2. Due to Security reasons, if customer enabled IIS X-Frame custom header so, in this case,also need to re-instate the following block of text in the same web.config file as follows:

    <httpProtocol> <customHeader> <add name=”X-Frame-Options" value=”ALLOW-FROM http://localhost/director/default.html" /> ​ </customHeaders></httpProtocol>

    Result:Citrix Director Home page

Note: The preceding two entries are needed only if IIS MultiSiteBinding is enabled AND IIS X-Frame custom header is configured. In a single domain/single site environment, only Step 1 is needed.

In a multi-domain, multi site IIS environment, with X-frame custom header enabled the multipleSiteBindingsEnabled should be set to True.

Caution!

In a single domain, enabling the “multipleSiteBindingsEnabled may cause a “Server Error in ‘/Director’ Application” error when trying to open the Citrix Director Logon page. It is recommended to enable “multipleSiteBindingsEnabled” only in an IIS environment with multiple sites and multi domains.

Related:

  • No Related Posts

Citrix Cloud TLS Version Deprecation

Receiver

Version

Windows

4.2.1000

Mac

12.0

Linux

13.2

Android

3.7

iOS

7.0

Chrome/HTML5

Latest (Browser must support TLS 1.2)

Citrix recommends upgrading to Citrix Workspace app if your version of Receiver is earlier than those listed above. Download here: https://www.citrix.com/products/receiver.html

Retrieving a list of users connecting on older Receiver versions

To retrieve a list of Receivers connecting to your Citrix Cloud environment, log into Citrix Cloud and click the Manage button for the Virtual Apps and Desktops service. The details include user, version, connection date, and endpoint device name.

Virtual Apps and Desktops (Full Edition)

  1. Click Monitor > Trends > Custom Reports > Create Reports.

  2. Select OData Query, provide a report name, and copy/paste the following query (change date range as needed).

  3. Click Save, and then Execute to open the list in Excel.

    Sessions?$filter = StartDate ge datetime’2019-02-01’’ and StartDate le datetime’2019-03-31’&$select = CurrentConnection/ClientVersion,CurrentConnection/ClientName,User/UserName,StartDate&$expand = CurrentConnection,User

Virtual Apps/Desktops Essentials

  1. Click Monitor, and then select a catalog.

  2. Click Export to open the list in Excel.

Citrix Cloud Management

To ensure successful connection to the Citrix Cloud management console (citrix.cloud.com), your browser must support TLS 1.2 (latest version of most web browsers).

Citrix Director

TLS 1.2 connection will be required when using OData APIs. To enforce use of TLS 1.2 on the client machine for clients such as MS Excel, PowerShell, LinqPad, refer to the following KB article: https://support.citrix.com/article/CTX245765

Citrix Cloud Connector

All connections to Citrix Cloud services from Citrix Cloud Connectors will require TLS 1.2. Citrix Provisioning and Machine Creation Services will allow TLS 1.0, 1.1, and TLS 1.2 connections by default (no action required) until later this year when it will change to TLS 1.2 only.

Optional: If your security policy requires strict enforcement of TLS 1.2 connections, the following registry setting changes are required on each Citrix Cloud Connector:

[HKEY_LOCAL_MACHINESOFTWAREWOW6432NodeMicrosoft.NETFrameworkv2.0.50727]
“SystemDefaultTlsVersions”=dword:00000001
“SchUseStrongCrypto”=dword:00000001
[HKEY_LOCAL_MACHINESOFTWAREWOW6432NodeMicrosoft.NETFrameworkv4.0.30319]
“SystemDefaultTlsVersions”=dword:00000001
“SchUseStrongCrypto”=dword:00000001
[HKEY_LOCAL_MACHINESOFTWAREMicrosoft.NETFrameworkv2.0.50727]
“SystemDefaultTlsVersions”=dword:00000001
“SchUseStrongCrypto”=dword:00000001
[HKEY_LOCAL_MACHINESOFTWAREMicrosoft.NETFrameworkv4.0.30319]
“SystemDefaultTlsVersions”=dword:00000001
“SchUseStrongCrypto”=dword:00000001


For more details, refer to the Microsoft article “Transport Layer Security (TLS) best practices with the .NET Framework”, section “SystemDefaultTlsVersions”
https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls#systemdefaulttlsversion

Troubleshooting

Since Citrix Cloud supports only TLS 1.2 and above, all clients accessing any data from Citrix Services with TLS versions 1.0 and 1.1 will see one of the following errors:

Director

Error:

System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. —> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. —> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host

Refer to the following article to configure clients for TLS 1.2 communication:

https://support.citrix.com/article/CTX245765

Receiver

Error:

“Unable to launch your app….Cannot connect to the Citrix XenApp server. SSL Error 4… The server rejected the connection.”

Refer to Upgrading to latest Receiver or Citrix Workspace app above.

Connector

If your Citrix Cloud Connector machine is not able to establish a connection with Citrix Cloud after Mar 15, 2019, check the following registry key to ensure TLS 1.2 is not disabled:

HKLM SYSTEMCurrentControlSetControlSecurityProvidersSCHANNEL

More details:

https://docs.microsoft.com/en-us/windows-server/security/tls/tls-registry-settings

https://docs.microsoft.com/en-us/windows/desktop/secauthn/protocols-in-tls-ssl–schannel-ssp-

Note: Internet Explorer group policy settings also control the values found in SCHANNEL registry key; Internet Explorer > Internet Properties can be used to check enabled/disabled protocols.

Related:

  • No Related Posts