Well Im not trying to install this project with a server.. Im using Server 2012 to deploy (Install over network) Windows (7, 10) to other computers. Its using PXE. Basically Im using network boot on clients I wish to install Windows on, the server responds and sends proper packages.
That's good to hear, and thanks for your great contribution! You really put your soul into this, and it's greatly appreciated :flowers2:
You will need to add the project to your windows image before deployment. I recommend running the query tool first on a station just to make sure there will be no problems. Its up to you though...
As The_Guardian said you will need to put it in the windows image. I'm sure you know how to do it but if needed, you would mount whatever WIM file/proper index and put the scripts folder under Windows/Setup. It is the same place the $OEM$ folder puts during the install.
Thanks to Mr.X for testing the retail key activation. I need to add code if retail.txt present then uninstall key first then proceed. I will do this later today. I have physical therapy plus got some running around to do today but I will get to it. Update: I added corrections to avoid the above issue described. Need to test and let Mr.X test before updating first post. I want to make sure this is addressed correctly before going public.
Sent to Mr.X for testing since I dont have time to test myself until this evening. If all goes good I will update first post either tonight or tomorrow. Thanks Mr.X for helping me test. Off to physical therapy....
Sorry for taking so long to get back on the update. I fixed the retail key if retail.txt file is present. Now any keys are cleared before applying. This should resolve that issue. I also found out if using kms a logoff is required in order to save login background oem image correctly. So remember if you for some odd reason decide to use kms then logoff and oem login background image will stay put after multiple restarts and shutdowns. System must be activated first before customization's hold. I have a few beta testing this now and if all goes as planned maybe tomorrow I can update first post. I am trying to make sure no bugs arise from additional code. Better to double check before releasing.
I am only waiting for feedback from testers. If good then I will update first post. I have done my part. lol Update: So far seems everything is working like it should. Neither I nor anyone could reproduce BALTAGY Lavono theme issue as not being saved or applied. I regret none of us can reproduce your issue BALTAGY. I will upload for all to enjoy this evening. Stay tuned...
Those that use kms for activation purposes the login screen will be kicked out on shutdown (not restart). Once boot sector runs then see's kms it will revert back to default windows login image. This isnt the case for a legit machine who activation is legit (not kms related). I am done looking into the kms and branding issue. If you want to customize then have a legit machine and the project will work as described. Or use windows 7. lol I am going to update first post. Stay tuned...
I'm much more interested in auto-activation than anything else btw so I'm fine with your project so far. Damn M$ destroying people's creativity lol
First post updated 9-19-2016. See change log for details. Fixed pic on first post so now it shows correctly. Guess the other image host is a banned host here at mdl.
Regarding my issue above with using this project on a Windows (Deployment) Server based on Server 2012 R2.. It works just fine in vmware with applying OEM-branding but my main pc wont apply it.. Of course its in Windows\Setup. There's no project.log either.
If no log file within the log directory either then it means oobe is disabled and you will need to add pid.txt file (with install key) to enable oobe mode again. Its mentioned in the txt files of the project.
How can OOBE be disabled when its ran from same server and installing same OS and it works in vmware? This is weird to me
Its because windows OS's now searches for oem and if oem (not all but most) will disable oobe mode. Your not installing on server but workstations thus each workstation will be queried and if it meets all requirements for oem then oobe is disabled. Either way, the trick is to include pid txt file with install key (installs only, not activated). You can specify the version as well with a ei.cfg. Just make sure install key and version matches. You can find install keys all day long on google.
@The_Guardian WinTel which removes telemetry is not a code, it's a poem! Music to my ears. Dude you totally rock. Get yourself a beer. Hypothetical question: Do you think it's achievable to block ANY and ALL connections between a Win7 PC and Microsoft?
You really need to check the win10 telemetry thread because some apps send out data. I do not address the apps because some user's use them. I only address system telemetry. Telemetry has been in effect since xp days. This is nothing new, just more of it in newer OS's. The WinTel.cmd works on all project supported OS's.