absolutely my pleasure .. and i mean that .. as i told Alex.. im not skilled in writing programs.. but i am willing to contribute in any way i can.. if you need any more testing/help .. don't hesitate to ask .. this way i don't feel like im just taking
Ok so WZOR.net has a link to an updated activator, mini-KMS_Activator_v1.041.exe. I downloaded it and now it supports Office 2010 and Windows OS. I hope Phazor can update his KMS package to include the new engine and support Office 2010.
File: mini-KMS_Activator_v1.041.exe CRC-32: 9b9f9357 MD4: 61a0e76d2b9fc0dc9742b3b19d1f954b MD5: a515493f173bb46b95a48c9e1cfb0933 SHA-1: 4b91b5b96420a226e82fc45de6c815979111a381
No, i definitely wont do that. ZWTs emu was a different case because it had no automation and no user interface whatsoever, but WZORs has, so there is absolutely no reason why someone couldnt just use that one. Besides, who is to say that this isnt just another ZWT-based app anyway? I have already seen one other 'product' where ZWTs emu was merely well hidden within the code, so just because someone distributes it as 'new' doesnt mean it really is new... (Which of course doesnt mean that is not new, it may well be. Im just saying it is not impossible that it is really based on ZWTs emu also.)
OK, took me but 5 minutes to find out that it IS ZWTs emulator. So no new 'engine' there, just a slightly fancier GUI made with Smart Install Maker...
So can you update your KMS proggie to support office 2010 enterprise? Even if the base KMS engine is the same, add GUI support for installing office 2010 keys.
I'm trying to use the activator with server 2008 R2 enterprise edition and no matter what I do I get an error "0x800705b4". Ideas?
ACTIVATOR.MINI.KMS.v1.051.FOR.NEW.MICROSOFT.VOLUME.PRODUCTS-FINAL FILE: mini-KMS_Activator_v1.051.exe SIZE: 1,070,607 byte CRC32: E06B74F6 MD5: A0E4F5BCD5AFC8B891CAFCACCEC37364 SHA-1: AFD54D5FD061171C398DCD2B4CD937DC1E99A1B7 The activator is based on ZWT KMS-Keygen. KMS-Keygen is installed as Windows Service, not too much memory used, around 2 mb of RAM. Code generated by KMS-Keygen is not always valid, that’s why sometimes activation may fail. In this case just repeat activation request. This is KMS-Keygen problem, but not the the activator fault. Activator works on 32 and 64 edition of Office 2010 and Windows 6.0 or newer. Activator has following functions: - Activation of Office 2010 VL products - Activation status check of Office 2010 products - Trial reset for all Office 2010 products and Windows 6.0 or newer - Entering of KMS-Client keys for all Windows VL editions - Activation of Windows 6.0+ VL products - Activation status check of Windows 6.0+ products
0x800705b4 is "timeout period expired", which possibly means broken connectivity. You might want to check firewall settings, etc. This is unfortunate. However, if you expect help, provide more info: - the exact Windows version/edition you want to activate (for example: Windows 7 Enterprise); - what methods have you tried and what kind of errors did they give you (with exact error messages text, if possible).
i got "Windows 7 Enterprise x64 Edition" downloaded it from microsoft free 90 days trial i tried Windows 7 Activator RemoveWAT but i still have a message that my windows not activated at start up.. and the 180 activation trick..did not work either...and the rest of activators not really supports the Enterprise edition... besides the mini-KMS Activator, did not work either..it keeps saying about the servers is offline and some kind of error like > 0x0ID somthin...i dont remember anyhow..i lost the hope of acitvating it....so i gave a try on Opa thread "The Official Windows 7 Repository" and downloaded the ultimate x64 and it working fine like a charm .. thank you guys for providing your help to activate the enterprise edition.
If the KMS Server is running, and you get a 'unavailable', then my guess would be that the Server doesnt have firewall permissions or the port is not set to 1688...
Do we need to run the kms emulator/server on the same machine being activated or can it be on a different machine/vm? When I try it locally, it works. This is the message I get trying to activate using another machine running kms.
I've had success running across the network, even on an XP machine. Try pounding /ato a couple times, and make sure the UTC time of the two systems are in sync.
Strange, I activated Office over the network just fine. Still no luck with Windows. WinFLP, are you using Enterprise with the default client key?