Garacesh Posted January 6, 2016 Posted January 6, 2016 Since Windows 10 doesn't want you to change a lot of stuff until it's activated, and I don't have the 25 machines required to use KMS, I'm attempting to use our MAK to authenticate them. I seem to always be getting the error 0xC004F014, but no further information. This page of common activation errors gives no information. This Technet post details the issues, but doesn't have an actual response, just a generic 'Go ask elsewhere' post. There is no embedded OEM key. This is a fresh install of Windows 10 from the ISO from VLSC. Using Windows 10 Version 1511 (OS Build 10586.0)
Garacesh Posted January 7, 2016 Author Posted January 7, 2016 Bump. Some more information if anyone else gets my issue. Using slmgr.vbs /ipk gives me an error 0xC004F069, which slui.exe tells me is "The Software Licensing Service reported that the product SKU is not found." This Microsoft page tells me that what that actually means is the timestamp between the machine and the KMS are wrong. Except that time is set domain-wide. And I'm also not using KMS, I'm trying to use MAK. So that's not exactly helpful. Still no solution as of yet.
DJ-1701 Posted January 7, 2016 Posted January 7, 2016 Very odd... as long as the device is able to access the Internet, it should be able to activate. Never had an issue before with previous OSes. Out of interest, which flavour of Windows 10 is it? Education?
Garacesh Posted January 7, 2016 Author Posted January 7, 2016 No, we're using Enterprise here. I've just double-checked the license keys from VLSC, it's definitely a MAK and it's definitely correct. The machine is definitely getting internet access.
Boredguy Posted January 7, 2016 Posted January 7, 2016 Does your MSVLC list product keys list an option for "Windows Srv 2012R2 DataCtr/Std KMS for Windows 10" If so, and you have more than 25 Windows 7 devices, add the key into your KMS and Windows 10 should activate just like your other clients.
Garacesh Posted January 7, 2016 Author Posted January 7, 2016 (edited) The current key on the machine, according to the System page, is XXXXX-XXXXX-XXXXX-XXXXX-2YT43, which makes me think it's trying to use the default upgrade key, but the vbs script to pull a key from reg is giving me -TCQGB (and googling that key doesn't get me any hits), which doesn't match the MAK I gave the deployment sequence in WDS. @Boredguy Hm, it can be any Windows clients? I thought it had to be of that type, i.e. Windows 10 in this case. No, it doesn't, at least not to that phrasing. I have the following for Server 2012: Windows Server 2012 Standard - Windows Server 2012 Standard Windows Server 2012 R2 Standard - Windows Server 2012 R2 (Std and DataCtr) Windows Server 2012 R2 Datacenter - Windows Server 2012 R2 (Std and DataCtr) Windows Server 2012 Essentials Windows Server 2012 Datacenter - Windows Server 2012 Datacenter Nothing about a KMS for Windows 10 in the 'Product' cell. Edit: In fact, the letters 'KMS' do not appear in that sequence anywhere but the 'Type' column (I've used the Export all keys: CSV option of VLSC) Some of those are KMS keys, though.. More Edit: There's also a bunch of entries beginning "Core Infrastructure Svr", too, but again none of them mention a W10 KMS Edit 3: And whereas our Windows 1 Enterprise listings have both a MAK and a KMS, all entries of Windows 10 only have MAKs Edited January 7, 2016 by Garacesh
Boredguy Posted January 7, 2016 Posted January 7, 2016 Yes @Garacesh, any version. Our KMS key is set to the new Windows 10 one and it activates 2012, 2008, 8 and 7 quite happily as well as 10 You had to phone MS to get the Windows 10 KMS key as they only provide MAK by default now, but it should only take a few minutes assuming you don't get an idiot who thinks you have to have a Server licence on your EES to be able to get that code...
DJ-1701 Posted January 7, 2016 Posted January 7, 2016 With regard to the MAK key, I assume you tested it after the machine was built as well and it still failed? Yes @Garacesh, any version. Our KMS key is set to the new Windows 10 one and it activates 2012, 2008, 8 and 7 quite happily as well as 10 You had to phone MS to get the Windows 10 KMS key as they only provide MAK by default now, but it should only take a few minutes assuming you don't get an idiot who thinks you have to have a Server licence on your EES to be able to get that code... KMS and Windows 10... The darn confusing thing is that there are in fact two different KMS keys for activating Windows 10... Windows Srv 2012R2 DataCtr/Std KMS for Windows 10 (which apparently activates Windows Server as well), and Windows 10 KMS. The KMS host activation doesn't accept the Windows 10 KMS key, just the Windows Srv 2012R2 DataCtr/Std KMS for Windows 10 one... but if you use the Domain KMS activation it happily accepts the Windows 10 KMS key and machines are activated when on the domain. Found that out via experimentation when Microsoft flat out refused to give me the Windows Srv 2012R2 DataCtr/Std KMS for Windows 10... though they did to another school... both schools had the same level of EES .
Garacesh Posted January 7, 2016 Author Posted January 7, 2016 Wow that line was absolutely awful.. And apparently after 18 minutes of being bounced around, despite the fact that they've already given us Windows 10 MAK keys, which shows we are eligible for KMS, all I get is "contact your reseller".... >.<
DJ-1701 Posted January 7, 2016 Posted January 7, 2016 I got that previously as well, I had to stand my ground with them until they spoke to their line manager and then put me though the the US to sort it... at which time they said they couldn't sort it because I was in the UK and gave me another number to call... 08009179016
Garacesh Posted January 7, 2016 Author Posted January 7, 2016 (edited) Thanks for that number! I owe you a pint @DJ-1701. No mess, no fuss, got them both He did only give me the Windows Srv 2012R2 DataCtr/Std KMS for Windows 10 key, but I asked for the other one citing your issues and now I have both Edit: So do I port the Srv 2012R2 key into the KMS, and use the Windows 10 KMS on the workstations? Not set this kinda stuff up before. All one big learning experience. Edited January 7, 2016 by Garacesh
Boredguy Posted January 7, 2016 Posted January 7, 2016 Just put the Svr 2012R2 key into your KMS server and that's it. I can make recommendations for what type of pint to give @DJ-1701 if you like
Garacesh Posted January 7, 2016 Author Posted January 7, 2016 Just put the Svr 2012R2 key into your KMS server and that's it. So then are ISO's obtained from VLSC are configured to use KMS by default?
DJ-1701 Posted January 7, 2016 Posted January 7, 2016 So then are ISO's obtained from VLSC are configured to use KMS by default? Yeah, by default they should look for your KMS Host Server that has been setup.
Boredguy Posted January 7, 2016 Posted January 7, 2016 Yeah, by default they should look for your KMS Host Server that has been setup. And MAK if you don't have KMS configured and the stars are aligned.
Garacesh Posted January 7, 2016 Author Posted January 7, 2016 Yeah, by default they should look for your KMS Host Server that has been setup. And MAK if you don't have KMS configured and the stars are aligned. So just to double-check (seriously, thanks again for all your help guys) I should generate a new deployment sequence in MDT that has no key configured, and it'll find my KMS and sort itself out, provided I've imported the new Server 2012 R2 key into the KMS? Then again.. This still doesn't get to the bottom of why the MAK doesn't work lol. But if I can get the KMS working then that's fine.
Boredguy Posted January 7, 2016 Posted January 7, 2016 So just to double-check (seriously, thanks again for all your help guys) I should generate a new deployment sequence in MDT that has no key configured, and it'll find my KMS and sort itself out, provided I've imported the new Server 2012 R2 key into the KMS? Then again.. This still doesn't get to the bottom of why the MAK doesn't work lol. But if I can get the KMS working then that's fine. That is correct. You can also force your current built station to use the KMS key "as is" if you run the Volume Activation Management Tool on your KMS server, and tell your station to Activate -> Volume Activate.
Garacesh Posted January 7, 2016 Author Posted January 7, 2016 (edited) That is correct. You can also force your current built station to use the KMS key "as is" if you run the Volume Activation Management Tool on your KMS server, and tell your station to Activate -> Volume Activate. No dice Volume Activation tools, Next. Active Directory-Based Activation, Next. Install your KMS host key, XXXXX-XXXXX-XXXXX-XXXXX-XXXXX, Enter a name, might as well call it Windows Srv 2012R2 DataCtr/Std KMS for Windows 10 so it's easily identifiable.. Next, Activate online, Commit. Yes. Error. Edit: KMS is Windows Server 2012 R2 Standard, so should definitely be OK. Edited January 7, 2016 by Garacesh
Boredguy Posted January 7, 2016 Posted January 7, 2016 (edited) You don't want to select AD based activation (that's the Windows 10 KMS only) The 2012 key is via the KMS Host option. Edited January 7, 2016 by Boredguy
Boredguy Posted January 7, 2016 Posted January 7, 2016 If you get an error (which you still might), here is a site that has all the steps to patch your KMS server to support Windows 10, removing your current KMS key, and adding the new one https://blog.workinghardinit.work/2015/08/12/find-and-update-your-kms-service-host-key-to-activate-windows-10/ 1
Garacesh Posted January 7, 2016 Author Posted January 7, 2016 (edited) Error 0xC004F050 The Software Licensing Service reported that the product key is invalid. Hotfix KB3058168 apparently does not apply to the machine. What the deuce.. Time to ring them back I suppose.. Edited January 7, 2016 by Garacesh
DJ-1701 Posted January 7, 2016 Posted January 7, 2016 Alternatively if you go through and add the Windows 10 KMS key to the AD based activation, that should work for any domain joined machines with Windows 10. Also it supports from just 1 KMS device on the domain.
sted Posted January 7, 2016 Posted January 7, 2016 you have used the right iso to install the os havnt you as there are a few for each version (its like trying to use a windows xp retail key with an oem disk it will just fail)
Garacesh Posted January 7, 2016 Author Posted January 7, 2016 It.. uh.. it turns out we haven't paid >.> We pay yearly and didn't get any reminders.. We're here thinking we've paid the whole subscription but it turns out we haven't lol. So we've had keys issued to us, but there's a block on them until we fork out some dolla. DEEERRRPP.. Queue frantic calls to suppliers..
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now