Ihave installed the software from the ISO file I downloaded from the volume licensing site. I have learned that this file installs a KMS client version of the software by default. I have both KMS and MAK keys for this software but since I'm only installing 2 instances of the software, MAK makes the most sense to me. I don't have a KMS host running on my network so I need to use MAK client. However, I cannot get my MAK keys to work when I run a powershell command such as slmgr.vbs -ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx. I always get the same result which is an error message 0xc004e016 - on a computer running ms windows non-core edition, run slui.exe to display the error text.
Basically, its telling me that it doesn't like the license code. So, is there a separate ISO file for MAK client installations or is there a way to convert this KMS client to a MAK client. There is some documentation on this on google but they did not work. Just received the same error message. Can anyone offer some assistance for this issue? Calls to MS support have so far provided no help.
The reason you can't activate it is because you are not connected to the internet. I learn it the hard way. 2012 R2's error is very generic. When you put the license key, it try active the license right way. Because you dont have internet, it cant verify it.
You can't activate windows by phone because you have not put in the correct product key number. Here are the steps and I was able to activate over the phone. I have not see any one post these steps yet. I spent 4 days with Microsoft trying to get some helps. With other user's input and I was able to put together the complete steps.
Ok, I went back to MS Volume Licensing and downloaded the ISO file again for MS Server 2012r2 and I noticed that it was different that the one that I had previously installed. I reinstalled this OS on the server and my MAK key worked this time. So all is good again. Thank you for your input.
That's it. For some reason Server 2012 R2 doesn't seem to sync up with an outside source at all, so until you set it manually, you're going to be off and activation and checking for updates won't work. For my install today the system thought it was November 2014 - 11 months ago!
Make sure you aren't accidentally using the KMS key - that needs to be installed on a KMS server and won't work directly. Also make sure you installed the correct version of Server 2012R2 - some ISOs give you the option to install Standard or Datacenter, but the license key from one will not work on the other.
If that still fails, the easiest thing to do would be to install the GUI and activate it through the GUI, since you'll be able to see the full error messages easily. One of the nice things about Server 2012 is you can add and remove the GUI at any time.
If it still fails, you'll have to call Microsoft support for them to verify the license key is correct or issue you a new one. Contacting wherever you bought the volume license may be easier than calling Microsoft directly - they may know who best to call to handle licensing issues.
Even though the server looked like it had internet, because it could reach the DNS servers. Internet traffic was being blocked by the firewall the client had in place. Once the policy allowed the IP out, activation completed successfully.
I would expect that although there is something in the app which resets the visibility, it is less likely that there is something which resets its parent. So if you create a window with extended style $WS_EX_TOOLWINDOW so that it has no icon on the task bar, and set the program window so that is the parent then you can just hide the toolwindow. It might work and then you wouldn't need to keep monitoring it.
But maybe rasim's script will do the job for you. When that is running you simply hold down the shift ket and minimize a Window and it disappears from the task bar and from view. Optionally you can use CTRL instead of SHIFT.
First is to create a new window and make the activation window a child of it. If my window is hidden the child will be hidden as well. It also won't have a taskbar icon because my windows doesn't have one.
After it becomes a child window I tried to just Sleep forever. A close look in process explorer shows that AutoIT's Sleep is using 0.01% CPU power so I wrote a little exe in C# to suspend a process using a given process ID.
Hide the activation window and suspend its process. I realized that slui.exe is running 2 times. I guess one process is creating the GUI and the other brings it into view after some time (which was my initial problem).
I've also attached the ResumeProcess.exe just in case someone needs it. You can just pass a process ID to them and they will suspend/resume for you. (I know this could've been done using AutoIT as well using DLL calls I was just too lazy )
3a8082e126