Citrix Workspace Msi

Posted on  by admin

Citrix does not recommend extracting the Receiver (Enterprise) .msi files instead of running the installer packages. However, there might be times when you have to extract the .msi files from CitrixReceiver.exe or CitrixReceiverEnterprise.exe manually, rather than running the installer package (for example, company policy prohibits the usage of .exe files). If you use the extracted .msi files for your installation, using the .exe installer package to upgrade or uninstall and reinstall might not work properly.

For Citrix-recommended Receiver (Enterprise) installation methods, refer to Citrix eDocs - Configure and install Receiver for Windows using command-line parameters.

Extract the .msi files

Run the following at command prompt:

Microsoft Teams installation. Note: We recommend installing the VDA before installing Teams in.

With the current version of Citrix Receiver for Windows at the time of this writing being 4.5, I will talk about some of the command line advanced command line install options available which allow you to be more precise and customisable with your Citrix Receiver installs. Citrix Workspace App for Windows. Citrix Virtual Apps (XenApp). The UiPathRemoteRuntime.msi installer is included in UiPathPlatformInstaller.exe, or you can obtain. In the Deployment Type pane, click Add to configure the deployment type for Citrix Receiver setup. The Create Deployment Type Wizard appears. In the General pane: Set the deployment type to Windows Installer (.msi file), select Manually specify the deployment type information and click Next. If I look at the Setup Files tab for the Citrix Receiver prerequisite you see the MSI being instructed to 1) download the source files from the internet then 2) various command line options are available based on the UI that is presented to the user or if the MSI is being told to uninstall from the system.

For 4.x use: CitrixReceiver.exe /extract [Destination_name, e.g. C:test ]

For 3.x use: CitrixReceiverEnterprise.exe /extract [Destination_name, e.g. C:test]
where Destination _name is a complete pathname to the directory into which the .msi files are extracted. The directory must exist already and /extract adds a subfolder called extract to that directory.

For example, if you create a C:test directory and run /extract, the extracted .msi files are put in C:testextract.

Uninstall Citrix Workspace

Note: If User Access Control (UAC) is enabled, Citrix advises that you install the .msi files in elevated mode. The .msi files are supported per-machine and require administrator privileges to deploy them.

Install the .msi files for Receiver

Use the following command line parameter:

Note: Double click installation for Receiver using individual .msi is not recommended for 4.4.x and 4.5

Install the Components:

When installing the Receiver.exe components, run the .msi files in the following order:

  1. RIInstaller.msi
  2. ICAWebWrapper.msi
  3. GenericUSB.msi
  4. DesktopViewer.msi
  5. CitrixHDXMediaStreamForFlash-ClientInstall.msi
  6. Vd3dClient.msi
  7. AuthManager.msi
  8. SSONWrapper.msi
  9. SelfServicePlugin.msi
  10. WebHelper.msi

During the execution of each of these msi packages, the following command line parameters need to specified:
REBOOT=ReallySuppress MSIDISABLERMRESTART=0 MSIRESTARTMANAGERCONTROL=0 NEED_RECEIVER=n TROLLEYINSTALL=1 ALLUSERS=1

Msi

The command to execute a msi package is as follows:

msiexec /i <path to the .msi package> REBOOT=ReallySuppress MSIDISABLERMRESTART=0 MSIRESTARTMANAGERCONTROL=0 NEED_RECEIVER=n TROLLEYINSTALL=1 ALLUSERS=1

For a non-admin user installation, the parameters are as follows:

REBOOT=ReallySuppress MSIDISABLERMRESTART=0 MSIRESTARTMANAGERCONTROL=0 NEED_RECEIVER=n TROLLEYINSTALL=1 ALLUSERS='

Note: GenericUSB and SSON are not supported for non-admin users, so no need to install GenericUSB.msi and SSONWrapper.msi for non-admin user installation.

Remove the Components:

Citrix Workspace Msi Product Code

