Supported Hypervisors for Virtual Desktops (XenDesktop) and Provisioning Services

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

Citrix is committed to ensuring that our products function with the latest VMware, Microsoft, and Citrix Hypervisors.

Click the following products to view the supported configurations matrix.

XenServer – Provisioning Services XenServer – XenDesktop
vSphere – Provisioning Services vSphere – XenDesktop
SCVMM – Provisioning Services SCVMM – XenDesktop
Nutanix Acropolis – Provisioning Services Nutanix Acropolis – XenDesktop

Note:

  • This matrix indicates supported configurations of Virtual Desktops (XenDesktop) and Provisioning Services with various hypervisor solutions. When Yes is listed for a combination, it means Citrix will provide technical support to assist with any issues encountered. Any known issues and requirements for certain combinations are indicated with notes.
  • XenApp 6.0 and 6.5 are hypervisor agnostic. If XenApp is deployed through Citrix Provisioning Services, refer to the Provisioning Services product support for the hypervisor.
  • This article will be updated periodically as new information becomes available.

What has changed from the last release of the matrix?

  • Added support for vSphere 6.7 update 2.
  • Added support for Citrix Hypervisor (XenServer) 8.0


Citrix Hypervisor (XenServer) – Provisioning Services (PVS)

Supported Hypervisors / XenServer Provisioning Services
1906/1903 1811 7.15 LTSR 7.6 LTSR
Citrix Hypervisor 8.0 Yes No Yes(With CU3 or higher) No
XenServer 7.6 Yes Yes Yes No
XenServer 7.5 No No Yes No
XenServer 7.1 LTSR Yes(CU2 only) Yes(CU2 only) Yes(Up to CU2) Yes(Up to CU2)
XenServer 7.0 No No No Yes

Go back to top

Citrix Hypervisor (XenServer) – Virtual Desktops (XenDesktop)

Supported Hypervisors

/XenServer
Virtual Desktops (XenDesktop)
1906/1903 1811 7.15 LTSR 7.6 LTSR
Citrix Hypervisor 8.0 Yes No Yes(With CU3 or higher) No
XenServer 7.6 Yes Yes Yes No
XenServer 7.5 No No Yes No
XenServer 7.1 LTSR Yes(CU2 only) Yes(CU2 only) Yes(Up to CU2) Yes(Up to CU2)
XenServer 7.0 No No No Yes

Go back to top


vSphere – Provisioning Services (PVS)

Note:

  • Citrix performs compatibility tests only with the major updates of VMware vSphere, like Update 1, 2 and so on. The minor updates like 1a, 1b, 2a and so on are not tested, however they are expected to work fine.
  • Testing of updates for the earlier version of VMware vSphere might be limited, as priority is given to the updates of the current version. When using earlier releases of these products, Citrix recommends validating product updates for proper functionality and interoperability in a test environment first before updating production environments.
Supported Hypervisors / vSphere Provisioning Services
1906/1903/1811 7.15 LTSR 7.6 LTSR
vSphere 6.7 (Up to update 2) Supported. Refer to CTX235513

for more details
(CU3 or higher) No
vSphere 6.5

(Up to update 2)
Supported.

Refer to CTX219808

for more details
Supported.

Refer to CTX219808
Supported.

Refer to CTX219808
vSphere 6

(Up to update 3)
Supported.

Refer to CTX200969

for more details
Supported.

Refer to CTX200969

for more details
Supported.

Refer to CTX200969

for more details
vSphere 5.5

(Up to update 3)
Supported.

Refer to CTX140135

for more details
Supported.

Refer to CTX140135

for more details
Supported.

Refer to CTX140135

for more details

Go back to top

vSphere – Virtual Desktops (XenDesktop)

Supported Hypervisors

/vSphere
Virtual Desktops (XenDesktop)
1906/1903/1811 7.15 LTSR 7.6 LTSR
vSphere 6.7 (Up to Update 2) Supported. Refer to CTX235513

for more details
CU3 or higher No
vSphere 6.5 (Up to update 2) Supported.Refer to CTX219808

for more details
Supported.Refer to CTX219808

for more details
Supported.Refer to CTX219808

for more details
vSphere 6 (Up to update 3) Supported.Refer to CTX200969

for more details
Supported.Refer to CTX200969

for more details
Supported.Refer to CTX200969

