Error “cannot connect to the hypervisor at object reference not set to an instance of an object” when running the XDSW

When running the XenDesktop Setup Wizard, it can fail with the following error:

“cannot connect to the hypervisor at <ADDRESS> object reference not set to an instance of an object”

The string <ADDRESS> will contain the actual URL of the vCenter Server.

This issue can appear when the DataCenter name on the VMWare side has a comma character anywhere in the name.

For example notice the use of the comma character in the following screenshot:

User-added image


  • No Related Posts

Recommended Hotfixes for XenApp 7.x

The following Citrix and Microsoft hotfixes are found to resolve the most common issues with XenApp/XenDesktop 7.6, and XenApp/XenDesktop 7.5 running on a Windows Server 2008 R2 or a Windows Server 2012 R2 platform. These hotfixes focus on basic functionality and stability.

Note :

1. Fixes for Current Releases will likely be released in the next Current Release; therefore, it is less likely that an individual fix would be released for a Current Release version. You may be asked to upgrade to the next version of a Current Release that includes the requested fix and new functionality.

2. This article aims to describe the recommended hotfixes before Citrix LTSR(7.6.300) and Citrix CR(7.7~7.14). Please go to for more hotfixes regarding LTSR and CR.

Issue: Attempts to restart the Citrix Device Redirector Service from within a VDA or RDP session can cause the service to remain in an unresponsive state rather than actually restarting.

Available Software Updates:

ICAWS760WX64047 – For VDA Core Services 7.6 for Windows Desktop OS (64-bit) – English
ICAWS760WX86047 – For VDA Core Services 7.6 for Windows Desktop OS (32-bit) – English
ICATS760WX64053 – For VDA Core Services 7.6 for Windows Server OS (64-bit) – English


  • The operating system experiences an error on picadm.sys and a blue screen appears with stop code 0x20.
  • A deadlock on picadm.sys can cause published applications to become unresponsive.
  • The operating system experiences an error on picadm.sys and a blue screen appears with stop code 0x50.
  • The VDA might become unresponsive at the “Welcome” screen due to a deadlock on picadm.sys.
  • Remote Desktop (RDP) connections to the server fail.

Available Software Update:

ICATS760WX64048 – For VDA Core Services 7.6 for Windows Server OS (64-bit) – English


Issue: Certain third-party published applications might fail to start on XenApp servers. As a result, the wfshell.exe process might close unexpectedly. When this error occurs, no indication that the session is starting or error messages appear on the user device.

Available Software Updates:

ICAWS760WX64042 – For VDA Core Services 7.6 for Windows Desktop OS (64-bit)-English
ICAWS760WX86042 – For VDA Core Services 7.6 for Windows Desktop OS (32-bit) – English
ICATS760WX64040 – For VDA Core Services 7.6 for Windows Server OS (64-bit) – English


Issue: Citrix XenApp 7.6 and XenDesktop 7.6 VDA Core Services running on Windows Server 2008 R2 (Server OS) might become unresponsive at the “Welcome” screen. If this occurs, new Receiver and Remote Desktop (RDP) connections to the server fail.

Available Software Updates:

ICAWS760WX64026 – For VDA Core Services 7.6 for Windows Desktop OS (64-bit) – English
ICAWS760WX86026 – For VDA Core Services 7.6 for Windows Desktop OS (32-bit) – English
ICATS760WX64032 – For VDA Core Services 7.6 for Windows Server OS (64-bit) – English


Issue: The Citrix Stack Control service quits unexpectedly if there is an invalid session key.

Available Software Update:

ICATS760WX64006 – For VDA Core Services 7.6 for Windows Server OS (64-bit) – English

XenApp 7.5/ 7.1


  • The memory consumption of the Monitoring Service can grow steadily until the service stops responding to requests from Director, eventually rendering Director unresponsive as well.
  • If the resource name (display name) changes on the Delivery Controller, users who previously subscribed to the applications cannot start the applications.
  • If you create virtual machines (VM) with Desktop Studio that uses Machine Creation Services and the VMs are hosted on a VMware hypervisor, attempts to update VMs that are part of the machine catalog fail.

