It will do what you are wanting without issue. The problem in current build version date has to do with Win10 Anniversary Versions only, not other OS's. This project should suit your needs without issue. You can always try in vmware with modded bios to see your results if you do not wish to test on real machine first. Run the query tool first and if it picks everything up then the oem project will also. Again, it should suit your needs with Win7.
I want to thank you guys for this awesome project. I managed to solve both my issue today. Simply remote the brands that we don't use in our environment from the OEMs 7zip file, the project itself was able to only apply to the machines with OEM_SLP while leaving the unbranded custom builds alone. Also if you are using MDT, extract the contents (decomplie, oobe, OEMs) to %OSDisk%\Setup\scripts right after Installation OS, it'll take care the rest for you. Thanks again!
Progress is being made on the win10 anniversary edition's...I found where the lock screen image is but need to find where the user pic is now. Then these two can be installed and stay put. This version is picky. lol
Ok, got user pic and login background sticking with over 5 restarts which also works for those that use kms activation method. It applies all user pics as oem but at least it stay put now. This will have to work until a more perfect solution arises. Let me do some final adjustments then will upload either tonight or tomorrow.
Think we have THE solution to our problem with win10 anniversary editions. A BIG thanks goes out to rockyanexpert for sharing this lil bit of info with me. We owe this member big time!
Seems there is a SystemData folder that holds info. Think this is where the background image is saved but need more testing which I will do this evening. Still dont know about the user pic. Got a busy day so be patient. Note: We have a problem...UFC fight and football on tonight so I highly doubt I will get around to testing tonight. More then likely it will be tomorrow.
First test in progress and this is without the reg file we have been using. Stand by for results... -Lock screen and login background image successfully applied but user pic is a no go. Trying with kms to see results... I have a theory for the user pic on login screen but need to test next to see if this theory might address it. Two mins to make changes, 30 mins to install and test. This is going to be a long day. lol
The user pic on login screen is always the guest image no matter if I replace it within script or not.
I will upload new project version date with corrections to lock screen and login background images. They will now stay in place after multiple reboots.
You did great, changing user pic manually is not a problem for me, I'm still happy Thanks for all who help
To me this isnt a big issue either but for some, we know someone will complain without reading this thread or even the included updated txt files which also explains this. Not in as much detail as two posts back but does give an explanation. I am uploading new version date of project now...
First post updated to 8-21-2016. See change log for details. Also updated credits on first post to include rockyanexpert.
I get from Zippyshare and Datafilehost different hashes: Code: File : Multi_OEM_Project_08.21.2016.7z CRC32 : 19CE6463 MD5 : 81DF22683A159606472ECD292CA1E3FC SHA1 : E3C7864FC13717464B587876FB9620437B62A0FD Haven't tried other filehosts but I guess it's the same...
I tried the above method for cmd prompt for login user pic but didnt work because it needs encoding. Going to try running powershell which can encode the reg entry correctly. Lets see the results...that failed also in home edition because of no group policy. FYI, ALL the old methods do NOT work with the new Win10 Anniversary builds in regards to the login user picture.