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

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

Topics - swoonhusker

I have an application install that silently installs a BIOS update but I would like to notify the user that they need to restart and give them the option to snooze/dismiss only to bother them about it again later in the day.

I love the PMPC notification that pops up for Intune updates and was wondering if it's possible for me to use this on my application?
Hello, I'm creating a custom app with an exe for InfoZoom (InfoZoom_2023_en-US.exe). It looks like the install is running but will time out because it is running in the background. Is there a way to run it without it being silent? I see the "Silent Install Parameters" is required when created it and I don't know why that is.
We have GlobalProtect 5.2.9 required to our autopilot device group so that it installs in the ESP.

I want to pilot GlobalProtect 6.2.2 but I'm not sure how to avoid 5.2.9 re-installing automatically.

In our testing it looks like we have to have an app (5.2.9) required for it to install in the ESP. If it is just in the ESP without a required deployment, then it will not install, so it has to be required.

So to pilot 6.2.2 the options I've found are:
1. Add a requirement script to version 5.2.9 so that it won't install if a newer version is installed.
2. Exclude a pilot collection from the 5.2.9 deployment.

If I did option 1, I see that PMPC gives the option on Intune Apps/Updates to "Override Win32 application options" and then to "Copy the requirements from previously created applications or updates when an updated application is created". This would stop a newer version such as 5.3.0 (if it existed) from installing if it was released and packaged by PMPC.

Option 2 isn't ideal if the pilot group was made available and some people are choosing to install it and some are not. We would have to get their devices and add it to a device collection.

I also considered turning on supersedence for 6.2.2 but I believe it would automatically upgrade everyone in the pilot users group (that's only an available deployment) from 5.2.9 to 6.2.2 and we don't want that to happen.

Is adding a requirement script to the old version (and using PMPC's option to copy the requirements) the best option we have in this scenario? Or do you have any better suggestions? I wonder if others have found a better way to make an available deployment of a new version of an app that has an old version of the app required because of the autopilot ESP.
In the PMPC right click options I'm able to change the Application name, localized name, description, and icon but I don't see the option to add keywords.

If I do this in the application in config manager, will it stay when the application is updated?

I'm setting up Java 8 update 221 as a base application and then will also setup the update rule, but I am hoping to get some advice from experts on here who have customized parts of the install with pre/post install scripts.

Here is what I have working so far:

-My post install script correctly changes the Java_Home environment variable.
-We manage Java exception sites with group policy.

Here is what I would like to figure out the best way to achieve:

-Our previous manual Java package (before Patch My PC) had us alter the baseline.versions file and change the revision number to one higher than what we downloaded. I'm wondering what is the purpose of this and is it necessary?
-I want to set some advanced settings in the Java control panel which include:
     -Mixed code security verification
     -Perform signed code certificate revocation checks on
     -Perform TLS certificate revocation checks on
-I would like to eliminate the Java expiration, messages about "do you want to run this application", and messages about "Java update needed"

Our old manual Java package had us make a lot of these changes in the deployment.properties file. I'm wondering if I were to update this file with a powershell script post install, would that achieve the same result or does something need to be done before install?

Please help me find the best way to achieve these. I would like to do them with a pre/post installation script if possible, but I would also be willing to use group policy if needed.