for more details
vSphere 5.5 (Up to update 3) Supported.Refer to CTX140135 for more details Supported.Refer to CTX140135for more details Supported.Refer to CTX140135for more details

Go back to top

SCVMM – Provisioning Services (PVS)

Supported Hypervisors / SCVMM Provisioning Services
1906/1903/1811 7.15 LTSR 7.6 LTSR
SCVMM 2016 Yes Yes No
SCVMM 2012 R2 Yes Yes Yes
SCVMM 2012 SP1 Yes Yes Yes
SCVMM 2012 Yes Yes Yes

Go back to top

SCVMM – Virtual Desktops (XenDesktop)

Supported Hypervisors / SCVMM Virtual Desktops (XenDesktop)
1906/1903/1811 7.15 LTSR 7.6 LTSR
SCVMM 2016 Yes Yes No
SCVMM 2012 R2 Yes Yes Yes
SCVMM 2012 SP1 Yes Yes Yes
SCVMM 2012 Yes Yes Yes

Go back to top

Nutanix Acropolis – Provisioning Services (PVS)

Supported Hypervisors / Nutanix Acropolis Provisioning Services
1906/1903/1811 7.15 LTSR 7.6 LTSR
Acropolis Operating System (AOS) 5.5 or later Yes Yes No

Go back to top

Nutanix Acropolis – Virtual Desktops (XenDesktop)

Supported Hypervisors / Nutanix Acropolis XenDesktop
1906/1903/1811 7.15 LTSR 7.6 LTSR
Acropolis Operating System (AOS) 4.6.1.x or later Supported. Refer to CTX202032

for more details.
Supported. Refer to CTX202032

for more details.
Supported. Refer to CTX202032

for more details.

Go back to top

Additional Resources

Related:

  • No Related Posts

Microsoft Windows Security Updates June 2019 overview

Microsoft released security updates for all supported versions of the Microsoft Windows operating system on the June 11, 2019 Patch Day.

Our overview of the June 2019 Patch Tuesday provides with you information about security and non-security updates that Microsoft released on this day.

The overview includes an executive summary, statistics, links to all updates, the list of known issues sorted by operating system, download links, and more.

Microsoft released the May 2019 Update for Windows 10 recently but it is available to users who seek for updates manually only at the time and only if the system is compatible.

You can check out the May 2019 Update overview here in case you missed it.

Microsoft Windows Security Updates June 2019

The following Excel spreadsheet lists security update information for June 2019. Click on the following link to download it to your system: Microsoft Windows Security Updates June 2019 Overview

Executive Summary

  • Microsoft released security updates for all supported versions of the Windows operating system in June 2019.
  • All client and server versions have critically rated vulnerabilities patched.
  • Microsoft released security updates for other products such as Internet Explorer, Microsoft Edge, Microsoft Office, Azure, Microsoft Exchange Server, and Skype.

Operating System Distribution

  • Windows 7: 42 vulnerabilities of which 3 are rated critical and 39 are rated important
    • CVE-2019-0722 | Windows Hyper-V Remote Code Execution Vulnerability
    • CVE-2019-0888 | ActiveX Data Objects (ADO) Remote Code Execution Vulnerability
    • CVE-2019-0985 | Microsoft Speech API Remote Code Execution Vulnerability
  • Windows 8.1: 35 vulnerabilities of which 3 are rated critical and 32 are rated important
    • same as 1903
  • Windows 10 version 1703: 41 vulnerabilities of which 4 is critical and 37 are important
    • same as 1709
  • Windows 10 version 1709: 43 vulnerabilities of which 4 is critical and 39 are important
    • CVE-2019-0709 | Windows Hyper-V Remote Code Execution Vulnerability
    • same as 1903
  • Windows 10 version 1803: 45 vulnerabilities of which 3 are critical and 43 are important
    • same as 1903
  • Windows 10 version 1809: 47 vulnerabilities of which 3 are critical and 44 are important
    • same as 1903
  • Windows 10 version 1903: 42 vulnerabilities of which 3 are critical and 39 are important.
    • CVE-2019-0620 | Windows Hyper-V Remote Code Execution Vulnerability
    • CVE-2019-0722 | Windows Hyper-V Remote Code Execution Vulnerability
    • CVE-2019-0888 | ActiveX Data Objects (ADO) Remote Code Execution Vulnerability

