[1703, cu] Activation issues with some machines

[Spangle]

Hi I deployed Windows 10 build 1703 over the summer using the Deployment Workbench to a mix of new machines and existing ones. I also set up one of my DC to activate Windows and Office by Active Directory.

 

Out of 600 odd machines, I have a suite of new machines and a suite of rebuilt machines that are running into activation issues. Initially the machines activate correctly after 7 days activation fails also office failed to start. Other machines don't appear to have an issue. I reactivated my own laptop against the server no problem and the rest of the school aren't baying for blood.

 

From the research I've been trawling through it points to the software protection service being some how restricted. Yet have try giving everything full rights to the service and still hit a brick wall. I have re built the machines which bought temporary relief until they tried to re licence.

 

I'm really stumped why these two suites in different depts. with different sets of software on keep falling over.

[KibosJ]

We've had a few 1703 builds fail to activate here too, installing the default KMS client key (no idea why I would have to do this) fixes the activation for us.

[Spangle]

If I try to install another Key KMS, MAK or even run slmgr.vbs -dli I get an 0xC0000022 error on these machines

[ITJS2015]

I have built a windows 10 1703 with no issues with licensing, my windows 10 key is already activated once its has finished and logged in. The office software I have to run word and activate the software through the internet as the key was pre installed in my image before sysprepping my machine and capturing it.

[Spangle]

I found the issue in the end. It was a rouge GPO playing havoc with C drive access. It had been created a few years ago to allow some music software to run. Evrything seems to have settled down now.