Messages

I have been seeing the same issue with this new version. I just got the rest of it dialed in correctly to deploy as an upgradable app, then this happens. So, is the change to the Deployment Type Progam going to stick with the latest app version, or will we need to go in each time the product updates and change this?

Re-Bumping, I guess. I tried to add this to the modify command line, but it doesn't add it to the /msi switch, which it would seem Adobe needs. I am really hoping there would be a way to do this, as this Continuous installer doesn't seem to cache the Acrobat Pro components even though the AcroRdrDCx642400420272_en_US.exe compressed file does contain the needed AcroPro.msi to install Pro. As such, the installer downloads the content from adobe when you sign in. If it could do the optional component switches, it should cache those so it's not pulled from Adobe. The main issue is, I have been seeing the downloader adobe uses is a bit buggy and visibly throws an error during the upgrade process from Reader to Pro. Not great from an end-user perspective. Throw me a bone?

Bump. Should I open a ticket for help with this? I was looking to use some of the command switches adobe lists in their docs for the Acrobat unified installer.. See here: https://www.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/singleinstaller.html
This is the part I am looking to add:
Optional components for 64-bit installs
Verify you're adhering to the Product compatiblity upgrade matrix.
Run the following:
Setup.exe /sAll /msi ADDLOCAL=OptionalFeatures,DistillerCJKNative,DistillerCJKSupport,PaperCaptureOptional,
PreFlightPlugin DISABLE_FIU_CHECK=1 TRANSITION_INSTALL_MODE=4 SKIP_WEBRCS_REINSTALL=1 SKIP_CEF_KILL=1

I am assuming I would add this to Modify Command Line? Will it work? If so, the issue is that I do not seem to be able to add lines that long (there is no character limit specified on the GUI), and I might also not be certain if it would work.

The idea here would be to install (but not activate) the optional components embedded in the local installer rather than relying upon the upgrader to download the Acrobat Std/Pro content from Adobe.

Help?

Thanks, Michael! More questions. Do the command switches referenced in the Adobe article you provided work with PatchMyPC? So far, I have been a little disappointed with Adobe's docs on this. What I was looking for was whether PatchMyPC's Acrobat 64bit unified install contains the upgrade files to upgrade to Pro (if or if not the proper command switches are used).

Thanks!
SS

I have added the pre-script and deployed it to a system with the MSI install of VLC 3.0.20.0 and the app deployment is showing 3.0.21 as installed, but the installed version is still the MSI version 3.0.20.0. Should it not see the 3.0.20, uninstall MSI, and install EXE, because it's not.

I understand that the Acrobat 64-bit installer contains the components for Acrobat Reader as well as the support for Acrobat licensed versions. I would like some understanding of how this version could be used to deploy to our environment in a fashion where users with an Acrobat Pro license would be able to use this version via some form of automation. Finding minimal information from Adobe, so if anyone has direction it would be appreciated.

Just receiving this report, but some systems are reporting that the Wacom Tablet Driver is requiring a system restart after updates apply with little time after restart. Not sure how many, but our default client setting is for updates is around 20 hours. This update was in a cumulative deployment so deadline is in the past. It is definitely different behavior than with other PmPC updates. If it is a simple as adding a /nostart to the modify command line option, I'll do it. It just seems like this should be in line with all of the others. Attached my managed conflicting app config which is our default.

I concur in asking for an update. I agree that this should generally on the software vendor, but if you offered to script the removal of the MSI version, that would work around this vendor's lack of action.

A curious point. It does seem that they should elevate the rating on their releases when they flip to 0-day. Does the text in the description for each product always come from the release notes? I would assume so. It probably explains how the text is always so different (Chrome never mentions High for their CVEs). I know PmPC is only going by what the developers release. Thanks for your help!

I've been trying to find a good set of parameters to use for catching Chrome, Edge Chromium, and Firefox updates, but I have noticed that they never seem to be listed with severity "Critical" despite being declared a 0-day eventually. That might be the way updates are classified and do not change, perhaps? So far, I have looked at this criteria:
Severity is "Important"
Description contains "CVE-2024" (which works for Edge Chromium and Mozilla Firefox) and "High CVE-2024" (which works for Google Chrome).

I am mainly curious if there is anything which differentiates an update as 0-Day (which by my perspective should be upgraded to "Critical."

Any help would be appreciated.
SS

I appreciate the OP's reason for this. If the PMPC notification window is generally all the users see, it would be preferred to have something with the same visual. The company logo, same general text, etc. Is there any chance on earth that window could be wrapped up in a form we could reuse? I have tried to use Powershell to script a dialog box, but it would take me a long time to make it look exactly like the PMPC box. I already have a script to check if a reboot is pending on a machine, if no user is logged in, reboot. If use is logged in, prompt to reboot or postphone for 1 day. After 3 days, it will reboot. But what it looks like is everything. Would love for it to look exactly like PmPC's box because that is now the Enterprise standard for us.

We are updating VLC for EXE x86, EXE x64. and MSI x64. I am seeing that this new release 3.0.21 does not seem to have a version for MSI x64. Is that per the developer or something we need make plans for? We have 1275 on EXE x64 but we also have 972 on MSI x64, so we will need to work through migrating them all to EXE x64 if this new version will not be updated any longer. Please let us know.

So I cannot figure out how to attach images, but we have both of those boxes ticked and I have 7 versions. 2 of which have no version numbers. All x64. Also, the 2nd from the latest version shows revision is at 48. Is that a lot? From the non-numbered, there are only 2. One is Edge 124.0.2478.51 (the one with 47 revisions), the other is 125.0.2535.79. The remaining 5 have version numbers between 120.0.2210.144 and 125.0.2535.67.