Volume Activation Issue


hello, we're running vamt3.1 on server 2008 r2.

first issue appeared when trying add kms key windows 10 enterprise. error saying wasn't valid vamt database. found out because admin created vamt database left company , database had him set owner. able change owner nt authority\system , can access in vamt.

windows 7 pro/enterprise , windows 8.1 enterprise machines still activate without issue.

the windows 10 enterprise kms key has been added vamt refuses activate. "no key management service contacted". i've forced client point correct kms host using slmgr /skms command, ensured correct key installed on client. there security-spp event shows "the client has sent activation request kms machine" , lists correct info kms host. kms event log on host shows "an activation request has been processed" client in question no other errors why client still won't activate.

i know there threshold of 25 requests before machines activated specific key/os that's trying activate or matter if it's mix of os'?

figured out! had install kb 3079821 on our 2008 r2 server, rebooted , installed , activated the server 2012 datactr/std kms windows 10 kms key found on our volume license site.

once activated, able start activating windows 10 clients.




Windows Server  >  Windows Server General Forum



Comments

Popular posts from this blog

server manager error: ADAM.events.xml could not be enumerated.

Cannot access Anywhere Access using domain name?

WMI Failure: Unable to update Local Resource Group