Citrix Receiver upgrade to 4.10 via Scripted Install – “Exit code is 1602 No Plugin found with UpgradeCode = {9FAB00CA-B032-4E4E-8D0C-E3B35802335D}”

Issue

When doing either a scripted upgrade of Citrix Receiver to v4.10.x from v4.x the installation fails.

A manual upgrade works as expected.

Upgrade Script example

.\CitrixReceiver.exe /noreboot /silent /includeSSON /ENABLE_SSON=Yes /EnableCEIP=false

TrolleyExpress.log file
C:\Users\<install user>\AppData\Local\Temp\CTXReceiverInstallLogs-20180524-160141\TrolleyExpress-20180524-160141

shows something similar to the following:

Error - CComponentManager::GetInstallStatus(598) - Installation NOT successful for 'XenApp Web Plugin', error: 1603.
Information - CComponentManager::GetInstallStatus(603) - Installation NOT successful for 'Citrix Receiver (DV)', it never fully tried to install, possibly due to issues.
Information - CComponentManager::GetInstallStatus(603) - Installation NOT successful for 'HDX Flash', it never fully tried to install, possibly due to issues.
Information - CComponentManager::GetInstallStatus(603) - Installation NOT successful for 'HDX Aero', it never fully tried to install, possibly due to issues.
Information - CComponentManager::GetInstallStatus(603) - Installation NOT successful for 'Authentication Manager', it never fully tried to install, possibly due to issues.
Information - CComponentManager::GetInstallStatus(603) - Installation NOT successful for 'Self Service Plug-in', it never fully tried to install, possibly due to issues.
Information - CComponentManager::GetInstallStatus(603) - Installation NOT successful for 'WebHelper', it never fully tried to install, possibly due to issues.
Information - CComponentManager::GetInstallStatus(645) - Created entry for RTME Plugin for reinstalling it if it was installed previously
Information - CComponentManager::GetInstallStatus(692) - Need to repaire plugin with UpgradeCode = {9FAB00CA-B032-4E4E-8D0C-E3B35802335D}
Information - CtxInstallHelpers::CInstalledClientPkg::FindInstalledClient(154) - No existing clients found with given upgrade code: {9FAB00CA-B032-4E4E-8D0C-E3B35802335D}
Information - CComponentManager::GetInstallStatus(704) - Repairs Receiver plugin with Product code = 
Information - CComponentManager::GetInstallStatus(713) - No Plugin found with UpgradeCode = {9FAB00CA-B032-4E4E-8D0C-E3B35802335D}
Information - CApp::SetExitCode(120) - Exit code is 1602 (called with 1603)
Information - CApp::Remove_Reg_Uninstall(1641) - CApp::Remove_Reg_Uninstall
Information - CApp::ExitInstance(1335) - Exit Code = 1602

“No Plugin found with UpgradeCode = {9FAB00CA-B032-4E4E-8D0C-E3B35802335D}”

Solution

• None currently, it’s a known issue with Citrix for upgrading to v4.10.x and 4.11.x, it’s meant to be resolved in v4.12.x.
• New installs and manual upgrades work as expected
• Upgrading to v4.9.x LTSR and earlier works as expected.

Advertisements

Workspace Environment Manager – Capture Screen

Workspace Environment Manager has a cool little feature for end users to use called ‘Capture Screen’, it can be accessed by right clicking on the WEM Agent in the System Tray.

This utility captures the users screen and lets them either Save the image or send it straight to a pre-configured email address (Service Desk etc). Enable Screen Capture in the WEM Administration Console under:

Advanced Settings > UI Agent Personalization > Helpdesk Options

By default the Comments field is greyed out on the end point and needs to be enabled within the WEM Administration Console.

To enable the Comments field you need to put the WEM variable “##UserScreenCaptureComment##” (without quotes) anywhere in the ‘Email Template’ field as below.

After putting in the variable, apply the settings in the WEM Administration Console and then refresh the WEM Agent on the end point. Now when selecting Capture Screen the Comments field is enabled for user input.

You can use a combination of variables through the Custom Subject and Email Template as below, remembering that ##UserScreenCaptureComment## needs to be somewhere in the Email Template.

User Comment:    ##UserScreenCaptureComment##
User Name:           ##UserName##
Display Name:      ##FullUserName##
XenApp Server:   ##ComputerName##
RDS Session ID:   ##RDSSessionID##
Client Name:       ##ClientName##

Refer here for possible variables to use: https://docs.citrix.com/en-us/workspace-environment-management/current-release/reference/dynamic-tokens.html

IGEL Profile Library

For a while I have been putting my common IGEL profiles into a GitHub repository, feel free to download them for your own use, contact me know if you want to upload any of your own to assist the @IGELCommunity !

https://github.com/carlbehrent/igelprofiles

Post IGEL Firmware – Missing new Citrix Receiver version

After applying the latest firmware to devices, I was looking at changing to the latest Citrix Receiver included in that firmware but the existing profile I was using didn’t show the latest Receiver, v13.7.0 was missing.

I had to change Profile ‘Based On’ to the newer firmware and SAVE, important to save the firmware change (and UMS won’t prompt to be saved either) or it still won’t commit the change.

After making this change above, the profile can be edited and you now can see the latest Receiver version.

IGEL Kiosk Mode Browser Settings

I was asked recently about creating a locked down Kiosk Browser Session in the IGEL Operating System. Below is the standard configuration I’d do when creating such a Profile. I will continue to update this post with any new information that might be relevant.

Create a Kiosk Browser Session

1. Create a new Profile, and give it a meaningful name.
2. Navigate to: Sessions > Browser > Browser Sessions
3. Select Add in the right hand window
4. Give a Session Name

Browser Session Options

Set Browser Home Page

1. Navigate to: Sessions > Browser > Browser Sessions > {Session Name} > Settings
2. Change ‘When browser starts’ to ‘Show my home page’
3. Enter ‘Home Page’ address for the browser to open with

Enable Browser Session AutoStart

Navigate to: Sessions > Browser > Browser Sessions > {Session Name}

To ensure the browser launches when the desktop has loaded you need to enable ‘AutoStart’. Along with this setting enable ‘Restart’, Restart means the browser will automatically relaunch if it is closed. Enabling ‘AutoStart Delay’ with a value (in seconds) is the time between the desktop loading and the browser automatically launching.

Set Browser to Full Screen

Navigate to: Sessions > Browser > Browser Sessions > {Session Name} > Window

To make the browser launch in full screen enable ‘Start in fullscreen mode’. While you here enable ‘Hide local filesystem’. Setting this will hide the local file system when you attempt to save files. ‘Hide configuration page of the browser’ will already be enabled.

Customizing the Menu & Toolbars

Navigate to: Sessions > Browser > Browser Sessions > {Session Name} > Menus & Toolbars

• Enable ‘Hide App Menu/Menu Bar‘
  • This removes the App Menu to the right hand side of the browser
• Enable ‘Hide Search input‘
  • This removes the search input from the browser
• Enable ‘Hide URL Input‘
  • This removes the URL input from the browser

• Enable ‘Hide Tabs Toolbar‘
  • This removes the tabs from the top of the browser and also the ability to launch new tabs

• Disable Browser Context Menu

Navigate to: Sessions > Browser > Browser Sessions > {Session Name} > Context

• Enable ‘Hide the browser’s context menu’
  • This completely removes the browser context menu (but not the Tab Context Menu) including:
    • Save Page As button
    • View Page Source / Info

IGEL Configuration Templates

IGEL have some great Profile templates available from their website which are a great starting point for ideas on what can be done within the IGEL OS.

Once the file has been downloaded, unzip it.

Within Universal Management Suite browse to:

System > Import > Import Profiles and browse to .\UMSDemonstration\Template via Import, then select the relevant IGEL OS

Once the templates have been imported it will look similar to this:

 

 

IGEL UMS – “Error: Cannot connect to remote management server”

Issue:

Scanning for new thin clients discovers the available thin clients, select ‘Include’ to bring the device into Universal Management Suite (UMS).

During the inclusion process it fails with the error “ERROR: Cannot connect to remote management server”.

Reason:

Communication between UMS server and thin client requires port 30001 to be open on the server running IGEL UMS. This is visible in the Windows Firewall log file (C:\Windows\System32\LogFiles\Firewall\pfirewall.log) if ‘Log dropped packets’ is enabled.

Solution:

• Allow the following ports on the Windows Firewall
  • 30001, 30005 (For further information refer to: http://edocs.igel.com/#10202276.htm)
• Disable Windows Firewall