Microsoft Configuration Manager and Intune (Enterprises/Paid) > Report Update Detection Issues (Enterprises Using ConfigMgr and Intune)

Citrix Workspace LTSR 19.12.1000.0

(1/2) > >>

The new Citrix Workspace LTSR 19.12.1000.0 package released on 7/21/2020 appears to have the following detection issues:

* It should supersede the Citrix Receiver 4.9 LTSR CUx packages and show as needed on devices with this package
* It does not detect pre-existing installs of Citrix Workspace LTSR (CU1 or pre CU1), so they cannot be updated with this package
ETA: The pre-existing installs of Receiver 4.9 LTSR and Workspace 1912 LTSR are system wide installs, not per user.

Thank you

So after taking a look at the applicability rules, it appears that Workspace LTSR also looks for the LTSROnly value =equal to True in the registry, where as the 4.9 LTSR package did not.  We had auto update disabled via GPO, which precludes us from setting this value using the Citrix ADMX, but I suppose I could set it with a GPO registry preference.  I would prefer to not have to enable the native auto updater in order to get a match for this setting.

Additionally, it would also still be nice if the package could see installs of the Receiver 4.9 LTSR as applicable for this package instead of only looking for Workspace installs.

Thank you

Andrew Jimenez:
So during our testing for Workspace LTSR, we found that if you install the application and do not define LTSROnly to equal true, then during an auto-update, the app will actually revert itself to non-ltsr. Additionally, there is no other indication for the LTSR app that the application is actually an LTSR release. Because of this, we chose to use the LTSROnly reg value to determine if the Citrix Workspace install is actually an LTSR installation. If you know of any other methods of determining if the app is in fact LTSR, we'd be happy to test that.

We are not superseding Citrix Receiver LTSR at this time because Receiver LTSR is still supported, once Receiver LTSR falls out of support, we will likely supersede it with the latest Workspace LTSR.

I would argue that if I am using a tool like this to patch Workspace LTSR, haven't bothered to disable the native auto update, and get put back on non LTSR, then that's on me..., but I see what you're saying.

Perhaps a nested OR for folks with AutoUpdate turned off that checks to see if AutoUpdate\Banned = True AND DisplayVersion is <1913.0.0.0 could work.

Thank you for your reply

Andrew Jimenez:
The issue there is that if you have both Workspace and Workspace LTSR published, since there is nothing else differentiating them, both would be applicable.

We did however add in the install string to set the LTSROnly flag, so if you deploy Workspace LTSR via our App method, future patches from Patch My PC will be LTSR.


[0] Message Index

[#] Next page

Go to full version