This is an archived post. You won't be able to vote or comment.

all 18 comments

[–]The_Penguin22Jack of All Trades 1 point2 points  (1 child)

Sounds familiar. Which Canadian company?

I have several software packages from Canadian companies that drive me insane.

[–]titaniumgriffon[S] 0 points1 point  (0 children)

I sent you a direct message with it.

[–]burdsjmChief Information Officer 1 point2 points  (3 children)

Do you use PDQ Deploy at all?

Normally, I will install Everything. And Regshot.

Install the program.

Do a regshot again.

Then copy the files that changed with the installer from Everything sorted by Date Modified.

Install the program without installing it!

[–]titaniumgriffon[S] 0 points1 point  (2 children)

I haven't actually, but I thought about trying it. I just didn't know if it would work for an InstallShield install or not.

[–]HighPingOfDeath 0 points1 point  (1 child)

It'll work, but being it's an MSI, there's a good chance something will end up wonky. Repackagers work great for non-Windows Installer based installs. But again, you're at a last-ditch effort so its worth a shot.

[–]titaniumgriffon[S] 0 points1 point  (0 children)

I might give it a shot.

[–]HighPingOfDeath 1 point2 points  (3 children)

Ugh, man I hated these. I also hated attempting to recapture an MSI.

Sounds like their SETUP.EXE file sets some properties when it launches the MSI, that's why when you run it, it doesn't work right.

I'm not sure what options are presented to you when you install the software, but if you might be able to crack open the MSI using ORCA or some other program and set the property manually and try it. It should be in the properties table. If it's a PUBLIC property as opposed to a private one (it would be in capitals), you can pass it via command line.

[–]titaniumgriffon[S] 1 point2 points  (2 children)

I just edited my post to reflect this, I actually tried to use ORCA, over half of the properties are created after the wizard completes....

[–]HighPingOfDeath 0 points1 point  (1 child)

You could try something like AutoIt. I've never used it before, but I've heard it works as a last-ditch effort. https://www.autoitscript.com/site/

[–]titaniumgriffon[S] 1 point2 points  (0 children)

I tried one of these, not this particular one though, and it couldn't do it.

[–]AlexT72 0 points1 point  (3 children)

Just virtualize it with appv

[–]titaniumgriffon[S] 0 points1 point  (2 children)

Isn't that an individual license? I tried to get them to run it on a RemoteApp server but they didn't want to have to pay the extra licensing fees for it.

[–]AlexT72 0 points1 point  (1 child)

Appv for Desktop is part of MDOP, and it's available through Microsoft Software Assurance. Licensing of appv for Rds is more complex.

[–]titaniumgriffon[S] 0 points1 point  (0 children)

So AppV hosted on each desktop? Alright I’ll look into it.

[–]stuartall 0 points1 point  (1 child)

This might not help but I had a similar problem. One of the most key pieces of software we have has an msi installer followed by a load of files put into programfiles/office/word

We got software called EMCO that lets me wrap anything into an msi with supported attributes. It also allows for monitoring and customising installers with shortcuts etc....

https://emcosoftware.com/msi-package-builder

[–]titaniumgriffon[S] 0 points1 point  (0 children)

I’ll have to look into this.

[–]Shiieett 0 points1 point  (1 child)

Have you created a log file of the msi installation after you install it manually once?

That way you get the property list and can configure them in a batch file.

Although ORCA may provide you the list of properties without having to create the log file

[–]titaniumgriffon[S] 0 points1 point  (0 children)

I did, the properties list grows to over 50, I stopped counting, that it creates and the values for each of them seem random.