Citrix Workspace Sccm



This post is Part 3 of a series of posts I am writing about configuring Citrix Workspace Environment Manager 1909. You can find the previous posts here:

Part 1 – Installing Citrix Workspace Environment Manager – https://www.virtualmanc.co.uk/2019/10/16/installing-citrix-workspace-environment-1909/

Part 2 –Configuring Workspace Environment Manager Endpoints – https://www.virtualmanc.co.uk/2019/10/20/configuring-citrix-workspace-environment-manager-1909-endpoints/

Citrix Workspace app for Windows is easy-to-install software that provides access to your applications and desktops using Citrix Virtual Apps and Desktops from a remote client device. Citrix Workspace app provides access from your desktop, Start menu, Citrix Workspace user interface, or web browsers.

  1. Citrix Connector 3.1 provides a bridge between Microsoft System Center Configuration Manager and XenApp or XenDesktop, enabling you to extend the use of Configuration Manager to your Citrix environments. Please note that the Citrix Connector 3.1 is compatible with XenApp 7.5, 7.6, 7.7, and 7.8 and XenDesktop 7.1, 7.5, 7.6, 7.7, and 7.8.
  2. U001f bu0003 v۶ o )Pu xm u0012u o݊b7 uR7Nz u0012 XS$KR y b 5 G 7 l+i m(u0002 e0u0018ff ' u000e tqJ 99 ' DA 8ԝu001cW u0010 FTs' Q 9u000e T3u001a u000e f; u0002.
  3. This document is to discuss the failure seen when publishing Citrix Workspace App through Ivanti Patch for SCCM. Citrix Workspace app 19.9.0.21' 341b01b9-35db.
  4. Note: Citrix Receiver for Windows Version 4.5 and later supports SCCM deployment. You can use Microsoft System Center Configuration Manager (SCCM) to deploy Citrix Receiver for Windows.
Citrix workspace deploy sccm

I had hoped to get this post out sooner but I have been really busy attending events and hunting for a new job! In this post we will discuss how to create and assign configuration sets to our servers so we can configure some settings and ensure that everything is working OK.

So first of all what is a configuration set??? The configuration set basically contains all the settings which we can apply to all the servers. We can have multiple configuration sets and apply them to either OU’s, computer objects or AD Groups. For this example we will apply it to a single server.

Create Configuration set

So the first step is to create the configuration set which will contain the settings that will be applied. To get us started there are some default templates which you can use. We will create a Configuration Set and then restore the configuration settings to give us our baseline.

1) In the WEM Console in the configuration set menu select Create to create new configuration set. Give it a name and a description

2) Select settings and press Next

3) Select Next

4) Now we can select which template we want to restore the settings from. For this example we will use VUEMAgentSettings.XML. Tick the System Optimization Settings, Agent Configuration Settings and System Monitoring Settings. After you have done this select Next.

5) Select the Restore Settings button to restore the settings

Citrix workspace msi for deployment

6) The settings will now be restored

Assign the configuration set to the server

Now that we have a configuration set we need to apply it to something. We will apply it to our Citrix worker server so that anybody who logs onto the server will get the settings we have configured. To do his perform the following steps:

1) In the WEM Console select Active Directory Objects, the Machines and point to the server you want the configuration set to apply to.

After doing so ensure that the State has a green tick box next to it showing that the agent is in a healthy state.

Citrix

Customise some settings

So now that we have a configuration set lets customise some settings to see what kind of things we can do with WEM. In the console ensure your configuration set is selected at the top of the screen and navigate to Policies and Profiles and then Environmental Settings.

From here you can see that there are lots of different options we can select. As you can see I have just selected some random ones so you can see the end result. I have performed random things like hidden the system clock and disabled the command prompt.

Configure the WEM Agent to run at logon

So now we have a configuration set, we have some settings and now need to have the WEM Agent run when the users logon so the settings to apply. 1password firefox extension not working. On the worker server that the users log onto configure the following registry key:

Citrix workspace 19.12.2000
  • Path: HKLMSoftwareMicrosoftWindowsCurrentVersionRun
  • Key: VUEMUIAgent
  • Type: REG_SZ
  • Value: c:Program Files (x86)CitrixWorkspace Environment Management AgentVUEMUIAgent.exe

Testing

OK now we are nearly there. The only thing left to do is to test it!! For the test I logged onto a Published Desktop as a normal user. As you can see from the screenshot below the settings which we have configured are applied successfully.

Citrix Workspace App Silent Install

I hope you enjoyed reading this post and if you have any questions or queries then please drop them in the comments below.

Till next time!

Hello,

I've followed the below article for Citrix Receiver deployment, using SCCM (v 1710):

I haven't been able to successfully deploy the application.

Citrix Workspace Sccm Deployment

During the course of troubleshooting, I've seen various errors, which I've been able to work through. I found the cleanup utility, which helped in making some progress.

This current behavior has me stuck.. The installation seems to go along fine, then I receive an error, which I think indicates that SCCM could not detect the application's presence. I don't know why, but the only application that seems to be installed is cdviewer.exe. The installation process seems to fail halfway through, but I can't determine why.

In my SCCM application for Citrix Receiver, I'm using the receiver version as the detection method. 4.10.1.7.

Installation switches are /silent, /rcu, /AutoUpdateCheck=disabled

Citrix Workspace Error 40008

Installation log file, and some screenshots, are attached.