Read my update: https://daniel.streefkerkonline.com/update-deploying-myob-premier-via-msi/
After many attempts over the years to get MYOB Premier deployed via AD GPO, I stumbled across a method this morning using only free tools.
These two tools are an essential part of my MSI toolkit, keeping in mind that i’m not some sort of MSI guru like the guys at appdeploy.com
1. Orca
2. WinInstall LE 2003 (WinInstall LE 2003 used to be distributed for free, but now you have to trawl around the net to find it)
The steps are as follows. I used this method for Premier 11, so that’s what i’ll use below.
- Import Premier’s MSI into WinInstall, making sure you tick the option to copy the source files
- In WinInstall, turn off components you don’t need installed. I did this over creating a transform file, as that’s overly complicated for my needs
- Close WinInstall and open Orca
- Delete CustomAction->ISVerifyScriptingRuntime
- Change Directory->ISYourProductDir to “PREMIE~1|Premier 11”
- Change Directory->ISYourCompanyDir to “MYOB|MYOB”
- Change Directory->KEY_NAME_SC to “MYOB|MYOB Premier 11”
- Save the MSI file and close Orca
This worked for me, so good luck.
User Error 
And then deploy using msiexec.exe /i?
Problem with that is that OfficeLink doesn’t get installed. At least that’s what I’m finding at the moment. This means reports etc can’t export to Excel.
Does your package, once installed, properly export to Excel?
I’m pulling my hair out trying to fix this.
LikeLike
By deploy, I meant by using Group Policy Objects in Active Directory.
I normally export stuff to Excel in CSV format, as it’s a rare occurrance.
LikeLike
Pingback: User Error