Deploying MSI with an MST file (SCCM)

WARNING: You currently have Javascript disabled!
This website will not function correctly without Javascript enabled.

ahaines

8 discussion posts

Hi, I'm looking to push out 9.1 to the PCs in our organisation that make use of DisplayFusion (most using 7.1 at present).

I've managed to script an uninstaller as we did have issues with it rebooting if in use and leaving behind a second installer (as two items are registered in Programs and Features). I've now got to do some test upgrading to 9.1 and this has worked fine. Annoyingly when I deployed it to our organisation the MSIEXEC process seems to get stuck during the install.

In System Center I've set a 60 minutes timeout and at this point it returns a failed/timed out installation, but the MSIEXEC process continues to run. From looking at the MSI readme you need to use a transform file in order for it not to stick, which I have done. I've have the following customisations:

Code
Copy
Select All

CUSTOM1=/VERYSILENT
CUSTOM2=/NORESTART
LAUNCHAFTER=1
STARTUPALL=1
STARTUPUSER=0

The guide does mention that you need an MST for it to be successful but also seems to suggest that the settings need to be:

Code
Copy
Select All

CUSTOM1=/VERYSILENT
LAUNCHAFTER=0
STARTUPALL=1
STARTUPUSER=0

Is it the LAUNCHAFTER property being set to 1 in our MST that is causing this issue?

May 10, 2018 • #1

That's the one, yep! If LAUNCHAFTER is enabled, the installer tries to launch DisplayFusion when it's done. But if the installing user is local system, or some other user that's not currently logged in, then it just never finishes. Setting LAUNCHAFTER=0 will prevent that, and DisplayFusion will still launch the next time a user logs in, assuming STARTUPALL=1.

If you have any further questions, definitely let me know.

Thanks!

May 10, 2018 • #2

ahaines

8 discussion posts

Thanks for clarifying. It's odd that my test VMs (and my own PC) didn't experience this same error.

We have about 100 PCs that now seem to be stuck in this state, I'm hoping if it attempts the install again with the newer MST file it may complete.

May 10, 2018 • #3

It might fail due to the installer already being running. The only thing I can think of there would be to reboot the machines before deploying the installer again, unless you can remotely kill the DisplayFusion setup process on the machines.

May 10, 2018 • #4

ahaines

8 discussion posts

Yes, the MSIEXEC process is still running on the majority of PCs. I've hopefully killed the processes remotely on all that have reported as failed.

When I manually did this and tried to install DisplayFusion after it stated that SYSTEM had a suspended installation that needed to be rolled back, which was fine.

See what tomorrow brings! Thanks again

May 10, 2018 • #5

No worries, let me know if you have any further questions.

May 10, 2018 • #6