Patcher for the Office 2011 Installer

[wadewei]

[QUOTE][u]Quote by: Goldberg[/u][p]Has anyone successfully deployed Office updates 14.1.0 and 14.1.2 in instaDMG? How did you do it?[/p][/QUOTE]

Goldberg,

As I mentioned already, I got them worked in InstaDMG, what need to do is let the updates apply the following droplet patches, the patches order does not matter.

[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]

Thanks for the authors of the patches.

Wade

[Tim Sutton]

I wrote the latter – but as I mentioned on the instadmg-dev forum, this patcher will try to apply every single .pkg within the 14.1.0 updater mpkg, because it patches every pkg installer to bypass its “should I be installed” check. I’ve not checked 14.1.2, but it seems that it worked for you?

On a standard install with all the default components, I haven’t seen any issues, but I can’t necessarily test all the components that may depend on some support libraries that may or may not have been installed with the original application(s).

And, it certainly will leave a half-functioning install of any additional components that weren’t installed with the original installer. For example, for labs I omit Outlook using InstallerChoices. Applying this patched update on top of such an installation will install an unusable Outlook (functioning, but with missing resources).

I know Microsoft has released an SP1 installer disc, but I haven’t yet heard anything conclusive about whether this works easily with InstaDMG. For now I leave my base image with 14.0.2 and let Munki do the rest, but if I could at least get SP1 installed in the image with confidence, that’d be nice. Anyone with feedback on this?

[Goldberg]

Yes, testing with both patch scripts works for 14.1.0 and 14.1.2. We don’t install Outlook and after applying the 14.1.0 and 14.1.2 updates I agree this is the case. For example, the Outlook icon is generic looking.

I tested with the SP1 disk. That worked too. Interesting the MS Office 2011 folder icon isn’t black, it’s generic. What’s up with that?

Thanks everyone for their help.

[bw38]

I hope this makes it as clear as possible for anyone that runs into this:

In order to get Office 2011, you will need to modify a few files (described already in this thread to some extent). Rather than manually modifying the files, the links below will provide a patcher applet for Office and its updates which does the necessary modifications to get Office to work with InstaDMG. The way the applets work is simple: drag the Office installer or update .pkg onto the patcher applet. It will run the scripts in the applet which will modify the .pkg for you.

I tested this today and it works. Here are the patchers you will need:

Apply to Office 2011 Installer
dl.dropbox.com/u/11466/Patch%20Office%202011%20Installer/Version%203/PatchOffice2011Installer.dmg

Apply to Office 14.1.0 and 14.1.2 (and Communicator 13.1.0 and 13.1.1 if you have a volume license)
dl.dropbox.com/u/11466/InstaDMG%20PatchOfficeUpdate%200.4.dmg

Apply to Office 14.1.0 and 14.1.2
dl.dropbox.com/u/429559/patchOffice2011_1410Update_v041.dmg

It doesn’t matter in what order you patch Office 14.1.0 and 14.1.2.

Download links to updates:
*Communicator 13.1.0: download.microsoft.com/download/6/6/2/6622B710-155F-4CB8-B625-6CA0421455DC/Communicator13.1_ALL.dmg

Communicator 13.1.1: download.microsoft.com/download/3/0/F/30FCD0B0-3B03-4621-BF6D-72515B9B80BA/Communicator13.1.1_ALL.dmg

Office 14.1.0: microsoft.com/downloads/info.aspx?na=41&srcfamilyid=ef1e612f-d8e3-4628-9fe4-ad136f0debd3&srcdisplaylang=en&u=http%3a%2f%2fdownload.microsoft.com%2fdownload%2f5%2fE%2fE%2f5EE76E3B-8D17-4BB1-AF4A-A33D38C8810F%2fOffice2011-1410UpdateEN.dmg

Office 14.1.2: microsoft.com/downloads/info.aspx?na=41&srcfamilyid=3c58555c-1eba-42fe-a10f-b30af9031e44&srcdisplaylang=en&u=http%3a%2f%2fdownload.microsoft.com%2fdownload%2f0%2f3%2f0%2f03025205-2044-4CE7-96C9-34E5157510FF%2fOffice2011-1412UpdateEN.dmg

Please note the following: once you create a checksum hash for these packages in your catalog file, you may find that the hash will change after your first run with these packages in an image. When you try to run InstaDMG a second time you may get an error message, you just need to make sure the checksum hash is valid is all. Not sure exactly what is changing except that something is definitely changing. All I can tell you is that it works. If someone disagrees or finds I made a mistake, by all means feel free to correct me.

*You may also get away with not having to use Communicator 13.1.0. It appears that 13.1.1 includes 13.1.0. You can test this on your own. I just know that it didn’t make a difference either way to include both updates.

Hope this has been helpful. If I have time maybe, I’ll find a way to add it to the wikis since there doesn’t seem to be much in the way of instructions on how to get Office 2011 installed via InstaDMG.

EDIT: The spamfilter absolutely blows on this forum. I had to take out h t t p : / / www. in all of the links just to get this post in. I’m grateful for the resource this forum provides, but it sure is frustrating to deal with the spam filter here. Can’t the spam filter be toned down just a bit? This may just go unnoticed but hopefully someone who manages the board can do something about it.

[malroy]

HI bw38,

the 14.1.2 PatchOfficeUpdae didnt work on Instadmg. i downloaded dl.dropbox.com/u/11466/InstaDMG%20PatchOfficeUpdate%200.4.dmg as i am volume license shop here.

after the instadmg build, i notice 14.1.2 patch was not applied.

The Offfice 2011 SP 1 installer work , thanks for that .

The Communicator 13.1.1 work like charm too.

I am wondering if you can help me.

i drag the update twice to the applelet and it still doesnt work.

Thanks
Roy

[QUOTE][u]Quote by: bw38[/u][p]I hope this makes it as clear as possible for anyone that runs into this:

In order to get Office 2011, you will need to modify a few files (described already in this thread to some extent). Rather than manually modifying the files, the links below will provide a patcher applet for Office and its updates which does the necessary modifications to get Office to work with InstaDMG. The way the applets work is simple: drag the Office installer or update .pkg onto the patcher applet. It will run the scripts in the applet which will modify the .pkg for you.

I tested this today and it works. Here are the patchers you will need:

Apply to Office 2011 Installer
dl.dropbox.com/u/11466/Patch%20Office%202011%20Installer/Version%203/PatchOffice2011Installer.dmg

Apply to Office 14.1.0 and 14.1.2 (and Communicator 13.1.0 and 13.1.1 if you have a volume license)
dl.dropbox.com/u/11466/InstaDMG%20PatchOfficeUpdate%200.4.dmg

Apply to Office 14.1.0 and 14.1.2
dl.dropbox.com/u/429559/patchOffice2011_1410Update_v041.dmg

It doesn’t matter in what order you patch Office 14.1.0 and 14.1.2.

Download links to updates:
*Communicator 13.1.0: download.microsoft.com/download/6/6/2/6622B710-155F-4CB8-B625-6CA0421455DC/Communicator13.1_ALL.dmg

Communicator 13.1.1: download.microsoft.com/download/3/0/F/30FCD0B0-3B03-4621-BF6D-72515B9B80BA/Communicator13.1.1_ALL.dmg

Office 14.1.0: microsoft.com/downloads/info.aspx?na=41&srcfamilyid=ef1e612f-d8e3-4628-9fe4-ad136f0debd3&srcdisplaylang=en&u=http%3a%2f%2fdownload.microsoft.com%2fdownload%2f5%2fE%2fE%2f5EE76E3B-8D17-4BB1-AF4A-A33D38C8810F%2fOffice2011-1410UpdateEN.dmg

Office 14.1.2: microsoft.com/downloads/info.aspx?na=41&srcfamilyid=3c58555c-1eba-42fe-a10f-b30af9031e44&srcdisplaylang=en&u=http%3a%2f%2fdownload.microsoft.com%2fdownload%2f0%2f3%2f0%2f03025205-2044-4CE7-96C9-34E5157510FF%2fOffice2011-1412UpdateEN.dmg

Please note the following: once you create a checksum hash for these packages in your catalog file, you may find that the hash will change after your first run with these packages in an image. When you try to run InstaDMG a second time you may get an error message, you just need to make sure the checksum hash is valid is all. Not sure exactly what is changing except that something is definitely changing. All I can tell you is that it works. If someone disagrees or finds I made a mistake, by all means feel free to correct me.

*You may also get away with not having to use Communicator 13.1.0. It appears that 13.1.1 includes 13.1.0. You can test this on your own. I just know that it didn’t make a difference either way to include both updates.

Hope this has been helpful. If I have time maybe, I’ll find a way to add it to the wikis since there doesn’t seem to be much in the way of instructions on how to get Office 2011 installed via InstaDMG.

EDIT: The spamfilter absolutely blows on this forum. I had to take out h t t p : / / www. in all of the links just to get this post in. I’m grateful for the resource this forum provides, but it sure is frustrating to deal with the spam filter here. Can’t the spam filter be toned down just a bit? This may just go unnoticed but hopefully someone who manages the board can do something about it.[/p][/QUOTE]

[Goldberg]

Roy,

I believe you have to drop the 14.1.2 update on both patches. That’s what worked for me. The problem with the patches, as previously stated, is if you customize the office install (via installerchoice or some other method) those apps not installed will get patched and those apps may not be fully functioning. For example, I don’t install Outlook but after I ran 14.1.0 and 14.1.2 I had an Outlook icon in the Office folder with a generic icon. I didn’t test it and I didn’t want it on the image.

Apply to Office 14.1.0 and 14.1.2 (and Communicator 13.1.0 and 13.1.1 if you have a volume license)
dl.dropbox.com/u/11466/InstaDMG%20PatchOfficeUpdate%200.4.dmg

Apply to Office 14.1.0 and 14.1.2
dl.dropbox.com/u/429559/patchOffice2011_1410Update_v041.dmg

[bw38]

Malroy,

Here is what I’m getting for my checksum before and after applying the two patchers on 14.1.2:
Before: Office 2011 14.1.2 Update Office 2011 14.1.2 Update.mpkg sha1:d6197dba51387ce19931d367e278bdc2ba45ca37
After: Office 2011 14.1.2 Update Office 2011 14.1.2 Update.mpkg sha1:ed99b2b0dfc658cd3180fb628d98e7a518e1f6e4

Could you confirm that’s what you get as well?

Also what order are you running the updates in your catalog? I have mine set as follows:
Office Installer
14.1.0
14.1.2

Edit: I noticed you said you dropped the update on the applet twice. I think this is the mistake causing your issue. You need to run through two patchers, not twice on one patcher. I provided the links to all three patchers you will need, two of which are required for Office 14.1.0 and 14.1.2. Could you confirm that you did indeed run the updates through both patchers?

[malroy]

HI bw38

my checksum is wrong , i don’t know why

the official download from Microsoft i get the same checksum as you sha1:d6197dba51387ce19931d367e278bdc2ba45ca37

First Patch (dl.dropbox.com/u/11466/InstaDMG%20PatchOfficeUpdate%200.4.dmg)

running the first patch this is what i get
sha1:d0ce0fdd98221a8848f8b079af8857c38b2d032f

Second Patch (dl.dropbox.com/u/429559/patchOffice2011_1410Update_v041.dmg)

sha1:a41bb83ed8346cea8f549c858055c910f46ff8ac

i don’t know why it look different that yours

at the mean time , is it possible for you to upload your copy of Office 2011 14.1.2 Update.mpkg ??

I am using the latest Office 2011 installer which already have SP1 built-in

which is first in the catalog then follow the 14.1.2 update

Thanks
Roy

[QUOTE][u]Quote by: bw38[/u][p]Malroy,

Here is what I’m getting for my checksum before and after applying the two patchers on 14.1.2:
Before: Office 2011 14.1.2 Update Office 2011 14.1.2 Update.mpkg sha1:d6197dba51387ce19931d367e278bdc2ba45ca37
After: Office 2011 14.1.2 Update Office 2011 14.1.2 Update.mpkg sha1:ed99b2b0dfc658cd3180fb628d98e7a518e1f6e4

Could you confirm that’s what you get as well?

Also what order are you running the updates in your catalog? I have mine set as follows:
Office Installer
14.1.0
14.1.2

Edit: I noticed you said you dropped the update on the applet twice. I think this is the mistake causing your issue. You need to run through two patchers, not twice on one patcher. I provided the links to all three patchers you will need, two of which are required for Office 14.1.0 and 14.1.2. Could you confirm that you did indeed run the updates through both patchers?[/p][/QUOTE]

[malroy]

