Messages

Hello,

Thank you for posting about this issue. We rolled this back within our catalog a few days ago, on 10/28/24, to version 8.0.38:

https://patchmypc.com/patch-my-pc-catalog-update-10-28-24

If you still have retained older version(s) of the application content we have the following articles detailing how to perform a rollback:

Intune --> https://patchmypc.com/how-to-rollback-a-third-party-update-in-intune
ConfigMgr --> https://patchmypc.com/how-to-rollback-a-third-party-software-update-in-configmgr

Respect! You are fast!
Thank you very much!

Hello PMPC team,

Apologies for the bold request in the subject, it was reported to me from a fellow DBA colleague that the latest version of "Oracle MySQL Workbench Community Edition 8.0.40 (x64)" has issues connecting to data sources. He has investigated further and the developers admitted that they omitted authentication plugins from the latest build as stated here Workbench 8.0.40 Authentication plugin not loaded.
Please remove it from your metadata for updates and new/updated applications as it will be replaced, also it would be great if a supersedence is set to version 8.0.38 for the updates as it will make easier the downgrade.

With regards

Hello,

The recommendation can be found here: https://www.adobe.com/devnet-docs/acrobatetk/tools/Wizard/basics.html#transform-mst-file-basics

• Once an MST is applied during an install, another MST can't be used later during an update (say, to change one setting).
• During an update or repair, the installer references the MST file that the installation used when it was first installed.
• The only way to use a different MST is to uninstall the product and then reinstall with a new MST file.

Perfect! Thank you a million Andrew!

Hi Andrew,

Thank you for the quick reply, can you please provide a link to Adobe's recommendation?

Thank you

Hello,

From time to time, Acrobat's auto update internal process is misbehaving and errors out.
In order to raise the compliance percentage, we are investigating the possibility to push updates through our PMPC service.
However, the initial installation of Acrobat Pro is happening via SCCM and the usage of an MST customization file.
The question here is, if we have to apply the MST file also when we update the product, does it make sense or it is not required from your experience PMPC engineers?

Thank you

Our plan is to remove the VC++ 2015-2019 and move to 2015-2022. Microsoft no longer provides updates for 2015-2019, and 2015-2022 should cover 2015-2019 when it is installed (this is why it does not let you install 2015-2019 when 2015-2022 is already installed, they are actually the same app and 2015-2022 is just a newer version).

We'll need to adjust the applicability rules for 2015-2022 to allow it to upgrade 2015-2019, then remove 2015-2019 from our catalog. I expect this to be completed by the end of March 2023.

Thanks for the reminder on this!

Happy New Year Andrew!

Has this change shipped? I still see updates of 2015-2019 trying to install when we do imaging/reimaging of devices.
At least for the runtimes published as updates, wouldn't it make sense to set the 2015-2019 as superseded by 2015-2022?
This would make our lives easier as we can target the 2015-2022 to machines that have 2015-2019 and upgrade them, right now they are just clashing.

Perfect!
Thank you and have a nice weekend!

Great news, thank you Andrew!
I guess it will be stated in the notification emails right?

Hi Andrew,

I checked on Microsoft's SharePoint resources for the VC++ requirements and it seems that we can go with 2015-2022 for the versions of SharePoint 2016 and onwards.
Also checked our servers and discussed this with our SharePoint Admins and we reached to the conclusion of using that one and replacing the 2015-2019 were it is installed.
Did you do any research from your side?

Yeah, we originally added DDM 2.x to the catalogue where it would uninstall 1.x. However we found supporting documentation that Dell suggests DDM v1 and v2 are independent and v2 isn't always the best option for some monitors. Therefore we added it as a separate product and fence of detection/applicability between the major versions.

That makes a lot of sense, the .Net 5 requirement is also a blocking issue as many of us don't include it in the standard list of software/runtimes.

Word of mouth suggests Dell are releasing an update for DDM 2.x next month to include a newer version of .NET.

Nice to know Adam! Thanks for sharing that info.

Our plan is to remove the VC++ 2015-2019 and move to 2015-2022. Microsoft no longer provides updates for 2015-2019, and 2015-2022 should cover 2015-2019 when it is installed (this is why it does not let you install 2015-2019 when 2015-2022 is already installed, they are actually the same app and 2015-2022 is just a newer version).

We'll need to adjust the applicability rules for 2015-2022 to allow it to upgrade 2015-2019, then remove 2015-2019 from our catalog. I expect this to be completed by the end of March 2023.

Thanks for the reminder on this!

I had a discussion with a SharePoint Admin colleague because I noticed that the installer installs the 2015-2019 redistributable, so AFAI understand, it will not be easy to get rid of it (I would love to have a clean environment with less versions to maintain).
Could you check with the SP PG if this is a hard requirement and if it can be covered by the 2015-2022 redistributable please?

Clock is ticking for MMS-MOA

Thank you very much Andrew!
If you're going to MMS-MOA in May, it would be great to meet there and talk about the product.

Dear moderators,

I was checking the options to change my profile's avatar and in the list there is an option named [custom], while I was browsing through I realised that those are the uploaded avatars of the forum's members.
I would like to request you to hide this option because it is exposing personal data to other users without consent.

Thank you

Hi Andrew,

Just checking if there is any development on this request.

Thank you!

Hi TimothyG, it seems this version is not a straight forward upgrade to 2.0.0.135 from 1.56.2110 and requires more testing.

First thing it's x64 only now I think.

Secondly the installer now is 62MB with a new Logo and new vendor. The previous installer was ~900KB.

Thirdly, it doesn't remove the previous version, and it seems the silent installs witch has changed.

I will update you as soon as I can.

4th The new version works much better than version 1.5 

I was about to request the detection of <2.0 versions and their removal before installing version 2.x on x64 devices, glad I found this thread!
However, I would like to ask for this to be extended to the updates section also, is this feasible Adam, Ben?