Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

Starmantle

My feedback

  1. 618 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    16 comments  ·  Ideas » Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    Noted  ·  sangeev responded

    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.

    Thanks,
    BobMN on behalf of SangeeV for SCCM OS Deployment

    Starmantle supported this idea  · 
  2. 19 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Ideas » Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    Starmantle commented  · 

    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.

  3. 216 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  Ideas » Setup and Server Infrastructure  ·  Flag idea as inappropriate…  ·  Admin →
    Starmantle supported this idea  · 
    Starmantle commented  · 

    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.

  4. 162 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Ideas » Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    Starmantle supported this idea  · 
  5. 145 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  5 comments  ·  Ideas » Setup and Server Infrastructure  ·  Flag idea as inappropriate…  ·  Admin →
    Starmantle supported this idea  · 
  6. 802 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  28 comments  ·  Ideas » Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    Starmantle commented  · 

    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.

Feedback and Knowledge Base