Messages

Hi Alex,

Yes the manually created relations of supersedence etc should be retained as the application updates to a newer version.

There is also a user voice about it you might want to upvote as well to stay up to date with it - https://ideas.patchmypc.com/ideas/PATCHMYPC-I-369

Hi Paul,

Thanks for that information I'll pass it onto our app support team

Hi Owaine,

If the correct file was placed in your local content repository then it would create the app/update for your Intune tenant.

To confirm can you please attach your patchmypc.log file or if it's easier email us at [email protected]

Hi,

We have had this idea come up previously on our ideas page.

https://ideas.patchmypc.com/ideas/PATCHMYPC-I-396

Currently, you could create your own schedule using a scheduled task, or any scheduling mechanism, and use the feature that was linked in another comment to trigger the synchronization from the command line. Does that capability fill this request?

https://ideas.patchmypc.com/ideas/PATCHMYPC-I-413

Hi Tyler,

We have a supported products page here - https://patchmypc.com/supported-products

If you have an app in mind that does what you're after which isn't on our supported products page, you can either put a request in via our ideas page - https://ideas.patchmypc.com/

Or we currently have custom apps in public preview you can try out and I've got some instructions for that here - https://docs.patchmypc.com/installation-guides/custom-apps-preview

Hi Dhammond,

For this Forticlient product, you will need to download the FortiClientSetup_7.0.11.0569_x64.zip, grab the MSI from the zip folder and put it into your local repository. The hashes should then match what we are expecting and this can be published successfully.

Is that the normal and expected behavior?

Yes, that's normal behavior, the publisher can create the apps and send them over to the SCCM console and from there it doesn't have access to remove.

If you remove apps from the publisher that won't sync and remove them from the SCCM console you would need to manually remove them.

Am having some issues with the internal updater in VSCode being 'on' by default when the app is pushed out via PMPC.
VSCode will initially deploy just fine, but the internal updater will attempt to update as soon as there is a new version and breaks the install.

Hi Trevor,

When you mention it attempts to update and breaks the install could you please elaborate on that?

We're now thinking about the SCCM-integrated WSUS environment, and whether it needs to continue operation.  Since we won't have a need to publish updates into WSUS-->SCCM, can we safely shut down WSUS?  Does PMPC have any dependency on WSUS for the other three functions (SCCM apps, Intune updates, Intune apps)?

Hi Korebreach,

You can simply uncheck the Updates in the publisher and that will stop any new updates from going through.

same here. I already tried to uncheck and check the default .net framework packages from "install features", I already run "sfc /scannow" and also I tried to repair the .net framework 7, but nothing changed.

I have the following .net framework packages installed:

Have you tried uninstalling and reinstalling the publisher on there?

-i "PATH_TO_CONFIG_FILE"

You could add that to the right click option modify command line

Hi,

Depending on the customizing you want to achieve, you can use the postscript to add the config file and then reference it with a script.

Did you have an example of what you are trying to achieve?