Here is the steps I got from JAMF Nation:
https://jamfnation.jamfsoftware.com/discussion.html?id=13946
I use Composer only because the resulting PKG installs faster, then creating a single bundled installer. I’ve created a single installer using Packages that first installs Office 14 SP3 and then 14.4.x updater, but it takes longer time for it to install then a pkg made in composer.
Here’s what has worked for us since we’ve been deploying Office 2011.
Setup a computer with a clean install of Mac OS X. Log in as a Admin account; not necessary to be root.
Open Composer, select New Package – Normal Snapshot. Name it: Microsoft_Office_2011-14.4.8
Install Office 2011 SP 3 using the install mpkg from Microsoft
Complete the Office Assistance, but bogus info since we will delete the Users folder later on
Check for updates via Help menu or download directly from Microsoft and install.
Open Lync and and check for updates – for some reason it’s not included when you update the Office suite.
Quit all Office apps.
Within Composer, click “Create Package Source” to take the final snap shot
Delete the following files/folders
/User/xxxxusername
/Library/Application Support/.blahxxxxxx….. (it’s a long random character file name.)
/Library/Preferences/.blahxxxxxx….. (it’s a long random character file name.)
For both /Applications/Microsoft Office 2011 and /Applications/Microsoft Lync.app, set the owner to “root” and the group to “wheel”. And click the gear to “Apply Owner and Group to” for both.
Click the Build as PKG.As you can see, I’ve done nothing to customize Office or avoid the Office setup assistant for our users. I have a second package that will install our custom template documents.
Here is an automation script to setup office 2011 exchange account:
http://www.officeformachelp.com/2010/11/use-casper-to-deploy-and-manage-office-for-mac-2011/
Here is another way of packaging office 2011 for mac with updated injected inside: