KMS activations for Server 2016

glenimp617 · 13 Oct 2016 at 10:19

How's everyone getting on activating their server 2016 builds this morning?

Don't worry, I fully expected a repeat of the 2012 / o2016 fiasco and logged a call with MS :rolleyes:

In the meantime I'm building a 2016 KMS server to sort it.

They don't learn do they

ecksmen · 13 Oct 2016 at 19:02

What's the required number of activations before it actualy works?

D3K · 13 Oct 2016 at 19:04

Isn't kms a hack?

On Holiday · 13 Oct 2016 at 19:07

D3K said:
Isn't kms a hack?

No.

Also, just downloaded 2016 now to try out, evaluation though, haven't got keys from VLSC yet.

kayomani · 13 Oct 2016 at 19:22

It is if you run a fake kms server :/

I tried 2016 out yesterday as a hyper-v client and it blue screened installing updates

Seemed ok once they were installed, interested to see the performance of nested vms but I didn't get far enough to try it.

glenimp617 · 14 Oct 2016 at 08:10

ecksmen said:
What's the required number of activations before it actualy works?

on 2012 r2 kms? zero as it doesn't work

2016 kms does though :cool:

I think it's 25 counts before it starts working.

Saundie · 15 Oct 2016 at 17:19

We don't bother with KMS for our servers for exactly this reason. Getting KMS to work for Windows clients and Office is annoying enough. In theory it's an excellent idea, but the implimentation, as you've also seen, isn't excellent at all. Fortunately I haven't had any problems with Windows 7 and Office 2013 activation for a while...