Stupid question time. Why are these files over 700 MB in size? I thought the programs are supposed to get smaller, and they seem to be getting bigger. Someone please explain.
Because that's not a program that's a Virtual Machine meaning there is an Operating System in that file
How can I bridge the TAP Adapter into my local network so that I can activate all of my machines? Currently the KMS emulator loads a TAP adapter at 10.3.0.x ip address and I (obviously) cannot ping it from another local machine (local network of 192.168.10.0/24). When I go to bridge the TAP and local adapter, it fails and errors out. How do I do this? Thanks
You don't point the other systems at the tap ip addresses. You point them at your system (192.168.10.0/24) The problem you might be having is that you might not have set up a firewall setting for your KMSServer.exe If you don't set up a firewall setting, it won't go beyond your own personal computer.
Oh really? How does that work (as far as the networking goes?) Is the TAP adapter Nat'd to the local adapter?
doubt it. Just for KMS emulators and ones that don't require a full VM to run. As soon as we get the tokens and the UUID for the Server 2012R2, we should be able to create our own KMS VMs like before. The emulators are a great stopgap until then, especially since they activate Server2012R2 which is of particular interest to me as I would like to migrate my 6 VMs (domain controller, etc) to 2k12R2 over my Christmas break.
Makes sense. However, my internet speed and bandwidth are too low for me to download an 800 MB file in anything less than a day. Guess I'll wait for something along the lines of MTK. But from what I can see, everyone appears to be doing a fantastic job. Great work, y'all.
Thanks! So if I understand correctly, the TAP driver and TAP device will stay installed, so re-activation after 30 days can be done silently? That's nice! At first I thought each activation cycle would involve installing TAP, activate, remove TAP.
It could be done in a method that requires uninstalling and reinstalling stuff, but that's counter-productive. Once it's installed, my $oem$ folder uses windows' built-in kms-host caching to re-activate itself every 7 days. Even the office script, once successfully activated, will re-activate in the background. I'm basically done with my final effort until someone figures out how to install the tap drivers silently in a way that that creates the tap9 connection that using devcon does. I am just finishing up some testing. Right now I have it either install tap+mirror+kmsserver or just kmsserver depending on whether or not you have build 9600+ installed. So, those using win7 or win8.0, server2008, or 2012, wont have the extra tap+mirror stuff and the net4.5 requirement that goes along with running the tunmirror service. On 8.1 and 2012r2 it already has net4.5 so it's not much of an issue. I'm still testing a few different installs and office stuff since I had to include a few tunmirror program checks. I was stuck on moving/deleting but I got around it when I realized I could simply include the program detection lines. I'll up it soon here...