Citrix Workspace

[AndAuf]

I wondered, why so many of my machines have 0x80240022 in wuahandler.log for some days now. Some hours later, I think I found the reason: the context Citrix Workspace App was installed with

There are two ways to install it initially:
- as User
- as Administrator/SYSTEM

If a user is offsite and wants to access your Citrix resources, he can install the Workspace App from citrix.com on his own - no special privileges required. Which actually is great.
But if he did so, the updater started in SYSTEM context by SCCM cannot install the update anymore. Which REALLY sucks.

This means, before SCCM/PatchmyPC can update the Workspace App, it has to uninstall any old version first.

[Justin Chalfant]

So, if a per-user install of the product is performed the installation using the SYSTEM-wide install won't work?

If so, I don't think we can do much about this scenario. You could potentially use a pre-script to perform some actions to remove the per-user. The best method would be to contact Cisco and see if they can improve the SYSTEM level installer.

I wondered, why so many of my machines have 0x80240022 in wuahandler.log for some days now. Some hours later, I think I found the reason: the context Citrix Workspace App was installed with

There are two ways to install it initially:
- as User
- as Administrator/SYSTEM

If a user is offsite and wants to access your Citrix resources, he can install the Workspace App from citrix.com on his own - no special privileges required. Which actually is great.
But if he did so, the updater started in SYSTEM context by SCCM cannot install the update anymore. Which REALLY sucks.

This means, before SCCM/PatchmyPC can update the Workspace App, it has to uninstall any old version first.

[AndAuf]

So, if a per-user install of the product is performed the installation using the SYSTEM-wide install won't work?

Yes.

And the real funny part is - but that is off topic to PatchmyPC: The new version needs a new VC++ runtime, which cannot be installed as user.