...
OS Deployment is used to create scripts to deploy images through DOS, Windows, or Linux pe environments. It isn't heavily as many of its uses are more easily accomplished using provisioning Provisioning.
Using Sysprep and Setup Manager (for Windows XP, from the Landesk Users guide)
Before creating OS deployment scripts, you should run Microsoft's Setup Manager
(setupmgr.exe) and create If you don't already have a sysprep.inf answer file for the images you're deploying. You can
then use this file as the basis for any OS deployment scripts you create by selecting the Use
existing sysprep.inf file as a template option on the Specify Sysprep file information
page of the wizard. Any OS deployment script settings you make in the wizard override the
equivalent options in the template sysprep.inf file.
Windows XP, you can run Setup Manager (setupmgr.exe) to create one. A wizard will walk you through the process of creating one. Using Sysprep on your Windows 2000/ XP images allows OS deployment to query the core
database for each device you're deploying and to migrate certain user settings, such as:
• Windows computer name
• GUID (the unique identifier used to identify devices in the core database)
You can also set these options globally for images you deploy:
• Time zone
• Volume license key
• Registered name and organization
• Workgroup/Domain/LDAP Organizational Unit (OU)
OS deployment uses information from the core database and from the image deployment
script to create a custom sysprep.inf for each device you're imaging. OS deployment then
injects that sysprep.inf into each device's image.
External Links
- Landesk Landing page - http://community.landesk.com/support/docs/DOC-23516