OfficeAs mentioned in a previous post[1], I recently had to set up a new KMS host for our company in order to support KMS activation for the latest Windows OSs.  Since we started from scratch with a new server, I also wanted to make sure that the Office KMS activation for both Office 2010 and Office 2013 were working as well from the same server (which was how the old KMS host was configured).  However the behavior of the Office KMS activation was not as well documented as it is was for OS activation.  As you may already know, Microsoft Operating Systems have a hierarchical nature to them[2].  You choose the ‘highest’ OS in that hierarchy that you are licensed for and apply that KMS key to the KMS host.  Once done, that OS and all ‘lower’ (as well as older) OS’s activate as well.  Fairly simple and only one key is needed to activate your entire organization.

But there was no clear cut documentation on whether or not that was the case with the Office activations or not.  But before we get into that any further, let’s first talk about what we did know.

The default KMS licensing service is not aware of any Office KMS keys so in order to install one you must first install a ‘hotfix’ that makes the service aware of the Office products.  There are currently two available: the Microsoft Office 2010 KMS Host License Pack[3] and the Microsoft Office 2013 Volume License Pack[4].  On our old server we had installed the 2010 license pack when 2010 was released.  Then, a few years later, we installed the 2013 pack.

Now back to the issue at hand.  The documentation does not mentioned anything about the relationship between these two products.  Are they independent of each other or are, like the OS KMS keys, hierarchical by nature?  I made the assumption that they were hierarchical and simply applied the 2013 pack.  However, my assumption proved wrong.  Office 2013 was activating just fine but Office 2010 was not.  The obvious solution at this point was to simply apply the 2010 pack and move on.  However, the fact that I was in an untested and undocumented scenario (office 2013 pack being installed before the 2010 pack) made me hesitant to just test that theory on our production server.  We don’t really have test or dev instances of KMS Hosts either because of the limited number of host activations we get with each key (as well as the complicated process of waiting for the minimum client counts before the host starts to actually work).

So I decided to take the hard road and actually ask Microsoft for the proper documentation on the proper way to set up your server to activate not only all of our licensed OS’s but also both version of Office.  As many of you may have experience, it was a long and painful road and in the end I never really got a clear answer from them.  Although my favorite response was a voice mail I got from the Microsoft Volume Licensing team which said

“both products can coexist on the same server. However there may, and we stress the word may, be some application issues.  We recommend one product version per server.  But hypothetically you could run both”

This, to me, was basically a non-answer and provided no help.  But a few days later I received a phone call with the same group and had an actual conversation.  The most vital piece of information I received from that conversation was the fact that the office team treats these products independently and that there was no hierarchical nature intended.  To me that confirmed that I did indeed need to install both key packs and the they ‘should’ not conflict with each other.  With that information I went a head and installed the Office 2010 key pack and, much to my relief, everything worked fine.  Our new KMS host now activates all OS’s as well as Office 2010 and Office 2013.

My only hope is that Microsoft learned something from this as well and will update their incomplete documentation.


windows-8-1-logo-sm

 

Anyone who has been paying attention to the RTM (Release to Manufacturer) story for Window 8.1 and Server 2012R2 knows that it has been rife with drama.  For those who missed it, here is the background in a nutshell.  Historically Software Assurance (SA), MSDN and TechNet customers have had access to the RTM bits almost as soon as the products were RTM’d.  However this time around Microsoft decided to change things and did not release the bits to us (I find myself among these customers at this time) when the RTM milestone was hit on August 27th.  We were told we would have to wait until the General Availability release on October 18th.

Apparently Microsoft was unable to predict the obvious backlash that was the result of this new policy.  So when the unexpected complaints started rolling in, they did the right thing and decided to release the bits early to the aforementioned groups.  This was great, with one exception.  Microsoft still was not going to release the software (and the requisite keys) to the SA customers though their standard Volume License Service Center (VLMC) site.  We were told (now you know specifically which group I am a part of) that we should just get our bits from our TechNet subscription (SA customers also get a TechNet subscription).  This was fine for testing but for those of us wanting to upgrade our KMS infrastructure (Licensing infrastructure for Servers and Enterprise version of Windows) and be ready for users by the October 18th GA date, we still needed our official KMS keys (which are provided by the VLMC site).

Well after some back and forth with various resellers and MS reps, it appears that our keys have finally shown up in VLMC site.  They are not in the obvious location so you need to dig deep to find them.  First off know that the RTM bits are still not available in the site and even if you “export all keys” from the “Download and Keys” tab you will still not find the keys there.  However if you navigate to the “Enrollment Details” page for your active enrollment and then click on the “Product Keys” sub-tab, you will find your MAK and KMS keys for both Windows 8.1 and Server 2012 R2.

This just leaves us one question to be answered.  I have heard rumors that I cannot apply these new KMS keys to the KMS server without first installing a patch to the server (currently running on Server 2008R2).  Yet I can find no official information about this patch.  Even our MS reps are at a loss on knowing anything more (yet they have heard the rumors as well).  MS, so far, seems to silent on this one.  Let’s hope they give us something soon.

Update: Our MS rep confirmed that the needed patch to update our KMS server would not be released until close to the GA date.  He suggested that if we opened a support ticket we could probably get early access to the patch.  I wasn’t a fan of that option.  Instead we simply installed a copy of the RTM Server 2012 R2 and applied our KMS key to that.  So far things are working well.  We have already hit our minimum counts for both server and client OS’s and should be migrating the server into production soon.  So after a bit of work and a lot of frustration, looks like we will be ready for GA in a few weeks.