I probably owe you guys an apology for the confusion... Yes, the problem is in deed that the 'set host machine name' command in KMSA 5.0 and earlier is simply just -skms 127.0.0.1 The thing is that at the time, when i made 5.0, i had no idea that some machines might explicitely require the port bit as well, because the KMS Service normally defaults to 1688 anyway, and my tests on several virtual and real setups never indicated that this could ever be a problem either. On the contrary, all in all i did like a dozen fresh installs and on every one of them it worked perfectly fine without setting a port number. Thats why i couldnt exactly see this coming, otherwise i would have put the port bit right from the beginning, of course. But thanks to bugreports i am aware of the issue now, and the command in 6.0 (which is to become UniKMS) has already been changed from plain 127.0.0.1 to localhost:1688 That way the port will be set right in any case, whether already at default or not, and this particular problem will no longer occur.
I did test the UniKMS Alpha when it was released a few weeks back simply because I trust this forum and its developers. At that time, the UniKMS failed and so did the Mini-KMS, for that matter even the ZWT. However, that was in the earliest days of the alpha release. I think with the success today, the problem seems to have been identified and solved also thanks to various members. Perhaps now when I need to, I can activate Enter/Pro thru your Uni-KMS.
The Alphas dont include any features like key installation and host machine name setting yet, these things are left to the tester. I only made them so i can gather some feedback on how well the basic application itself works, because if many people had reported problems i would have had to try a different approach. (Which doesnt seem to be necessary.)
Looking forward to the new version. I like the KMS activator, since I can use it on Windows 2008 R2 and Windows 7 Enterprise. Keep up the good work Phazor
As always i will do my best. Feedback is looking good so far (no crashes or anything) so 6.0 should become a nice universal KMS solution for Windows and Office. (Thanks to Team ZWT of course, without which there would be no offline KMS activation.)
command line commands can accomplish the same thing the KMS Activator does. It is just a GUI and works well but it is simply an overlay for sending the commands to the ZWT KMS server. I'm not trying to take away from the work on the program, it is great and many people find it useful. I am just saying don't be a 1 trick pony. If something doesn't work have an alternative available. Another activation method using KMS is to find one of the KMS Servers on the internet. A great tool that I found was IR4, since windows is fully functional in non-activated mode it just rearms forever by copying the activation files from your fresh install and stores them letting you replace them after your 150 days are up, giving you your rearms back. Though if you trip activation you will have to use one of your rearms. I haven't tried any of the loaders since the old one in Vista, and those hung my VMs at the BIOS screen. They work fine for the most part on physical machines. You can always just load a SLIC table into the BIOS too.