Topics

I have published UltraVNC to Intune using the PatchMyPC Publishing service.  After testing the install on a client, I changed some of the settings for the app in the PatchMyPC Publishing settings (Added an inf file to include and added the /loadinf parameter to the command line).  After running a publishing service sync, I tested the app install again on a pc, but it doesn't appear to have used the updated command line or inf file. 

Looking through the patchmypc log file (attached), I see when the sync ran it updated the updated command line argument and the additional file on the package source for configmgr and triggered a package refresh, but when it gets to the intune part it just says that the app is already published, with no indication that it sees changes which need to be published to the server.

I've been looking forward to SCCM 1806, so that I could use the new Third Party Updates feature instead of SCUP to import the PatchMyPC catalog. I was able to add the custom catalog successfully, but when I try to subscribe to the catalog I'm getting an error. 

Unable to create the subscription.  The console failed to download "PatchMyPC Updates" from "CATALOG URL" because of error code 193.  For more information, see SMSAdminUI logfile.

The log file referred to in the error message only contains one line related to the subscription attempt, which is not at all helpful:

[84, PID:5328][08/06/2018 10:38:37] :error in downloading

As a test, I pasted the catalog URL into Internet Explorer, and successfully downloaded PatchmyPC.cab, so the URL seems to be correct.

Does anyone here know what the error code '193' represents? 

What could be causing this to fail?

Edit: I just found the new guide you posted for this.  I decided to add the trial catalog, as the video demonstrated.  After adding the trial catalog, I was able to subscribe to it successfully.  I imported my patchmypc catalog URL in SCUP (my previous SCUP db was lost, so when I launched SCUP it was a fresh instance with no catalogs configured.), and it successfully imported the catalog contents. So, again, this would seem to confirm that the URL is valid, as I was able to import it in SCUP.  It's only SCCM that fails to download / subscribe to the catalog. 

Someone pointed out to me today that Java 8 update 66 has been available for download since early November, but we're running v8.55.  Looking in SCUP, it appears that PMPC hasn't put out an update for 8.66.  Was that an oversight, or is there a reason it was left out?

Thanks!

I think we're at a point now where we can deploy Java 8 without breaking anything, but now that I'm ready to do it, I wonder about the best way to do it.  Java 7 updates have been coming via the patchmypc catalog, so I don't have an application in SCCM for the version of Java 7 currently installed on our workstations.  That means I can't mark the Java 8 application as superseding the Java 7 application.  I considered just adding the guid for the Java 7 version to the "installable rules" for the java 8 update in SCUP, but would that uninstall Java 7 in the process or simply install Java 8 along side 7?

At this point, I'm thinking my best option would be to create an application for Java 7 update 71 (we hadn't moved up to 75 yet), and use it just for the sake of being superseded by the java 8 application, to be sure it uninstalls.