VM's Power State Does Not Update And Shows As “Unknown” After vCenter Server Reboots

This is an issue with Citrix hypervisor communication library plugin since version Xenapp/XenDesktop version 7.16.

When vCenter server goes alive after reboot i.e “https://<vCenter FQDN>/sdk” becomes accessible, BrokerHostingPlugin still fails to login the vCenter server with exception “The session is not authenticated.”.

CDF Traces from Delivery Controller

,BrokerHostingPlugin,,0,,1,Information,”Attempting connection”,””

,BrokerHostingPlugin,,0,,1,Information,”***** Get Hypervisor Certificate for Connection to ‘https://<vCenter FQDN>/sdk​​​​​​​’ *****”,””

,BrokerHostingPlugin,,0,,1,Information,”Certificate is untrusted: False”,””

,BrokerHostingPlugin,,0,,1,Information,”Time elapsed to get the hypervisor certificate: xxms”,””

,BrokerHostingPlugin,,0,,1,Information,”***** Login Connection – 0 to ‘​​​​​​​https://<vCenter FQDN>/sdk’ as ‘#login_name#‘ *****”,””

,BrokerHostingPlugin,,0,,1,Information,”VMware plugin initialisation times: create service xms, content time xxxms, total xxxms”,””

,BrokerHostingPlugin,,0,,1,Information,”Connected to ‘VMware vCenter Server #vCenter version info#’“,””

,BrokerHostingPlugin,,0,,1,Error,”System.Web.Services.Protocols.SoapException: The session is not authenticated.

,BrokerHostingPlugin,,0,,1,Information,”Connection attempt threw exception System.Web.Services.Protocols.SoapException: The session is not authenticated.

,BrokerHostingPlugin,,0,,1,Information,”Connection is still down”,””

,BrokerHostingPlugin,,0,,1,Information,”Sleeping for 00:00:30 before trying to reconnect again”,””

Related:

  • No Related Posts

Client Drive Mapping Fails when File Size is Larger than 4GB

In XenApp and XenDesktop, very large files that have a file size greater than 4GB are not supported with Client Drive Mapping.

For Example, when viewing a file which is greater than 4GB using a published Windows Explorer instance in a XenApp Client Mapped Drive, file size will be incorrectly displayed.

The following error message might appear:

“The file <filename> is too large for the destination file system”

When copying a file with file size greater than 4GB using a CDM mapped drive, the file is partially copied, resulting in an incomplete target file being written.

Related:

  • No Related Posts

How to Create Machine Catalog using MCS in Azure Resource Manager

Pre-requisites

  • Access to the XenApp and XenDesktop Service of Citrix Cloud.
  • An Azure Subscription.
  • An Azure Active Directory (Azure AD) user account in the directory associated with your subscription, which is also co-administrator of the subscription.
  • An ARM virtual network and subnet in your preferred region with connectivity to an AD controller and Citrix Cloud Connector.
  • “Microsoft Azure” host connection
  • To create an MCS machine catalog, XenDesktop requires a master image that will be used as a template for all the machines in that catalog.

User-added image

Creating Master Image from Virtual Machine deployed in Azure Resource Manager

Create a virtual machine (VM) in Azure using the Azure Resource Manager gallery image with either the Server OS or Desktop OS (based on whether you want to create Server OS catalog or Desktop OS catalog).

Refer to Citrix Documentation – install Citrix VDA software on the VM for more information.

Install the applications on the VM that you want to publish using this master image. Shutdown the VM from Azure Portal once you have finished installing applications. Make sure that the power status for the VM in Azure Portal is Stopped (deallocated)

User-added image

When creating MCS catalog we need to use the .vhd file that represents OS disk associated with this VM as master image for the catalog. If you have the experience of using Microsoft Azure Classic connection type in XenDesktop, you would have captured specialized image of the VM at this stage, but for Microsoft Azure connection type you don’t have to capture the VM image, you will only shutdown the VM and use the VHD associated with the VM as master image.

Create MCS Catalog