Available Software Updates:

Update 3 – For Citrix XenDesktop 7.1 Delivery Controller x64 – English
Update 3 – For Citrix XenDesktop 7.1 Delivery Controller x86 – English



  • VDAs can becomes stuck in the “initializing” state of registration process. The issue occurs after the Citrix Desktop Service is running for several days without being restarted.
  • When the function “CName” is enabled, VDA registration can take excessively long.

Available Software Updates:

BrokerAgent750WX64003 – For Broker Agent 7.1/7.5 for Windows OS (64-bit) – English
BrokerAgent750WX86003 – For Broker Agent 7.1/7.5 for Windows OS (32-bit) – English


Issue: Installing hotfixes for XenApp 7.5, and XenDesktop 7.1 and 7.5 VDA Core Services for Windows Desktop and Server OS released before September 2014 causes the ICA Session performance monitor counter to be removed. This can have an adverse effect on the operation of tools and processes that rely on these counters.

Available Software Updates:

ICAWS750WX64011 – For VDA Core Services 7.1/7.5 for Windows Desktop OS (64-bit) – English
ICAWS750WX86011 – For VDA Core Services 7.1/7.5 for Windows Desktop OS (32-bit) – English
ICATS750WX64011 – For VDA Core Services 7.1/7.5 for Windows Server OS (64-bit) – English


Issue:The Citrix Print Manager Service (CpSvc.exe) process might exit unexpectedly.

Available Software Updates:

ICAWS750WX64019 – For VDA Core Services 7.1/7.5 for Windows Desktop OS (64-bit) – English
ICAWS750WX86019 – For VDA Core Services 7.1/7.5 for Windows Desktop OS (32-bit) – English
ICATS750WX64019 – For VDA Core Services 7.1/7.5 for Windows Server OS (64-bit) – English



  • This fix addresses an intermittent high memory utilization issue of the Broker Service on the Controller.
  • This fix addresses a memory consumption issue of the Monitoring Service.

Available Software Updates:

Update 3 – For Citrix XenDesktop 7.1 Delivery Controller x64 – English
Update 3 – For Citrix XenDesktop 7.1 Delivery Controller x86 – English


Refer to the complete list of all the available HotFixes for

XenApp 7.6 64-bit32-bit

XenApp 7.5 64-bit32-bit

Microsoft HotFixes (including links to Microsoft HotFix list)

Windows Server 2012 R2 contains most of the following hotfixes (exceptions noted inline). Microsoft has published the following KB article specific to Remote Desktop Services: Available Updates for Remote Desktop Services (Terminal Services) in Windows Server 2012 R2. For Microsoft Hotfixes applicable to the Windows Server 2008 R2 and the Windows 7 platforms, see the “Microsoft Hotfixes” section in the following article: CTX129229 – Recommended Hotfixes for XenApp 6.x on Windows Server 2008 R2.

Note: The descriptions of the Microsoft fixes listed in this article (CTX142357) might not match the descriptions in the Microsoft articles for the following Microsoft fixes. This is not an error. The issue description listed by Citrix in the following matrix was resolved by an earlier version of that file however it has been superseded by the article/fix currently listed.

KB Number Issue description
  • UPM driver load breaks if this KB is not applied.
KB3078676 – NEW
  • This article describes an issue in which even 1530 is logged, and user profile service (ProfSvc) leaks paged pool memory and handles in Windows 8.1, Windows RT 8.1, or Windows Server 2012 R2. This issue occurs if the ProfSvc service loads and then unloads a user profile. Additionally, the following event is logged in the Event viewer: Event ID 1530. Description: Windows detects your registry file is still in use by other applications or servers. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. No user action is required.
