Provisioning
- George Moore (Deactivated)
Overview
Provisioning consists of a large list of various actions that are grouped into templates. These templates can have a wide variety of uses, but are most often used for configuring computers after they have been imaged. A provisioning template can join a computer to a domain, install software, change registry settings, map network drives, copy or delete files, and a host of other actions. The result is an extremely powerful tool that can control a computer in both Windows and WinPE.
Provisioning Process and Technical Details
(taken from Landesk users guide)
The center of provisioning is the agent ldprovision, located in the /ldlogon/provisioning folder.
This agent consists of small applications for each action. The agent resides on the target
device. It is placed there through a PXE server or a physical boot media such as a USB drive
or a CD.
The provisioning process is completed as the agent does the following:
- It requests a template's configuration settings from a web service on the core server
- It checks the preboot type tag to ensure it is running in the correct preboot
environment - It performs the actions in the order designated in the configuration
- It reboots the device (if necessary)
- It injects a version of itself into the target OS so it can continue working when the real
OS loads after the reboot - It sends feedback to the web service on the core
The agent spans any reboots required, immediately moving to the next action after the
reboot. Most provisioning work can be done before you receive a new device. You can create a
template and create the task for the template to run on the new device. The task will not run
until the provisioning agent runs on the new device.
Example Templates
Information on the Tufts IT Knowledgebase is intended for IT Professionals at Tufts.
If you have a question about a Tufts IT service or computer/account support, please contact your IT support group.