Management and Security
Using installation scripts in provisioning templates
Use the Install scripts tool (Tools > Provisioning > OS Provisioning) to create a template out of one or more installation scripts, which can then be used for scripted installation actions in templates. Provisioning supports batch file scripts, shell scripts, and many others.
The Deploy image, Scripted install, and Inject script actions use scripts like sysprep.inf or unattend.txt. You can use the Install scripts tool to insert variables into your scripts; for example, a device name can be inserted into a sysprep.inf file.
Install scripts supports many key value pairs, such as:
|%ldHostname%||The host name|
|%ldDeviceID%||GUID of the device|
If the win.inf file already has a key value pair that exists as a user-defined variable, Install scripts will replace it with the new user-defined variable.
To pass variables through an installation script as a variable (not to be replaced by the provisioning process), encapsulate the variable in double percent signs (for example,
Notes on using scripts
- In Windows, a valid, active, formatted partition must exist before the Scripted install action can occur.
- The network installation source must have drivers for the target device injected correctly or put into the OEM's PnP driver path (for additional information, refer to the Microsoft installation documentation).
- Currently, only a command-line installation using winnt32 works.
- The file cmdlines.txt is used to append commands to the final OS boot.
- Currently, PXE/RIS is not supported.
- If the installation fails, you can troubleshoot the error by looking in the \ManagementSuite\ldlogon\provisioning\config folder to see the installation script with the variables replaced. Access this folder any time you need to troubleshoot after modifying a script or using a script in the Inject script or Deploy image actions.
- The temporary directory used for provisioning is %systemdrive%/ldprovisioning.
Was this article useful?