KB3127673 – NEW
  • The Stop error 0x000000C2 might be caused by an error handling issue in the win32k.sys file.
  • The Stop error 0x0000003B might be caused by a synchronization issue in the dcgkrnl.sys file.
  • The parameters in Stop error messages may vary, depending on the configuration of the computer.
  • Not all “Stop 0x000000C2” errors or “Stop 0x0000003B” errors are caused by one of these issues.
KB3055615 – NEW
  • A windows Server 2012 R2 Server becomes slow and unresponsive if update 2927901 is installed.
  • You have update 2927901 installed on a Windows Server 2012 R2 server.
  • You have users who frequently log in and log off the server through Remote Desktop.
  • Memory leak occurs when you create or delete CSV snapshots by using a VSS hardware provider
  • IIS crashes occasionally when a request is sent to a default document in Windows 8.1 or Windows Server 2012 R2
  • You receive Stop error 0xD1 in Windows Server 2012 R2 or Windows 8
  • Device does not exist error after you reinsert a USB COM port device
  • Remote Desktop session freezes when you run an application in the session in Windows 8.1 or Windows Server 2012 R2.
  • A network printer is deleted unexpectedly in Windows
  • Users who have the remote audio setting enabled cause the RD Session Host servers to freeze intermittently in Windows Server 2012 R2 or Windows Server 2008 R2 SP1
  • You are logged on with a temporary profile to a remote desktop session after an unexpected restart of Windows Server 2012
  • Memory leak occurs in the Dwm.exe process on a Remote Desktop computer that is running Windows 8 or Windows Server 2012
  • Memory leak occurs when you play mp4 files in Windows 8.1 or Windows Server 2012 R2
  • Computer freezes when you switch to another account in Windows 8.1 or Windows Server 2012 R2
  • An NTFS volume is flagged as dirty after each restart, and CHKDSK can find no issues
  • Print jobs are intermittently processed slowly through Windows 8.1-based or Windows Server 2012 R2-based printer servers
  • Network printers that use TCP/IP port cannot print after first document has printed in Windows


  • No Related Posts

Error:”Operation Not Permitted” on NetScaler VPX on Hyper-V while modifying interface

In ns.logs it was observed that other parameters are also getting set while making changes to the inteface Alias from GUI.The parameter which was failing was the set ha monitor ON parameter.



ns.log.0:Sep 15 15:59:04 <> 09/15/2015:20:59:04 GMT NLR-A-NS01 0-PPE-0 : default GUI CMD_EXECUTED 139 0 : User nsroot – Remote_ip – Command “set interface 0/1 -speed AUTO -duplex AUTO -flowControl OFF -autoneg ENABLED -haMonitor ON -mtu 1500 -tagall OFF -state ENABLED -lacpMode DISABLED -lagtype NODE -ifAlias MANAGEMENT -throughput 0 -linkRedundancy OFF -bandwidthHigh 0 -bandwidthNormal 0 -intftype “Hyper v” -ifnum 0/1 -lldpmode NONE -lrsetPriority 1024″ – Status “ERROR: Operation not permitted”

This an expected behaviour as per Issue Id: TSK0312538

When VPX is installed on top of a hypervisor – the interfaces are registered based on what the hypervisors expose.

There will be several parameter given back to VPX when it tries to register – physical link state being one of them.

The way the drivers are written specific to each hypervisor is different – and in case of Hyper-V the physical link state information is not passed through the virtual interface, unlike Xenserver which passes on this information.

As a result since VPX does not have link state information in case of Hyper-V it will flag this information and on execution of the HAMON set command rejects as it does not apply in this scenario.

User-added image


  • No Related Posts

Support statement on storage migration of MCS machines

Background :

Customers using XenDesktop Machine Creation Service (MCS) with VMWare, Xenserver or Hyper-v as hypervisor may want to relocate the desktops to another datastore for various reasons such as datastore running out of space or datastore performance. This article tells why Citrix does not support the datastore migration of VMs.

Reason :

During the MCS catalog creation :

