Microsoft Office 2011 for Mac! Silent Installer!

Transcription

1 Microsoft Office 2011 for Mac Silent Installer By Gilbert Palau Enterprise OSX - The Enterprise Community of OSX Administrators

2 Overview In this guide we are going to build a silent installation of Microsoft Office + Lync 2011 for Mac. We are going to use Packages to add the Upgrade to , Lync, Silverlight, Flip4Mac, Enterprise Vault and a patch file to our.pkg. If you don t use Enterprise Vault please ignore it. Tools For this project I will be using Stephan Sudre's Integrated Packaging Environment, Packages, which is free, located at The Packages User Guide is available online at:

3 Removing Installer application quit function We are going to begin by removing the Office 2011 Installer application quit function. This function forces you to shutdown browsers and applications before the installation runs. This aspect is more often than not a headache to Mac admins who want to remotely deploy the installer(s). 1. Open Terminal and run this command to expand the contents of the Office installer or update installer package into a new directory. For this example, I will be expanding the contents into a folder called office_build: pkgutil expand /your/path/to/office 2011 Installer.pkg office_build This will create a folder called office_build with a number of installer packages inside. The problem script will be inside the package whose name includes all_quit. 2. Run the next command to edit the script (adjusting for the name of the all_quit installer package): pico /office_build/office2011_all_quit_14.2.x.combo.pkg/scripts/preinstall 3. Replace all of the script s current contents with the following content: The exit 0 will cause the script to exit immediately without causing other ill-effects. 4. To convert the directory back into an installer-package, type the following in Terminal: pkgutil flatten office_build /path/to/office 2011 Installer.pkg At this point, you will have an Office 2011 installer where the application quitting function will not run. This should make deploying the modified Office 2011 installer or update installer easier. Note: The flattening will remove the digital certificate that the Office 2011 installers normally include. For most deployment tools, this should not be a problem but Gatekeeper may flag it if the installer is downloaded via a web browser.

4 Creating the Raw Package in Packages 1. Set up a new Packages project and select Raw Package. 2. In this case we are going to rename the project Microsoft Office 2011 SP

5 3. Once the Packages project opens, click on the Project tab. You will want to make sure that the information you enter is correctly set here. In this example, I m not changing any of the options from what is set by default. 4. Next, click on the Settings tab. In the case of this example, I want to install with root privileges and not require a logout, restart or shutdown. For this to happen, I am choosing the following options in the Settings section: In the Post-Installation Behavior section, set On Success: to Do Nothing In the Options section, check the box for Require admin password for installation. In the Identifier type: com.yourcompany.pkg.microsoftoffice2011sp41441 where yourcompany is your company name.

6 5. On the Scripts tab in your Packages project, select your installers and drag them into the Additional Resources section of your Packages project. In the case of this example, I m selecting the following installers: Office with Service Pack 2 Installer.pkg Office Update.pkg EV-Client-for-mac-10-04HF2.mpkg ms-lync pkg Flip4Mac.pkg Silverlight.pkg com.microsoft.office.licensing.plist 6. The last part is telling the installers to run. For this you will need a post-install script. On the next page is the script I am using. If you have trouble reading it, you can also get it from:

7 #/bin/bash # Determine OS version osvers=$(sw_vers - productversion awk - F. '{print $2}') # Determine working directory install_dir=`dirname $0` # Location of Microsoft Office Volume License file office_license="$3/library/preferences/com.microsoft.office.licensing.plist" # Backup location for Microsoft Office 2011 Volume License file license_backup="$3/tmp/com.microsoft.office.licensing.plist" # Install Office 2011 using the specified installer packages in the working directory /usr/sbin/installer - dumplog - verbose - pkg $install_dir/"office Installer.pkg" - target "$3" /usr/sbin/installer - dumplog - verbose - pkg $install_dir/"uni- ms- lync pkg" - target "$3" /usr/sbin/installer - dumplog - verbose - pkg $install_dir/"silverlight.pkg" - target "$3" /usr/sbin/installer - dumplog - verbose - pkg $install_dir/"flip4mac.pkg" - target "$3" /usr/sbin/installer - dumplog - verbose - pkg $install_dir/"ev- client- for- mac HF2.mpkg" - target "$3" # Copy a backup of the Microsoft Office 2011 Volume License file to /tmp. If the license file is # not available as /Library/Preferences/com.microsoft.office.licensing.plist, restore from the # backup license file included with this installer. if [[ - f "$office_license" ]]; then cp "$office_license" "$license_backup" fi if [[ - f "$office_license" ]]; then cp "$install_dir/com.microsoft.office.licensing.plist" "$license_backup" fi /usr/sbin/installer - dumplog - verbose - pkg "$install_dir/office Update.pkg" - target "$3" # If the Microsoft Office 2011 Volume License file has been removed from its proper # location, restore it using the backup file stored in /tmp and then set the correct # permissions on the file. if [[ - f "$office_license" ]] && [[ - f "$license_backup" ]]; then cp "$license_backup" "$office_license" chown root:wheel "$office_license" fi # Remove the backup file from /tmp if [[ -f "$license_backup" ]]; then rm "$license_backup" fi exit 0 Notice that the $install_dir in the postinstall script refers to the path to the packages working directory. That s where Packages will be storing these installers, inside the

