Jump to content

Recommended Posts

Posted (edited)
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)

 

Yes, he obtained the ISO and keys from VLSC.

Edited by DJ-1701
Posted
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..

 

In that case be aware you may need to contact them again for new KMS keys if your agreement number is not the same.

Posted
In that case be aware you may need to contact them again for new KMS keys if your agreement number is not the same.

 

Well. Bugger. Joyous lol. Still, it's progress, at least.. See, now that explains why the MAK wasn't valid lol.

  • Thanks 1
Posted

Oh come on xD Every-bloody-where I go. It's more likely to do with the email domain change we did a while ago.

 

Still, hopefully once this is resolved I'll be good to go! It's annoying not being able to change some of the settings because it's not valid, and whilst I understand why they did that, it's still a setback I could do without.

  • Thanks 2
Posted
Now if @clairelangton was around during the day, I'm sure lots of comments about you being distracted from noticing the licencing slipup could be mentioned ;P

 

Well I guess texting, and we don't know when the licenses were meant to be renewed ;)...

 

It also depends who is signed up to get the e-mails from Microsoft that the licenses are expiring. If this isn't sent to IT, could easily be glossed over.

  • 3 months later...
Posted

Sorry to dredge up an old thread, ladies and gents, but just to double check, I'm supposed to activate the Windows Srv 2012R2 DataCtr/Std KMS for Windows 10 key on the Domain Controller, right? (i.e. slmgr /ipk $Key)

 

Running it on a Server2012R2 DC and getting Error: 0xC004F050 The Software Licensing Service reported that the product key is invalid when I try. Just want to make sure I'm using the right key before I phone them back up and whinge..

Posted
Sorry to dredge up an old thread, ladies and gents, but just to double check, I'm supposed to activate the Windows Srv 2012R2 DataCtr/Std KMS for Windows 10 key on the Domain Controller, right? (i.e. slmgr /ipk $Key)

 

Running it on a Server2012R2 DC and getting Error: 0xC004F050 The Software Licensing Service reported that the product key is invalid when I try. Just want to make sure I'm using the right key before I phone them back up and whinge..

Do you have this update installed: https://support.microsoft.com/en-us/kb/3058168

Posted

Just added the windows 10 KMS code to our 2008R2 host (with patch) and works well.

using the Windows Srv 2012R2 DataCtr/Std KMS for Windows 10 key. As a standard windows 2012r2 doesnt do it.

Posted
We do not have the KMS on the Domain Controller.

One of our multiple DC's (that redundancy, though) is also the KMS controller.

 

Update: Using the Volume Activation Tools wizard gives me "Invalid product key or license mismatch. Please confirm this product key is entered correctly and is valid for this application or Windows edition."

 

Guess I'm gonna have to ring them up again D:

Posted
Line quality is absolutely abysmal :/ 2 transfers later, with quality getting worse each time, I'm connected to some guy who can barely hear me, and I, him. Halfway through reading out my email for the third time, phonetically (not fun when it's over 20 characters long..) all I get is BEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEP until I eventually hang up. Urgh. I'll try again later.
Posted (edited)

 

Ah, didn't see that post.

 

What do you know, that's sorted it. WSUS doesn't push hotfixes automatically (with good reason) so I had to push it manually. Thanks!

 

Edit: So just to check I have this right.. iso's of Windows 10 downloaded from VLSC automatically search for KMS and thus need no key applying during imaging, yes?

Edited by Garacesh
Posted
Ah, didn't see that post.

 

What do you know, that's sorted it. WSUS doesn't push hotfixes automatically (with good reason) so I had to push it manually. Thanks!

 

Edit: So just to check I have this right.. iso's of Windows 10 downloaded from VLSC automatically search for KMS and thus need no key applying during imaging, yes?

 

Correct, the client will communicate with the server and pick up the license as long as you have a KMS server setup. :)

Posted
Ah, didn't see that post.

 

What do you know, that's sorted it. WSUS doesn't push hotfixes automatically (with good reason) so I had to push it manually. Thanks!

 

Edit: So just to check I have this right.. iso's of Windows 10 downloaded from VLSC automatically search for KMS and thus need no key applying during imaging, yes?

in theory yes but I ahd it last week where because the bios key was windows 7/8 it came up with a daft message (sorry I cant remember it) but adding the generic windows 10 kms code to the deployment task in mdt fixed thatg they all activated fine with that

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 account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...