Multi OEM/Retail Project

Let me explain the process of the "if" added kms solution. At the point of run once login the reg file calls script to do cleanup and check activation. All activations if present will show activated by this point so if kms isnt need of course it will be skipped and cleanup will finish. If no other activation is present then kms will turn on and do its thing to activate (win8.x and win10). Win10 upgrade is even activated before run once reg entry is ran so it too will show activated and kms skipped. If win7 enterprise then kms can activated and will. I am not replacing oem activation or even paid retail license keys but instead creating another option if all else fails. I have seen a need for this in the past and others have mentioned it to me but I was more focused on bug fixes. Ppl can still use the paid retail license key by creating or editing existing pid.txt file and entering the key there but need retail.txt file in order to skip activation's within the script and windows will auto apply it.

Let me also explain that kms activation's are not piracy but used in corporate computers to activate many workstations with one image. This is very common in the business world and M$ will never get rid of it because of this.

 

Seems I opened a can of worms here with this discussion. lol

 

If you did not pay for the key then it is already pirated. lol

 

You need to login to view this posts content.

 

After all the discussions in the thread and in pm on the subject of kms I will make it an option that users can add if they wish. Keeping it separate and not automatic within the project. I will add the layout under options folder and users can add/replace if they need it. Making it auto seems to make users uneasy even though the script could be made smart to avoid conflicts with other activation's. This should be everyone's mind at ease.

The only draw back to this type of method is it will not show activated in log file if kms is used since it is separate.

 

You are taking what I am saying out of context. Dont worry kms is kept separate (optional) as said above in previous post. If you have embedded keys and vl licenses you are legal. This should be obvious. lol

If embedded (oem) then script will apply your embedded key and brand accordingly.

If vl license then insert your key in pid.txt file to sources folder of iso and included retail.txt file in project to skip script activation and allow windows to auto apply pid.txt vl license key.

If retail then insert your key in pid.txt file to source folder of iso and included retail.txt file in project to skip script activation and allow windows to auto apply pid.txt retail license key.

Those who wish to activate through kms then add "optional" files and folders to Setup folder of project and it will then apply kms and log license status.

 

@ Mr.X and BALTAGY,
I am sending you both a test beta version for testing. Also conflicts have been corrected and this should not be an issue anymore, period. Let me upload and I will pm you both with beta...

@ BALTAGY,
You pm box is full and I cant send the test build for you to test. Let me know when you clear you pm box.

 

The reason I expanded this project is because I have friends who own legit retail licenses but could not use the project as it was originally. Then there were some that used kms for business or home use and has been requested for many months to be able to use or have included as an optional activation method. All of which are legit activation methods but it is how end users decide to use it. The project main purpose is for legit activation and branding. How the end user wishes to use this project is totally up to the end users themselves. It is not the intent of this project to circumvent any activation method but to make activation and branding a simple process with as less interaction as possible.

 

Done, check your inbox.

 

Think kms might have been a mistake. I will update the first post some time later today with conflict resolution as well but will not include the kms. Its confusing everyone. Just so others know I will say this again, if you mod a machine, mod it for the oem brand (what ever it is) or conflict resolution will not work correctly. There are too many variables to address everything when querying. If you mod a Dell make sure it has Dell mod slic. If you mod as something else the query will not be correct and you will complain to me about it but it is your fault ultimately. lol Just saying.

Edited: Those who have the beta version of this project can still use the kms script and set it up within the Setup folder and script will still work with it. The script has if exist so if setup correctly it will find it and run the kms script. But to support it in this project means I have to support the kms as well. I dont want that responsibility. The thread will turn into a kms support thread instead of the main project. I dont have the time either. If anyone wants to fork this project with the kms script go for it but I wont support the kms part myself.

If questions about the kms activation script I was using contact abbodi1406 because he is the creator of the kms script minus the cleanup section. Everything else was done by him. I thank him for his permission but I choose to decline kms from being included.

 

@ BALTAGY,
Can you please try the updated v10 build 1 query tool on that machine if you still have it. Its same version and build but updated it to hopefully correct your issue. The project is updated as well with 9-3-2016 same version date (uploading now so give me a bit). Project is uploaded now. If unsure of what version you have check the hash values.

 

First post updated 9-3-2016 to correct some oem conflicts. Hopefully this resolves BALTAGY's issue. I am trying bro. lol

 

The project has fix as well so your good to go. Glad it finally worked out. lol

 

First post updated with same version date to reflect silent update which addresses script crashing. Sorry about that.

New hashes for project with query tool:

Spoiler

CRC32: 069A4B16
MD5: 1755EFB00288498A2A3635680BC9214A
SHA-1: 1AC7A8AD51AB2DCF5DD667E9B3003A78ECB0FADB