New Contributor

Hello all, I feel as if I should know this, but admittedly, I do not...

Is there a good method to follow for deploying MPKG's? In particular, the
new XML File Format Converter from Microsoft, or any of their other

Part two of this, is what about installers that have EULA's, or other parts
of an installer interface that require user intervention?

Thanks all...
-- Tim Nicometo
Mayo Clinic
timn at
(507) 255-3034


New Contributor

I pretty much never push out packages just for those types of reasons. Just build a dmg and include the pref, all problems solved.

Eric Winkelhake | Technology Services ? Mundocom | Re:Sources IT
35 West Wacker Drive, Suite 3000 | Chicago, IL 60601
Office: 312-220-1669 | Mobile: 312-519-5632
Email: Eric.Winkelhake at
Open a Service Desk Ticket | Navigating IT | Training Now

Not applicable

I just finished creating a package with Composer. I just installed the
Office 11.5 update and the XML Converter and turned it into a DMG. Seems
to be working fine.


Not applicable

I actually just deployed the new Office Converter using Microsoft's mpkg. I didn't use Casper as this was a one machine deal, but it was as simple as scp'ing the mpkg over the the machine, then ssh'ing into the box and using the installer command.

The installer command has been invaluable, hooray to apple for making command line versions of most of their apps. Just run "sudo installer -pkg <path to pkg or mpkg> -target <target drive>", so my command becomes 'sudo installer -pkg Open XML File Format Converter 1.0.mpkg -target /' and everything works great. You can also add the '-verbose' option if you feel safer seeing more output.

A few notes: This particular installer will quit all Office apps without prompting you when run from the command line, be sure you save everything first. Parts of the installer that require user intervention (i.e. EULA) are skipped, but make sure you run this as sudo if it needs root privileges.

This has been working great for me, even wrote a script that will run this for any pkg's or mpkg's in the current directory to ease in deployment, but if you've got Casper, I would think that it would be more streamlined to just use composer and make a dmg package.

Hope that helps,

Ryan Harter
UW - Stevens Point
Workstation Developer
Ryan.Harter at

Contributor III


What Chad and Eric have stated I agree with. I attempted to use MPKGs, but they often won't work being pushed for various reasons. If you need to do other things like EULA supression, serialization, etc. then you are almost always better off building a DMG with Composer. That's what I've resorted to with Office 2008. I am able to use some of the additional bundled software MPKGs with like Final Cut Studio for additional audio content and motion content etc, but you need to make sure you check the logs if the MPKG fails to may not appear to have failed up front, but check the logs. This was happening with the previous Office 2008 (service pack 1) 12.1.0 update that was an MPKG. I thought, great...I can push out the pre-made MPKG, but no such luck.

Good luck!


Not applicable

i look for a command line version for the installer with a silent flag.