MCS creates a Provisioning scheme which is associated to the HypervisorconectionID and storage ID, the storages which are defined under the hosting unit in the hosting tab on Studio console has those catalog IDs mapped, also all these information gets stored in the database during the creation of the catalog.

So if we go ahead and migrate those VMs and put them on a new storage, first of all DDC do not identify those VMs as our DB has those VMs mapped to other storage IDs and Provisioning IDs.

Even if we create a new host connection, we will not be able to map the existing Provisioning scheme with the new Hypervisor Connection due to limitation of Xendesktop Powershell SDKs.

1. When we create a MCS catalog HypervisorconnectionID and HostingUnitID gets mapped to the MCS catalog or Proviosning Scheme. Examples :

This is our Hypervisor connection which we created using studio under hosting tab :

User-added image

Can retrieve the same information using powershell using the following commands :

PS C:Usersadministrator.ANUJ>asnp Citrix*

PS C:Usersadministrator.ANUJ> cd xdhyp:

PS XDHyp:> cd .connections

PS XDHyp:Connections> ls

User-added image

Same goes to hostingunit :

User-added image

Using powershell :

Run the following commands :

PS C:Usersadministrator.ANUJ>asnp Citrix*

PS C:Usersadministrator.ANUJ> cd xdhyp:

PS XDHyp:> cd .hostingunits

PS XDHyp:Connections> ls

User-added image

2. Now we have to consider the Hypervisorconnection ID and HostingunitID From our example :

HypervisorConnectionName : XDHost

HypervisorConnectionUid : 4fcfdde4-6799-43d8-a7c1-4aec168889ce

HostingUnitName : XDresource

HostingUnitUid : a567b103-d54e-4dc8-9455-a04171c35d68

A. Run Get-ProvScheme to get an output of MCS created catalogs and match the hosting unit name and hostingunit ID :

User-added image

b. Prov scheme or MCS catalog created with that Hosting resource should show the same ID.

3. One more alternate to check the same thing using VMs identity :

PS XDHyp:HostingUnits> Get-ProvVM -VMName “PVD2″(PVD2 is the machine name)

User-added image

Take the output and compare with above IDs.

If the IDs matches, we will get to know the machines are associated to these storages, and there is no way to change these IDs using commands or GUI.

Note : Modifying the DB tables using DB queries are not supported.

Work Around currently available:

  1. If it is a case of MCS Random catalog, we strictly recommend to create a new catalog with the available master image.
  2. If it is a MCS Dedicated catalog , we can remove the machines from the catalog (via Studio, this operation will delete the machine’s entry from the XenDesktop database), leave them in hypervisor and their machine accounts on active directory, we can now use the same machine to create a new catalog (non MCS/PVS) and import those machine in this catalog. (You can also add these machines to an existing non MCS/PVS catalog).
  3. If it is a case of MCS with PVD machines, we can go through backup and restore process as per

Note :

This documentation is only valid for MCS not PVS or any 3rd party technology to add machines into the catalog.


How to update RAM or CPU within MCS Catalog

To change RAM size for a catalog follow these steps.

1. Load Citrix snappin:

asnp citrix*

2. On XenDesktop Controller Server, run the command to validate the name of the catalog and memory size:

Memory size in the example is 2048

Get-ProvScheme “Name of Catalog to Modify RAM”

User-added image
3. Change the RAM size of the catalog by running the command:

Set-ProvScheme -ProvisioningSchemeName MCS-Windows7 -VMMemoryMB 3072

User-added image

Additional Notes:

  1. Before modifying the catalog on Citrix Studio, all the virtual machines running on the hypervisor associated to the catalog has to be manually updated to the new allocated RAM.
  2. Manually update the master image to reflect the new changes.
  3. All new machines created from the catalog will be allocated with the new memory size.


Citrix Hypervisor Hardware Compatibility List Explained

This article provides an understanding of the Citrix Hypervisor Hardware Compatibility List (HCL). This article also contains information about how products get qualified for inclusion in the HCL and what listing in the HCL represents from a support perspective.

