• Welcome to Support Forum: Get Support for Patch My PC Products and Services.
 

Recent posts

#1
I've been getting the following error since last week:

"A web error occurred while downloading the file: ConnectFailure Unable to connect to the remote server"
#2
Hi there, can anyone assist with troubleshooting a post-install script for an Intune App? The relevant Script Runner log lines are below:

<![LOG[Running script TVPI.bat]LOG]!><time="11:13:36.186730" date="10-15-2024" component="ScriptRunner" context="" type="1" thread="1" file="">
<![LOG[Running Bat Script. ]LOG]!><time="11:13:36.188731" date="10-15-2024" component="ScriptRunner" context="" type="1" thread="1" file="">
<![LOG[Exiting With code: 403]LOG]!><time="11:13:36.577587" date="10-15-2024" component="ScriptRunner" context="" type="1" thread="1" file="">

If I copy the BAT file locally and run from admin cmd it works perfectly. From the error code I guess its not able to find or open the BAT file, but why not?  Image of the Post Install config for the app is attached.
#3
PMPC custom apps can be an alternative to using PSADT + ServiceUI to prompt the user to close running apps. You would not need to combine both, but you could of course upload a PSADT script purely for its installation logic - I would not try to mix and match UI elements from both.

Also, if just using PSADT + ServiceUI, PSADT now has an example launcher script that solves the original problem you describe (where running serviceui.exe with no users logged on results in an error):

https://github.com/PSAppDeployToolkit/PSAppDeployToolkit/tree/main/Examples/ServiceUI
#4
I will discuss this internally - but normally we only configure updates to be able to detect and migrate from a different package type (e.g. EXE->MSI or x86->x64) when the vendor just offers a single installer type and they changed it.

There are a few options at your disposal to migrate users over - for example you can create a pre-script that will allow the EXE variant to uninstall the MSI (this script can help), then push this out to a collection of all devices that have the MSI variant installed.
#5
Sorry about that, I just switched it to v24.003.20112
In the next major home updater, We will only use the Acrobat 64-Bit MUI EXE, so it will always be up to date and will work for everyone with every language.
#6
Hi Dan, we'd appreciate an option to rollover our clients from MSI to EXE for VLC since it might be a while before this is resolved, can we have a seperate SKU for VLC just for this purpose?
#7
I would like to rate this article as very good and comprehensive. The author has presented clearly, providing insight into the topic.
#8
Hello,

This is the only report of this issue we have received. Would you please open a support case here: https://patchmypc.com/technical-support and provide the logs listed here: https://patchmypc.com/collecting-log-files-for-patch-my-pc-support#application-troubleshooting-client-logs-intune

Thanks!
#9
Patch My PC 4.5.0.4 | Definitions: 13-October-2024 | 10/14/2024 1:41:45 PM

Failed to get download information for Acrobat Reader DC 24.003.20180 Download URL: https://ardownload2.adobe.com/pub/adobe/reader/win/AcrobatDC/2400320180/AcroRdrDC2400320180_en_US.exe

Not Found
The requested URL /pub/adobe/reader/win/AcrobatDC/2400320180/AcroRdrDC2400320180_en_US.exe was not found on this server.

Only seems to affect the 32-bit .exe download. The 64-bit .exe link as well as the .msp links for both architectures all seem to work. Not sure why the 32-bit MSP download is under /pub/adobe/reader while 64 bit is at /pub/adobe/acrobat, but changing acrobat to reader doesnt seem to fix the 32-bit reader .exe download

MSP Downloads
64 bit works: https://ardownload2.adobe.com/pub/adobe/acrobat/win/AcrobatDC/2400320180/AcroRdrDCx64Upd2400320180.msp
32 bit works: https://ardownload2.adobe.com/pub/adobe/reader/win/AcrobatDC/2400320180/AcroRdrDCUpd2400320180.msp

EXE Downloads
64 bit works: https://ardownload2.adobe.com/pub/adobe/acrobat/win/AcrobatDC/2400320180/AcroRdrDCx642400320180_en_US.exe
32 bit broken: https://ardownload2.adobe.com/pub/adobe/acrobat/win/AcrobatDC/2400320180/AcroRdrDC2400320180_en_US.exe
#10
I was able to repo this in the lab. Issue is that the Adobe installer is creating the icon after we initially delete it during our processes.

But, if you add 'DISABLEDESKTOPSHORTCUT=1' to the command line, the shortcut will not be created by the installer.

You can do this by utilizing the 'Modify Command line' feature.