Windows Server products

  • Windows Server 2008 R2: 42 vulnerabilities: 3 are critical and 39 are important.
    • CVE-2019-0722 | Windows Hyper-V Remote Code Execution Vulnerability
    • CVE-2019-0888 | ActiveX Data Objects (ADO) Remote Code Execution Vulnerability
    • CVE-2019-0985 | Microsoft Speech API Remote Code Execution Vulnerability
  • Windows Server 2012 R2: 34 vulnerabilities: 3 are critical and 31 are important.
    • Same as Server 2019
  • Windows Server 2016: 39 vulnerabilities: 4 are critical and 35 are important
    • CVE-2019-0709 | Windows Hyper-V Remote Code Execution Vulnerability
    • Same as Server 2019
  • Windows Server 2019: 47 vulnerabilities: 3 are critical and 44 are important.
    • CVE-2019-0620 | Windows Hyper-V Remote Code Execution Vulnerability
    • CVE-2019-0722 | Windows Hyper-V Remote Code Execution Vulnerability
    • CVE-2019-0888 | ActiveX Data Objects (ADO) Remote Code Execution Vulnerability

Other Microsoft Products

  • Internet Explorer 11: 7 vulnerability, 5 critical, 2 important
    • CVE-2019-1080 | Scripting Engine Memory Corruption Vulnerability
    • CVE-2019-1055 | Scripting Engine Memory Corruption Vulnerability
    • CVE-2019-1038 | Microsoft Browser Memory Corruption Vulnerability
    • CVE-2019-0988 | Scripting Engine Memory Corruption Vulnerability
    • CVE-2019-0920 | Scripting Engine Memory Corruption Vulnerability
  • Microsoft Edge: 14 vulnerabilities, 12 critical, 2 important
    • CVE-2019-0989 | Chakra Scripting Engine Memory Corruption Vulnerability
    • CVE-2019-0990 | Scripting Engine Information Disclosure Vulnerability
    • CVE-2019-0991 | Chakra Scripting Engine Memory Corruption Vulnerability
    • CVE-2019-0992 | Chakra Scripting Engine Memory Corruption Vulnerability
    • CVE-2019-0993 | Chakra Scripting Engine Memory Corruption Vulnerability
    • CVE-2019-1002 | Chakra Scripting Engine Memory Corruption Vulnerability
    • CVE-2019-1003 | Chakra Scripting Engine Memory Corruption Vulnerability
    • CVE-2019-1023 | Scripting Engine Information Disclosure Vulnerability
    • CVE-2019-1024 | Chakra Scripting Engine Memory Corruption Vulnerability
    • CVE-2019-1038 | Microsoft Browser Memory Corruption Vulnerability
    • CVE-2019-1051 | Chakra Scripting Engine Memory Corruption Vulnerability
    • CVE-2019-1052 | Chakra Scripting Engine Memory Corruption Vulnerability

Windows Security Updates

Windows 7 SP1 and Server 2008 R2

KB4503292 — Monthly Rollup

  • Fixed a HTTP and HTTPS string character limit issue in Internet Explorer.
  • Security updates

KB4503269 — Security-only Update

  • Security updates only

Windows 8.1 and Server 2012 R2

KB4503276 — Monthly Rollup

  • Patched a security vulnerability by “intentionally preventing connections between Windows and Bluetooth devices that are not secure and use well-known keys to encrypt connections”.
  • Fixed the Preboot Execution Environment known issue.
  • Fixed a HTTP and HTTPS string character limit issue in Internet Explorer.
  • Security updates.

KB4503290 — Security-only Rollup

  • Same as KB4503276 with the exception of the IE string character limit issue.

Windows 10 version Windows 10 version 1709

KB4503284

  • Fixed Bluetooth vulnerability.
  • Fixed an IE11 issue that could prevent IE from opening if no or a malformed search provider was set as the default.
  • security updates

Windows 10 version 1803

  • Fixed the Preboot Execution Environment issue.
  • Same as 1709

Windows 10 version 1809

  • Fixed a Windows Mixed Reality keyboard rendering issue.
  • Fixed a Bluetooth vulnerability.
  • Fixed the Preboot environment issue.
  • Updated Broadcom Wi-Fi firmware to Microsoft HoloLens.
  • Fixed the IE11 default search provider issue.
  • Security updates

Windows 10 version 1903

  • Fixed Bluetooth vulnerability.
  • Security updates.

Other security updates

KB4503259 — Cumulative security update for Internet Explorer: June 11, 2019

