Management and Security powered by Landesk

Configuring a provisioning template

A template is a series of actions or building blocks to be applied to the device in a particular order. Prior to configuring a provisioning template, you must first create the template framework. Once a template is in place, you can leverage either predefined templates or construct your own using configuration settings.

If the settings are in place, you can then configure the template itself with actions. Depending on the configuration settings selected for a template, this may pre-populate this dialog with actions associated with that configuration.

For example, you want to create a Mac deploy template, so you selected the Default Mac Configuration from the template types. When you double-click the newly-created template, it will display the configuration alongside a list of predefined actions for each stage of the provisioning process. All you then need to do is provide values for each action, such as specifying a partition to erase, identifying the path and filename of a desired image, and what software to install upon OS installation completion.

We recommend leveraging the default templates currently available before you start adding your own actions. When configuring your own template, we recommend including all actions associated with a process, even if it means having multiple tasks associated with all five stages of the provisioning process. If you split actions between multiple templates, this may contribute to action conflicts that could render damage to an OS installation.

Follow these steps to configure a template.

 
To configure a provisioning template
  1. In the OS provisioning tree, double-click a provisioning template.
  2. In the left navigation pane, click Action list.
  3. In the middle pane, select the section in which you want the action to occur.
    • System migration: Features and components that need to be saved before modifying the system or when migrating a device to other hardware or a virtual machine. For example, this section can include actions to capture profile information when migrating to Windows 10, delete folders or files when reassigning a device from an old to a new user, and mount a drive when accessing migration or image files on a corporate server.
    • Pre-OS installation: Actions that are performed when the device boots into a pre-installation environment. For example, you can create or format partitions on Windows devices as well as create Fusion Drives on Mac devices.
    • OS Install: Actions that are performed in the pre-installation environment (Windows PE) when the OS is installed.
    • Post-OS Installation: Actions that are performed in the target operating system after it has been installed, such as running a patch management task.
    • System configuration: Additional application installation/execution and system configuration in the installed OS. For example, add driver installation tasks to this section.
  4. Click Add.
  5. In the Name field, type a specific name for the action.
  6. In the Description field, type a detailed description of the action.
  7. In the Type list, select an action type.
  8. Under Action variables, click Add to add a variable that applies to this action only. Specify the values in the text boxes, select the variable type, and click OK.
  9. Under Selected action properties, complete the data required for the action type. This data varies depending on the action type you selected.
  10. When the action is defined, click Apply to save it and continue editing the template. When you have finished defining the template, click OK.

 


Was this article useful?    

The topic was:

Inaccurate

Incomplete

Not what I expected

Other