Quantcast
Channel: Ivanti User Community : All Content - OS Deployment and Provisioning
Viewing all articles
Browse latest Browse all 1803

Getting started with OS Deployment (OSD) for Windows 7 in LANDESK® Management Suite 9.5 or 9.0 SP4

$
0
0

Issue:

How do you set up OSD to deploy a Windows 7 image with the LANDESK imaging tool (IMAGEW.EXE v2)?

How can an image be captured for use with OSD?

 

Resolution:

 

Quick Reference

The general overview of the steps required is outlined below. Continue reading for more detailed information.

 

  1. Capture an image of Windows 7 for deployment.
  2. Create an OSD script to deploy the Windows 7 image.
  3. Add the OSD deployment script to the PXE Boot Menu.
  4. Add drivers for Hardware Independent Imaging (HII).
  5. PXE Boot a computer and Deploy the Windows 7 image.

 

Capture an image of Windows 7 for deployment

For information on capturing a Windows 7 image see: How to Capture a Windows 7 image with OSD in LANDESK® Management Suite 9.0 SP2

 

Create an OSD script to deploy the Windows 7 image

StartOSD.png

 

1. Open the Operating System Deployment (OSD) tool in the LANDESK Console by selecting Tools | Distribution | OS Deployment.

 

NewWINPEscript.png

 

2. In the OSD tool, right-click All OSD Scripts and select the New Windows PE Configuration option.

 

 

 

DeployScript.png

 

3. Select the Deploy Image option and click OK.

 

DeployGeneral.png

 

4. On the General page, enter a name and a description for the capture script. Then click on Methods and credentials.

 

 

 

DeployCredentials.png

 

5. On the Methods and credentials page, select the Classical download option.

6. Check the box for Image uses SysPrep and Use Hardware-independent Imaging (HII).

7, Enter a domain user and password for a user that has access to the imaging tool and to the image share where the image is stored.

8. Click on Image type and path.

 

DeployPath.png

 

9. On the on Image type and path page, select LANDESK Imagew V2 from the Select the image type drop-down list.

10. Enter the UNC path to the image to be deployed.

11. Enter the UNC path to the imaging tool. The path shown is the default location for the imaging tool.

12. Specify the partition which is the System or C drive. With a default install of Windows 7, the System partition is 2 because Windows 7 creates a 100 MB partition as the first partition.

13. Click on SysPrep options.

 

DeploySysprepOpts.png

 

14. On the SysPrep options page, select Windows 7 from the Select a Windows product drop-down list.

15. Make sure the Use existing SYSPREP file as a template box is unchecked.

16. Click on Image settings under the SysPrep options.

 

DeploySysprepSettings.png

 

17. On the Image settings page, select the appropriate time zone from the Time zone drop-down list.

18. Enter the Volume license key.

19. Enter the Name and Organization if desired.

20. Click on Network credentials.

 

DeloySysprepDomain.png

 

21. On the Network credentials page, Select the Domain radio button and enter the domain the computer will join.

22. Specify a domain user and password that can join the computer to the domain.

23. Check the box for Add device to an Active Directory OU and specify the OU if the computers will be added to a specific OU.

24. Click on Naming convention.

 

DeploySysprepName.png

 

25, On the Naming convention page, check the box for First attempt to get and use existing computer names from the Inventory database if desired.

26. Modify the other options as desired.

27. Click on Hardware-independent imaging.

DeploySysprepHII.png

 

In SP3, the only option available is to check the box Using UNC to copy driver files. Without this box checked, the drivers will be downloaded using HTTP. The following steps are for SP2:

28. On the Hardware-independent imaging page, select the Auto Detect option.

29. Uncheck the box Using UNC to copy driver files.

30. Click on LANDESK agent.

DeploySysprepAgent.png

 

31. On the LANDESK agent page, enter the UNC path to the Core Server's LDLOGON share which is where WSCFG32.EXE is located.

32. Enter a domain user and password that has access to the LDLOGON share of the Core Server.

33. Click Save.

DeployOptions.png

 

34. Click OK.

 

 

Add the OSD deployment script to the PXE Boot Menu

StartBootMenu.png

 

1. In the LANDESK Console, select Tools | Distribution | PXE Boot Menu.

DeployScriptToMenu.png

 

2. In the OSD tool, click the OSD deployment script and drag it to the PXE Boot Menu tool and drop it on the PXE Boot Menu. If the LANDESK tools are tabbed, drag the OSD script to the PXE Boot Menu tab which will activate the PXE Boot Menu tool so that the script can be dropped on the menu.

DeployBootMenuCon.png

3. Click the Update button.

 

 

Add drivers for Hardware Independent Imaging (HII)

For information on adding drivers for HII in 9.0 SP2 see: LDMS Version 9 HII Quick Start Guide

Add all drivers for all computers that the drivers are not already included in the captured image.

 

For 9.5 and 9.0 SP3 see: Hardware Independent Imaging (HII)

PXE Boot a computer and Deploy the Windows 7 Image

1. PXE boot the computer. Follow the computer manufacturers instructions on how to PXE Boot the computer. This requires configuring the BIOS settings to do a Network boot.

 

 

PXEbootF8.png

 

2. Press F8 when the option comes up when the computer is booted. The PROXY IP address should be the IP address of the PXE Representative for the subnet.

 

WINPEmenu.png

 

3. Select WinPE Menu in the list and press enter.

WINPEloading.png

 

4. Wait for WINPE to load and for the PXE Boot Menu to come up.

DeployPXEMenu.png

 

5. Select the OSD deployment script (Deploy_Windows_7_Image) that was created previously and click OK.

ImageDeploying.png

 

6. Wait for the image to deploy. When the deployment is complete, the computer will restart and run through the sysprep process. During the sysprep process the computer will restart several times.


Viewing all articles
Browse latest Browse all 1803

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>