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.

capture_screen_menu

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

enable_screen_captre

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

screen_capture_blank

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

email_template

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.

screen_capture_ready

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.

email_template_ready

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

Citrix Self-Service Password Reset “Cannot access your server address!”


Environment:

  • Windows Server 2016
  • Citrix XenApp 7.15
  • Citrix XenApp Self-Service Password Reset 1.1.0.15097

Issue:

Creating a new ‘User Configuration’ in the ‘Enable Self-Service Password Reset’ section

SSPR

  • The Service Address returns and error “Cannot access your service address!”.

sspr_error

  • Browsing to https://fqdn/MPMService returns “Error 403 – Forbidden: Access is denied”
  • Event Viewer has the following:

SSPR_EV

 

Resolution:

Either:

  1. Disable the Internet Explorer proxy server, if possible
  2. Enable ‘Bypass proxy server for local addresses’
  3. Create a proxy server exception

 

 

 

 

Citrix WEM – “Manage Printer” Application


We are currently using an on house written app that allows users to add/remove/set as printer their network printers.

Our users like this custom tool because its so simple to navigate around but going into our new XenApp 7.15 environment on Windows Server 2016 OS this tool doesn’t work.

In this new environment we are going to implement Citrix Workspace Environment Management (WEM) and I noticed it comes with the ‘Manage Printers’ function as part of the WEM agent deployed to the XenApp Member servers, this tool is very good but its semi hidden away and takes a couple of clicks to find it where our users were used to having a desktop printer icon to get to the custom app.

I decided to see if the WEM ‘Manage Printers’ function can be made into a desktop icon, the details to turn this into an application are:

  • Command Line: C:\Program Files (x86)\Norskale\Norskale Agent Host\PrnsMgmtUtil.exe
  • Working Directory: C:\Program Files (x86)\Norskale\Norskale Agent Host
  • Icon File: C:\Windows\System32\shell32.dll
  • Icon Index: 16
  • Display Name: Printer Management
  • Action Type: Create Application Shortcut

Dont forget to ‘assign’ the new application in Action Assignment.

NetScaler SDX – Unknown Device, not supported by Command Center


Environment:

  • Citrix NetScaler SDX appliances
  • Citrix Command Centre 5.x (and think it occurs in version 4.x also) on Windows Server 2008 R2

Issue:

While running a NetScaler SDX discovery in Command Centre the discovery fails with the following error message:

“Unknown device ; <sdx_ip_address> ; not supported by command center”

(The discovery of the NetScaler VPX instances discovered fine independently)

– Checked discovery logs and found the below error:

Troubleshooting Steps:

– Checked from the Command Centre server and was able to ping and SSH to SDX Management IP with same credentials used in the Command Centre NetScaler SDX profile.
– In the C:\Program Files (x86)\Citrix\Citrix Command Center\logs\discoveryLogs.txt log file, I could see it was trying to add the NetScaler SDX as “CBSDX” (CloudBridge SDX I assume).

  • INVENTORYERR: Device not recognized as CBSDX. SYSID null <sdx_ip_address>
  • INVENTORYERR: Exception while login to =<sdx_ip_address>
  • Localized : English : nsroot failed to login

Resolution:

Within Command Centre,

  • On the Administration tab,
  • Under Settings,
  • Click SSL Settings and then
  • Select the Enable TLSv1 option
  • Restart the Command Centre service.

NOTE: After restarting the Command Centre service and its running again, it can take a while before your able to log in again.

Check the service status in the C:\Program Files (x86)\Citrix\Citrix Command Center\logs\wrapper.log file

INFO | jvm 1 | 2016/05/23 14:47:00 | Starting up as Primary Server and correcting the Server information in the Database.
INFO | jvm 1 | 2016/05/23 14:47:00 |
INFO | jvm 1 | 2016/05/23 14:47:01 |
INFO | jvm 1 | 2016/05/23 14:47:01 | Starting Citrix Command Center “Primary” Server Modules, please wait
INFO | jvm 1 | 2016/05/23 14:47:15 |
INFO | jvm 1 | 2016/05/23 14:47:15 |
INFO | jvm 1 | 2016/05/23 14:47:15 |
INFO | jvm 1 | 2016/05/23 14:47:15 | Process : SyslogServerBE [ Started ]
INFO | jvm 1 | 2016/05/23 14:47:16 | Process : ProcessTest [ Started ]
INFO | jvm 1 | 2016/05/23 14:47:17 | Process : ShutdownDatabaseServer [ Started ]
INFO | jvm 1 | 2016/05/23 14:47:19 | Process : CLIRMIService [ Started ]

If you see a lot of [Failed] statues, restart the Command Centre server.

 

“Please wait for User Profile Services” – Logon delay


Environment

  • Windows Server 2008 R2
  • Citrix XenApp 6.5 RU5

Issue

During users logon to XenApp published applications and published desktops there can be a lengthy delay on “Please wait for the User Profile Services”, it can hang on this for up to 30 secs.

Solution

In the Group Policy Management browse to:

  • Computer Configuration
    • Administrative Templates
      • System
        • User Profiles

Modify the policy setting “Set maximum wait time for the network if a user has a roaming user profile or remote home directory” to “Enabled” and set the value Wait for network for maximum (seconds) to 0.

User session stuck on XenApp server


Environment

  • Windows Server 2008 R2
  • Citrix XenApp 6.5

Issue

User’s session is stuck on XenApp server, logging off from AppCenter doesn’t remove them.

Resolution 

1.Log onto the RDS server and launch Remote Desktop Services Manager or connect via another server.

2.Get the Session ID of the hung session from the Session tab:

  • Session: Disconnected
  • User: <Blank>
  • ID: <number>
  • State: Disconnected
  • ClientName: <Blank>
  • LogOnTime: Unknown

3.Click on Processes tab

4.Click on ID column to sort the processes by ID

5.Find the hung ID number

6.There is normally 3 processes visible

  • LogonUI.exe
  • Winlogon.exe
  • Csrss.exe

7.Right-click on winlogon.exe and End Process, once you end this process the other 2 will disappear.

8.DO NOT end process on csrss.exe, this will crash and reboot the RDS server

9.Now the user has cleared from the RDS server and from AppCenter.