R2 and force myself to use Win2016 Server to solve problems? Running slmgr.vbs /dli on server I see requests are flowing and they fail every time. Then I turned a Win10 Pro on, used slmgr.vbs to remove the old MAK key, applied GVLK key for Win10 ( W269N-WFGWX-YVC9B-4J6C9-T83GX), then run slmgr.vbs /ato to register license but I keep getting error 0xC004F074. So I gave up I know I should have tried using powershell commands: anyone can eventually help me?Īnyway, being in the need of configuring it very quickly, I installed Win2012 Server R2, installed role, configured service applying the KMS key and activating it and everything started. But when I tried to configure it using Volume Activation Tools it failed to start, no way for me to make it work. I have to create a KMS infrastructure in my company: I've read loads of MS docs and how-tos, I've searched the net but I'm still unable to make it work as expected.ĭNS is configured properly, returning the server name for SRV requests on _vlmcs._tcp.įirst I tried to install a Win2016 server and maybe this should have been the best solution to license Win7, Win8, Win10 and Office 2016, but nowadays it's impossible to have a GUI so I used server manager and connected to server (powersheel connection worked too), then installed "volume activation" role.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |