Were no AD Activation keys floating around. I've even tried removing the MAK key from the KMS server, and ensured there I install the GVLK key on my client, then a few minutes later (or after opening Office) the key is reverted to my MAK key. To 500 installs (Even though on the Microsoft Volume License Service Center it claims to have 2.1k seats?). The MAK key I have installed was for testing, and was limited ![]() It's been running great for a few months with no hiccups using the GVLK/KMS host keys. I have a KMS key and a MAK key installed on my 2012R2 VAMT 3.0 server (With all the Win10/Office 2016 patches). Maybe I'm just terrible at Google, but this issue has such a generic description I get results for every "Change/View Office Key" article on the Nowhere on the interwebs have I been able to find a problem quite like what I started seeing yesterday.
0 Comments
Leave a Reply. |