2016 tp4 works like it should...like win10. The server 2012r2 has some win7 image names and win10 so I am thinking of doing something different. I can adjust this one. Can you check the screen folder....thats the one for lockscreen that I need to know. You didnt show the contents of the screen folder. Like above pic, this one is the only one backed up. Easy fix so no biggie. Also what is the extension of the user, user-40 and user-200?
What are the screen images extension? png? bmp? jpg? Also I cant tell but is there a img100 pic? If so what extension?
Another beta coming at ya for testing on 2012r2 and if it works now, test 2012. Give me a minute to compile...
Can you give me the full names with extesions so I can add the ones that arent included? Thats all I need to fix this one.
New beta decompile.exe sent to you, apologized. Share log when done testing 2012r2 so I can see its progress. The script was failing for 2012r2 but I am hoping it is fixed now.
Log File : Code: ---Hardware incompatibility and slipsteaming has been known to cause branding failures--- 05/12/2015 1:50:38,66 Project Version Date: 12-04-2015. 05/12/2015 1:50:38,66 Files present and extracted successfully. 05/12/2015 1:50:38,68 OEMs folder found successfully. 05/12/2015 1:50:38,82 Defined Windows Server 2012 R2 Standard x64 version ServerStandard editon found. 05/12/2015 1:50:40,40 Defined DELL manufacture found for branding and possible activation. 05/12/2015 1:50:40,63 License Status: Error, not licensed. 05/12/2015 1:50:40,63 Force theme text file not present. 05/12/2015 1:50:40,71 x64 reg file successfully ran and applied. 05/12/2015 1:50:48,17 Syspdt=PowerEdge 2850 found and applied successfully. 05/12/2015 1:50:48,17 Backgrounds folder created successfully. 05/12/2015 1:50:48,18 User.bmp backed-up and replaced successfully. 05/12/2015 1:50:48,18 Theme backed-up and replaced with $OEM$.theme successfully. 05/12/2015 1:50:48,18 Info folder created successfully. 05/12/2015 1:50:48,20 Files moved to System32\oobe\Info folder successfully. 05/12/2015 1:50:56,18 RunOnce reg entry added successfully. 05/12/2015 1:50:56,18 Script has completed successfully. same thing not fixed
Is the imag100 pic been backed up and replaced (lockscreen)? If not then that too is failing. The whole user pictures part fails but are included...works on other os's but not this server. Hell if I know at this point. Servers are a pita! I dont think servers are meant for this because everything is setup the same but fails. In fact the script doesnt even ouput the failure. This is the strange part. I dont want to do this anymore. Too much time and no demand for it. Most companies dont give a crap what branding there is. lol Seriously, find someone else to spend the huge amount of time this will require. I dont have the time so calling it quits.
lol let forget about it we give it try but no luck focus on Standard OS no more Server S#it This just for Branding BUT Activation would be more craziness NO !
Whats the issue I've been busy ironing out multilingual issues on the powershell oem side. I want to see server branded hehe.
Mmm it's so complicated to brand some server OS Script work fine but something not correctly do the branding on server 2012r2 maybe if we have legit dell machine with real info cert slic ... Maybe we can do progress
@ Smorgan, A good example of branding failure would be the 2012r2 version. It doesnt brand all the user images in the ProgramData\Mirosoft\User Account Pictures\ and will not replace the img100.jpg file for lockscreen. The failure varies with different server edition versions. Unfortunately, I dont have the time to put into this right now to find out why the script fails with servers. The only server that brands correctly is the 2016 tp4...the others all fail. I really need to see how Dell brands the server versions but I do not have access to one. I bet Dell deosnt do complete branding like we are trying to do. Branding isn't a necessity in the corporate world. Think I might know why the failures occur. If the desktop experience and themes are not enabled before branding then the images might not be present. This would explain the failures in those area's. Just a theory but seems justified.
if that so we must find solution to PRE-enable Desktop Experience and run themes services before branding during OS installation i try google it if i get any ideas about that