Citrix maintains a Hardware Compatibility list for Citrix Hypervisor containing information about which hardware and software components are currently certified and supported for use with Citrix Hypervisor.

Because of the use of industry-standard open source device drivers in Citrix Hypervisor, the actual hardware compatibility for Citrix Hypervisor is broader than what is listed on the HCL. For servers and storage not specifically listed on the HCL, Citrix provides a self-certification test kit and program. The self-certification test kit includes tools and processes to follow for certifying specific servers and storage, and should be completed with the assistance of a Citrix Hypervisor Systems Engineer from Citrix or a Citrix Solution Provider. Completed self-certification test documentation can be e-mailed to Once the submission has been reviewed and accepted by the Citrix Hypervisor HCL team, the hardware is added to the HCL and is eligible for full support.

The Citrix Ready program is used to qualify hardware for inclusion on the Citrix Hypervisor HCL.

Users and vendors are encouraged to submit the configurations of systems on which they have successfully installed Citrix solutions to share the information with the Citrix Ready community verified site.

Verification Test Kits and Forms for Citrix Hypervisor can be downloaded from

The following test kits are available to allow vendors to demonstrate the compatibility of their computer systems with Citrix Hypervisor:

  • Citrix Hypervisor GPU Self-Test Kit

  • Citrix Hypervisor Hardware Test Kit

  • Citrix Hypervisor Storage Hardware Test Kit

  • Citrix Hypervisor hclIntegrated ISV Self-Certification Kit

When the Citrix Ready team has reviewed the submissions, they will consider including the tested hardware on the HCL. For some hardware and software components, Citrix will undertake to qualify the component for inclusion on the HCL.

  • Hardware and software that is included on the HCL and is supported by the hardware vendor is fully supported by Citrix.
  • Hardware and software that is included on the HCL, but is no longer supported by the hardware vendor is not entitled to support from Citrix.
  • Hardware and software not included on the HCL is not entitled to support from Citrix.

If your environment includes hardware that is not entitled to support from Citrix, Citrix might ask you to attempt to reproduce an issue using supported hardware and software. If the issue is found to be related to the unsupported components and that a resolution would require an enhancement to Citrix products that are beyond the scope of a support engagement, Citrix reserves the right to close the support case without providing a resolution.

If during the analysis and troubleshooting of the reported issue, Citrix determines that the issue is related to an issue with a component provided by a third party vendor, Citrix attempts to find a workaround for the issue. If a workaround is not possible, Citrix might ask the customer to open a support incident with the third-party vendor to allow parallel troubleshooting to take place. If in the end, the issue is determined to be only addressable by the third party vendor, and in addition, that vendor refuses to provide any workaround because they do not support interoperability with our technology or because they no longer support the component, then Citrix reserves the right to close the case without providing a resolution.


XenDesktop Setup Wizard Failed to Create Target Devices in Hyper-V SCVMM

XenDesktop Setup Wizard Failed to Create Target Devices in Hyper-V SCVMM


Get the wizard to create VMs in Hyper-V


CDF shows:

SCVMM not returning a job ID

SCVMM has no record of the job

Wizard completes without error, but 1 machine fails

verfiying settings:

-Hyper V – on scvmm – posh execution policy – allow unrestricted – no chg

-create VMs manually from template – ok

-template settings – ok

-legacy nic 1st, synthetic nic 2nd

VMs a re-pooled w/ WC drive on template (on local storage)

VMM console installed on all DDCs


App Layering – How to deploy Microsoft SCCM in a layer

SCCM is best deployed in the platform layer. It is best to install the client as one of the last components on the platform layer to ensure that the client is sealed correctly before attempting to finalize the layer. Sealing a layer is the process of completing all outstanding processes, for example NGEN processes.

Note: Deploying the SCCM client in the OS layer is not recommended, because it requires handling the agent startup on the packaging machine whenever you create or update a layer.

