Modify LiteTouch CustomSettings.ini/vbs/wsf to skip repartitioning task

I have been given a bootable USB stick that contains a LiteTouch deployment that we are using for our Win7 migrations. I have also been investigating USMT hardlink backups/restores and my problem is that the LiteTouch deployment has a task in there that
repartitions and wipes the drive.
While I am unable to modify the tasks via LiteTouch / MDT, I am able to modify the contents of the USB stick, so I thought perhaps there is something I can put in the CustomSettings.ini to prevent this step from happening. I added:
DeploymentType=REFRESH
OSDStateStorePath=c:\backup
OSDMigrateAdditionalRestoreOptions=/nocompress /hardlink
thinking that the DeploymentType being refresh would instruct the deployment to not do a repartition/wipe, but that didn't work.
The USB has an autorun.inf which calls upon BDD_autorun.wsf, which in turn executes the LiteTouch.vbs script. I tried modifying that to pass in the DeploymentType flag:
If oShell.Popup( WelcomeMessage1 & vbNewLine & WelcomeMessage2, 15, WelcomeHeader1, 1 or 64) = 1 then
oShell.Run "cscript.exe //nologo """ & WScript.ScriptFullName & "\..\LiteTouch.vbs /DeploymentType:REFRESH""",,FALSE
End if
but that too failed.
Does anyone know how or what can modify to prevent the repartitioning step to occur by just modifying the CustomSettings.ini, or any vb/wsf file?
thanks,

MDT Litetouch.wsf launched ( as see in bdd.log ) the Stand Alone Task Sequencer
About to run command: "C:\MININT\Tools\X86\TsmBootstrap.exe" /env:SAStart LiteTouch 12/11/2013 2:33:57 PM 0 (0x0000)
Property LTIDirty is now = TRUE LiteTouch 12/11/2013 2:33:57 PM 0 (0x0000)
Command completed, return code = -2147467259 LiteTouch 12/11/2013 2:34:01 PM 0 (0x0000)
Litetouch deployment failed, Return Code = -2147467259 0x80004005 LiteTouch 12/11/2013 2:34:01 PM 0 (0x0000)
However, as you can see, the Task Seqence Manager returned an error.
Going into the smsts.log file, we can see that one of the steps returned an error:
!--------------------------------------------------------------------------------------------! TSManager 12/11/2013 2:34:00 PM 5640 (0x1608)
Expand a string: WinPEandFullOS TSManager 12/11/2013 2:34:00 PM 5640 (0x1608)
Executing command line: cmd /c copy "%SCRIPTROOT%\custom\CustomSettings2.bak" "x:\windows\system32\CustomSettings2.ini" TSManager 12/11/2013 2:34:00 PM 5640 (0x1608)
Process completed with exit code 1 TSManager 12/11/2013 2:34:00 PM 5640 (0x1608)
!--------------------------------------------------------------------------------------------! TSManager 12/11/2013 2:34:00 PM 5640 (0x1608)
Failed to run the action: Copy Custom Settings.
Incorrect function. (Error: 00000001; Source: Windows) TSManager 12/11/2013 2:34:00 PM 5640 (0x1608)
The step was *NOT* marked as "continue on error" in the MDT Task Sequence, so... the task sequence died.
Either: remove the step, Mark it as "continue on error", or some other error in your command needs to be fixed.
Keith Garner - keithga.wordpress.com