8 Package-built installer s embedded directory where it stores the items defined in the Additional Resources section. The -target value is defined as $3 because some information is passed along by the Packages-built installer to its included scripts when those scripts are run by the installation process. (For more information, see the PackageMaker How-To available here: s.sudre.free.fr/stuff/packagemaker_howto.html and search on the page for $3). In this case, -target being defined as $3 nears that the post install script will install all the packages I listed above in the script into the desired drive. The script also governs what order the installers run in, so in this case the main Office 2011 installer runs first and the update runs next after the first job finishes. The -dumplog and -verbose flags are to help tracking the progress of installation if you re looking at the installer log. 7. Also there is a problem that s been observed with previous Microsoft Office 2011 Installers ( and it usually involves the volume license file not being applied when it should be. This behavior may be seen with the update in the following cases: Office 2011 is installed and then updated to while nobody is logged in. Office 2011 is installed and then updated to without any Office applications being launched between the initial installation and update. These two scenarios will likely apply if you re building a new machine using an automated deployment tool, but likely will not if you re a home user. With luck, this will only be an issue for and Microsoft will fix this issue in the next 14.4.x update. In the meantime, the easiest fix I ve found in my testing this week is to get the necessary volume license file from a machine that has Office 14.3.x installed on it and put it back on an as-needed basis. The needed file is /Library/Preferences/com.microsoft.office.licensing.plist. If you have a volume-licensed version of Office 2011 installed on your Mac, you should have this file. To address the issue of installing without losing your volume license, we have injected this file in the code I am providing above. So with this installation you will be able to take your own com.microsoft.office.licensing.plist license file to build a unified Office 2011 SP installer package that does not prompt for a product key. :) 8. Once you have got the post-install script built, run the command script below to make the script executable: sudo chmod a+x /path/to/postinstall.sh

9 9. Once completed, add the post-install script to your Packages project. 10. Last step is to build the package. To do this you can either press Command-B or you can go to the menu above and click on Build.

10 Signing the installer An additional advantage of re-packaging using Packages is that Packages by default creates flat packages ( which can be signed with a Developer ID ( This will allow your packages to be accepted by Gatekeeper ( Gatekeeper is a feature introduced in OS X Mountain Lion that helps protect users from downloading and installing malicious software. Signing the Packages-built flat package provides a way to accommodate Gatekeeper if you have installer packages which otherwise aren t signed or can t be signed. To sign your installers, you will need to have an Apple Developer Connection membership. If you re an ADC member, you can obtain an Developer ID Installer certificate from Apple using Xcode ( Once you have your Developer ID Installer certificate installed, you can sign the Packages-built package with the following command: productsign - - sign "Developer ID Installer: FirstName LastName" /path/from/ package_name.pkg /path/to/signedpackage_name.pkg (This is all one line) In the case of this example, I will sign it with the following command: productsign - - sign "Developer ID Installer: Gilbert Palau" "/path/from/ Microsoft Office 2011 SP pkg" "/path/to/microsoft Office 2011 SP pkg" (This is all one line) To verify that your package has been signed, check your installer package to verify that it has a lock icon in the top-right corner. Next, click the lock icon to verify that the certificate is showing up as a valid Apple Developer ID Installer certificate.