This information is a supplement to the guidance in the Create a Machine Catalog article. After creating master image, you are all set to create MCS catalog. Please follow the steps as described below to create MCS catalog.

  1. Launch the Studio from your Citrix Cloud client portal and navigate to Machine Catalogs in the left hand pane.

  2. Right click Machine Catalogs and click on Create Machine Catalog to launch the machine creation wizard.

  3. Click Next on the Introduction page.

    User-added image

  4. On the Operating System page Select Server OS or Desktop OS based on what type of catalog you want to create and click Next.

    User-added image

  5. On the Machine Management page, select Citrix Machine Creation Service (MCS) as the deployment technology and select the Microsoft Azure hosting resource and click Next.

    User-added image

Master Image Selection – This page provides a tree view which you can navigate to select the master image VHD. At the topmost level are all the resource groups in your subscription except those which represent the MCS catalog created by XenDesktop. When you select and expand a particular resource group, it shows the list of all storage accounts for the Azure Umanaged Disks in that resource group. If there are no storage accounts in that resource group, there will not be any child items under that resource group. If you have manually created number of resource groups and storage accounts to host your manually created VMs in your subscription, the master image page will show all those resource groups, storage accounts, containers and VHDs even though not all those VHDs are master images that you want to use for the provisioning. Select the storage account that has your master image. When you expand the storage account, it shows list of containers inside the storage account. Expand the container that has master image VHD and select the VHD that you want to use as master image for the catalog.

User-added image

In the case of Azure Unmanaged Disk, you need to know the VHD path in order to select it. If you have stood up a VM in Azure and prepared it to be used as a master image and you want to know the VHD path, follow the steps below:

  1. Select the resource group that has your master image VM.

  2. Select the master image VM and click Settings

  3. Click on Disks then Click OS Disks and copy the disk path.

    User-added image
    User-added image

  4. OS disk path is structured as https://<storage account name>.blob.core.window.net/<container name>/<image name>.vhd

  5. You can use the disk path obtained in the step above to navigate the tree view to select image.

In the case of Azure Managed disk, it will be available directly under the Resource Group that you had created or as a part of the Virtual Machine’s Resource Group, as show below:

Note: If you don’t shutdown the master image VM and select the corresponding VHD to create a catalog, the catalog creation will fail. So make sure if you are selecting the VHD which is attached to running VM instance, the VM is in Stopped(deallocated) state.

  1. Storage type selection – XenDesktop supports Locally Redundant Standard or Premium storage for provisioning VMs in Azure. Your master image VHD can be hosted in any type of storage account, but for the VMs to be provisioned in Azure, XenDesktop will create new storage accounts based on storage type you selected.

    User-added image

  2. XenDesktop will provision maximum 40 VMs in single storage account due to IOPS limitations in Azure. For example if you want to create 100 VM catalog, you will find 3 storage accounts created and VM distribution in each storage account will be 40, 40 and 20.

  3. VM instance size selection – XenDesktop will show only those VM instance sizes which are supported for the selected storage type in the previous step. Enter number of VMs and select the VM instance size of your choice and click Next.

    User-added image

  4. Network Card Selection – Select network card and the associated network. Only one network card is supported.

    User-added image

  5. Select resource location domain and enter machine naming scheme.

    User-added image

  6. Enter credentials for your resource location Active Directory.

    User-added image

  7. Review the catalog summary, enter the catalog name and click Finish to start provisioning.

    User-added image

  8. Once the provisioning is complete, you will find new resource group created in your Azure subscription which hosts, all the VMs, storage accounts and network adapters for the catalog you provisioned. The default power state for the VMs after provisioning is Stopped(deallocated).

    User-added image

Once the provisioning is complete, you will find new resource group created in your subscription that has VM RDSDesk-01 as per the naming scheme we provided, NIC corresponding to that VM and a storage account that XenDesktop created to host the OS disk and the identity disk for the VM. The VM will be hosted on the same network as that of the selected hosting resource during catalog creation and the default power state of the VM will be Shutdown(deallocated).

The resource group created by XenDesktop during the MCS provisioning will have following naming convention

citrix-xd-<ProvisioningSchemeUid>-<xxxxx>

To find out which resource group in the Azure portal corresponds to the catalog you created from studio, follow the steps below.

  1. Connect to your XenApp and XenDesktop service using Remote PowerShell SDK. Please visit this link to find our how to interact with your Citrix Cloud environment using Remote PowerShell SDK.
  2. Run command Get-ProvScheme -ProvisioningSchemeName <Catalog Name>
  3. Note down the ‘ProvisioningSchemeUid’ from the output of the above command.
  4. Go to the Azure portal and search for the resource group name that contains ‘ProvisioningSchemeUid’ you obtained in step 3.
  • Note:

    As a best practice you should always create a copy of your master image and use the copied image as input to the provisioning process. In future if you want to update the catalog, you can start the master image VM and make necessary changes, shut it down and again create a copy of the image which will be your update image. This helps you to use the master image VM to create multiple image updates.

    Remember to shutdown the master image VM from Azure portal before starting to create the catalog. The master image needs to be copied into catalog’s storage account once provisioning starts, so we need to make sure it is not in use by any VM, otherwise it will lead to image copy failure and eventually provisioning failure.

  • Make sure you have sufficient cores, NIC quota in your subscription to provision VMs. You are most likely going to run out of these two quotas. You may not be able to check your subscription quota limits,
  • If your master image VM is provisioned in the Premium storage account then just shutting down the VM from the portal isn’t enough. You also need to detach the disk from the VM to use it as master image in provisioning. But in Azure Resource Manager you can not detach the disk while the VM is still available. So you need to delete the VM from the portal, this will only delete the VM but keep the OS disk in the storage account. The NIC corresponding to the VM also needs to be deleted separately.
User-added image

Related:

Director Version Matrix – Install or Upgrade compatibility of Director with Delivery Controller, VDA

Important: All new features of Director will be available and work as expected only in combination with the required minimum versions of the Delivery Controller (DC) and the VDA listed below.

Note: This article is applicable to XenApp 6.5 and later, XenDesktop 7 and later.

Director Version Features Dependency

(Min Version required)


Edition
1906 Session Auto Reconnect DC 7 1906 and VDA 1906 All
Session startup duration DC 7 1906 and VDA 1903 All
Desktop probing DC 7 1906 and Citrix Probe Agent 1903 Premium
7.9 and later Citrix Profile Management Duration in Profile Load VDA 1903 All
1811 Profile load DC 7 1811 and VDA 1811 All
Hypervisor Alerts Monitoring DC 7 1811 Premium
Application probing DC 7 1811 and Probe Agent 1811 Premium
Microsoft RDS license health DC 7 1811 and VDA 7.16 All
Key RTOP Data display DC 7 1811 and VDA 1808 Premium
1808 Export of Filters data DC 7 1808 and VDA 1808 All
Interactive Session drill down DC 7 1808 and VDA 1808
GPO drill down DC 7 1808 and VDA 1808
Machine historical data available using OData API DC 7 1808
7.18 Application probing DC 7.18 Platinum
Built-in alert policies
Health Assistant link None All
Interactive Session drill-down
7.17 PIV smart card authentication None All
7.16 Application Analytics DC 7.16 || VDA 7.15 All
OData API V.4 DC 7.16 All
Shadow Linux VDA users VDA 7.16 All
Domain local group support None All
Machine console access DC 7.16 All
7.15 Application Failure Monitoring DC 7.15 || VDA 7.15 All
7.14 Application-centric troubleshooting DC 7.13 || VDA 7.13 All
Disk Monitoring DC 7.14 || VDA 7.14 All
GPU Monitoring DC 7.14 || VDA 7.14 All
7.13 Application-centric troubleshooting DC 7.13 || VDA 7.13 Platinum
Transport protocol on Session Details panel DC 7.x || VDA 7.13 All
7.12 User-friendly Connection and Machine failure descriptions DC 7.12 || VDA 7.x All
Increased historical data availability in Enterprise edition Enterprise
Custom Reporting Platinum
Automate Director notifications with SNMP traps Platinum
7.11 Resource utilization reporting DC 7.11 || VDA 7.11 All
Alerting extended for CPU, Memory and ICA RTT conditions DC 7.11 || VDA 7.11 Platinum
Export report improvements DC 7.11 || VDA 7.x All
Automate Director notifications with Citrix Octoblu DC 7.11 || VDA 7.x Platinum
Integration with NetScaler MAS DC 7.11 || VDA 7.x