Hi Goldberg,

My wrong, now i realize that i have too, i dont use a installerchoice here

i tried the two patch and get the wrong checksum.

Thanks
Roy

[QUOTE][u]Quote by: Goldberg[/u][p]Roy,

I believe you have to drop the 14.1.2 update on both patches. That’s what worked for me. The problem with the patches, as previously stated, is if you customize the office install (via installerchoice or some other method) those apps not installed will get patched and those apps may not be fully functioning. For example, I don’t install Outlook but after I ran 14.1.0 and 14.1.2 I had an Outlook icon in the Office folder with a generic icon. I didn’t test it and I didn’t want it on the image.

Apply to Office 14.1.0 and 14.1.2 (and Communicator 13.1.0 and 13.1.1 if you have a volume license)
dl.dropbox.com/u/11466/InstaDMG%20PatchOfficeUpdate%200.4.dmg

Apply to Office 14.1.0 and 14.1.2
dl.dropbox.com/u/429559/patchOffice2011_1410Update_v041.dmg[/p][/QUOTE]

[bw38]

I’d have no problem sending you the patched update 14.1.2. Check your PM. Also, I wonder if it has something to do with the fact that I’m using the original Office 2011 disc (not Office 2011 SP1). Just grasping at straws here.

On another note, it appears that after writing that tutorial I am now unable to get Communicator 13.1.1 to work (but 13.1.0 works fine)! Bizzare. Malroy, could you provide the hash you get after applying the patch?

Download from MS gives me:
sha1:4e374af45d09ea861bd2eb6a59ecc1648de7a670

After applying Office this patcher: dl.dropbox.com/u/11466/InstaDMG%20PatchOfficeUpdate%200.4.dmg
sha1:18e49c02bde4114e76fca167f54b4e48fa1b656c

Perhaps you could send me the Communicator update patched in a similar fashion? Just PM me if you can’t post it here.

[bw38]

Just wanted to post that I created a basic wiki article outlining how to include Office 2011 into InstaDMG using the patchers that have been discussed in this thread. I encourage anyone to make any necessary modifications to the article. Wiki can be found here: http://www.osxdeployment.com/wiki/Office_2011

With that said, I have been unable to get Communicator 13.1.1 to work with the patchers. Has anyone else had luck getting it to work?

[bw38]

With Communicator 13.1.2 out, it seems the patcher works again. I tested this twice and both times the latest version was installed. You do need to install Communicator 13.1.0 before 13.1.2.

The update can be downloaded here: microsoft.com/download/en/details.aspx?id=26835

[bgolden]

I have tried using the patcher, and it works, making the correct changes to the postflight script, but when I use it to install (not through a built image, but on it’s own) for testing. The setup assistant asks me to enter my key or purchase one. What am I doing wrong?

[bw38]

I actually had this happen recently too when I used the Office 2011 SP1 iso from Microsoft. I just got my hands on it and decided to test it out, but it didn’t work. I didn’t really get to dig too much into it though since I have the original Office 2011 installer which works fine for me. I’m not sure if others have had similar issues either.

Could you tell us what installer of Office 2011 you’re using? And which patchers you’ve applied to it?

[bw38]

It’s been a while since I baked my last image but once again I find myself not being able to get Communicator 13.1.2 to work! I thought I was going crazy when I said it worked with 13.1.1, but suddenly stopped working. But now I know for fact that something is screwy here.

The last time I created an image with InstaDMG was on Aug 1, 2011 using svn rev 420. Suddenly I checked out the latest svn (rev 425) for InstaDMG and it just stopped working. Just to note when I check out the latest svn, I download it to a new folder all together and manually move over any of my the catalogs, packages, etc. to the new InstaDMG folder. But I don’t believe this should be causing issues. Someone correct me if I’m wrong on that.

It’s rather minor in the grand scheme of things, but it drives me nuts that everything else in the image works fine except this one update (which worked at one point but not anymore). I’ve upload a zip file with two debug logs from rev 420 and rev 425.

http://www.woofiles.com/dl-263064-DlQcnpRz-InstaDMGdebugfile.zip

There’s definitely a lot more activity going on when it gets to the point of installing Communicator 13.1.2 in rev 420 compared to 425. But I’m not entirely sure what it means if anything at all. Any ideas here?

[Author]

Posts