KB4474419 — SHA-2 code signing support update for Windows Server 2008 R2, Windows 7, and Windows Server 2008: March 12, 2019

KB4503285 — Security Monthly Quality Rollup for Windows Embedded 8 Standard and Windows Server 2012

KB4503287 — Security Only Quality Update for Windows Server 2008

KB4503308 — Security update for Adobe Flash Player

KB4503267 — Cumulative Update for Windows 10 Version 1607 and Windows Server Version 1607

KB4503291 — Cumulative Update for Windows 10 Version 1507

KB4503537 — Servicing Stack Update for Windows 10 Version 1607, and Windows Server 2016

KB4504369 — Servicing Stack Update for Windows 10 Version 1809, and Windows Server 2019

Known Issues

Windows 7 SP1 and Server 2008 R2

  1. Issue with McAfee Enterprise products that may cause the system to have slow startups or become unresponsive.
  2. Internet Explorer 11 may stop working when “loading or interacting with Power BI reports”.
    • Workaround: republish with Markers turned off.

Windows 8.1 and Server 2012 R2

  1. Same as Windows 7 SP1 and Server 2008 R2
  2. Certain operations on Cluster Shared Volumes still fail. Workaround is still valid.

Windows 10 version 1709, 1803

  1. Certain operations on Cluster Shared Volumes still fail. Workaround is still valid.

Windows 10 version 1809

  1. Certain operations on Cluster Shared Volumes still fail. Workaround is still valid.
  2. A printing issue in Microsoft Edge and other UWP apps that throws “Your printer has experienced an unexpected configuration problem. 0x80070007e.” errors.
    • Workaround: use another browser to print.
  3. Error “0x800f0982 – PSFX_E_MATCHING_COMPONENT_NOT_FOUND”after installing KB4493509 on devices with certain Asian languages.

Windows 10 version 1903

  1. Windows Sandbox may fail to start with ERROR_FILE_NOT_FOUND (0x80070002)

Security advisories and updates

ADV190015 | June 2019 Adobe Flash Security Update

ADV190016 | Bluetooth Low Energy Advisory

ADV990001 | Latest Servicing Stack Updates

Non-security related updates

KB4497935 for Windows 10 version 1903 and Windows Server 1903

KB4497934 for Windows 10 version 1809 and Windows Server 2019

KB4505056 for Windows 10 version 1809 and Windows Server 2019

KB4499183 for Windows 10 version 1803

KB4505064 for Windows 10 version 1803

KB4499147 for Windows 10 version 1709

KB4505062 for Windows 10 version 1709

KB4499162 for Windows 10 version 1703

KB4505055 for Windows 10 version 1703

KB4499177 for Windows 10 version 1607 and Windows Server 2016

KB4505052 for Windows 10 version 1607 and Windows Server 2016

KB4503539 — Dynamic Update for Windows 10 Version 1803

KB4494454 — Update for Windows 10

KB4501226 — Update for POSReady 2009

KB890830 — Windows Malicious Software Removal Tool – June 2019

Microsoft Office Updates

You find Office update information here.

How to download and install the June 2019 security updates

windows security updates june 2019

All Windows client systems are configured to download and install security updates automatically shortly after release. It is possible to run manual checks for updates to install these as early as possible.

We suggest that backups are created before any updates are installed as updates may introduce issues of their own or in worst case, break the system.

You can run a manual check for updates in the following way:

  1. Tap on the Windows-key, type Windows Update, and select the result.
  2. A click on “check for updates” runs a manual check. Updates may be installed automatically or on user request depending on system settings.

Direct update downloads

Windows 7 SP1 and Windows Server 2008 R2 SP

  • KB4503292 — 2019-06 Security Monthly Quality Rollup for Windows 7
  • KB4503269 — 2019-06 Security Only Quality Update for Windows 7

Windows 8.1 and Windows Server 2012 R2

  • KB4503276 — 2019-06 Security Monthly Quality Rollup for Windows 8.1
  • KB4503290 — 2019-06 Security Only Quality Update for Windows 8.1

Windows 10 (version 1709)

  • KB4503279 — 2019-06 Cumulative Update for Windows 10 Version 1709

Windows 10 (version 1803)

  • KB4503286 — 2019-06 Cumulative Update for Windows 10 Version 1803

Windows 10 (version 1809)

  • KB4503327 — 2019-06 Cumulative Update for Windows 10 Version 1809

