Add "GraphPad Prism" to Supported Products

Good News! GraphPad Prism has been added to the catalog as of today - https://patchmypc.com/patch-my-pc-catalog-update-08-08-23

You can edit the cmd line to point to the xml file you distribute to these users separately from PMPC and call out an uninstall if you have an older version installed already.


from their install notes PDF:

The MSI installer supports the following switches to allow you to customize the installation:

QUIET - standard MSI switch to perform installation without displaying a user interface

STARTUPCONFIGPATH - path to xml configuration file to be copied to install dir

UNINSTALLPRISM9 - uninstalls Prism 9, defaults to 0

UNINSTALLPRISM8 - uninstalls Prism 8, defaults to 0

UNINSTALLPRISM7 - uninstalls Prism 7, defaults to 0

APPDIR - specify the installation directory

STARTPRISM - launch Prism after installation, can be 1 or 0

A common scenario is when you want to: do a silent installation, install to the default Program Files

directory and deploy XML configuration file for silent activation. You may use STARTUPCONFIGPATH to

install the configuration file, but this file must be present on the client computer that the MSI installer is

running on. You cannot designate a server name, IP address or mapped drive letter. Here is an example

for that scenario:

msiexec.exe /QUIET /i "path\InstallPrism10.msi" STARTUPCONFIGPATH=c:\temp

If the folder name includes spaces, use quotation marks around the path:

msiexec.exe /QUIET /i "path\InstallPrism10.msi" STARTUPCONFIGPATH="c:\some temp folder"

If you want to install Prism into a custom directory, use APPDIR like:

msiexec.exe /QUIET /i "path\InstallPrism10.msi" APPDIR="C:\Prism\"

By default, the Prism 10 MSI installer will leave Prism 9 installed if they exist in a different directory. If you

want to uninstall Prism 9, use UNINSTALLPRISM9=1, like:

4

msiexec.exe /QUIET /i "path\InstallPrism10.msi" UNINSTALLPRISM9=1

If you want Prism to launch after installation use STARTPRISM like

msiexec.exe /i "path\InstallPrism10.msi" STARTPRISM=1

Note that if you use /QUIET switch, STARTPRISM is ignored.

We have version 9.3.1.471 in Intune that will need to be updated to current, we will not maintain multiple versions once this becomes available through PMPC. Can this be handled with Intune's Supercedence? Or will the upgrade happen through script?

Nothing personal against anyone here, but the installers that make it through PMPCs Publisher need to come from the official source. I'm assuming that would always be the case.

I have installers for v7, 8, and 9. Historically it's been my experience that upgrading versions doesn't uninstall previous versions, it installs them to a new folder in Program Files with the updated versioning. Minor updates do not do this. They can, however, both read the same license so you can have 8 and 9 installed, for example, and have both function.

Let me know if you would like installers and I can get those to you. I don't think we kept them for all the point updates though.

Ok, thank you. I will do some more testing later today / tomorrow and I'll plan on adding just the latest version. If the need to maintain previous major versions comes up we can always add them later.

Here is a link to version 9. I'm not sure about the licensing, I think it needs to be active to use the application so I don't think versions should need to be separated but I'm sure someone else will chime in with more experience.

https://somumaryland-my.sharepoint.com/:u:/g/personal/mkyser_som_umaryland_edu/EUSil888vAdFqVC-nNj7sDcBEwduHe-TA1jvxJKFJTuBeQ?e=rD4DTj

Looking for additional feedback to assist with getting this application added to the catalog. Should we separate each major version (i.e. 9, 10) and only patch within those versions? And/Or upgrade from any older version to the latest? I'm not sure how the licensing works, so wanted to ask those who are more familiar with the application. Also, does anyone have a link to an older version of 9 or 10 (not the latest)? We would need an older version to validate the update process within each major version. I tested an upgrade from 9 to 10 but it leaves the old version behind so just want to confirm whether the upgrade behavior is the same or different within a specific major version.

Very glad to see this changed to Started, particularly relevant timing with version 10 released recently. As Paul said below, the installer can have an xml file included in the same directory that it is installed from. This is not a required file, but one of the things it includes is the license key so it will auto-activate.

I know you've cancelled adding other software to Supported Products because of this additional file requirement, but in this case it's not required. Even if you don't think you can support the install, having at least the Updates supported would be so helpful. Thanks!

https://www.graphpad.com/updates is the download link to the latest version. Install needs an .xml file in the following format with the name "prism-config.xml" in order to auto-activate, but isn't required to install, will prompt for code on running.
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<silent-activation>true</silent-activation>
<serial-number>#####</serial-number>
</configuration>

Mutiple installs here as well, and no easy version upgrade path. Please add to the library!

Hundreds of installs as well - would be great for life science industry.

Second this, we have hundreds of installs of this deployed, and are paid enterprise customers.