Patcher for the Office 2011 Installer

[mgb123]

I’ve attempted to drop the ‘Office Installer’ file from the original install media onto the patcher.

I only see it for a second or so in my Dock and then it disappears. Is this the expected behavior?

[bw38]

Yes that’s the expected behavior. If you feel it’s not actually doing anything, you can compare checksums before and after dropping on the patcher. You should see a difference.

[dknisely]

I think I must be an idiot, but I can’t seem to get the patcher to do anything. Is it supposed to work on the “Communicator13.1_ALL.dmg” file? I still get the same error when I try to run the updated version. Am I supposed to drop the dmg file on the patcher or the extracted mpkg file? Neither has any effect.

Any help would be appreciated as the repeated requests by Microsoft Office Autoupdater are very annoying and it appears there are new features in 13.1.

[dead2sin]

[QUOTE][u]Quote by: dknisely[/u][p]I think I must be an idiot, but I can’t seem to get the patcher to do anything. Is it supposed to work on the “Communicator13.1_ALL.dmg” file? I still get the same error when I try to run the updated version. Am I supposed to drop the dmg file on the patcher or the extracted mpkg file? Neither has any effect.

Any help would be appreciated as the repeated requests by Microsoft Office Autoupdater are very annoying and it appears there are new features in 13.1.[/p][/QUOTE]

For Communicator, you’ll want the Office Update Patcher: [url]http://dl.dropbox.com/u/11466/InstaDMG%20PatchOfficeUpdate%200.4.dmg[/url]

The Update patcher will patch 2008, 2011 and Communicator updates.

The Office 2011 Installer patcher is strictly for the Office 2011 installer.

Basically, you need to drag the .pkg/.mpkg to your desktop or any other folder that isn’t a read-only DMG. Then, drop the .mpkg on the patcher and it will make the changes necessary for it to work with InstaDMG.

If you mount the .dmg from Microsoft and try to just drag the .mpkg onto the patcher directly, it won’t do anything because the .dmg is read only.

Let me know if you run into any other issues.

Nate

[wadewei]

[QUOTE][u]Quote by: dead2sin[/u][p][QUOTE][u]Quote by: dknisely[/u][p]I think I must be an idiot, but I can’t seem to get the patcher to do anything. Is it supposed to work on the “Communicator13.1_ALL.dmg” file? I still get the same error when I try to run the updated version. Am I supposed to drop the dmg file on the patcher or the extracted mpkg file? Neither has any effect.

Any help would be appreciated as the repeated requests by Microsoft Office Autoupdater are very annoying and it appears there are new features in 13.1.[/p][/QUOTE]

For Communicator, you’ll want the Office Update Patcher: [url]http://dl.dropbox.com/u/11466/InstaDMG%20PatchOfficeUpdate%200.4.dmg[/url]

The Update patcher will patch 2008, 2011 and Communicator updates.

The Office 2011 Installer patcher is strictly for the Office 2011 installer.

Basically, you need to drag the .pkg/.mpkg to your desktop or any other folder that isn’t a read-only DMG. Then, drop the .mpkg on the patcher and it will make the changes necessary for it to work with InstaDMG.

If you mount the .dmg from Microsoft and try to just drag the .mpkg onto the patcher directly, it won’t do anything because the .dmg is read only.

Let me know if you run into any other issues.

Nate[/p][/QUOTE]

Hi, Nate

Thanks for your patchs.

But I can not download Update patch from http://dl.dropbox.com/u/11466/InstaDMG%20PatchOfficeUpdate%200.4.dmg, and can not download Installer patch V1 though I tried many times with the help of friends in different places, I just can download Installer patch V2 and V3.
So would you mind sending Update patch and installer patch v1 to my email [email protected]?
And
For installer Patch, Is the installing process as V1—->V2—->V3? or just installing V3 is OK?

Thanks very much.

Wade

[dead2sin]

You only need the latest patcher version. The versions are simply improvements to the patcher that make it work with newer versions of updates/office versions, etc.

Its strange you cannot download those files from dropbox…it must be some sort of network issue or perhaps a content filter (I just tested the links again and they work).

I’ll send both to you.

Nate

[cyberatz]

No special patcher is required to fix this 😯

Basically, download the update file (see links above) from MS. Kill any running instances of Communicator. Move the file from your Applications folder to trash. Run the updater. The updater will basically reinstall communicator with the correct 13.1.0 version.

None of this patcher stuff.

Enjoy.

[dead2sin]

[QUOTE][u]Quote by: cyberatz[/u][p]No special patcher is required to fix this 😯

Basically, download the update file (see links above) from MS. Kill any running instances of Communicator. Move the file from your Applications folder to trash. Run the updater. The updater will basically reinstall communicator with the correct 13.1.0 version.

None of this patcher stuff.

Enjoy.

[/p][/QUOTE]

This is specifically for building images using InstaDMG. Communicator shouldn’t be installed on your build system to begin with, so I assume you are referring to installing the update on a standard client system?

Nate

[wadewei]

[QUOTE][u]Quote by: dead2sin[/u][p][QUOTE][u]Quote by: cyberatz[/u][p]No special patcher is required to fix this 😯

Basically, download the update file (see links above) from MS. Kill any running instances of Communicator. Move the file from your Applications folder to trash. Run the updater. The updater will basically reinstall communicator with the correct 13.1.0 version.

None of this patcher stuff.

Enjoy.

[/p][/QUOTE]

This is specifically for building images using InstaDMG. Communicator shouldn’t be installed on your build system to begin with, so I assume you are referring to installing the update on a standard client system?

Nate[/p][/QUOTE]

Any luck for new published update ” Office Update 14.1.0 and 14.1.2″? I’ve tried with InstaDMG(with the OfficeUpdatePatch run for them) and DeployStudio, but no luck, still stayed in 14.0.2

[wadewei]

[QUOTE][u]Quote by: wadewei[/u][p][QUOTE][u]Quote by: dead2sin[/u][p][QUOTE][u]Quote by: cyberatz[/u][p]No special patcher is required to fix this 😯

Basically, download the update file (see links above) from MS. Kill any running instances of Communicator. Move the file from your Applications folder to trash. Run the updater. The updater will basically reinstall communicator with the correct 13.1.0 version.

None of this patcher stuff.

Enjoy.

[/p][/QUOTE]

This is specifically for building images using InstaDMG. Communicator shouldn’t be installed on your build system to begin with, so I assume you are referring to installing the update on a standard client system?

Nate[/p][/QUOTE]

Any luck for new published update ” Office Update 14.1.0 and 14.1.2″? I’ve tried with InstaDMG(with the OfficeUpdatePatch run for them) and DeployStudio, but no luck, still stayed in 14.0.2

[/p][/QUOTE]

With the following patchs run, the problem was gone with InstaDMG, not tested yet with DeployStudio

[url]http://dl.dropbox.com/u/11466/InstaDMG%20PatchOfficeUpdate%200.4.dmg[/url]
and
[url]http://dl.dropbox.com/u/429559/patchOffice2011_1410Update_v041.dmg[/url]

Cheers and Thanks,

Wade

[dmueller]

One other alternative you can use is through a post setup script (needs to be run with sudo). Here is an example function I have used to solve the patching problem for now without having to modify the mpkg files:

[code]
OfficeUpdate2011() {
# Update Office 2011 to 14.1.2 – temporary workaround
echo “Updating Office 2011 manually to 14.1.2”
if [ -e “/usr/local/scripts/Office 2011 14.1.0 Update.mpkg” ]; then
installer -package “/usr/local/scripts/Office 2011 14.1.0 Update.mpkg” -target / > /dev/null
rm -R “/usr/local/scripts/Office 2011 14.1.0 Update.mpkg”
if [ -e “/usr/local/scripts/Office 2011 14.1.2 Update.mpkg” ]; then
installer -package “/usr/local/scripts/Office 2011 14.1.2 Update.mpkg” -target / > /dev/null
rm -R “/usr/local/scripts/Office 2011 14.1.2 Update.mpkg”
fi
fi

echo “Updating Communicator for Office 2011 manually to 13.1.1”
if [ -e “/usr/local/scripts/Communicator Installer.mpkg” ]; then
installer -package “/usr/local/scripts/Communicator Installer.mpkg” -target / > /dev/null
rm -R “/usr/local/scripts/Communicator Installer.mpkg”
fi
}
[/code]

14.0.2 was already incorporated through Instadmg on my base image. This piece is part of a postsetup script that makes some additional setting adjustments, as well as applying softwareupdates.

Kind regards,

[bostonmacosx]

Could you go into some detail as what you mean by post setup script…where exactly do you place the script you posted and how do you get the installers onto the disk.

Thanks
Rob

[dmueller]

Sure thing.

I use a manual script to affect configuration changes after the image has been dropped to disk. I do this because we will, depending on the system, add the Application DVD utilities (iLife, CPU tools, etc) before delivery to the end-user. The post setup will name the machine, add it to Active Directory, modify the networks services, etc. I also will have it run softwareupdate to patch the system and iLife. I would place it in the same location (/usr/local/scripts/postsetup.sh for example).

As for the Microsoft patches; The SP1 (14.1.0) and update 14.1.2 are available at mactopia.com
Communicator is a bit more difficult to find. I had to trace it with Wireshark while downloading the 13.1.1 update through Microsoft’s Autoupdate utility.

Why do I have it set as a function? So it is easy to remark out of the script without having to comment out all of the lines. It helps keep the script modular too.

The piece I posted is just a function within the larger script.

I would post an example if I could get it past the spam block 🙁

Regards,

Edit: How I add them to the disk image: I created and installer through Iceberg that drops the files in that location from a custom catalog file through Instadmg

[dmueller]

This should give you a rough idea:

[code]#!/bin/bash

# Check to make sure we are root
check_root() {
if [ `whoami` != “root” ]
then
/bin/echo “You need to be root to do this. Run the script using sudo.”
exit 0;
fi
}

AutoUpdate() {
# Make sure the system is updated with any current software updates.
sudo softwareupdate -i -a
}

OfficeUpdate2011() {
# Update Office 2011 to 14.1.2 – temporary workaround
echo “Updating Office 2011 manually to 14.1.2”
if [ -e “/usr/local/scripts/Office 2011 14.1.0 Update.mpkg” ]; then
installer -package “/usr/local/scripts/Office 2011 14.1.0 Update.mpkg” -target / > /dev/null
rm -R “/usr/local/scripts/Office 2011 14.1.0 Update.mpkg”
if [ -e “/usr/local/scripts/Office 2011 14.1.2 Update.mpkg” ]; then
installer -package “/usr/local/scripts/Office 2011 14.1.2 Update.mpkg” -target / > /dev/null
rm -R “/usr/local/scripts/Office 2011 14.1.2 Update.mpkg”
fi
fi

echo “Updating Communicator for Office 2011 manually to 13.1.1”
if [ -e “/usr/local/scripts/Communicator Installer.mpkg” ]; then
installer -package “/usr/local/scripts/Communicator Installer.mpkg” -target / > /dev/null
rm -R “/usr/local/scripts/Communicator Installer.mpkg”
fi
}

Cleanup() {
srm “$0”
}

# Call the functions in the following order
check_root
AutoUpdate
#OfficeUpdate2011
Cleanup[/code]

[Goldberg]

Has anyone successfully deployed Office updates 14.1.0 and 14.1.2 in instaDMG? How did you do it?

[Author]

Posts