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

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Justin Chalfant (Patch My PC)

#136
The best thing you can do to support our app today is to share the word on social media and leave a Facebook review https://www.facebook.com/PatchMyPC/reviews/.

We don't currently take donations anymore, and this will be removed in the next update.
#138
During a silent installation, I believe our service would be auto-closed and reopen to close our handle on the DLL's.

Quote from: merlinfrombelgium on May 28, 2020, 06:19:47 AM
The PmP Publishing Service is installed on the only WSUS server in this environment. The same server is also the ConfigMgr (CM) Primary Site Server.

The CM Admin Console is normally operated remotely from this server. Which is why I didn't notice until today I that the CM Console wouldn't connect to the SMS Provider.



The Admin Console version on this server appears to be behind at version 1910. The Site is at 2002.



Upon running ConsoleSetup.exe from the CM tools folder, it tells me the PmP service is in the way of completing the update.



Could it be that the service prevents an auto-update of the console and eventually causes the 'cannot connect' error?
in any case, I wanted to make you aware of this. You might want to document this as expected behaviour if the WSUS server has the CM Console installed on it.
#140
Can you send a screenshot of the updated version being updated by our product?
#142
Can you please open a case using this link https://patchmypc.com/technical-support, and attach the logs requested so we can see when this is happening.
#144
A new update will be posted today for this product that will resolve this 404 download.

Quote from: fpr on May 06, 2020, 08:21:37 AM
We get errors when trying to publish Gant Project 2.8.11.
We are using SCCM Catalog for Updates on SCCM Server 1910 with latest hotfixes.

The errors is:
SyncUpdate: An unexpected error ocurred attempting to download content from 'https://github.com/bardsoftware/ganttproject/releases/download/ganttproject-2.8.11/ganttproject-2.8.11-r2393.exe':   SMS_ISVUPDATES_SYNCAGENT   06.05.2020 16:01:36   2636 (0x0A4C)

If I try to reach the link within a browser, I get a 404 error, so I guess, the link is not valid.
Any chance to correct that?
Thanks in advance!

#145
Unfortunately, WinMerge doesn't sign their install, so you will be unable to publish it directly using the in-console publishing feature. You can use our Publisher or SCUP as a workaround. More details about this error here: https://patchmypc.com/unsigned-updates-fail-with-error-srvmsg-sms-isvupdates-syncagent-updatecontent-trust-fail-badsig

You could also consider switching to our Publisher completely, more info here;

   What's the Difference Between Our Publishing Service and SCCM 1806+ In-Console Publishing? - https://patchmypc.com/faq-scup-catalog#publishing-service-vs-sccm-publishing


Quote from: fpr on May 06, 2020, 08:25:42 AM
When we try to publish WinMerge 2.16.6 x64 and x86 version, we get the following errors:

SyncUpdate: File 'C:\Program Files\Microsoft Configuration Manager\ISVTemp\eetywxs5.cbg\WinMerge-2.16.6-x64-Setup_no_support_for_per-user_installation.exe' does not appear to be signed or there was an error retrieving the signing certificate.  Signatures are required.   SMS_ISVUPDATES_SYNCAGENT   06.05.2020 16:02:12   17812 (0x4594)

and

SyncUpdate: File 'C:\Program Files\Microsoft Configuration Manager\ISVTemp\tz1xaynw.gaq\WinMerge-2.16.6-Setup.exe' does not appear to be signed or there was an error retrieving the signing certificate.  Signatures are required.   SMS_ISVUPDATES_SYNCAGENT   06.05.2020 16:02:36   18820 (0x4984)

We are using SCCM Catalog for Updates on SCCM Server 1910 with latest hotfixes.
Is there any chance to fix it?
Thanks in advance!

#146
Since this is a licensed app, you will need to do the instructions in this guide: https://patchmypc.com/local-content-repository-for-licensed-applications-that-require-manual-download

Quote from: fpr on May 06, 2020, 08:16:38 AM
We get errors since a while when trying to publish Cisco AnyConnect 4.8 Secure Mobility Center and Diagnostics and Reporting Tool.
We are using SCCM Catalog for Updates on SCCM Server 1910 with latest hotfixes.

The errors are:

SyncUpdate: An unexpected error ocurred attempting to download content from 'file://localhost/PatchMyPCRepository/anyconnect-win-4.8.03052-dart-predeploy-k9.msi':   SMS_ISVUPDATES_SYNCAGENT   06.05.2020 16:01:34   16504 (0x4078)

and

SyncUpdate: An unexpected error ocurred attempting to download content from 'file://localhost/PatchMyPCRepository/anyconnect-win-4.8.03052-core-vpn-predeploy-k9.msi':   SMS_ISVUPDATES_SYNCAGENT   06.05.2020 16:01:34   16504 (0x4078)

I'm pretty sure the download link is wrong.
Is there anything we can do?
Thanks in advance!

#147
Quote from: [email protected] on April 28, 2020, 03:37:39 PM
We don't understand how most apps work, but a few do not. Are we supposed to whitelist all of the domains listed?

It's probably based on the firewall/filter it's common for not all to be blocked. You need to whitelist the domains of any products you enabled.
#148
Thanks for the information, we are going to review this product today. If it does add the shortcuts for us, and there is no command line to suppress it we will be removing this product from the home updater.

Quote from: voltagex on April 26, 2020, 10:30:44 PM
See attached screenshots - you can see the file that's dropped if you unpack the installer with innounp
#149
These rules aren't correct, here's a direct view from the catalog schema for this update. The only variable would be a possible SCUP issue in the import that lost some of our rules.


Quote from: BobS on April 24, 2020, 02:54:07 PM
And, this:
#150
Hey Bob,

I think I remember this in the past. This appears to be a SCUP bug. Our rules are not MSI only I would recommend reaching out to Microsoft on this issue. Our update always had the Program Files rules included.