After some playing with new script...all OS's will now list oem name for wallpaper and theme....vista is the only exception because it doesn't show a title or name for the wallpaper (only show listed image but you can make out the oem in the pic). There is nothing I can do about vista so if you have a complaint, take it up with M$. lol I will upload new version soon (within 24 hrs).
You could play around with the OEM settings in the registry so that the information is displayed in the System Info page. Just a thought. Also when I get back from vacation I'll look into using powershell with this.
Given the flexibility of the pack you could conceivably just make 1 module and that would be the entire OEM pack. On that note I will be back in like 2 weeks catch ya on the flip side.
so the proper OEM is selected automatically during install? Or do I have to specify it somehow. Readme wasn't completely clear.
The first post states to add the $oem$ folder to sources folder of the iso or media....that's it. I have repeated this statement every three or four pages. Its the same as the first post. lol
Kept same version date but did a silent update to the multi oem project to correct grammar and also if extracted files cannot be found then the output'd file will now show on desktop instead of at the root of the systemdrive. Grammar was never my favorite class as most can tell. lol
In a corporate environment, it is interesting to force the theme to a custom theme of organization. To have information that license has been applied, I customized the install.cmd file. Install.cmd After: SET OEMS=%windir%....... SET MARCA= After: ::check • set 'MAN=?' -> if ex......... IF EXIST "%windir%\Setup\scripts\Force_Theme_[readme].txt" SET MARCA=%MAN% Modify: reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OEMInformation" /f /v "Model" /t REG_SZ /d "%SYSPDT%" >nul reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OEMInformation" /f /v "Model" /t REG_SZ /d "%MARCA% %SYSPDT%" >nul Translated with google translator. I'm spanish
There was no need to do all that editing. lol All you had to do is create your custom folder (MARCA) and put wallpapers, info, etc. in it (insert that into the OEM's folder, 7-zipped or not)...then add Force_Theme_[readme].txt file in scripts folder with MARCA only in it and it would have worked perfectly. All that editing wasn't really needed. lol Google Translate... In the future it might be best to ask in this thread and wait a little bit for a response to save yourself a lot of time. En el futuro podria ser mejor preguntar en este hilo y esperar un poco para una respuesta para salvar a su auto un monton de tiempo. Note to others: His above editing broke the original force theme txt file and possibly other things...always ask here in this thread before editing anything to save yourself time and headaches. I have created this project to handle requests such as this and editing will only break other parts, trust me. If end users edit the original scripts and it fails, don't bother posting in this thread to complain because I will ignore the post based on the fact it is not original anymore.
Hello, sorry for my poor english Bug !! I just use 'Multi Oem Project' in an image in VirtualBox. At the end of the installation I have the theme of virtualbox. If I change themes again, I'm the chosen theme. If I change a second time I have no choice but different theme. Why? thank you
You didn't say what OS... Update: I checked win 7 and I can change themes back and forth but I think you might be confusing theme with background image...you must choose the oem theme first then it will show background image in the listing. Win 8.x/win10 acts similar to win 7 which means you must choose the oem theme first then in backgrounds the oem image will show. I have changed theme/background several times in each OS/rebooted and I can always choose the oem theme from the list. I think you are confusing theme with background image is all. The project works just like it should.
Is this project do anything more than in win7 to Apply OEM theme and certs & skipping Product Key dialog box?
If legit oem machine you will not see the key dialog screen but if you are wanting to use kms then use a install key to skip product key dialog (win8.x-10). The project does all oem branding including theme, background, user image, oem info, oem logo, lockscreen, etc. In win 10 it enables advanced logon screen per requests. If win 8.x-10 if msdm table is found in bios then it oem activates. If vista/win7 if matching cert and key are found then it oem activates those. That's all this project does.
x86 & x64 all in one quick question I have an all edition install both x86 and x64 in one dvd do I copy the $$oem folder to both source folders. Sources and Sourc64 folder??