The WinOps Blog

As SCCM Task Sequence, in landesk you can use Provisionning Template to deploy your master on new PC:

This section contains the steps required to image a computer with Windows 7 using IMAGEW.EXE v2. It is intended to be used by experienced LANDesk administrators as a reference and does not go into detail on the process. The details will be covered later in this document. Following are the steps required to provision a computer:

1. Capture the Windows 7 image to be deployed. For help with capturing the Windows 7 image, reference this Community article. For 9.0 SP2, the image to be deployed must be captured after running SYSPREP.EXE in Audit mode with the Generalize box unchecked. This will also work for 9.0 SP3 but is not required. In 9.0 SP3, the image can be captured in OOBE mode with the Generalize option.
2. Import the UNATTEND.XML file attached to the Community article.
3. Import the provisioning template attached to the Community article.
4. Create a LANDesk agent to be used for provisioning if Software Distribution Packages will be deployed with the provisioning template. Instructions for creating the provisioning agent are in this Community article.
5. Modify the imported provisioning template.
6. Enter the variables used by the UNATTEND.XML and the provisioning template.
7. Add drivers for Hardware Independent Imaging (HII). For help with adding drivers for HII in 9.0 SP2, reference this Community article. For help with adding drivers for HII in 9.0 SP3, reference this Community article.
8. Add NIC and Disk drivers to WINPE for the computers that will be imaged. For help with injecting drivers into WINPE, reference this Community article. In 9.0 SP2, WINPE requires Vista 32-bit compatible drivers. . In 9.0 SP3, WINPE requires Windows 7 32-bit compatible drivers.
9. Add devices to be provisioned in the LANDesk Console if they are not already available in the Console.
10. Schedule the provisioning template and start the task.
11. PXE Boot the computers that were added to the provisioning task and wait for the task to complete.

Capture the windows 7 image

For help with capturing the Windows 7 image, reference this Community article. The image to be deployed must be captured after running SYSPREP.EXE in Audit mode with the Generalize box unchecked. This will also work for 9.0 SP3 but is not required. In 9.0 SP3, the image can be captured in OOBE mode with the Generalize option.

Import the UNATTEND.xml file

1. For 64-bit Windows 7, copy the Win7x64Unattend.xml file to a directory on the Core Server. For 32-bit Windows 7, copy the Win7Unattend.xml file to a directory on the Core Server. The files are attached to this Community article.

2. In the Operating system deployment tool in the LANDesk Console on the Core Server, click on Provisioning templates in the left pane.

3. Click the Install scripts icon along the top of the Operating system deployment tool.

4. In the Install scripts window, click the Browse button and browse to the directory where the appropriate unattend.xml file was copied to the Core Server.

5. In the Script name box type in a name for this unattend.xml file.

6. In the Description box, enter a description if desired.

7. Select the Target operating system from the drop-down list.

8. Click to place a checkmark in the box for Insert variables into script.

9. Click the Import button to import the unttaned.xml file. The Script name will appear in the Install scripts list if it is successful.

Import the provisioning template

1. Copy the provisioning template file to a directory on the Core Server. The file is attached to this Community article.

2. In the Operating system deployment tool in the LANDesk Console on the Core Server, click on

Provisioning templates in the left pane.

3. Click the Import templates icon along the top of the Operating system deployment tool.

4. Click the Browse button in the Import templates window and browse to the location of the provisioning template that was copied to the Core Server in step 1.

5. Click the Import button.

6. Click OK.

7. Click the Close button in the Import templates window. The imported template will show up in the Operating system deployment tool under Provisioning templates | My templates | All my templates.

Create Provisioning agent

This step can be skipped if the provisioning template will not include any Software Distribution packages. Create a LANDesk agent to be used for provisioning. Instructions for creating the provisioning agent are in this Community article.

Modify the imported provisioning template

1.In the Operating system deployment tool, double-click the provisioning template that was imported in the Provisioning templates | My templates | All my templates folder.

2. Expand OS Installation and click on Deploy image.

3. Replace <MASTERNAME>.TBI with the name of the Windows 7 image to be deployed.

4. Click on the Set Active action.

5. If the Windows 7 image only contains a single partition, uncheck the box for Windows 7/Windows Server 2008 R2 with a separate system partition. A default install of Windows 7 will have a separate system partition (100 MB) which requires this box to be checked.

6. Click on the AssignDrive action.

7. If the Windows 7 image only has a single partition, change the Partition id to 1. A default install of Windows 7 will have a separate system partition (100 MB) which requires this to be 2. If the image also contains an OEM partition, the Partition id will need to be set to 3.

8. Expand Post-OS installation and click on the Inject script action.

9. Select the unattend.xml file that was imported earlier from the Script name drop-down list.

10. If the image being deployed has the drivers for the computer that it will be deployed to, the Inject HII drivers action can be deleted.

11. Expand System configuration and click the Install Provisioning Agent action.

12. Select the Provisioning Agent created earlier from the Configuration name drop-down list. If the provisioning template will not include any software distribution packages, this action can be deleted. If the Install Provisioning Agent action is deleted, the GetLocalTasks action will also need to be deleted.

13. Click the GetLocalTasks action.

14. Select the Software distribution package from the drop-down list. Additional Software Distribution actions can be added to install additional Software Distribution packages.

15. Click the Install LANDesk Agent action.

16. Select the desired LANDesk Agent from the Configuration name drop-down list.

17. Click the Shutdown action.

18. Select either Reboot or Shut down for the Shutdown action. Do not select the Boot to Managed WinPE(Virtual Boot) option.

19. Click OK to save the changes to the template.