Deploy SCCM in a platform layer

To deploy SCCM in a layer:

1.In the App Layering management console, select the Layers tab and the Platform Layers subtab.

2.Click Create Platform Layer and complete the Create Platform Layer wizard using these tips:

·On the Create Platform Wizard Connector page if you do not yet have a connector configuration, click New and follow the steps to create one for on your hypervisor.

·For Platform Types, select the radio button for creating and updating layers. Then choose your hypervisor from the dropdown menu.

·On the Confirm and Complete page, verify your settings and click Create Layer.

3.Once you’ve created the platform layer machine, connect to and log into the packaging machine.

4.Install your platform and SCCM software on the packaging machine:

·If you use a connection broker, install it.

·If the App Layering appliance is installed on a different hypervisor than the one where you will be creating this layer, install the hypervisor tools next.

·If you use provisioning software that is not Citrix Provisioning, install it next.

·Install SCCM last, unless you are also installing Citrix Provisioning.

·If you use Citrix Provisioning, install it last.

When installing SCCM, follow all of the steps in the Microsoft article, [Implementing SCCM in a XenDesktop environment](

Note: These steps apply to running the SCCM client in any VDI environment.

5.Open an administrator command window and execute the SEALSCCMClient.cmd script included in the App Layering OS Machine Tools download:


Note: Run the SEALSCCMClient.cmd script whenever you update this layer.

6.Double-click the Shutdown For Finalize icon to verify the layer and shut down the packaging machine.

·If the connector configuration selected in the wizard is set to use Offload Compositing, the layer is automatically finalized.

·If the connector configuration is not set to Offload Compositing, finalize the layer manually, as described in the detailed steps in this article.

Start the CCMEXEC service before starting Software Center

Always start the CCMEXEC service before starting Software Center and trying to interface with the server to get the status of applications and installing them. If the service is not running, the Software Center sometimes shows an error starting up, and you have to start it manually.

The layering service checks to see if the CCMEXEC is configured, and if it is, starts the service as part of the machine’s startup process. Once logged into the machine, the service should already be running, and you are less likely to run into the scenario where starting the app results in an error.

What to expect from installed applications

The SCCM server dictates and reports which applications are installed for which user on what machine.

In a non-persistent world, a user often logs into a different machine on each login. The server views every one of those logins as a new combination of the specific user from that specific machine, so it only shows the applications that it was informed about when the user installed the application from that machine. There is no way of asking the SCCM server to inventory the installed applications on a machine and report the apps found for the current user. However, when a user logs onto their desktop, the only time they need to go into the Software Center is to install an application that they don’t currently have.

In the scenario where the software is not already available from the Start menu or the desktop, users can still install the application that they need.If a user is confused about an application that they think they have installed already, they can click on the install, and the server will check to see if it is installed. If the application is already installed, the status changes to “Uninstall” and shows the application in the installed applications list and the date it was installed.


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.


  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


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
Hotfix Zip File sha256 db7280bd8f791c91d0d2839e1d04f50f2887e2c26f48eb1cbedeb66b930c718f
Size of the Zip file 31.51 MB

Files Updated


More Information

For more information, see Citrix Hypervisor Documentation.

If you experience any difficulties, contact Citrix Technical Support.


How to create a template for the connector and provisioning application

It is recommended to have a template set in the connector configuration.. This ensures the VMs being created and the published image are based on the same hardware specifications and also prevents issues with the time.

1) Find the Gold Image used to create the base OS Layer or use a vm which is known to be configured as wanted and working properly. Preferably use a vm with the same OS and build.

2) Make a clone of either of the VMs

3) Edit the cloned vm and remove all hard disks

4) Convert the vm to a template

5) Use the template in our connector configuration and as the template to create new VMs with the provisioning software. This is critical for PVS devices to stream properly.

NOTE: Possible issues are wrong NICs in the production desktops, issues with the hypervisor tools and associated components, possible BSOD when accessing a desktop. session.