ByPassing Customsettings.ini in MDT

You can run MDT  from UNC, no need for PXE, USB or Disc. Start litetouch.vbs from  the \\SERVER\Share$\Scripts folder. You can also bypass global rules that are in customsettings.ini

These conditions can include but are not limited to:

  • Task Sequence (specify TS, bypass prompt in wizard)
  • Apps (Include, or Exclude Bundles)
  • Hostname (Prompt & Override defaults called in Customsettings.ini)
  • State Restore (Wipe & Load vs. Refresh)

So, even if you’re running LTI without SCCM, you can call out to the LTI engine and use switches to the specify what TS you’re running and what prompts you do or do not run from the wizard.

For example you could create shortcuts that kick off a refresh with specific conditions that override the rules in your CustomSettings.ini

  • Build Image TS (Set Capture)
  • Call 32bit TS Win7 no prompts
  • Call 64bit TS Win7 no prompts
  • Call Windows 10×64 w/ prompts
  • Call Windows 10×64 w/o prompts
  • Call all prompts (Task Sequence, Domain, Name, Applications ala cart)



Create Shortcuts and point them to the Litetouch.vbs


Use switches to explicitly call a task sequence, or enable prompts you usually disable.


Override Tasksequence called in customsettings.ini

\\SERVERNAME\SHARE$\scripts\litetouch.vbs /skiptasksequence:yes /tasksequenceid:win10-64bit

Override Skip Prompt in customsettings.ini

\\SERVERNAME\SHARE$\scripts\litetouch.vbs /skiptasksequence:no /SkipApplications:no

Override Applications and/or Locale called in customsettings.ini

\\SERVERNAME\SHARE$\scripts\litetouch.vbs /SkipApplications:no /SkipLocaleSelection:no

Override Domain Settings and/or timezone called in customsettings.ini

\\SERVERNAME\SHARE$\scripts\litetouch.vbs /SkipDomainMembership:yes /skiptimezone:yes

No Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

MDT – Joining a Computer to a Domain Using PowerShell

Using PowerShell scripts within a task sequence provides more flexibility than using the CustomSettings.ini file to join a computer to a domain. The parameters of the CustomSettings.ini file are common to any deployment you perform. That’s why creating a custom PowerShell script to join your domain will be customize to …

Task Sequence Tasks Explained

This document explains the tasks that you will find in standard task sequence. Initialization > Gather local only – gathers deployment configuration settings from local sources that apply to the target computer [ZTIGather.wsf] Validation > Validate – verifies that the target computer meets the specified deployment requirement conditions. Such as …

How MDT uses XML to install Applications

Have you ever thought about what actually happens when you import applications into your MDT environment? How does the task sequence know what application to install? How does it know what command-line arguments to specify during the application install process? Technically, as a user, all that is required of us …