MAS version 11.1 Build 49.16
Platinum
7.9 Logon Duration Breakdown DC 7.9 || VDA 7.x All
7.7 Proactive monitoring and alerting DC 7.7 || VDA 7.x Platinum
SCOM integration DC 7.7 || VDA 7.x || SCOM 2012 R2 || PowerShell 3.0 or later* Platinum
Windows Authentication Integration DC 7.x || VDA 7.x All
Desktop and Server OS Usage DC 7.7 || VDA 7.x Platinum

* Director and SCOM server must have the same PowerShell version

Upgrade sequence – XenApp and XenDesktop Components

Illustration of the upgrade sequence is as below. To upgrade all the installed components, run the installer on all the machines containing respective components.

User-added image

Note: Once DC is updated successfully, the Studio will prompt you to upgrade the Site. Complete this step for the new features to be available in Director.

How Do I Articles

Related:

  • No Related Posts

Citrix UPS Printers are not visible via Control Panel, Devices And Printers


This is an known issue with printers provided by Citrix Universal Printer server on windows operating systems Windows Server 2019, Windows Server 2016, Windows 10, Windows Server 2012r2, Windows Server 2012.

Citrix is working with Microsoft to correct this interaction between Microsoft operating systems and Citrix universal print server print provider.


Citrix Documentation:

This issue has been documented in our XenApp/XenDesktop documentation since 7.5

  • Universal Print Server printers selected in the virtual desktop do not appear in the Devices and Printers window in Windows Control Panel. However, when users are working in applications, they can print using those printers. This issue occurs only on Windows Server 2012, Windows 2012 R2 , Windows 10 and Windows 8 platforms. [#335153]

Microsoft Documentation:

The Device Setup Manager service is discussed in the following article from Microsoft it applies to both Windows 8 and Windows 2012.

Device setup user experience in Windows 8

Microsoft released a hotfix for server 2012r2 which partially addressed some issues with 3rd party print provider visibility in newer windows releases.

However this was not a complete solution, and printers provided by Citrix Universal Print Server remained not visible.​

https://support.microsoft.com/en-us/help/2966038/printer-managed-by-custom-print-providers-is-not-visible-in-devices-an

Related:

  • No Related Posts

HDX Flash Redirection Compatibility

HDX Flash Redirection is a technology that allows Flash-based videos to be rendered on the end user device (Windows or Linux) while appearing seamlessly integrated with the server-side web browser. HDX Flash provides a better user experience by offloading Adobe Flash rendering from the Citrix XenApp or XenDesktop server to the user device. The objective is to offload 80% or more of websites that leverage Flash. When Adobe Flash content cannot be redirected to the user device, the technology attempts to gracefully fall back to server-side rendering. Websites that cannot use Flash Redirection are blacklisted, either automatically by the software or manually by a system administrator.

If client-side Flash rendering is not desired, the HDX Flash Redirection technology can be disabled by using policies but the scalability benefits of HDX Flash Redirection are lost.

Compatibility Matrix

HDX Flash Redirection behavior might be affected by the Adobe Flash version, the XenApp or XenDesktop VDA version, as well as the Receiver version used to access applications and desktops. The browser version seems to have the largest impact on the specific Flash Redirection behavior that could be experienced in your environment.

Citrix has tested a variety of Adobe Flash and Internet Explorer versions against different XenApp and XenDesktop versions to determine the stability of Flash Redirection with these different combinations and to ensure that Flash Redirection works as expected. The following matrix comprises the scope of our testing:

Note

  • On July 25, 2017, Adobe announced End of Life (EOL) for Flash. Adobe plans to stop updating and distributing the Flash Player at the end of 2020. Microsoft announced that they are phasing out Flash support in Internet Explorer before the Adobe date. They are removing Flash from Windows by the end of 2020. When that happens, users can no longer enable or run Flash in Internet Explorer. Citrix aligns with Microsoft policy and continues to maintain and support HDX Flash Redirection until the end of 2020. More information available on https://docs.citrix.com/en-us/xenapp-and-xendesktop/7-15-ltsr/multimedia/flash-redirection.html
  • Adobe no longer has Extended Support Release (ESR) versions of Flash. Customers are recommended to use the supported versions of Flash as outlined in the matrix below.
  • Some websites stream content using HTML5 by default, such as Youtube.com and may prompt to install Flash even after adding to Compatibility View. To use Flash Redirection on such websites, Emulation Mode should be used.(for example IE9 mode) The later section of the article outlines steps to enable Emulation Mode.
  • Beginning January 12, 2016, Microsoft supports only the most current version of Internet Explorer available for an operating system. Flash Redirection will be supported on the latest version of Internet Explorer supported on the operating system. For details, refer to Microsoft Lifecycle Support policy for Internet Explorer.
Platforms
Versions Tested Up To
Adobe Flash 32.0 32.0.0.207
Internet Explorer
11
11.0.10240.17319
Receiver for Windows 4.9 4.9.6000
Workspace App 1905

Citrix recommends the XenApp or XenDesktop component updates below used in our testing to achieve the best Flash Redirection experience.

These hotfixes contain several Flash Redirection related fixes that provide more stability to environments using Flash Redirection, particularly those which resulted in blacklisting websites and Flash videos not playing.

Website Content: Adobe Flash technology and content is frequently updated on many websites that might impact Flash Redirection particularly with Internet Explorer 11. Some of these website specific issues can be resolved by one of the following workarounds:

  • Enable Internet Explorer Compatibility View and add the website(s) to the list.
  • Enable Emulation Mode on the user device. In Internet Explorer, on the Tools menu, click F12 Developer Tools. In the far left of the DOM Explorer screen, scroll down the list and select the Emulation icon. In Document Mode, select 9 or 10. Microsoft Enterprise Mode Site List Manager can be utilized to automate the Document Mode.

Platforms

Versions

Updates

XenApp

6.5

HDXFlash200WX64008

XenApp / XenDesktop

7.6, 7.15, 1903, 1906

The following articles provide a list of fixes included in XenDesktop/XenApp 7.6 version along with related fix information:

CTX138196 (Desktop OS), CTX142117 (Server OS)

List of Flash Related Articles

For more information, see the following articles: List of Flash Related Articles.

Installation and Configuration

CTX126529 – How to Enable Server-Side Content Fetching in HDX MediaStream for Flash

CTX124190 – How to Deploy and Configure HDX MediaStream for Flash

CTX125413 – How to Change the Background Color of Client-Rendered Flash Content for HDX MediaStream Flash Redirection

Known Issues and Limitations

CTX214127 – Citrix Known Issues With Adobe Flash Update 18.0.0.360

CTX214103 – Citrix Known Issues With Adobe Flash 22

CTX201150 – Adobe Flash 18 – Citrix Known Issues

CTX126702 – HDX MediaStream for Flash – Client-Side Content Fetching Limitations

CTX125324 – HDX MediaStream Flash Redirection – Network Latency Performance Issues

CTX124756 – HDX MediaStream for Flash Creates an Unknown Security Identifier in the ICA-tcp Port Permissions on Windows 2003 Feature Pack 2 Servers

CTX132751 – Windows Volume Control not working in VDA with HDX MediaStream for Flash v2

CTX128586 – HDX Monitor Tool Fails to Launch

CTX130847 – IMA Modules to Select when Recording a CDF Trace for a HDX MediaStream Flash Redirection Issues

CTX137799 – Internet Explorer 10 – Citrix Known Issues

CTX139939 – Microsoft Internet Explorer 11 – Citrix Known Issues

Troubleshooting

CTX134786 – Troubleshooting Flash V2 on Linux

CTX127188 – Troubleshooting Guide For Citrix HDX Components

CTX126491 – HDX Experience Monitor for XenApp

CTX135817 – HDX Monitor 3.x

CTX141595 – How to Enable HDX Flash Logging for Server-Side Rendering Failure

Related:

Supported Databases for XenApp and XenDesktop Components

Citrix is committed to ensuring that our products function with the latest Microsoft SQL databases. Citrix supplies best efforts to ensure compatibility with upcoming database releases. New versions of supported databases released after our products have been released, must work. However, Citrix recommends creating a test environment to ensure there are no unforeseen issues related to changes made to the new version or update of the third-party product. Individuals wishing to use the new release with current Citrix products must perform their own testing before using the platform. Citrix does not support any BETA versions of third-party products.

This document will be updated periodically as new information becomes available.

What has changed from the last release of the matrix

  • Updated support for Virtual Apps and Desktops (XenApp/XenDesktop) 7 1906
Supported Databases Virtual Apps and Desktops (XenApp/XenDesktop) 7.15LTSR / 1811 / 1903 / 1906 XenApp/XenDesktop 7.6 LTSR Provisioning Services 7.15 LTSR / 1811 / 1903 / 1906 Provisioning Services 7.6 LTSR XenApp 6.5 HRP07
SQL 2017
x64 Yes Yes Yes (1) Yes (1) Yes
Express Yes Yes Yes (1) Yes (1) Yes
SQL 2016 SP1, SP2
x64 Yes Yes Yes (1) Yes (1) Yes
Express Yes Yes Yes (1) Yes (1) Yes
SQL 2014 SP1, SP2, SP3
x86 Yes Yes Yes (1) Yes (1) Yes
x64 Yes Yes Yes (1) Yes (1) Yes
Express Yes Yes Yes Yes Yes
SQL 2012 SP1, SP2, SP3, SP4
x86 Yes Yes Yes (1) Yes (1) Yes
x64 Yes Yes Yes (1) Yes (1) Yes
Express Yes Yes Yes Yes Yes
SQL 2012
x86 Yes Yes Yes (1) Yes (1) Yes
x64 Yes Yes Yes (1) Yes (1) Yes
Express Yes (2) Yes (2) Yes Yes Yes
SQL 2008 R2 SP2, SP3
x86 Yes Yes Yes Yes Yes
x64 Yes Yes Yes Yes Yes
Express Yes Yes Yes Yes Yes

  1. PVS 7.7 onwards Always ON is supported. PVS 7.11 introduced Multi-subnet Failover
  2. Known issue using SQL 2012 and above with XenDesktop, Refer to article ‘CTX132438 – Unable to Create New XenDesktop Site Using SQL 2012 Server’

Note:

  • The x86 and x64 versions of SQL (version 2012 and later) have been validated with Always On, Clustered, Standalone and Mirrored modes.
  • The Express edition has been validated only as Standalone.

Related:

Citrix Webcam not supported in x64 application like Google Chrome or Microsoft Teams

Webcam redirection is not supported in 64-bit applications with XenApp / XenDesktop 7.16 or older. This was fixed on 7.17 and Receiver 4.11 for Windows.

Also, note downloading Google Chrome and installing – you may note that the application appears in the folder:

C:Program Files (x86)GoogleChromeApplication

User-added image
Which would normally indicate that application is 32bit; however, checking Task manager displays as 64bit application:

User-added image
Capturing a CDF trace and observe that similar information is logged on the VDA CDF trace when a 64-bit application attempts to use a webcam (aka Media capture)…

112496 0 2017/04/09 09:44:12:15668 3036 4020 -1 HostMMTransport IcaMMTransport::Connect 9 Error [Id=1] IcaMMTransport::Connect: Media capture is not supported for 64-bit applications.

Install *Google Chrome for business* available now as Chrome MSI 32-bit to resolve the issue.

Related:

  • No Related Posts

Citrix MSI Log Analyzer

Description

The Citrix MSI Log Analyzer is designed to assist with the following scenarios:

  • When failure occurred during install or upgrade or uninstall of XenApp/XenDesktop
  • The Citrix MSI Log Analyzer analyzes the failure and provides helpful info for troubleshooting the issue
  • The Citrix MSI Log Analyzer will also try to point to a knowledge base article helpful to troubleshoot and resolve the issue

What’s New in v1.2.0.9

  • Added support for Storefront logs
  • Added support for uploading experience metrics through TLS 1.2/TLS 1.1.
  • Minor bug fixes and inputs from the feedback

Prerequisites

The user needs to be a Local Administrator on the target machine in order to run the tool.

How to use Citrix MSI Log Analyzer

The Citrix MSI Log Analyzer is a standalone executable file and does not require installation. Just download the tool to a local folder and execute the application.

Citrix MSI Log Analyzer offers various command line to deal with different use cases.

  1. To analyze the failure in the msi log file:

    CitrixMSILogAnalyzer.exe -msilogfile <msi log file path>



    Look for MSI log file under %TEMP%CitrixXenDesktop InstallerMSI Log files” folder and specify the absolute path of the failing msi log file in the above command line.

  2. To analyze the failure from the XenApp/XenDesktop Metainstaller log file::

    CitrixMSILogAnalyzer.exe -metainstallerlogfolder <metainstaller log folder path>

    Example: CitrixMSILogAnalyzer.exe -metainstallerlogfolder “C:UsersxxxxAppDataLocalTempCitrixXenDesktop Installer” where xxxx is the admin user name specific to the user environment

  3. To analyze Citrix XenApp/XenDesktop failure log file under temp folder

    CitrixMSILogAnalyzer.exe

    This option is useful to run the tool on the target machine where the MSI installation failure happened and one is not sure on where to look for msi failure log file.

  4. To view help:

    CitrixMSILogAnalyzer.exe -help

Note: In order to improve Citrix XenApp/XenDesktop and Citrix MSI Log Analyzer, the troubleshooting data not containing any identifiable information from the tool is uploaded to Citrix. This can be controlled using –upload [Yes | No]

Output from the tool

The output of the tool on the console provides:

1. Troubleshooting info of the actual error

2. CTX article to troubleshoot or resolve the issue

3. Log file saved under %TEMP% with prefix mLog_*.txt. The exact name and path is displayed in the output.

Delete Citrix MSI Log Analyzer

Delete the downloaded executable from the current directory. One may also cleanup mLog_*.txt files under %TEMP% directory

Contact Information:

Questions? Concerns? Send any feedback to:

https://podio.com/webforms/18778954/1263577

Disclaimer

These software applications are provided to you as is with no representations, warranties or conditions of any kind. You may use and distribute it at your own risk. CITRIX DISCLAIMS ALL WARRANTIES WHATSOEVER, EXPRESS, IMPLIED, WRITTEN, ORAL OR STATUTORY, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NONINFRINGEMENT. Without limiting the generality of the foregoing, you acknowledge and agree that (a) the software application may exhibit errors, design flaws or other problems, possibly resulting in loss of data or damage to property; (b) it may not be possible to make the software application fully functional; and (c) Citrix may, without notice or liability to you, cease to make available the current version and/or any future versions of the software application. In no event should the code be used to support of ultra-hazardous activities, including but not limited to life support or blasting activities. NEITHER CITRIX NOR ITS AFFILIATES OR AGENTS WILL BE LIABLE, UNDER BREACH OF CONTRACT OR ANY OTHER THEORY OF LIABILITY, FOR ANY DAMAGES WHATSOEVER ARISING FROM USE OF THE SOFTWARE APPLICATION, INCLUDING WITHOUT LIMITATION DIRECT, SPECIAL, INCIDENTAL, PUNITIVE, CONSEQUENTIAL OR OTHER DAMAGES, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. You agree to indemnify and defend Citrix against any and all claims arising from your use, modification or distribution of the code.

Related: