Appeared to be a proper way to get rid of that chaos in my head, by trying to bring all these little pieces, provided all over here, in an order. May be at least it can help others now a bit. Regards EDIT: Corrected a mistake in client-part of my little essay. No NEED to install any patches, my bad. Try edited version.
and get the key to match your installation. Once you have that, enter this into the command prompt. This step might not be needed if you use Windows 8 Pro or Enterprise. You cannot activate a CORE install of Win8 with KMS btw. What is a CORE install exactly? So I shouldn't install a Pro or Enterprise version then?
I overlooked one small point when doing the win 8 kms server activaton backup in advance tokens manager is for win8 ultimate I have only got pro x64 so I cant add the activation
sorry i meant Enterprise I try to restore the tokens and it says this backup is for a different version of windows
Probably worth looking @ ENT in the long run as it has a few more features like Window2Go etc. Your choice really.
So, all KMS instances that are being installed still have the same Extended PID. This Extended PID appears in every activated W8 client. Can't Microsoft release an update that deactivates every client with this Extended PID? Are we really safe? I mean the whole things sounds too good to be true. A KMS that's permanently activated and hands out legit activations for eternity? Surely they must have a killswitch somewhere. I would. Edit: Or did they really forget about VMs with never-changing hardware?
MS knew how to block hard/soft mod in vista, but didn't do it in win7......so worry about the kms block in win9.
I am just little unsure ware to copy activation files to and how to overwrite the uuid then i think ive got it
For that info check the pdf-file, where uuid is found. For uuid navigate file browser to install-directory of your vm and open the *.vmx-file with text editor, search for the string and overwrite with proper uuid from pdf. DONE! Regards
I can think of a few reasons, eg: Windows 7 VHD is smaller Less ram needed for VM, Windows 7 runs fine with just 512MB For KMS host based on Windows 7 i can add one reason more, eg: Also activates Vista Clients
Yes you are right but setup will be like this 1. KMS Host Plus 2. Windows 7 VHD is smaller = 5 GB approx Less ram needed for VM = true Windows 7 runs fine with just 512MB = true Plus 3.Windows 8 vhd or other PC with windows 8 (For which we are setting up all this) when script can remove that second load then why to keep that. Rest it up to individual which way they want to go EDIT: Who told you that windows 8 host cant activate Vista? Thanks