Multi OEM/Retail Project

good work BOB
tested work fine for me

 

Note: The title heading of this thread states oem/retail, not kms. lol

 

Win8.x uses the file that alphawaves edited back in the day to show login background. Nothing can be done from this point as of yet. At least win10 had a work around but win8.x is now the issue.

 

I found something interesting for login background screen in win8.x.

Update: That didnt work so trying another method.

 

I highly doubt M$ will fix win8.x for login background image since they are focused on win10. They will say upgrade. lol

I have read 3 years worth of comments on M$ tech site relating to win8.x login screen color/image and M$ has not replied once so win8.x will never have login screen custom image from this project.

 

Let me also address another issue with the new win10 anniversary update. I have had multiple pm's about kms knocking out the user pic for login in windows 10. The commonality for all of these pm's is kms all vl method. I am not familar with kms all vl method mentioned in the kms section. I only use kmspico that I run silently from setupcomplete.cmd file for testing purposes. I have done multiple restarts and shutdowns and images stay put so if having issues with kms try pico and see your results.

Update: BALTAGY tested windows toolkit and it also works with project images. Must be something with kms all vl then I guess.

 

I edited first post about the limitations of win8.x and the system login background color instead of external image.

 

Sent a pm to you

 

Decisions decisions. lol

 

Thanks to BALTAGY for sharing his log files I am now able to fix any and all conflicts in either the query tool and the project itself. Conflict between Hasee and PB but led to a better resolution. Also something special that might get added that some have wanted included. Not saying just yet because I need to ask for permission first then if allowed will share what might be to come.

 

I will be adding kms as a backup solution in option folder of project for those that wish to use it or not. If used will auto renew but Vista is not supported. Vista isnt used much anymore so I dont see this being a problem. I will work on this more this weekend because I need to add some checks so not to interfere with main project scripting.

 

Let me ask everyone what they would prefer, myself I dont care. Would you all like it to be an optional addon that users add themselves to the project or auto included but modified to address any conflicts? You all tell me what you would like.

 

If you are talking about KMS activation then I'd prefer it to be auto included. I strongly believe it won't harm whatsoever.

 

I did notice some glitches if not a vl version for win7 but will add checks to avoid this within our script so if not win7 vl version then deletion will happen. I dont think most would have noticed it but my ocd says add some checks. lol I will wait and get more feedback from others but thanks for your input Mr.X.

 

I think auto included will be better so project will active all systems with option to disable it and use another KMS if people want

 

"Multi-OEM-Retail-Project" - I recon leave it out or include it but have it disabled by default...

 

that should be optional. because i install windows to lots of notebooks and desktops that have original ms licenses. kms will make them pirated.

 

First of all, i would like to thank you The Guardian and his team for making this awesomeeee Tools.....
This is one hell of a breakthrough, i must say...

If you do not mind and if you have time, may a computer noob like me ask some questions regarding Multi OEM Retail Project?

I have tried using Multi OEM Retail Project with Windows 7 on several notebook such as: Asus K40IN, Asus N43SL, and Dell Inspiron 14.
The installation is a big success and i had the login screen and system information like a real OEM.
But, after installing, i had to use Daz Loader to activate the laptop because it is not OEM activated.

My questions are:
1. After i activate with Daz Loader, the activation is a success. But i cannot validate my Windows 7 by going to the microsoft website. Some times the Windows 7 genuine checker just cannot determine whether the machine has original key or i get not genuine warning. (Is it possible to validate after using Multi OEM Retail Project?). If yes, can you please tell me how to do it.
2. For Windows 8.1 and 10, how to activate the OEM key installed by Multi OEM Retail Project. Is it instantly activated after i inject 8.1 and 10 ISO by using Multi OEM Retail Project?
3. What is OEM-DM key?

Thank you very much for your attention in reading this.

Once again, i would like to say thank you for this amazing tool.

Even Mr.Burn said Excellent to this awesome tool.

 

Think some dont understand the activation process within the scripts of this project. This might get into a lengthy discussion. If bios slic or bios key present then of course that takes president over any kms activation so oem activation will not be issue. Win7 enterprise with kms is common. Win8.x and win10 kms is common for vl editions but script can convert retail to vl if not activated already. oem activation will ALWAYS come first before any other method. Adding retail keys into pid.txt with retail.txt file will bypass oem and use your paid retail key instead.

 

Many variables here and without query tool results and log file it is hard to say. Could be slic or key not included in project or possibly no slic in bios. Hard to say without query tool results.txt file and log file from the project.

With win7 if slic present in bios and slic is included in project you can validate. As far as Daz loader you will need to ask him since he is the dev of that tool.

Win8.x and win10 both use oem-dm key located in the bios for oem activation. Yes, it will be auto activated if legit key. Some manufactures like HP for example use same key for multiple computers and if they use it too much then M$ will not accept key. This happened to a friend of mine and he called M$ and HP and basically they pointed the finger at each other. He bought retail version and used the retail key instead since HP used the key too many times in different computers.

oem-dm key is the activation key that is made within the oem bios to avoid piracy.