Similar Messages

  • MDT CustomSettings.ini

    I tried putting domain join information in the Default section of CustomSettings.ini but that breaks my capture task sequence. However, if I put it in the TaskSequence like [006] it doesn't fill in the OU. Also, the userid/password doesn't match what I used.
    Is that information ignored and only pulled from Bootstrap.ini? I also pass in ADGroup in the task sequence but if the OU portion isn't working i'm assuming that won't work either. 
    Has anyone else seen this problem? It is fine if the domain join portion is copied to each TS so that capture's still work but I would like it to pass the OU and ADGroup automatically. 

    As a side note I found it much easier in the end to break out the capture to its own deployment share.  It cut a lot of unnecessary logic and scripting out of the deployment share settings and allowed me to update the capture with whatever without interfering
    with the deployment side.
    It is really not necessary to use a 2nd deploymentshare only for capturing. That's just bad management by the person who is responisble for the share. It's perfectly possible to do this within one share, only if you put some effort in to it!
    If this post is helpful please click "Mark for answer", thanks! Kind regards
    This response does not help. I myself am leaning towards the second share because the way we need to use DomainJoin as a Location Database setting breaks the capture task completely. It does not matter where you put DoCapture, Join workgroup, or  try to
    null the joindomain variable. Even greyed out, if that entry is there MDT does not care. 
    See my thread at Capture Task Broken
    Nathaniel Scriven

  • Applications not being processed in CustomSettings.ini or missing from ZTIApplications

    Using MDT 2012 Update 1 and started having a weird issue where MandatoryApplications properties are being skipped over during the deployment process.
    CustomSettings.ini is configured to process [Default] first, followed by model specific subsections for fixing up minor things that are specific to that model. There are MandatoryApplications settings under each subsection, and it ends up looking similar
    to this...
    [Settings]
    Priority=Default, Model
    [Default]
    MandatoryApplications001={f3389f14-6071-414b-b989-08e35cf82f27}
    [HP EliteBook 840 G1]
    MandatoryApplications002={d13e2dc4-3b27-4173-b143-30b5f57d7e53}
    Applications defined under [Default] install just fine, but nothing under the model subsections installs. No errors, also.
    BDD.log shows...
    ------ Processing the [DEFAULT] section ------ ZTIGather 4/17/2014 9:48:41 AM 0 (0x0000)
    Property MANDATORYAPPLICATIONS001 is now = {f3389f14-6071-414b-b989-08e35cf82f27} ZTIGather 4/17/2014 9:48:42 AM 0 (0x0000)
    Added value from [DEFAULT]: MANDATORYAPPLICATIONS = {f3389f14-6071-414b-b989-08e35cf82f27} ZTIGather 4/17/2014 9:48:42 AM 0 (0x0000)
    ------ Processing the [HP EliteBook 840 G1] section ------ ZTIGather 4/17/2014 9:48:42 AM 0 (0x0000)
    ------ Done processing \\Server\ProductionShare$\Control\CustomSettings.ini ------ ZTIGather 4/17/2014 9:48:43 AM 0 (0x0000)
    ZTIApplications.log shows...
    Microsoft Deployment Toolkit version: 6.1.2373.0 ZTIApplications 4/17/2014 10:06:35 AM 0 (0x0000)
    The task sequencer log is located at C:\Users\ADMINI~1\AppData\Local\Temp\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log. ZTIApplications 4/17/2014 10:06:35 AM 0 (0x0000)
    Write all logging text to \\Server\productionshare$\logs ZTIApplications 4/17/2014 10:06:35 AM 0 (0x0000)
    Validating connection to \\Server\productionshare$\logs ZTIApplications 4/17/2014 10:06:35 AM 0 (0x0000)
    Already connected to server Server as that is where this script is running from. ZTIApplications 4/17/2014 10:06:35 AM 0 (0x0000)
    Language/Locale Identified (in order of precedence): 1033,0409,0x0409,9,0009,0x0009 ZTIApplications 4/17/2014 10:06:35 AM 0 (0x0000)
    Processing Application Type: MandatoryApplications ZTIApplications 4/17/2014 10:06:35 AM 0 (0x0000)
    Ready to install applications: ZTIApplications 4/17/2014 10:06:36 AM 0 (0x0000)
    ################ ZTIApplications 4/17/2014 10:06:36 AM 0 (0x0000)
    Entry: {f3389f14-6071-414b-b989-08e35cf82f27} ZTIApplications 4/17/2014 10:06:36 AM 0 (0x0000)
    Name: SysConfigs ZTIApplications 4/17/2014 10:06:36 AM 0 (0x0000)
    ################ ZTIApplications 4/17/2014 10:06:36 AM 0 (0x0000)
    Using a local or mapped drive, no connection is required. ZTIApplications 4/17/2014 10:06:36 AM 0 (0x0000)
    Change directory: Z:\Applications\SysConfigs ZTIApplications 4/17/2014 10:06:36 AM 0 (0x0000)
    Run Command: \\Server\ProductionShare$\Tools\X64\bddrun.exe sysconfigs.bat ZTIApplications 4/17/2014 10:06:36 AM 0 (0x0000)
    ZTI installing application ZTIApplications 4/17/2014 10:06:36 AM 0 (0x0000)
    Event 41031 sent: ZTI installing application ZTIApplications 4/17/2014 10:06:36 AM 0 (0x0000)
    About to run command: \\Server\ProductionShare$\Tools\X64\bddrun.exe sysconfigs.bat ZTIApplications 4/17/2014 10:06:36 AM 0 (0x0000)
    Command has been started (process ID 3624) ZTIApplications 4/17/2014 10:06:36 AM 0 (0x0000)
    Return code from command = 0 ZTIApplications 4/17/2014 10:06:36 AM 0 (0x0000)
    Application SysConfigs installed successfully ZTIApplications 4/17/2014 10:06:36 AM 0 (0x0000)
    Event 41033 sent: Application SysConfigs installed successfully ZTIApplications 4/17/2014 10:06:36 AM 0 (0x0000)
    Property InstalledApplications001 is now = {f3389f14-6071-414b-b989-08e35cf82f27} ZTIApplications 4/17/2014 10:06:36 AM 0 (0x0000)
    Processing Application Type: Applications ZTIApplications 4/17/2014 10:06:37 AM 0 (0x0000)
    Application List is empty, exiting ZTIApplications.wsf ZTIApplications 4/17/2014 10:06:37 AM 0 (0x0000)
    ZTIApplications processing completed successfully. ZTIApplications 4/17/2014 10:06:37 AM 0 (0x0000)
    Event 41001 sent: ZTIApplications processing completed successfully. ZTIApplications 4/17/2014 10:06:37 AM 0 (0x0000)
    So it ends up looking like the Applications List is not being properly populated, or something is just not processing CustomSettings.ini correctly. I've double-checked that the applications are hidden and enabled on the share, and have deleted/recreated
    the applications on the share.
    Anyone have any ideas?

    For each section in your CS.ini, start your applications list with 001, like this :
    [Settings]
    Priority=Default, Model
    [Default]
    MandatoryApplications001={f3389f14-6071-414b-b989-08e35cf82f27}
    [HP EliteBook 840 G1]
    MandatoryApplications001={d13e2dc4-3b27-4173-b143-30b5f57d7e53}

  • MDT 2013, OSDComputerName in customsettings.ini issue.

    Hi all just wanted to post this since I was running into this issue at my workplace.  Upgraded to MDT 2013 recently, thought some more bugs would be worked out by now.  One in particular I found was with my customsettings.ini.  Now since I
    upgraded you can obviously tell I was utilizing MDT in 2010 and 2012 versions before this.  SO I simply updated my deployment share, I did not create a new one.  Our current customsettings.ini was layed out as so below:
    [Settings]
    Priority=TaskSequenceID, Default
    [Default]
    _SMSTSORGNAME=%TaskSequenceID% on %OSDComputername%
    SkipAdminPassword=YES
    SkipApplications=NO
    SkipAppsOnUpgrade=YES
    SkipProductKey=YES
    SkipBDDWelcome=YES
    SkipBitLocker=YES
    SkipCapture=NO
    SkipComputerBackup=YES
    SkipDeploymentType=YES
    SkipLocaleSelection=YES
    SkipUserData=YES
    SkipWizard=NO
    DeploymentType=NEWCOMPUTER
    DoNotCreateExtraPartition=YES
    KeyboardLocale=en-US
    OSInstall=YES
    UILanguage=en-US
    UserID=(redacted)
    UserLocale=en-US
    UserDomain=(redacted)
    UserPassword=(redacted)
    TimeZone=035
    TimeZoneName=Eastern Standard Time
    EventService=(redacted)
    [WW-STAFF-WINXP]
    _SMSTSORGNAME=%TaskSequenceName% on %OSDComputername%
    SkipComputerName=YES
    OSDComputerName=(redacted)
    SkipDomainMembership=YES
    SkipTimeZone=NO
    SkipFinalSummary=NO
    FinishAction=REBOOT
    [TEST-WW-WIN7X86]
    _SMSTSORGNAME=WW Win7 Test Image on %OSDComputername%
    SkipComputerName=YES
    OSDComputerName=(redacted)
    SkipDomainMembership=YES
    SkipTimeZone=NO
    SkipFinalSummary=NO
    FinishAction=REBOOT
    [WW-STAFF-WINXP-2]
    _SMSTSORGNAME=%TaskSequenceName% on %OSDComputername%
    SkipComputerName=YES
    OSDComputerName=(redacted)
    SkipDomainMembership=YES
    SkipTimeZone=NO
    SkipFinalSummary=NO
    FinishAction=REBOOT
    [WW-CLASIMG-WINXP]
    _SMSTSORGNAME=%TaskSequenceName% on %OSDComputername%
    SkipComputerName=YES
    OSDComputerName=(redacted)
    SkipDomainMembership=NO
    SkipTimeZone=NO
    SkipFinalSummary=NO
    FinishAction=REBOOT
    [WW-STAFF-WIN7X86]
    _SMSTSORGNAME=%TaskSequenceName% on %OSDComputername%
    SkipComputerName=YES
    OSDComputerName=(redacted)
    SkipDomainMembership=YES
    SkipTimeZone=NO
    SkipFinalSummary=NO
    FinishAction=REBOOT
    [WW-STAFF-WIN7X64]
    _SMSTSORGNAME=%TaskSequenceName% on %OSDComputername%
    SkipComputerName=YES
    OSDComputerName=(redacted)
    SkipDomainMembership=YES
    SkipTimeZone=NO
    SkipFinalSummary=NO
    FinishAction=REBOOT
    Now this seems pretty straight forward.  Based on task sequence you choose you get alternate settings.  Well since the move to mdt 2013 the alternate setting, in particular the skip computer name, skip domain membership and osdcomputer name fields
    were not working.  It would prompt for computer name and domain membership every time.  So after a bit of troubleshooting, and NO HELP whatsoever from the researching online, I discovered it no longer will detect unless those particular exceptions
    are under the default profile instead of separate task sequence id's.  Hopefully this will be an easy update fix in the future, but who knows.  Luckily I can still run my setups without issue with it in the default portion.  Fixed customsettings.ini
    below:
    [Settings]
    Priority=TaskSequenceID, Default
    [Default]
    _SMSTSORGNAME=%TaskSequenceID% on %OSDComputername%
    SkipAdminPassword=YES
    SkipApplications=NO
    SkipComputerName=YES
    OSDComputerName=(redacted)
    SkipDomainMembership=YES
    SkipAppsOnUpgrade=YES
    SkipProductKey=YES
    SkipBDDWelcome=YES
    SkipBitLocker=YES
    SkipCapture=NO
    SkipComputerBackup=YES
    SkipDeploymentType=YES
    SkipLocaleSelection=YES
    SkipUserData=YES
    SkipWizard=NO
    DeploymentType=NEWCOMPUTER
    DoNotCreateExtraPartition=YES
    KeyboardLocale=en-US
    OSInstall=YES
    UILanguage=en-US
    UserID=(redacted)
    UserLocale=en-US
    UserDomain=(redacted)
    UserPassword=(redacted)
    TimeZone=035
    TimeZoneName=Eastern Standard Time
    EventService=(redacted)
    [WW-STAFF-WINXP]
    _SMSTSORGNAME=%TaskSequenceName% on %OSDComputername%
    SkipTimeZone=NO
    SkipFinalSummary=NO
    FinishAction=REBOOT
    [TEST-WW-WIN7X86]
    _SMSTSORGNAME=WW Win7 Test Image on %OSDComputername%
    SkipTimeZone=NO
    SkipFinalSummary=NO
    FinishAction=REBOOT
    [WW-STAFF-WINXP-2]
    _SMSTSORGNAME=%TaskSequenceName% on %OSDComputername%
    SkipTimeZone=NO
    SkipFinalSummary=NO
    FinishAction=REBOOT
    [WW-CLASIMG-WINXP]
    _SMSTSORGNAME=%TaskSequenceName% on %OSDComputername%
    SkipTimeZone=NO
    SkipFinalSummary=NO
    FinishAction=REBOOT
    [WW-STAFF-WIN7X86]
    _SMSTSORGNAME=%TaskSequenceName% on %OSDComputername%
    SkipTimeZone=NO
    SkipFinalSummary=NO
    FinishAction=REBOOT
    [WW-STAFF-WIN7X64]
    _SMSTSORGNAME=%TaskSequenceName% on %OSDComputername%
    SkipTimeZone=NO
    SkipFinalSummary=NO
    FinishAction=REBOOT

    Check your task sequence, go the the "Gather" steps, there are three of them in the default standard client task sequence, and verify that instead of "Gather locally", "Use this file to process the rules" is checked, and provide the following text: CustomSettings.ini,
    do this on all the three steps, try again and let us know!
    Also not sure what happens, but I would definitely paste the TaskSequenceID specified rules above the Default section. I know that priority provides in which orders the rules needed to be processed, but still I would post them above Default.
    Cheers!
    If this post is helpful please click "Mark for answer", thanks! Kind regards

  • Getting MDT wizard prompts despite customsettings.ini

    I have customsettings.ini set to have most fields filled out except computer name and admin password.
    When I launch a deployment the fields are all pre-populated with data (time zone, language etc.), however, I still have to click next through each option.
    What's missing in this customsettings.ini file?
    [Default]
    SkipBDDWelcome=YES
    SkipUserData=YES
    SkipComputerBackup=YES
    SkipProductKey=YES
    SkipPackageDisplay=YES
    SkipLocaleSelection=YES
    SkipTimeZone=YES
    SkipRoles=YES
    SkipApplications=YES
    SkipCapture=YES
    SkipBitLocker=YES
    SkipSummary=YES
    ApplyGPOPack=YES
    OSInstall=Y
    SkipLocaleSelection=YES
    KeyboardLocale=En-US
    UserLocale=En-US
    UILanguage=En-US
    SkipTimeZone=YES
    TimeZoneName=Pacific Standard Time
    SkipAdminPassword=NO
    SkipComputerName=NO
    OSDComputerName=%SERIALNUMBER%
    BitsPerPel=32
    VRefresh=60
    XResolution=1
    YResolution=1

    It might be useful to take a look at the ToolKit Reference.docx and verify you have the properties set for each screen you want skipped. That being said a couple of things that jump out to me:
    SkipUserData=YES
    UserDataLocation=NONE
    SkipComputerBackup=YES
    ComputerBackupLocation=NONE
    What pages are displaying that you wouldn't expect to?  SkipLocaleSelection does have all the proper settings.
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • CustomSettings.ini Issue

    All,
    Here is a customsettings.ini file I have been working on.  We would like the two laptops to be encrypted using bitlocker and then to store the code in AD, however I keep getting the bitlocker wizard window appear for all 4 machines when going through
    the initial wizard and it is set to the default of not encrypting.  Can anyone advise as to where I am going wrong with this.
    [Settings]
    Priority=TaskSequenceID, Default
    Properties=MyCustomProperty
    [001]
    DriverGroup001=Lenovo_M73
    DriverSelectionProfile=nothing
    BDEInstallSuppress=YES
    SkipBitLocker=YES
    [002]
    MandatoryApplications001={77d768d5-2fcf-46f7-9c45-bc2b5527753f}
    DriverGroup001=Dell_E6440
    DriverSelectionProfile=nothing
    BDEInstallSuppress=NO
    BDEDriveLetter=S:
    BDEDriveSize=300
    BDEInstall=TPM
    BDERecoveryKey=AD
    [003]
    DriverGroup001=Optiplex_7010
    DriverSelectionProfile=nothing
    BDEInstallSuppress=YES
    SkipBitLocker=YES
    [004]
    DriverGroup001=Lenovo_T440
    DriverSelectionProfile=nothing
    BDEInstallSuppress=NO
    BDEDriveLetter=S:
    BDEDriveSize=300
    BDEInstall=TPM
    BDERecoveryKey=AD
    [Default]
    OSInstall=Y
    SkipCapture=NO
    SkipAdminPassword=YES
    SkipProductKey=YES
    SkipApplications=YES
    SkipComputerBackup=NO
    SkipLocaleSelection=YES
    UILanguage=en-US
    InputLocale=en-GB
    SystemLocale=en-GB
    UserLocale=en-GB
    KeyboardLocale=en-gb;0809:00000809
    SkipTimeZone=YES
    Timezone=085
    Timezonename=GMT Standard Time
    SkipUserData=YES
    _SMSTSORGNAME=xxxxxxxx
    Administrators001=xxx.xxxxx\Domain Admins
    SkipDomainMembership=NO
    MachineObjectOU=OU=BitlockerTestMachines,OU=computers.hdc,DC=xxxx,DC=xxxxx
    JoinDomain=xxxxx.local
    DomainAdmin=xxxxxxx
    DomainAdminPassword=xxxxxx
    DomainAdminDomain=xxx.xxxxx
    MandatoryApplications001={fdd87302-919c-466a-ab6b-75f1bbd63a9d}
    MandatoryApplications002={84a4267e-3fd5-4596-a2b2-f9d7540e1fce}
    MandatoryApplications003={d807ab54-ab4d-4125-8d43-c6256398e6c4}
    WSUSServer=http://WSUS3:8530
     Many Thanks

    I don't typically recommend putting specific settings keyed off of TaskSequenceID for the reasons you are coming across now. Instead I recommend working around the issue.
    See Johan's Guide:
    http://www.deployvista.com/tabid/36/EntryID/139/language/en-US/Default.aspx
    For your specific question, there are two options:
    1. Add a step into the task sequence to import settings from a specific ini file per Task Sequence:
        cscript.exe %scriptRoot%\ztigather.wsf /LocalOnly /inifile:%scriptRoot%\..\control\%TaskSequenceID%\MyCS.ini
    2. Additionally, when I want to *force* custom settings for form factor type I've used the following:
    [Settings]
    Priority=UUID, Role, Default
    [Default]
    SubSection=ISVM-%ISVM%-%ISLaptop%
    [ISVM-True-False]
    ; Bitlocker is not supported on Virtual Machines
    SkipBitlocker=YES
    OSDBitLockerMode=NONE
    BdeInstallSuppress=YES
    [ISVM-False-False]
    ; Desktops are not required to have bitlocker
    OSDBitLockerMode=NONE
    BdeInstallSuppress=NO
    [ISVM-False-True]
    ; Laptops are required to have bitlocker TPM + Pin
    OSDBitLockerMode=TPM
    BdeInstallSuppress=NO
    Keith Garner - keithga.wordpress.com

  • How can I specify different settings in CustomSettings.ini based on the OS that is being deployed?

    I originally thought this could be achieved using "OSVersion" or "OSCurrentVersion" but (unless I'm mistaken) those variables are in fact tied to the OS from witch you actually launch the MDT Wizard right? i.e. say I run MDT from within
    Windows PE to deploy Windows 8. The "OSVersion" and "OSCurrentVersion" will contain values for the Windows PE instance that is currently running MDT and not the Windows 8 OS I am actually deploying right? Assuming that is the case then
    is there some variable in MDT that stores version information about the OS you are currently deploying? If so can I use that in CustomSettings.ini to specify different settings for specific OSes I deploy?

    Rens,
    First thanks for responding. Next please don't take my response the wrong way but this is a bit of a pet peeve of mine. Maybe I'm just "doing it wrong" but I have used the TaskSequenceID trick in the past and thats actually where my problem lies.
    Too many people are recommending this course of action without including the caveats. Your response implies that using TaskSequenceID is as simple as just adding "TaskSequenceID" to priority and then creating entries based on the TSIDs themselves.
    In reality getting this to work is far more challenging. One needs to only check the following threads (and several others) for the issues other people are having when they try to use TaskSequenceID in CustomSettings.ini:
    http://social.technet.microsoft.com/Forums/en-US/e17a1952-d1f7-41ef-8231-0d6fcc41882e/mdt-2012-settings-per-task-sequence?forum=mdt#f0810428-e6fd-468e-8c76-ca18b210c191
    http://social.technet.microsoft.com/Forums/en-US/320aafee-07d2-4b96-9138-a902fec7edf5/mdt-2012-custom-rules-by-tasksequenceid-not-working-now
    In fact, following the steps outlined here was the *only* way I was able to get TaskSequenceID to work for me:
    http://www.the-d-spot.org/wordpress/2012/07/20/how-to-use-different-settings-per-task-sequence-with-mdt-2012/
    Even then its causing some erratic issues in some areas like button lag in the Wizard because ZTIGather has to run twice and pre-checked Applications in the wizard still installing even if they are unchecked. Since my needs are more OS-specific (as opposed
    to Task Sequence specific) I was hoping for a better solution. I suppose I can check BDD.log but I was hoping someone here had already encounter this same issue and hit upon a solution they could share. 
    Anyone?

  • Time Zone Variables in CustomSettings.ini

    Hello,
    I am trying to automate a Windows Deploy and am having trouble getting the correct time zone set when I have select Time Zone and Computer Name set to OFF in my custom settings.ini.
    Currently, I have a section in the customsettings.ini that is something along the lines of:
    [GetOffice]
    Subsection=#LEFT("%OSDComputerName%",3)#
    as we are using the mdt database to pre-stage the computer name based upon the mac address, and the 1st 3 characters designate the office location. Then I have another section afterwards for each possible name:
    [XXX]
    TimeZone=Eastern Standard Time
    TimeZoneName=Eastern Standard Time
    As an example. However, I notice that when I have SkipComputerName=YES and SkipTimeZone=YES it defaults to the basic time zone. Is this behavior that anyone else has noticed? If so, how did you overcome it?
    Edit 1:
    Upon further investigation, I notice that the time zone is set properly but the time is not adjusted correctly. Is there perhaps a way to adjust this?

    The below link will help you include correct values
    http://www.myitforum.com/forums/TimeZone-property-in-CustomSettingsini-m184737.aspx
    Regards, Shweta Karalkar

  • MDT+SCCM 2012 Task Sequence Customsettings.ini

    Hi ,
    PLease find attached customsettings.ini,
    i am using MDT SCCM 2012 integrated Task Sequence, 
    Requirment :-
    1. Detect locations based on Gateway
    2.Once detected check if its Laptop or Desktop, if laptop Encrypt and also check if Desktop or Laptop to place them in right OU,
    please check if the cs.ini has the right settings and suggest how to name machine with automatic sequencential numbers like lon-8001 then next machine lon-8002
    can the automatic sequencctial naming be added to cs.ini, please suggest.
    Thanks
    please suggest

    Looks like you are on the right track, for advanced naming, you can check out Mikes post on the subject:
    http://blogs.technet.com/b/mniehaus/archive/2009/12/06/ris-style-naming-with-mdt-2010-use-a-web-service.aspx
    Sorry, it's not an easy fix.
    Keith Garner - Principal Consultant [owner] -
    http://DeploymentLive.com

  • Localise Windows 8.1 with customsettings.ini

    I have these settings in my customsettings.ini
    UserLocale=en-AU
    SystemLocale=en-AU
    KeyboardLocale=0c09:00000409
    UILanguage=en-AU
    GeoID=12
    and I have the gather step specifying that file and it still doesnt apply. Im still getting english(US). What am I missing please?
    David Z

    Please check if this is relevant to your environment:
    http://blogs.technet.com/b/cameronk/archive/2012/08/22/why-aren-t-my-settings-on-the-language-page-setting-correctly-a-must-read-for-language-usage-with-mdt-2012-update-1-udi.aspx

  • CustomSettings.ini and Applications001, Applications002..

    In my customsettings.ini I have configured some applications to be automatically selected (I dont want them to be mandatory) when choosing applications to install.
    applications001={GUID}
    applications002={GUID}
    This works fine, applications are preselected and I can unselect them if I want in MDT Wizard page applications section. But the problem is that when I unlesect them they are still installed during application install phase. Why?

    To change settings from a cs.ini file from *within* the Wizard, check Johan's post:
    http://social.technet.microsoft.com/Forums/en-US/97d1bcc7-5292-4619-8892-723cb540e8dd/what-to-expect-with-mdt-2013-multicast-from-wds-2008-r2?forum=mdt
    Keith Garner - keithga.wordpress.com

  • Building OSDComputer in CustomSettings.ini

    Hello all,
    I realize this is more of an MDT question.  Trying to use CustomSettings.ini to name a machine based on default gateway and serial number properties, which is working great.  However, sometimes I get a machine that isn't defined in CustomSettings.ini
    and the OSDComputerName ends up being MININT.
    Here is a much lighter sample of my CustomSettings.ini:
    [Settings]
    Priority=Init, DefaultGateway, Default
    Properties=MyCustomProperty, ComputerLocationName, ComputerSerialNumber
    [Init]
    ComputerSerialNumber=#Left("%SerialNumber%",7)#
    [DefaultGateway]
    192.168.0.1=Site1
    192.168.0.2=Site2
    192.168.0.3=Site3
    192.168.0.4=Site4
    192.168.0.5=Site5
    [Site1]
    ComputerLocationName=NA
    [Site2]
    ComputerLocationName=AMEA
    [Site3]
    ComputerLocationName=ESP
    [Site4]
    ComputerLocationName=CAN
    [Site5]
    ComputerLocationName=GER
    [Default]
    OSInstall=Y
    OSDComputerName=%ComputerLocationName%%ComputerSerialNumber%
    SkipCapture=YES
    SkipAdminPassword=NO
    SkipProductKey=YES
    What I'm hoping to achieve is a "catch-all".  If the machine is not in a default gateway captured in the CustomSettings.ini, I'd like OSDComputerName to equal COR%ComputerSerialNumber%
    Is this possible to do within CustomSettings.ini?  Much appreciated for any input.
    Thanks!

    Just create a CatchAll section, that will have  a lower priority, like this:
    (Bold is what I've changed in your CustomSettings.ini file).
    [Settings]
    Priority=Init, DefaultGateway, CatchAll, Default
    Properties=MyCustomProperty, ComputerLocationName, ComputerSerialNumber
    [Init]
    ComputerSerialNumber=#Left("%SerialNumber%",7)#
    [DefaultGateway]
    10.50.50.250=Site1
    192.168.0.2=Site2
    192.168.0.3=Site3
    192.168.0.4=Site4
    192.168.0.5=Site5
    [Site1]
    ComputerLocationName=NA
    [Site2]
    ComputerLocationName=AMEA
    [Site3]
    ComputerLocationName=ESP
    [Site4]
    ComputerLocationName=CAN
    [Site5]
    ComputerLocationName=GER
    [CatchAll]
    ComputerLocationName=COR
    [Default]
    OSInstall=Y
    OSDComputerName=%ComputerLocationName%%ComputerSerialNumber%
    SkipCapture=YES
    SkipAdminPassword=NO
    SkipProductKey=YES
    Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs:
    www.ronnipedersen.com/ and www.SCUG.dk/ | Twitter
    @ronnipedersen

  • Modify value in INI

    Hi,
    I'm new in VBscript, but fairly good in PoewrShell.
    However since the targeted machines are in WinXP, need some basic help on a vbscript.
    An excel file would have the below columns:
    pcname,user, value1, value2
    based on the pcname and user, the value in INI for value1 and value2 will be captured from the Excel file.
    Any idea how to start? any sample script that I can refer to? 
    Jabez Gan [MVP] - http://www.msblog.org Contributing Author for: (Sybex) MCTS: Windows Server 2008 Applications Infrastructure Configuration Study Guide: Exam 70-643

    Here are some Excel script to get you started.
    http://gallery.technet.microsoft.com/scriptcenter/site/search?f%5B0%5D.Type=RootCategory&f%5B0%5D.Value=Office&f%5B0%5D.Text=Office&f%5B1%5D.Type=SubCategory&f%5B1%5D.Value=Microsoft%20Excel&f%5B1%5D.Text=Microsoft%20Excel
    ¯\_(ツ)_/¯

  • Poblem with OSDComputerName in CustomSettings.ini

    Hi!!
    So my goal here is to set the timezone based on the first two chars in %OSDComputerName%, so if the computer is named CN-COMPUTER01 I want it to take the timezone in [CN] section, if this fails I want it to set it based on the defaultgateway.
    This works fine when I debug it with ZTIGather but in a OSD-deployment the %OSDComputerName% does not get resolved. So in BDD.log I see that it's looking for the section [%O], The first two characters in the variable %OSDComputerName%, not the actual value.
    [Settings]
    Priority=Init, ByCountryCode, DefaultGateway, Default
    Properties=MyCustomProperty, TheCountryCode
    [Init]
    TheCountryCode=#Left("%OSDComputerName%",2)#
    [ByCountryCode]
    SubSection=%TheCountryCode%
    [DefaultGateway]
    <IP>=CN
    <IP>=BD
    <IP>=FI
    <IP>=IN
    [BD]
    TimeZone=195
    TimeZoneName=Central Asia Standard Time
    [CN]
    TimeZone=210
    TimeZoneName=China Standard Time
    [FI]
    TimeZone=125
    TimeZoneName=FLE Standard Time
    [Default]
    OSInstall=Y
    SkipCapture=YES
    SkipAdminPassword=YES
    SkipProductKey=YES
    KeyboardLocale=041d;0000041d
    InputLocale=sv-SE
    Language=sv-SE
    UserLocale=sv-SE
    SystemLocale=sv-SE
    UILanguage=en-US
    TimeZone=110
    TimeZoneName=W. Europe Standard Time
    Any ideas? Why does it not resolve the variable?
    EDIT: btw, I use SCCM 2012 R2 for OSD.

    The task sequence stores the computer name during the deployment in the
    _SMSTSMachineName variable. The OSDComputerName variable can be used to adjust that value during the deployment. For more information see:
    http://technet.microsoft.com/en-us/library/hh273375.aspx
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • Customsettings.ini - if model is and architecture is

    Hi
    as topic. .. how can I install applications or set settings based on:
    if architecture is x64 and model is 2056wvx for instance..
    I'm pretty sure there's a way.. but can't remember the correct way of the syntax..
    Thanks in advance...
    Martin
    Kindest regards, Martin

    The below works...   check out Part 22 - Speeding up development time in
    MDT 2010 on http://www.deploymentresearch.com/Videos.aspx for instructions on how to quickly simulate a deployment (without running a full deployment) and test your rules. You can also create
    an application bundle in MDT, add both the x86 and x64 app to the bundle, set the platform filter on each app, and then just advertise the bundle to the Model
    Sample with two separate apps
    [Settings]
    Priority=Model, Default
    Properties=
    [Default]
    OSInstall=YES
    [HP EliteBook 8540w]
    Subsection=%Model%-%Architecture%
    [HP EliteBook 8540w-X86]
    MandatoryApplications001={980fc0ac-68eb-4227-bc57-49ac352e18d5}
    [HP EliteBook 8540w-X64]
    MandatoryApplications001={980fc0ac-68eb-4227-bc57-49ac352e18d4}
    Sample with app bundle
    [Settings]
    Priority=Model, Default
    Properties=
    [Default]
    OSInstall=YES
    [HP EliteBook 8540w]
    MandatoryApplications001={980fc0ac-68eb-4227-bc57-49ac352e18d5}
    / Johan
    Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deployvista.com

Maybe you are looking for

  • Vintage internal hard drives

    I have a mac pro from 2006. This is considered vintage.  the internal hard drive is missing. I have dealt with several on line shops that give me several different hard drives I can have intalled but the mac repair shop stated that I had to be sure o

  • No Flex Charts with SDK 3.5

    Hi guys.  I am experiencing a problem with not being able to use Flex's chart components with sdk 3.5 I have Flex Builder Professional. Charts work with the 3.0 and 3.2 SDK but not 3.5 Am I missing something?

  • Function (or BAPI, ...) to skip calls and release calls in maintenance plan

    Hi, gurus! We need to find a function (or BAPI, ...) in order to skip a call number in a maintenance plan. We need a function (or BAPI, ...) to release a call in a maintenance plan, too. We could use a call-transaction to IP10, but we guess there cou

  • Updating File in KM

    Hi Experts , I have a requirement wherein i need to update a file in kept in a KM repository .  This file contains a numeric value that we need to change . Can anyone please provide the code for same . I went through KM API's and found that the updat

  • Windows 7 64bit Problem

    So i finally get windows 7 booted up in bootcamp, and i find out i need 64bit. So i get rid of my 32 bit and my partition, re partition it, and load up 64 bit windows. When i go to my windows support drivers and click the setup.exe file, it says it i