1. Both works in the same concept, KMS_VL_ALL is a script batch - KMSpico is a .net4 app both works in offline. 2. NO wmc option is not available once you activate using KMS.
I have been playing with your scripts. After looking at all the posts of this thread, it appears that some problems there a timing issues. For these reasons timeout commands have been added to various scripts. Fot the TuneMiiror, we could loop on the ping command until it is ok (of course we have to limit the number of iterations to an acceptable number of times). For the KMSServer,one option would be using the PortQry program from M$ which can test if port 1688 is listening (command : portqry.exe -n 192.168.1.26 -e 1688 -Q. Completion code is 0 is port is listening).
Replaced timeout /t 3 /nobreak >nul 2>&1 with ping -a -n 4 10.3.0.1 -4 >nul 2>&1 its work well. NOTES: To see ping -a -n 4 10.3.0.1 -4 working remove >nul 2>&1 from cmd line.
first of all, a big thank you for your hard work and also for precise answers also pun is saying opposite thing. after activating win8pro using MS-toolkit,dn i added wmc using legal key without problem In win8.1pro case according to you this is not possible with this version of script/KMS activation, we may get this feature in future release of the activation method?
In 8.0 you could activate pro with kms and then upgrade to a free wmc key. This is not the case in 8.1 You have to install directly to ProWMC if you want to use ProWMC with KMS activation. You also have to use one of the KMS Server emulators here on MDL as real KMS servers don't support KMS activation for Core/CoreN/ProWMC
It will, I used it to activate ProWMC. It is only 45 days activation though, unlike normal 180-day KMS activations.
So then what key do I use? Im not asking for someone to give me a key. Im just curious as to which key I should be using. I think I might 1 of those free WMC keys M$ was giving out a while back.
Tap driver and Tunmirror are necessary for kms v6 protocol for self-activation. They are not necessary for activating others. You can also fool the self-activation's localhost block by making a router forwarding procedure, but I don't know the process well enough to describe it. KMS v6 is used in build 9600 and on Office 2013 using those systems.