The problem with that is that it will require a restart for those to be enabled....oobe.cmd only runs once so again...a problem. This is why 2016 tp4 installing server with desktop experience option works perfect....all images are present thus the branding works perfect. End users can always enable through dism in iso as an alt. Obviously this would not be ideal for noobs but servers arent meant for noobs anyways. To test this theory I am going to remove the backup part (where I believe the script fails) since there might not be images to backup and see if script will move the user images to correctly location...will do this for the img100.jpg as well. This might work and then again, might not. This explains why the failure isnt logged also...it looks for the .bak image file which isnt there. If it does work then when experience and themes are enabled the images will already be there. Worth a shot anyways, right? lol
I mean you could make a oobe.cmd that is called twice by editing the run once registry area. It doesn't sound pretty but it would fix the issue. I know its a crappy answer but its an option lol. Enable all your server stuff then run the oobe again. reg add "HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce" /v "Oobe" /t REG_SZ /d "C:\windows\setup\scripts\Oobe.cmd" /f That is what I'm thinking ^^^
You still need to do a restart in order to enable it. I'm not trying to be non-optimistic just saying though. Good luck.
give it try and see Edit : testing now ... failed Code: Enabling DesktopExperience and others features (ServerMediaFoundation + InkAndHandwritingServices) on offline (DISM) --> ISO --> VM --> fail info after OS Install : Desktop Experience installed DELL Theme Installed but not selected by default same problem with "img100.jpg" & "user"
That is ran well after oobe.cmd file is ran thus some images will not be replaced. Doing from desktop is a different ballgame.
Maybe servers dont allow some editing or is locked down. Either way, requires more time then what I have right now. I will do some tests on my end over the next few weeks but to work on this everyday, not going to happen. lol Myself personally dont see the importance of having branding for servers anyways. This is why I never really got into them with this project. The times I have played with them, nothing but major problems with branding every time. Only home users with servers really wish to do this type of thing, corporate world can care less. lol
Think this might have something to do with the theme being applied in 2012r2. The user images and img100.jpg more then likely need some permissions. Will test this process in the next few days to see if this makes a difference.
I fully agree as introducing server branding makes it overtly complex. Ultimately it is up to you on whether you want server branding to be honest.
Dont know if this will help in any way but I found this tool a few years back to change theme by cmd. No idea if it works in OOBE though. I created it on 7 x64 and its been working on 7, 8 & 10 both x86 and x64 for as long as I can remember. I cant remember exactly where I found the guide (had it in a txt file) but credit where its due! Spoiler Might be some help to you, might not...
I dont need a tool to do it. Let me make myself clear...the project works in vista-win10 but we are "trying" to do branding for servers and that is different. I posted the reg entry for server 2012r2 that needs to be added to script so that theme is auto enabled when you enable desktop experience and themes. Servers are a different ballgame but it still might be possible. Time and testing will tell... Thanks for trying to help though.
Spoiler No worries. Didnt know if it was something that could be invoked during OOBE to help 'set' the theme but reading back last few pages seems its not that simple lol Keep it up though but don't sweat if you cant!
read first post : try to force THEMES by : Code: • You can force install 'ANY' brand theme by reading and using the Force_Theme_[readme].txt