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

Nextcloud in newer versions

(1/3) > >>

crispy_nicia:
Hello everyone,

I think something is wrong with the Detection/Installable Rule of Nextcloud in the PatchMyPC catalog.
In older versions two registry keys Value and Version strings are checked, in more recent versions (for example 3.2.4.20210) the following is checked:
Windows Version >= Custom Version.

The automatic update via PatchMyPC currently does not work at all for the Nextcloud installations in my environment. Are there any known problems?

Thanks a lot

Adam Cook:
I just compared the applicability logic for the first update we added to our catalogue for Nextcloud  (3.2.1.20210) versus what's in there today (3.2.4.20210) and I do not spot any differences like you suggest.

There are not any known problems for Nextcloud.

When you say "does not work at all", what are you experiencing?

crispy_nicia:
Thanks for the tip Adam!
I have to admit that I was not familiar with the possibility of using the options for applicability rules via Patch My PC Publishing Service. I looked for it in System Center Updates Publisher, which we don't use for productive updates anymore. Unfortunately, the above mentioned rule is specified in it. Never mind, please ignore it.

I have now done the following steps: the entry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{E4F354C3-4074-484E-9158-A74D9588652F} was present. When I changed the value under DisplayVersion from 3.2.3.20210624 to 3.2.3, the update was also provided to me for the client. I have now been able to recreate this on several clients. Strange.

Is it possible to change the value (test wise) in the update?
From 3.2.4.20210
To 3.2.4

<bar:RegSzToVersion RegType32="true" Key="HKEY_LOOP_TARGET" Subkey="\" Comparison="LessThan" Data="3.2.4.20210" Value="DisplayVersion" />

The problem with long version numbers is also familiar to me from MECM. Sometimes the value of the version number has to be changed from version (number) to text. Is this perhaps due to the locale?


Thanks a lot

Adam Cook:
Thanks for the detail! We will update this in the next catalogue release.

Andrew Jimenez:
This should be updated in today's catalog release. Please reach out if you still run into issues!

Navigation

[0] Message Index

[#] Next page

Go to full version