locked
Customsettings.ini values not working when booting into PXE RRS feed

  • Question

  • I have several values in the customsettings.ini that are not been passed down when I'm trying to build a machine using PXE. When the machine boots into PXE and I select the Task sequence I get prompt for questions that should have been handled by the customsettings.ini file. Has anyone seen this problem. Here are the values I've been asked even after they were set by customsettings.ini.

     I get prompt to enter password, ProductKey, configured BitLocker and domain information. Below is my file

    Settings]
    Priority=Default
    Properties=MDT2013CustomProperties

    [Default]
    _SMSTSOrgName=Running %TaskSequenceID% on %Model%
    DriverSelectionProfile=Nothing
    DriverInjectionMode=ALL
    DriverGroup001=Windows10\%Model%
    OSInstall=Y
    SLShare=\\AG-MDT01\MDTLogs
    SkipTimeZone=YES
    TimeZone=035
    TimeZoneName=Eastern Standard Time
    DoNotCreateExtraPartition=YES
    DoCapture=Yes
    DeploymentType=NEWCOMPUTER
    SkipCapture=No
    SkipAdminPassword=YES
    AdminPassword=*******
    SkipProductKey=YES
    SkipComputerBackup=YES
    SkipBitLocker=YES
    SkipComputerName=NO
    SkipUserData=YES
    SkipLocaleSelection=YES
    SkipTaskSequence=NO
    SkipApplications=YES
    SkipSummary=YES
    SkipBDDWelcome=YES

    FinishAction=REBOOT

    ;Join Domain
    SkipDomainMembership=YES
    DomainAdmin=administrator
    DomainAdminDomain=Domain
    DomainAdminPassword=********
    JoinDomain=domain.local
    EventService=http://AG-MDT01:9800

    all this works if I create a Media boot using the same values.

    Thursday, April 7, 2016 7:01 PM

Answers

  • It may be a typo when you entered you customsettings.ini file but the opening [ is missing from [Settings].  This would not allow the file to be parsed properly thus the settings in it would not be carried out.  This error would not carry over to the Media customsettings.ini as they are generated separately.
    • Marked as answer by Ty Glander Wednesday, April 27, 2016 4:20 AM
    Tuesday, April 12, 2016 1:05 PM

All replies

  • Take a look at your logs. There is information on logs in the forum FAQ.

    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    Thursday, April 7, 2016 7:02 PM
  • Can anyone point me on the right direction on why the customsettings.ini are not working while booting under WinPE and PXE.

    thanks in advanced.

    Friday, April 8, 2016 11:46 AM
  • As Ty mentioned check the logs. The logs will show where it is getting its customsettings.ini and what is being processed. Maybe you haven't updated the boot image on your PXE server and that image is pointing somewhere else? The logs usually paint a pretty good picture on what's going on.

    If it were me I'd dump the driver stuff and put that in the task sequence itself. See - http://deploymentresearch.com/Research/Post/325/MDT-2013-Lite-Touch-Driver-Management

    I see you have it set to capture so if you're building a reference image, you can verify some of your steps using this guide - http://deploymentresearch.com/Research/Post/496/Building-a-Windows-10-Reference-Image-using-MDT-2013-Update-1


    If this post is helpful please vote it as Helpful or click Mark for answer.

    Friday, April 8, 2016 1:31 PM
  • It may be a typo when you entered you customsettings.ini file but the opening [ is missing from [Settings].  This would not allow the file to be parsed properly thus the settings in it would not be carried out.  This error would not carry over to the Media customsettings.ini as they are generated separately.
    • Marked as answer by Ty Glander Wednesday, April 27, 2016 4:20 AM
    Tuesday, April 12, 2016 1:05 PM