Microsoft Office 2013 x86 with service pack 1
Office Customization Tool 15.0.4635.1000 published 7/1/2014
Windows 7 Enterprise x64
created an MSP file that uses the MAK key and auto activates with the Lync and other Office products installed. The license returns the following:
---------------------------------------
SKU ID: 1b9f11e3-c85c-4e1b-bb29-879ad2c909e3
LICENSE NAME: Office 15, OfficeLyncVL_KMS_Client edition
LICENSE DESCRIPTION: Office 15, VOLUME_KMSCLIENT channel
LICENSE STATUS: ---LICENSED---
REMAINING GRACE: 178 days (256345 minute(s) before expiring)
Last 5 characters of installed product key: TCK7R
KMS machine name from DNS: xxx.xxx.xxx.xxx:xxxx
Activation Interval: 120 minutes
Renewal Interval: 10080 minutes
KMS host caching: Enabled
---------------------------------------
SKU ID: 2b88c4f2-ea8f-43cd-805e-4d41346e18a7
LICENSE NAME: Office 15, OfficeProPlusVL_MAK edition
LICENSE DESCRIPTION: Office 15, RETAIL(MAK) channel
LICENSE STATUS: ---LICENSED---
Last 5 characters of installed product key: PDHT7
---------------------------------------
Why is the Lync software using the Office 15, OfficeLyncVL_KMS_Client edition license instead of the Office 15, OfficeProPlusVL_MAK edition license like it should be?
Using the same x86 office package on a x86 system will do proper license so Lync does use the Office 15, OfficeProPlusVL_MAK .
If install by hand instead of automating with the OCT MSP file and then hand entering the MAK will install a Lync that uses the Office 15, OfficeProPlusVL_MAK when doing x86 office on x64 system. I am guessing something is still wrong with the admin files.
Using a x64 office package on a x86 system will do proper license so Lync does use the Office 15, OfficeProPlusVL_MAK .
Thanks,
Larry
