Win 8.x • Win 7 • Vista - 'Multi-OEM' ISO Project

You need to login to view this posts content.

 

Anyone had luck using this with MDT 2013? what would be the best solution for multiple installation? (50+)

 

Thank you, that's great
but lenovo wallpaper not same as original wallpaper
i upload it from my laptop
[h=3][/h]

 

The ones contained in this project are original, of course. However it's impossible to have ALL original ones from every and each brand and model.

 

You need to login to view this posts content.

 

oobe.cmd file works regardless if oem or retail. If oem then use firstlogin.cmd....if not oem then use setupcomplete.cmd. I have had no issues with using the oobe.cmd file for oem or retail using win 8 or 8.x....just make sure to use correct firstlogin or setupcomplete cmd and all will be good.

In fact, if truly oem machine with dm-key in bios the oobe.cmd file included in this project will extract the key and apply it during the setup process of windows. Everything is done for you. Of course, if using this project on a non oem machine you will have to find a way to activate it....either through kms or phone activation.

Searchengine did a great job on this project. Thanks again Searchengine!

 

Agreed, searchengine did a splendid amazing job indeed. It's a pity he left MDL cerberus8855, could you help us keeping this project alive and updated?

 

He left? Really? Why do you say that? Sure he is not just busy like most of us? As far as keeping it alive, not much to be done to it really that I can see.

He was online here at this site today...look at the first post of this thread and see when last edited...

 

You need to login to view this posts content.

 

mmm...maybe he just needs a vacation....heck we all do for that matter. lol Who knows and if that is the case then he will surely be missed. As far as ppl asking me to pick up this project, I see no need like I said earlier plus the source for the tools used to extract the dm-key and apply it are not available so I or anyone could not do anything with that unless you rebuild it yourself from scratch, which can be done but no need for they work like they should. Maybe he feels this project is done now and some ppl are just getting on his nerves. It happens to all of us at some point in life. I don't know for sure but I wish him the best reguardless. Thanks for all your hard work searchengine and hope you keep in touch at least.

 

Damn. I wish to be optimistic but... no. Someone who needs vacation just do and that's it, maybe a little "say you later on, a few days, weeks", but asking for account deletion?

 

We don't know why he said that and that is his right and I as well as others need to respect that. Just saying. Maybe something happened and he is just tired of it...who knows. I know he will be missed not only for his projects but also his character. He is a good man. I wish him well in what ever he does.

 

Well this is true and I agree with you and all my due respects to him, all the best for him.

 

You need to login to view this posts content.

 

Oh, could you do that, please? I can't believe this either. Let me tell you I didn't know him at all but his work is awesome and speaks by itself.

 

I'll see what I can do. Hopefully, I still have the number somewhere. Not promising anything tho.

 

Windows 8.1 with Update [CSL-Core-Pro AIO] x64 for OEM machines

I did my Windows 8.1 with Update [CSL-Core-Pro AIO] x64 dedicated for OEM machines (UEFI) with the following sku selection screen:
Windows 8.1 Single Language with Update
Windows 8.1 with Update
Windows 8.1 Pro with Update

ei.cfg file is the same used in this Multi-OEM project:

Code:

[EditionID]


[Channel]
OEM
[VL]
0

I am testing on VM for a first stage. The problem is with sku CSL, no OEM branding as expected as the other skus.

Any thoughts?

 

Can you tell me the actual name of win 8.1 single lang. from windows after you installed it. Like does it say Windows 8 Single Lang or something else from the information window? I don't have that ISO so I cant test....kinda guessing for now. Need to know what the actual name that version in windows to understand more. Thx.

If I cant tell from that info, could you possibly upload somewhere so I could test it in VMware...since I don't have that version. Would make it easier and faster to troubleshoot myself.

Just from what you said above it looks as if the script is breaking before the branding. Probably at the check version but not for sure. I'm shooting in the dark for I don't have that ISO to test.