No clue mate, haven't been following things on the forum just lately. I just grabbed it from the post a couple of days ago and binned my previous version. It's still my preferred KMS solution, just great. Edit: There's a changelog in the post... Code: v2 -Fixed a bug in KMS_VL_ALL script on x64 systems Therefore I assume abbodi would have also applied the same fix to the $oem$ folder stuff.
Going to link your post to Ratiborus and await... ed. Here it is his response: Sorry bodmas and anyone else requesting for the same feature. Well in my signature you might find some of those solutions his talking about
Reply to your post 3272 with a question???? So what you are saying is creating above firewall rules + installing KMSServerService on Server 2012 R2 will serve as Local KMS Host and I don't have to use MTK2.5.1 on any other OS installed within the lab (Home lab). I have 1 Server 2012 R2 Data Center that, I would like to make it KMS host and install few other Server 2012 R2 for other lab exercise. These servers should get activated using local KMS Host activation.
Thank you Jackmonter5. This is what, I will do. 1. Install Server 2012 R2 and use MTK 2.5.1 to activate the product - Install ADDS 2. Install Hyper-v role, create Win 7 virtual machine and install KMSServerService from MTK 2.5.1 3. Create DNS entry on DNS server as per above 4. Create Server 2012 R2 virtual machine to test for local kms activation. Will perform above test during this weekend. I will disable firewall on the DOMAIN. So no need to create firewall exception rules.
Thank you for this I was looking for something to get this working for my local lab and THANK YOU. It worked....