When removing the components, remove them in the following order:

  1. SelfServicePlugin.msi
  2. SSONWrapper.msi
  3. AuthManager.msi
  4. Vd3dClient.msi
  5. CitrixHDXMediaStreamForFlash-ClientInstall.msi
  6. DesktopViewer.msi
  7. GenericUSB.msi
  8. ICAWebWrapper.msi
  9. RIInstaller.msi
  10. WebHelper.msi

Each .msi file has an Add/Remove (Control Panel on Windows XP or Windows Server 2003) or Programs and Features (Control Panel on Windows Vista, Windows 7, and Windows Server 2008) entry in the following format:

Name of packageName displayed in Add/Remove or Programs and Features
RIInstaller.msiCitrix Receiver Inside
ICAWebWrapper.msiOnline Plug-in
PNAWrapper.msiCitrix Receiver (PNA)
SSONWrapper.msiCitrix Receiver (SSON)
CitrixHDXMediaStreamForFlash-ClientInstall.msiCitrix Receiver (HDX Flash Redirection)
DesktopViewer.msiCitrix Receiver (DV)
GenericUSB.msiCitrix Receiver (USB)
Vd3d.msiCitrix Receiver (Aero)
AuthManager.msiCitrix Authentication Manager
CitrixReceiverUpdater-User.msiCitrix Receiver Updater
SelfServicePlugin.msiCitrix Single Sign-On Plug-in

Note: CitrixReceiverUpdater-user.msi is not included in Citrix Receiver from version 4.3 onwards

Last year I wrote a blog about how to deploy the Citrix Receiver (which is now replaced by the Citrix Workspace app) via Intune. Like described in that blog, the executable consists of 10 MSIs that need to be installed on a Windows 10 device when you are not able to use the store app of Citrix in the Microsoft app store.

With the new Windows app (Win32) app type you are able to deploy more complex Win32 apps via Microsoft Intune. So, the Citrix Receiver is a great app to test the new feature in Microsoft Intune with.

Citrix

To be able to use this app format you need to wrap the file into a format that is supported by Microsoft Intune. The INTUNEWIN format is a format especially for Microsoft Intune and which allows you to wrap executables or multi file MSI installs, a great addition.

The Intune Win32 App Packaging Tool is the tool to be used to “wrap” the installation files into the INTUNEWIM format. The packaging tool can be downloaded here.

After downloading the packaging tool you need to follow the next steps to package the Citrix Receiver.

  1. Download the Citrix Receiver 4.12
  2. Extract the Intune Win32 App Packaging tool and execute the following command;

intunewinapputil -c . -s citrixreceiver.exe -o .

-c = source path with all setup files

-s = setup file for the Citrix Receiver

-o = output path

  1. After successfully creating the new package we need to add the package to Microsoft Intune, this can be done in the Intune console via https://portal.azure.com > Intune > Client Apps > Apps and click Add.
  2. First step is to add the App package file citrixreceiver.intunewin, click OK
  3. Click App information and supply the Name, Description and Publisher as mandatory fields and click OK
  4. Click Program and supply the following information and click OK:
    1. Install command: citrixreceiver.exe /silent
    2. Uninstall command: citrixreceiver.exe /uninstall
    3. Install behaviour: System

You need to add the command line that allows you to install and uninstall the Citrix Receiver unattended. Of course, this differs per application.

  1. Click Requirements and supply the Operation System Architecture, Minimum Operation System version, Disk space required (MB), Physical memory required (MB), Minimum number of logical processors required, Minimum CPU speed required (MHz) and click OK.
  2. Click Detection Rules and supply the way to check if an application is already installed on a device, this can be done via a manual rule by checking the existence of an MSI product code, if a file or folder exists or if a registry key exists. Also, a detection script can be used. After configuring the detection rules, click OK.
  3. Click Return codes and check if the default return codes are okay and click OK
  4. Next, click Add to add the app to Intune.

Next you can deploy the app to your Windows 10 devices and you will see that the Citrix Receiver is being installed using the new app you have just created. In the console you can see if the deployments are successful or not.

Comments