Just did my first production push of Office 2011 (14.0.0) + 14.1.0 + 14.2.1.

Everything went fine and no licensing issues.

FYI, you should have no need to install the 14.1.4 update since 14.2.1 covers everything back to 14.1.0.

Still having licensing issues with
Office 2011 with SP1 + 14.2.0 + 14.2.1

The 14.2.1 update incorporates 14.2.0. No need to install both. See what happens if you leave 14.2.0 out of the mix.

I have been playing with this today. I am working on a new imaging configuration so there isn't much in it right now. If I just install 14.0.0 and 14.1.0, the office appications will open just fine. If I add 14.2.1 to the configuration they start asking me to enter a product key. Something in the 14.2.1 package seems to be removing the volume license key that is laid down by the first package.

At this point I have been doing a complete reimage each time to test the difference. The base os is 10.7.3. The only other things getting installed are Adobe CS5.5, iLife 11 and iWork 09.

Bill, this is happening when using Microsoft's supplied installer packages and not repackaging yourself. Correct?

None of the above methods worked for me.

So I have downloaded Office 2011 with SP2 from Microsoft VLSC and 14.2.1 update.

Everything works fine now.
1. Install Office 2011 with SP2
2. Install Office 14.2.1 Update

Do not touch 14.2.0 update.

I have several reports of people running other applications (not exchange based) and claiming disruption of the service after SP2 and even patch installation.

Very bad move by Microsoft.
My Search bar doesn't search anymore, after the identity upgrade.
Patch didn't fix it.

O_o

Yes this is happening with the microsoft supplied installers. they are set to install at reboot in the image configuration.

Paolo try reindexing. I noticed after this borked update that searching and some other strange Adobe issues popped up! Once we patched them... they all went away. Very bad MS.

Greetings and Salutations

Sorry to be so long to reply about the Product Activation issue for Volume License users (that includes Education institutions that have not had to input product keys). We have been able to reproduce in house and I want to make sure the scenario matches yours.

To reproduce this behavior we have found that you need to be 
• pushing both the last Setup Build you have in your establishment (14.0 or 14.1) and the updater (14.2.1 or 14.2.0) at the same time, OR
• pushing the 14.2.x updater to a machine that a) has had the setup build pushed via ARD or some imaging like Casper that does not invoke the setup assistant and b) never run any of the office applications

Does this match the scenarios you see?

We do not have a fix, but we have a workaround. Everyone with volume licenses should have access to the 14.2.0 setup image now, and you can push the 14.2.0 setup image (rather than the 14.0 or 14.1 setup image) with the 14.2.1 updater and not have this issue.

Please either email me or respond back here if you are seeing something different.

Thanks

David Pelton

To those who are not having an update actually change the bits

Could the folks that are seeing this issue with the lack of upgrade, please pass on some information?

1) The install log, in particular the top section where it says the options chosen and gives the list of packages to install. of course, any errors in the install log would also be appreciated

2) Launch console on the machine that is receiving the update and send up that console log.

3) Please (for me being the not completely educated on the finer points of Casper) elaborate on the procedure being used to apply the update so I can attempt to reproduce in house.

Thanks and sorry for these difficulties.

David Pelton

@David Pelton

I've seen this once in my environment. I was pushing 14.0.0 + 14.1.0 + 14.2.1 consecutively using Casper. This seems to match your first scenario.

I'll try to get an install log Monday. Should be found in /private/var/log/install.log*, I believe.

@David Pelton

Looks like I misread your Intention. The solution to this issue is to begin with the volume license installer that includes SP2 and upgrade from there. That sounds reasonable.

Thanks again for coming to us in the forums.

Any now we have 14.2.2

http://support.microsoft.com/kb/2665351

Like 14.2.1 this update looks like it is a full SP2 installer. No need to install 14.2.0.

FYI 14.2.3 is a combo update as well.

I haven't done any testing yet but 14.2.3 should correct the world-writable permissions issue introduced by 14.2.0. It should also avoid the lost license for volume license customers and the "unable to rebuild" Outlook database issues. (It will still require an Outlook database rebuild if updating from 14.1.x.)

Therefore, I believe the safest install methods would be either:

• 14.0.0 + 14.1.0 + 14.2.3


• 14.2.0 (volume license) + 14.2.3