Hi. I’m setting the status back to Noted – this was mixed up with the item “Add support for TFTP Window Size” – that has been Started and is available in the 1603 tech preview build.
BobMN on behalf of SangeeV for SCCM OS Deployment
Use AutoIt to create a simple prompt .. and check for password XYZ... Return exit code 0 only on success.. then you just need to put this EXE into your TS.. put everything after it into a folder.. with a conditional "if last step was exit 0' (I don't remember the exact syntax). Its not perfect.. but it should work.. I do something similar with the pre-execution hook on pxe boot.
gMSA is actually the perfect solution.. Install a gMSA on the main sccm server.. use group policy to include that account into the local administrator group of every machine. ... And restrict the gMSA to 1 way authentication.. so it can only be used from the main server.. That "should" actually work right now. You might have to set the account in sccm using powershell rather than the gui... I will be trying this soon.
Thanks for the feedback – we have this recorded in our database to expose these options as a task sequence step or property or something different. Nothing is scheduled/planned yet.
145 votesNoted · 5 comments · Ideas » Setup and Server Infrastructure · Flag idea as inappropriate… · Admin →
Here is how I implemented drivers injection... (the only drivers in the SCCM console.. are those required for WinPE)
- Manually Install Drivers on each and every make/model combo.. then copy the drivers off each of those machines up into a network share...
- In TS... I Collect the Make/Model.. and standardize them.. removing spaces.. (replacing every Dell or Dell, Inc, etc.. with DELL)
- In TS.. I map that network share.. and run a "Dism /image:%OSDisk%\ /Add-Driver /driver:Z:\Drivers\10\%SMake%\%SModel% /recurse /ForceUnsigned" command to install the drivers apropriate to that particular machine.