Enter the variables

1. In the Operating system deployment tool, click on Provisioning templates then click the Public variables icon along the top of the window.

The public variables shown in the screenshot above are there by default. The Replace value for the coreIP and corename variables can be changed if necessary but the Search value (variable name) should not be changed because they are critical for proper functionality of provisioning. The Search values are case-sensitive.

2. Click the Add button.

3. Enter AdminPass in the Search value box. AdminPass is used in the UNATTEND.XML file.

4. Select Sensitive data from the Type drop-down list.

5. In the Replacement value and Confirm replacement value boxes, enter the password that will be assigned to the Local Administrator account for the computer when the image is deployed.

6. Click OK.

AdminPass now shows up in the Public variables window.

7. Click the Add button.

8. Enter Win7ProdKey in the Search value box. Win7ProdKey is used in the UNATTEND.XML file.

9. Select String from the Type drop-down list.

10. In the Replacement value box, enter the Windows 7 product key.

11. Click OK.

12. Repeat this process to add the following variables:

a. Search Value: ImageShare Type: String Replacement value: UNC path to share where the image is stored. ImageShare is used in the provisioning template.

b. Search Value: Domain Type: String Replacement value: Name of the domain that the computer will join. Domain is used in multiple actions in the provisioning template.

c. Search Value: LDUser Type: String Replacement value: The user account used to map drives, install the LANDesk agent and join the domain. LDUser is used in multiple actions in the provisioning template.

d. Search Value: LDPass Type: Sensitive data Replacement value: Password for LDUser account. LDPass is used in multiple actions in the provisioning template.

e. Search Value: ImageTool Type: String Replacement value: UNC path to IMAGEW.EXE v2. Default location is \\<CoreServerName>\ldmain

ImageTool is used in the provisioning template.

Add drivers for hardware independent imaging (HII)

This step can be skipped if the Inject HII drivers action was deleted from the provisioning template. For help with adding drivers for HII in 9.0 SP2, reference this Community article. For help with adding drivers for HII in 9.0 SP3, reference this Community article.

add nic and disk drivers to winpe

For help with injecting drivers into WINPE, reference this Community article. In 9.0 SP2, WINPE requires Vista 32-bit compatible drivers. . In 9.0 SP3, WINPE requires Windows 7 32-bit compatible drivers.

add devices to be provisioned

This section can be skipped if the computers to be imaged are already in All Devices in the LANDesk Console.

1. In the LANDesk Console, expand Configuration.

2. Right-click Bare Metal Server and select Add Devices.

3. In the Add a bare metal server window, select MAC address from the Identifier type drop-down list.

4. Click the Add button.

5. In the Bare Metal Server window, enter the Computer Name in the Name box. This will be the name of the computer after the image is deployed with the provisioning template.

6. Make sure the Identifier type has MAC address, then enter the MAC address for the computer to be imaged in the Identifier box.

7. Click the Add button.

8. The MAC address will show up in Server identifiers. Click OK.

9. The computer added will now show up in the Add a bare metal server window. Additional computers can be added by clicking the Add button and then repeating steps 5 through 9 for each computer to be added. Click OK when finished adding computers.

The computers added will show up in the LANDesk Console in the Configuration | Bare Metal Server folder.

Schedule the provisioning template and start the task

1. In the Operating system deployment window, right-click the provisioning template in the Provisioning templates | My templates | All my templates folder and select the Schedule Template option.

The provisioning template will show up in the Scheduled tasks tool.

2. Drag the computer(s) from the Bare Metal Server folder or from All Devices and drop them on the provisioning task.

3. Turn off the computers that were added to the task.

4. In the Scheduled tasks tool, right-click the provisioning task and select Start now.

5. Wait for the Status to show Delayed and the Result to show Policy has been made available for all computers in the task.

Pxe boot the computers and wait for task to complete

1. PXE Boot (Network boot) the computer(s) in the provisioning task. When the computer(s) are PXE booted, they will automatically start running the provisioning template.

2. Wait for the provisioning task to complete. The computer(s) will reboot at least 3 times during the provisioning process. Following are screenshots showing various stages during the process:

Right after PXE booting the computer showing it automatically detecting the provisioning task.

Loading WINPE from the PXE representative. The IP address shown is the IP address of the PXE representative.

WINPE has successfully loaded and is starting to run the provisioning template.

Provisioning template is now on the Deploy Image action. 4 minutes is the time remaining for the image to be deployed.

The image has been successfully restored and is now setting the drive letter for the OS partition for the injection of the UNATTEND.XML.

The UNATTEND.XML file has been copied to the restored OS along with the HII drivers and then CTOS rebooted the computer into the OS. When the OS boots for the first time, sysprep runs to do some initial configuration and then reboots the computer again. It has joined the domain and is now installing the provisioning agent.

The provisioning agent successfully installed and the Software Distribution action completed successfully. The LANDesk agent is now being installed before the shutdown action runs which is the last action in the provisioning template. When the agent finishes, the computer will shutdown unless the shutdown action was changed from the default. After the shutdown action runs, the provisioning process is complete and the task will show the results.

References:

Hardware Independent Imaging (HII) :

http://community.landesk.com/support/docs/DOC-24084
LANDesk OS Deployment Landing Page :

http://community.landesk.com/support/docs/DOC-23516

http://community.landesk.com/support/docs/DOC-9485
LANDesk Provisioning Landing Page :

http://community.landesk.com/support/docs/DOC-23470
LANDesk 9 HII - Adding Setup.exe Drivers during HII process :

http://community.landesk.com/support/docs/DOC-8674