Windows 10 (version 1903)

  • KB4503293 — 2019-06 Cumulative Update for Windows 10 Version 1903

Additional resources

Summary
Article Name
Microsoft Windows Security Updates June 2019 overview
Description
Detailed overview of the Microsoft June 2019 Patch Day covering Windows security and non-security updates, advisories, known issues, and more.
Author
Martin Brinkmann
Publisher
Ghacks Technology News
Logo
Ghacks Technology News
Advertisement

Related:

  • No Related Posts

Starting March 1, 2019, Bay Area Systems Will Begin Providing It Support Services on the Latest …

SAN FRANCISCO (PRWEB)February 23, 2019

Bay Area Systems, Inc. (http://www.BayAreaSystems.com), premier Information Technology (IT) consulting provider in San Francisco Bay Area, is on the forefront of providing cost-effective IT outsourcing solutions for small businesses.

Starting March 1, 2019, Bay Area Systems will begin providing IT support services on the latest Microsoft Server: Windows Server 2019. Through utilization of Microsoft Windows Server 2019’s native Hyper-V virtualization technology, Bay Area Systems helped deployed web server farms, clustered database servers, remote desktop workstations, and cloud computing platforms. When businesses need Virtual Private Network (VPN) access and remote desktop services; rather than adding individual workstations to be used for remote office desktop connection needs, virtual workstations offer the same experience with greater efficiency. Clients praise our virtual machine solutions that are space saving (often one server can serve the needs of 10 – 30 servers and/or workstations, reducing the need to have these physical machines scattered around in the office); energy saving in terms of electricity needs as well as cooling requirements; easy deployment – adding a server or workstation is much faster than having to order an additional machine, and often may not be of the same exact specification; fast recovery – by utilizing the cloning feature, essential virtual machines can be cloned and quickly replaced should a catastrophic software error occurred.

Microsoft Windows Server 2019’s Server Core App Compatibility feature on demand (FOD) significantly improves the app compatibility of the Windows Server Core installation option by including a subset of binaries and components from Windows Server with the Desktop Experience, without adding the Windows Server Desktop Experience graphical environment itself.

Windows Defender ATP Exploit Guard is a new set of host-intrusion prevention capabilities. The four components of Windows Defender Exploit Guard (Attack Surface Reduction (ASR), Network protection, Controlled folder access, Exploit protection) are designed to lock down the device against a wide variety of attack vectors and block behaviors commonly used in malware attacks, while enabling you to balance security risk and productivity requirements.

Microsoft Windows Server 2019’s Security with Software Defined Networking (SDN) delivers many features to increase cutstomer confidence in running workloads, either on-premises, or as a service provider in the cloud.

Windows Server 2019 also has a new Storage Migration Service that makes it easier to migrate servers to a newer version of Windows Server. It provides a graphical tool that inventories data on servers, transfers the data and configuration to newer servers, and then optionally moves the identities of the old servers to the new servers so that apps and users don’t have to change anything.

Hyper-V virtual server provides one of the most stable platforms for virtual machines, and the multitude of tools available making cloning, clustering and failover available to support critical business needs. The time it takes to restore a cloned Microsoft Exchange Server in Hyper-V could be as little as 2 hours, compared to having to rebuild a physical server, reinstall Operating Systems and Exchange Server, setup accounts, and can easily take 6 to 8 hours and thousands of dollars. In Windows Server 2019, you can now add NIC on the fly without taking down the server.

Bay Area Systems have fully tested and deployed Hyper-V solutions to solve customers’ growing needs of testing new Operating Systems as well as program upgrades. It is much more convenient, and cost-effective, to use a virtual machine to test system integration, software upgrades, patches, and new installations before deploying into the production environment. Efficient resource sharing and distribution in Hyper-V also ensure a much better performance for individual virtual machines than purchasing separate physical units.

The combination of cutting-edge, professional services of Bay Area Systems and production proven virtual machine solutions provided by Microsoft’s Windows Server 2019 will serve to deliver energy saving, cost-effective, cutting-edge, fast and complete services to Bay Area Systems customers.

Since 2002,Bay Area Systems has provided cost-effective computer systems and network support and services to small businesses all around the San Francisco Bay Area. Bay Area Systems LLC has become a pioneer in providing customized technology solutions that are efficient, cost-effective, and improve bottom line of small businesses. Bay Area Systems’ business model is based on their passion to provide the best customer service experience in the industry, and building long-term business relationship with their customers.

Related:

  • No Related Posts

How to deploy dedicated Ubuntu VDA through MCS

Step 1: Create Ubuntu 16.04 VM on Hypervisor such as VMware vSphere or Citrix XenServer

Step 2: Install Hypervisor tools

Step 3: Install Linux VDA

sudo dpkg -i <PATH>/<Linux VDA deb>

sudo apt-get install -f

Step 4: Set up the runtime environment to complete installation

sudo /opt/Citrix/VDA/sbin/ctxinstall.sh

Step 5: Configure mcs.conf

Change variables in /var/xdl/mcs/mcs.conf. The mcs.conf configuration file contains variables for setting MCS and the Linux VDA. The following are variables you can set as required:

dns: Sets the DNS IP address.

AD_INTEGRATION: Sets Winbind or SSSD (SSSD is not supported on SUSE).

WORKGROUP: Sets the workgroup name (case-sensitive) if it is configured in AD.

For dedicated single session VDA, set VDI_MODE=Y

Step 6: Shutdown VM and take snapshot.

Related:

  • No Related Posts

XenServer 7.1 Cumulative Update 2

Who Should Install This Cumulative Update?

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.

Information About this Cumulative Update

Component Details
Prerequisite
  • XenServer 7.1 CU1.

  • Licensed customer with Customer Success Service

Post-update tasks Restart Host
Content live patchable* No
Revision History Published on December 12, 2018
* Available to Enterprise Customers.

Included in this Cumulative Update

This cumulative update includes the following previously released hotfixes.

This cumulative update also includes additional fixes. For a list of the issues resolved by XenServer 7.1 CU2, see the Citrix XenServer 7.1 Cumulative Update 2 Release Notes.

Installing the Cumulative Update

Customers should use either XenCenter or the XenServer Command Line Interface (CLI) to apply this cumulative update. When the installation is complete, see the Post-update tasks in the table Information About this Cumulative Update 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 cumulative update update package only. Click the following link to download the source code for any modified open source components XS71ECU2-sources.iso. The source code is not necessary for cumulative update installation: it is provided to fulfill licensing obligations.

Installing the Cumulative Update by using XenCenter

Before installing this cumulative update, it is recommended that you update your version of XenCenter to the latest available version for XenServer 7.1 CU 2.

Choose an Installation Mechanism

There are three mechanisms to install a cumulative update:

  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 cumulative update using the Automated Updates feature, seeApply Automated Updates.

For information about installing a cumulative update using the Download update from Citrix option, see Apply an updates to a pool.

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

  1. Download the cumulative update to a known location on a computer that has XenCenter installed.
  2. Unzip the cumulative update 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 XS71ECU2.iso and then click Open.
  6. Click Next.
  7. Select the pool or hosts you wish to apply the cumulative update 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. In addition, the Install Update wizard checks whether a live patch (this is an Enterprise Edition feature) is available for the cumulative update and if the live patch can be successfully applied to the hosts.

    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. If the update contains a live patch that can be successfully applied to the hosts, it displays No action required on the Tasks to be performed screen.
  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 Cumulative Update by using the xe Command Line Interface

  1. Download the cumulative update 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>XS71ECU2.iso

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

    1dbfd41c-a53d-41e7-aa64-a8f39e0baac8

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

    xe update-pool-apply uuid=<UUID_of_file>

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

    xe upload-apply host-uuid=<UUID_of_host> uuid=<UUID_of_file>

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

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

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

  6. If the cumulative update is applied successfully, carry out any specified post-update task on each host, starting with the master.

Files

Hotfix File

Component Details
Hotfix Filename XS71ECU2.iso
Hotfix File sha256 64b9d387cfc79fb97245a2425babaa4f46ccf9edf4730cde18fea7fe954a0f42
Hotfix Source Filename XS71ECU2-sources.iso
Hotfix Source File sha256 e46f7d3fb31b8e4bafcd5a49c06ce7b0d55f486489efd618514452aafb6c4305
Hotfix Zip Filename XS71ECU2.zip
Hotfix Zip File sha256 7cb0130b2ac64e4c5c7ccbe57ea232ff1224888b0a4848d20d8ca0674614ba08
Size of the Zip file 277.16 MB

Files Updated

biosdevname-0.3.10-3.x86_64.rpm
blktap-3.5.0-xs.1+1.0_71.1.2.x86_64.rpm
broadcom-bnxt-en-1.5.5.p1-1.x86_64.rpm
busybox-1.22.1-2.x86_64.rpm
ca-certificates-2015.2.6-73.el7.noarch.rpm
citrix-crypto-module-1.0.2n-11.x86_64.rpm
dracut-033-360.el7.centos.xs13.x86_64.rpm
dracut-network-033-360.el7.centos.xs13.x86_64.rpm
ethtool-4.5-3.el7.x86_64.rpm
forkexecd-1.1.2-2.el7.centos.x86_64.rpm
glibc-2.17-106.el7_2.4.x86_64.rpm
glibc-common-2.17-106.el7_2.4.x86_64.rpm
gpumon-0.4.0-3.el7.centos.x86_64.rpm
guest-templates-json-1.1.4-1.noarch.rpm
guest-templates-json-data-linux-1.1.4-1.noarch.rpm
guest-templates-json-data-other-1.1.4-1.noarch.rpm
guest-templates-json-data-windows-1.1.4-1.noarch.rpm
guest-templates-json-data-xenapp-1.1.4-1.noarch.rpm
host-upgrade-plugin-1.1.3.1-1.x86_64.rpm
intel-e1000e-3.4.0.2-1.x86_64.rpm
kernel-4.4.27-600.1.12.x86_64.rpm
kexec-tools-2.0.4-32.x86_64.rpm
kpatch-0.3.2-4.x86_64.rpm
kpatch-4.4.0+2-modules-0.3.2-4.x86_64.rpm
kpatch-modules-0.3.2-4.x86_64.rpm
linux-guest-loader-2.0.2-1.noarch.rpm
linux-firmware-20170622-3.2.noarch.rpm
linux-guest-loader-data-2.0.2-1.noarch.rpm
message-switch-1.4.1-2.el7.centos.x86_64.rpm
microcode_ctl-2.1-26.xs1.x86_64.rpm
ocaml-xenops-tools-1.0.1-5.el7.centos.x86_64.rpm
openssl-1.0.2k-8.el7.x86_64.rpm
openssl-libs-1.0.2k-8.el7.x86_64.rpm
openssl-perl-1.0.2k-8.el7.x86_64.rpm
openvswitch-2.3.2-24.1.3.1.x86_64.rpm
pbis-open-8.2.2-1.7.2.x86_64.rpm
pbis-open-upgrade-8.2.2-4.x86_64.rpm
qlogic-fastlinq-8.10.11.0.p1-1.x86_64.rpm
rrd2csv-1.0.2-3.el7.centos.x86_64.rpm
rrdd-plugins-1.0.4-4.el7.centos.x86_64.rpm
security-tools-1.0.1-1.x86_64.rpm
sm-1.17.0-xs.2+1.0_71.1.6.x86_64.rpm
sm-cli-0.9.8-2.el7.centos.x86_64.rpm
sm-rawhba-1.17.0-xs.2+1.0_71.1.6.x86_64.rpm
squeezed-0.13.2-2.el7.centos.x86_64.rpm
stunnel_xs-4.56-6.el7.centos.xs4.x86_64.rpm
tzdata-2018c-1.el7.noarch.rpm
v6d-citrix-10.0.9-1.el7.centos.x86_64.rpm
vendor-drivers-1.0.0-1.x86_64.rpm
vendor-update-keys-1.3.6-2.noarch.rpm
vgpu-7.1.0.1-1.x86_64.rpm
vhd-tool-0.11.4-2.el7.centos.x86_64.rpm
xapi-storage-0.9.0-3.el7.centos.x86_64.rpm
xapi-core-1.14.45-2.x86_64.rpm
xapi-storage-script-0.13.0-2.el7.centos.x86_64.rpm
xapi-tests-1.14.45-2.x86_64.rpm
xapi-xe-1.14.45-2.x86_64.rpm
xcp-networkd-0.13.6-2.el7.centos.x86_64.rpm
xcp-python-libs-2.0.5-2.noarch.rpm
xcp-rrdd-1.2.0-4.el7.centos.x86_64.rpm
xencenter-7.1.3.6923-1.noarch.rpm
xenopsd-0.17.12-2.el7.centos.x86_64.rpm
xenopsd-xc-0.17.12-2.el7.centos.x86_64.rpm
xenopsd-xenlight-0.17.12-2.el7.centos.x86_64.rpm
xenops-cli-1.0.2-3.el7.centos.x86_64.rpm
xenserver-docs-7.1.0-17.noarch.rpm
xenserver-firstboot-1.0.1.3-1.noarch.rpm
xenserver-pv-tools-7.2.101-1.noarch.rpm
xenserver-release-7.1.2-2.x86_64.rpm
xenserver-release-config-7.1.2-2.x86_64.rpm
xen-dom0-libs-4.7.6-1.26.x86_64.rpm
xen-device-model-0.10.2.xs-1.3.x86_64.rpm
xen-dom0-tools-4.7.6-1.26.x86_64.rpm
xen-hypervisor-4.7.6-1.26.x86_64.rpm
xen-libs-4.7.6-1.26.x86_64.rpm
xen-tools-4.7.6-1.26.x86_64.rpm
xsconsole-10.0.1-1.x86_64.rpm
xs-obsolete-packages-1-1.noarch.rpm

More Information

For more information, see the XenServer 7.1 Documentation.

If you experience any difficulties, contact Citrix Technical Support.

Related:

  • No Related Posts

Upgrading OE on Unity that is configured for file services only

it depends what you understand as “disrupt connectivity”

a reboot – no matter how fast – will always be kind of disruptive on the lower levels

and a client will have to at least re-establish the TCP connection

The question is more how much of that is visible to the client OS and application

NFS clients using default hard mounts will just see a pause in I/O but no error to applications

The OS and protocol stack will of course re-establish the connection, recover locks, ….

for CIFS clients it depends on the application and OS

Windows itself will automatically reconnect

cluster aware application that retry internally should be ok

simple applications like copying files via explorer.exe can stop and show a “Try again” dialog

For those application that really require transparent failover – like SharePoint or Hyper-V over SMB shares you can enable SMB CA (Continuous Availability) per share

then they will also just pause and resume I/O similar to NFS

See the NAS white paper and Microsoft details about CA in SMB3

Why dont you just try it ??

all an upgrade is doing is a SP reboot – which you can easily do even from the GUI

If you dont want to use your hardware Unity as VSA will show the same behaviour

Related:

  • No Related Posts

FAQ: Personal vDisk in XenDesktop

Q: Can multiple PvDs be associated to a device/user?

A: There can only be one PvD per Virtual Machine. The PvD is assigned to a Virtual Machine when building the catalog of desktops. The pool type for a PvD catalog is a pooled static, which the desktop is assigned to the user on first use.

Q: Is the PvD a 1-1 mapping per user?

A: Actually, it is a 1:1 mapping to a Virtual Machine in a catalog, which is then assigned to the user on first use. A PvD is attached to a Virtual Machine assigned to the user. The administrator can move a PvD to a new virtual machine in a recovery situation.

Q: If you create a catalog for pooled with PvD, it does not mean that the user is always required to be assigned to that Virtual Machine defeating one of the benefits of a pooled?

A: The base image is still shared and updated across the pool. However, once the user makes an initial connection to a Virtual Machine, the Virtual Machine is kept assigned to the user.

Note: You must connect early in the starting stage long before you know who the user is in order to maximize the application compatibility for services, devices etc.

Q: How does the pooled with personal vDisk catalog affect idle pool?

A: After the user connects, this user is kept assigned to the Virtual Machine.

You must connect early in the starting stage long before you know who the user is in order to maximize the application compatibility for services, devices etc. So for hypervisor resource management, instead of idle pool management, you would use power management to handle Virtual Machine idle workloads.

Q: What Operating Systems are supported for PvD?

A: Windows 7 x86, Windows 7 x64, and Windows 10 up to v1607.

Q: Does Citrix 7.15 LTSR support Windows 10 1703 Semi-Annual Servicing Channel (SAC)?

A: Yes, XenApp and XenDesktop 7.15 LTSR supports Windows 10 1703 SAC. Reference Citrix product documentation for more information.

Q: Is PvD only for Desktop Operating Systems or will it also work with Server Operating Systems?

A: It is only supported on Desktop Operating Systems.

Design and Deploy

Q: What kinds of risks are there for BSODs with PvDs?

A: PvD is architected to be compatible with a wide range of Windows software, including software that loads the drivers. However, drivers that load in phase 0 or software that alters the networking stack of the machine (through the installation of additional miniports or intermediate or protocol drivers) might cause PvD to not operate as expected. You must install these types of software in the base Virtual Machine image.

Related: