Issue

• WINPE is failing to load drivers that have been injected.
• WINPE is corrupt and needs to rebuild it.
• Need to create a new BOOT.WIM.
• BOOT.WIM file is missing from the Managementsuite\LANDesk\VBOOT folder on the Core Server.

Resolution

1. MOVE all of the following files on the Core Server to a Temp folder as a backup if they exist:
   • Managementsuite\BOOT.WIM.BAK
   • Managementsuite\BOOTMEDIA.WIM.BAK
   • Managementsuite\BOOT_x64.WIM.BAK
   • Managementsuite\LANDesk\VBOOT\BOOT.WIM.BAK
   • Managementsuite\LANDesk\VBOOT\BOOTMEDIA.WIM.BAK
   • Managementsuite\LANDesk\VBOOT\BOOT_x64.WIM.BAK
   • Managementsuite\LANDesk\VBOOT\BOOT.WIM
   • Managementsuite\LANDesk\VBOOT\BOOTMEDIA.WIM
   • Managementsuite\LANDesk\VBOOT\BOOT_x64.WIM
2. Copy BOOT.WIM and BOOT_x64.WIM from the Managementsuite\LANDesk\VBOOT\Clean folder to the Managementsuite\LANDesk\VBOOT folder on the Core Server.
3. In Windows Explorer, right-click OSD.UPGRADE.EXE in the Managementsuite folder on the Core Server and select the "Run as administrator" option. This will open a command prompt window that will stay open until it is finished.
4. When OSD.UPGRADE.EXE finishes, inject any required NIC or Disk Controller drivers into WINPE through the LANDESK Console.
5. For 2016 and older versions, redeploy all PXE representatives. For 2016.3 and newer versions, wait for the PXE reps to automatically download the BOOT.WIM and BOOT_x64.WIM files from the Core Server.

• Introduction
• Changes in Internet Information Services (IIS)
• Configuring the NetBoot Install Files Repository
• Space Requirements on the Elected Representative

Introduction

LANDESK 2016.3 introduced Self-Electing Subnet Services. This changes the way NetBoot Services are configured. Self-Electing Subnet Services will need to be enabled alongside PXE Services in the Client Connectivity Agent Settings for managed devices:

For more information on the full configuration, please visit How To: Configure PXE services in LDMS 2016.3.

Changes in Internet Information Services (IIS)

NetBoot Installers includes files that have zero-value extensions. IIS is not configured by default to account for these file types, so the IIS MIME Types need to be updated.

Open Internet Information Services (IIS) Manager on the Core Server and browse to the Default Web Site. From there, select MIME Types:

In the MIME Types Action Window, select Add... Configure the new "." MIME Type as follows:

Click OK. It is not necessary to run an IISReset.

Configuring the NetBoot Install Files Repository

By default, the NetBoot Image location on the core will be http://corename/landesk/vboot/Netboot.

This location can be configured in the Operating System Provisioning tool in the LANDESK Management Console.

Go to Tools > Provisioning > OS Provisioning. Select Preboot and click ManageNetBoot Image Mappings:

Click OK once the desired Configurations have been made.

At this point, the Self-Elected PXE Representatives will need to check in with the Core Server to Acknowledge the updated Repository Settings. This can be done in two ways:

• Manually restarting the LANDESK PXE Service on the Elected Representative.
• Waiting for the Elected Representative to check in via the Polling Frequency (Configured in the Self-Electing Subnet Services Tool).

When this is done, the pxesvc.log located on the Representative under C:\ProgramData\LANDesk\Log will log something similar to the following:

Thu, 16 Feb 2017 12:32:35 Redirecting and resolving paths for Default.
Thu, 16 Feb 2017 12:32:35 Original path: http://ldcore20163/ldlogon/mac/NBIs/Stamped.nbi/, redirected path: http://ldcore20163.ADAY.local/ldlogon/mac/NBIs/Stamped.nbi/
Thu, 16 Feb 2017 12:32:35 Redirected path: http://ldcore20163/ldlogon/mac/NBIs/Stamped.nbi/, resolved path: http://ldcore20163/ldlogon/mac/NBIs/Stamped.nbi/
Thu, 16 Feb 2017 12:32:35 Redirecting and resolving paths for VMware7,1.
Thu, 16 Feb 2017 12:32:35 Original path: http://ldcore20163/ldlogon/mac/NBIs/Stamped.nbi/, redirected path: http://ldcore20163/ldlogon/mac/NBIs/Stamped.nbi/
Thu, 16 Feb 2017 12:32:35 Redirected path: http://ldcore20163/ldlogon/mac/NBIs/Stamped.nbi/, resolved path: http://ldcore20163/ldlogon/mac/NBIs/Stamped.nbi/
Thu, 16 Feb 2017 12:32:35 ******* Leaving GetNetbootFiles *******

Space Requirements on the Elected Representative

The Space Requirements on the Elected Representatives is very little. Elected PXE Representatives will redirect the NetBooted Macs to the Core/Preferred Server in order to pull down the full NBI.

A typical size for a LANDESK Stamped NBI will be around 550MB. The NBI files copied down the PXE Representatives will be around 20-30MB in size. On the Representative, they are located under C:\Program Files (x86)\LANDesk\PXE\System\images\mac.

Error message:

The error message is located in the agent install log (C:\ProgramData\LANDesk\Log\wscfg32.log). The last message in the log will look like so:

Tue, 12 Sep 2017 09:32:59 INI:  EXEC49=C:\Program Files (x86)\LANDesk\LDClient\SCSDiscovery.exe, /Output Silent SystemDiscovery /NoFile, NOWINDOW + INSTALLONLY

Tue, 12 Sep 2017 09:32:59 Starting process: C:\Program Files (x86)\LANDesk\LDClient\SCSDiscovery.exe /Output Silent SystemDiscovery /NoFile

The agent install will be hung from that point on.

Cause:

SCSDiscovery.exe Is used to determine if the device is vPro capable. The device may not be ready to run that EXE and it may not have access to the DLL's it needs to determine vPro functionality. This is usually because the OS is booting up for the first time and goes through additional configuration on the initial boot.

Solution / Workaround:

Add a 200 second wait (This time can be adjusted as needed) as the first action is System Configuration. This will allow the OS to go through it's initial configuration/OS setup. In general, it's a good idea to put a wait at the beginning of System Configuration to allow the OS enough time to boot properly.

Overview

This document contains the steps necessary to deploy a Windows 10 image in provisioning using ImageW v2. Although it mentions Windows 10, the same steps will work for Windows 7, 8 and 8.1.

Capture the Windows 10 image

For help with capturing the image, refer to the following Community article:

How to capture a Windows 10 image using IMAGEW.EXE.

Import the UNATTEND.XML file

1. Copy the Winx64Unattend.xml file to a directory on the Core Server. The file is in the Provisioning.zip file attached to the following Community article:

How to Deploy a Windows 10 image using IMAGEW.EXE

2. In the Operating system provisioning tool in the LANDESK Comsole on the Core Server, click on Provisioning templates in the left pane.

3. Click Tools at the top of the window then click Install Scripts.

4. In the Install scripts window, click the Browse button and browse to the folder where the Winx64Unattend.xml file was copied and select it.

5. In the Script name box, enter a name for this unattend file to uniquely identify it.

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

7. Select Windows for the Target operating system.

8. Click the Import button to import the unattend file into the database. The Script name will appear in the Install scripts list if it is successful.

Import the Provisioning Template

1. Copy the provisioning template Win10Deploy.xtp to a folder on the Core Server. The template is in the Provisioning.zip file attached to the following Community article:

How to Deploy a Windows 10 image using IMAGEW.EXE

2. In the Operating system provisioning 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 sytem provisioning tool.

4. Click the Browse button in the Import templates window and browse to the location where the template was copied in step 1 and select it.

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 provisioning tool under Provisioning templates | My templates | All my templates with a name starting with Win10Deploy and includes a Date/Time stamp. The template name can be changed after it is imported.

Modify the Imported Provisioning Template

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

2. Expand the OS-installation section of the template and click on the Deploy Image action.

3. Make sure that LANDESK ImageW V2 is selected for the image type.

4. Enter the UNC path including the filename to the Windows 10 image to be deployed. The file will have a .TBI extension.

5. Click the Validate button which updates the Command-line then click Apply.

6. Click on the Inject unattend file action under the Post-OS installation section of the template.

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

8. Click the Apply button.

9. If the OS being deployed already has the drivers for the computer to be imaged or you are not planning on using LANDESK Hardware independent imaging, the Hardware independent imaging action can be deleted from the template in the Post-OS installation and System configuration sections.

10. Click on the Install LANDESK Agent action in the System configuration section of the template.

11. Select the desired LANDESK Agent from the Configuration name drop-down list.

12. Click the Apply button.

13. Add additional actions to the template if desired. Do this by right-clicking the section of the template and select the Add Action option. There is an action to join the domain and an action to run software distribution packages as well as many others. After adding any actions, be sure to click the Apply button.

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

Enter the Variables

1. In the Operating system provisioning tool, click on Provisioning templates in the left pane.

2. Click Tools and click Public Variables.

The public variables shown in the screenshot above are there by default. The Replace value for the variables corename and coreIP can be changed if needed but do not change the Search value (variable name) for them or it will break provisioning. The Search values are case-sensitive.

3. Click the Add button.

4. Enter AdminPass in the Search value box. This variable is used in the unattend.xml file.

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

6. In the Replacement value and Confirm replacement value boxes, enter the password which will be assigned to the local Administrator account on the computer when the image is deployed.

7. Click OK.

AdminPass now shows up in the Public variables window.

8. Click Add.

9. Enter WinProdKey in the Search value box. This variable is used in the unattend.xml file.

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

11. Enter the Windows 10 product key in the Replacement value box.

12. Click OK.

13. Click Add.

14. Enter Company in the Search value box. This variable is used in the unattend.xml file.

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

16. Enter your Company name in the Replacement value box.

17. Click OK.

18. Click OK to close the Public variables window.

Add Drivers for Hardware Independent Imaging (HII)

This step can be skipped if the HII actions were deleted from the template.

For help with HII, click F1 in the LANDESK Console and search for HII.

Add Devices to be Imaged

This section can be skipped if the devices are already in the LANDESK Console under All Devices.

1. In the LANDESK Console, expand Configuration.

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

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

4. Click the Add button.

5. In the Bare Metal Device window, enter a name for the device in the Name box. The name entered will be the computers name after it is imaged.

6. Make sure the Identifier type has MAC address selected then enter the MAC address of the of the computer 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 show up in the Add a bare metal device window. Click OK.

10. The computer added will show up in the LANDESK Console in the Configuration | Bare Metal Devices folder after the LANDESK Inventory Server service processes it.

Add the Image Server as a Preferred Server

Setup a preferred server for the computer where the image share is located if it has not already been done. Following Community article has information on setting up preferred servers:

How to configure the Preferred Server (Target) for Content Replication

Schedule the Template and start the Task

1. Drag the computer(s) from the Bare Metal Devices folder or from All Devices and drop them on the template that was imported earlier.

2. Click Save.

3. Make sure all devices targeted for the task are off.

4. Right-click the task and select Start now | All.

5. Wait a minute to give the task time to initialize.

Network Boot the Devices and Wait for the Task to Complete

1. Network boot (PXE boot) the computer(s) in the provisioning task. When the computer(s) are PXE booted, they will automatically load WINPE and run the template. For help with network booting the computer(s), refer to the computers documentation.

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

Downloading WINPE from the PXE Representative. The IP address shown is the IP address of the PXE Representative.

WINPE is loading.

WINPE has successfully loaded and has started to run the provisioning template.

ImageW is currently running to deploy the image.

The image has been deployed and the computer has rebooted to load the OS. It has started going through the sysprep process to load the OS for the first time.

The OS rebooted and is continuing to load for the first time processing the unattend.xml file.

Sysprep has completed and is now running the actions in the System Configuration section of the template. When the template is done, the computer will shutdown.

Alternate Method to Start a Provisioning Template on a Computer

For this method, skip the following sections of this document:

Add Devices to be Imaged

Schedule the Template and Start the Task

Network Boot the Devices and Wait for the Task to Complete

1. If the computers all do a BIOS boot then you can skip to step 3. If the devices do a UEFI boot, Click Preboot | PXE Boot Options in the Operating system provisioning tool.

2. Make sure there is a check in the Always PXE Boot UEFI Devices and click Save.

3. Network boot (PXE boot) the computer and click F8 when it shows on the screen. Refer to the computers manual if you need help PXE booting it.

4. Select WinPE Provisioning and hit Enter on the keyboard.

5. WINPE is downloading from the PXE Representative. The IP address shown is the IP address of the PXE Representative.

6. WINPE has downloaded and is now starting on the computer.

7. Enter the Domain, Username and Password for an account that has rights to provisioning in the LANDESK Console. Use the same account that you login with to the LANDESK Console.

8. Click OK.

9. Click on the Provisioning template under All my templates and click OK.

10. The template is now running. Wait for it to finish. The computer will shutdown when the template is done. Refer to the screenshots in the previous section to see various stages of the provisioning process.

Issue:

While building the HII database, the following error pops up:

"Processing drivers for HII failed.  Error "Index was outside the bounds of the array."

Cause:

Microsoft changed the format for INF files.

Solution:

Download and install 2016.3 SU3 (See note below) by referring to the following document: LANDESK Management and Security 2016.x and newer Sustaining Patch Information

Provisioning Template Process: Online vs Offline Compared

Ivanti Endpoint Manager Provisioning functions through the creation of Provisioning Templates.  By default, the device being provisioned will download the template itself and all related files during the provisioning process.  Sometimes it may be desirable to provision offline devices or devices that do not have a direct network connection to the core server.  In such cases, you can build a Disconnected Provisioning Template that can be deployed via DVD disk or USB drive.

Startnet.cmd

When a provisioning template begins, the startnet.cmd script is executed.  This script sets up the WinPE environment for OS Provisioning.  A sample script is attached to this document, and can also be viewed within your Boot.wim or in WinPE itself.  In WinPE it's located here:

x:\windows\system32\startnet.cmd

Offline Check

One section of the script executes a utility called OfflineCheck.  OfflineCheck scans all the mounted volumes looking for offline_task.xml.  Offline_task.xml is essentially the offline version of the template and actions to be executed, and should only exist in offline templates.  If the file doesn’t exist it is assumed that this is not an offline template and provisioning proceeds in online mode.

When Online

The startnet.cmd script is running in online mode and tries to resolve the Core Server's IP address.  If it fails to resolve, the template fails.  If it's able to resolve the IP it next attempts to ping the core by name.  If this fails, the template will still continue.  The startnet.cmd script then continues with standard actions such as an inventory miniscan, starting the remote control client, and eventually provisioning.

When Offline

All of the online processes are skipped and the device begins provisioning according to the offline_task.xml. 

Troubleshooting

On occasion an offline template may run in online mode.  To troubleshoot this, we will want to compare the startnet.cmd script in WinPE with a known good copy such as the attached.  Next, check to see the offline_task.xml exists.  Its possible the Offline Provisioning Media did not create successfully or was modified post creation.

If all the above looks correct, watch the execution of the startnet.cmd script when WinPE first loads with the assumption that some action within is failing.  This process will generate an offlinecheck.log that is fairly verbose and should identify the problem.  One common failure is when copying some files to the ramdisk (X: drive).

In extreme cases you could mount the boot.wim and modify the startnet.cmd script to remove the “@echo off” from the beginning, in order to get better visibility to exactly where it is failing.

How To:

This is quick guide on how to automatically copy the WinPE Provisioning .LOG and .TXT files that are used when troubleshooting action handlers in WinPE provisioning. The logs that are generated during WinPE are removed once the device reboots and moves onto the "System Configuration" section of the provisioning template. This configuration will make it so you don't have to babysit the provisioning task, add a wait before CTOS, remote in, and manually copy/review the log files when troubleshooting action handlers. This will allow you to "set it and forget it" and review the logs when it's convenient for you.

Step by Step:

     1. Create a copy of the template you are troubleshooting.

     2. Add the following 4 actions after the action that you are trying to troubleshoot, or add them BEFORE the "Configure Target OS" action in the Post-OS Installation step (If you are using a template that uses CTOS).

     3. Once those actions are added to the template, run the template and allow it to complete the copy file actions.

     4. Verify that the logs were copied over to the share that you configured in the "Map Drive" section. If everything was configured correctly, you should see your logs and .TXT files like so:

Attached below is the template that I used when creating this document. I used public variables for the user account/password and the CoreName variable. If you would like to use those variables as well, make sure you configure those for your environment.

Information

LANDESK Management Suite includes support for OS Provisioning clients to download vBoot related files from a PXE Server.

Now the Boot.wim file that contains the Windows PE image does not have to come directly from the Core.  A peer or preferred server can now be utilized.

The boot images are over 200 megabytes so it can be important to store the boot images on the local subnet or in a more optimal location for the client than the Core may provide.

New "Attempt Peer, "Attempt Preferred Server", and "Allow Source" radio buttons have been added to the "Boot to Managed WinPE (Virtual Boot)" selection for the "Reboot/Shutdown" Provisioning Action.  Note: Downloading of the boot.wim from Preferred Server or Peer at this time only applies to Vboot (Virtual Boot).  It does not apply to PXE boot.

This eliminates the need for the clients to go back to the core to download the 200+ megabytes of support files in order to virtual boot.

In order for the vboot files to be accessible to the clients, the proper web share must be configured on the Preferred Server.

Resolution

Attached to this article is a .ZIP file Containing the following:

• Deploy PXE Rep and Configure IIS.ldms  (Package Bundle)
• ps-pxe-setup.bat

Steps to import and configure package bundle.

1. Download the attached PreferredServerWithPxeHostVboot.zip file
2. Unzip the downloaded .zip file to the desired location on the core server.
3. Open the Distribution Packages tool in the LANDESK Management Suite console.
4. Right click "My Packages" and select "Import"
5. Browse to the location where the .ZIP file was uncompressed to.
6. Double click the Deploy PXE Rep and Configure IIS.ldms file.
7. This will import a package bundle into the LANDESK Management Suite console under "My Packages"
   Click here for more information about Package Bundles.
8. Within this bundle, you will find a package called Configure Preferred Server to host vboot files.
9. In addition, this bundle contains the default PXE Representative Deployment package.
10. Copy the ps-pxe-setup.bat file to your regular software distribution share.
11. Modify the properties of the Configure Preferred Server to host vboot files package for your environment

          a. Modify the server name under the Package Information section to reflect the proper server name for your package share

          b. Under the Additional Files section browse to the location where you have copied the ps-pxe-setup.bat file and add it as an additional file
              (By default in the imported package this defaults to http://coreservername/ldlogon.

Scenarios for distributing package bundle or only the distribution package:

Scenario 1:

• PXE Representative is already installed on the Preferred Server

    In this instance, you can simply select the package Configure Preferred Server to host vboot files, right-click and select "Create scheduled task".

Scenario 2:

• PXE Representative is not installed on the Preferred Server and you want to configure IIS to host the vboot files

          In this instance, right-click the package bundle called "Deploy PXE Rep and Configure IIS" and select "Create Scheduled Task".

     This will first configure install the PXE Representative and then configure the Preferred Package Server to host the vboot files in a Web Application called "landesk" and a virtual directory below that called "vboot"
     This virtual directory points to the following physical path:

"%programfiles(x86)%"\landesk\pxe\system\image\boot"

• Description
• What to Expect from Conditionals
• Adding Conditionals to a Template
• Utilizing Conditionals in conjunction with Public Variables

Description

This document is intended to cover the newly added feature of Conditionals in LANDESK Provisioning. Conditionals are best used to consolidate templates, allowing flexibility for:

• Multiple Images
• Software Distribution
• Disk Configuration
• Hardware Types
• BIOS Architecture

What to Expect from Conditionals

• Conditionals in LANDESK provisioning use "If and Else" arguments to determine multiple outcomes for a template.
• Stacking of multiple "if" conditionals is allowed. LANDESK will address all "if" conditionals one at a time.
• "Else" conditionals will only apply to the "if" conditional directly preceding it.
• Conditionals can be used at any point in the provisioning template, in any section.
• Custom scripts can be used in conjunction with Conditionals.
  • A successful script (return 0) will result in an "if" conditional being executed.
  • A non-successful script (not return 0) will result in LANDESK skipping past the associated conditional, or moving on to a corresponding "else" conditional.

Adding Conditionals to a Template

In this case, a default Deploy Template will be customized using Conditionals. To create such a template, browse to Tools>Provisioning. In the Operating System Provisioning tool, clickNew Template>Deploy Template.

Fill out the required fields and clickCreate.Should look something like this:

Right Clickany of the actions, and selectAdd Condition> If or Else

Utilizing Conditionals in conjunction with Public Variables

In LANDESK 2016, a new action type was introduced called Compare Variable. This action is extremely useful when using conditionals in provisioning. The following is an example of where to use this new feature:

We have an Image for Laptops and an Image for Desktops. How do we utilize both images in one Template?

This scenario will use the same template created above. The first step in using conditionals is to find a characteristic that LANDESK can use to differentiate between devices. LANDESK Inventory yields a different value for Desktops and Laptops.

For this example, we have "Chassis Type" recorded as NoteBook and Mini Tower. These values can be used as conditional arguments using Public Variables.

To add "Chassis Type" to public variables, open the Operating System Provisioning tool and select theTools drop-down list from the toolbar. Then select Public Variables.

Select Add. Enter any Search Value that seems fitting - needs to be one word. The Type will be set to "Database value." The replacement value will be set to the entry in inventory; "Computer"."System"."Chassis Type"

SelectOK.

Open the properties of the base template created above and right click the OS installation section from the Action List. Select Add Condition> If.

Right click the newly created condition and select Add Action. Select Compare Variable in the "Type" drop-down list. Select the variable created above in the "Variable" drop-down list and enter Mini Tower in the blank space. Click Apply.

Right Click OS installation once more and select Add Action. Select Deploy Image from the drop-down list, name the action appropriately, and click OK. Fill out the action properties to deploy the desktop image.

Now do the same with the Notebook image, only this time use an Else conditional. It should look something like this:

Purpose

  UEFI is only supported in Provisioning and not OSD. There are two ways to execute the provisioning template:

1.   Schedule provisioning template based on the Mac address added into Bare Metal device,Please refer to this article: How to PXE Boot devices with UEFI
2.   Boot the UEFI client machine into WinPE manually,  then choose the provisioning template in public folder to execute, This article outlines how to launch public provisioning template with UEFI devices manually.

How To

On the core server

• From the console go to Tools > Provisioning > OS Provisioning.
• On the Operating System Provisioning window select the Preboot dropdown
• Select PXE Boot Options

• Check on option for Always PXE Boot devices UEFI

On the client machine

• Boot the client machine with network, UEFI does not support the F8 menu
• Input the username and password on the provisioning UI

Core Server: LDMS 2016 + SU4

SU4 download link:

http://community.landesk.com/downloads/patch/component/LD2016/LD2016_SU4.exe

For a Windows10 installation, Microsoft makes it possible to do an in-place upgrade from any older version without having to wipe or reload the device. Here is a HowTo of how to implement this with LANDESK Management Suite.

- Download the Win10 ISO

- Extract the contents to your LANDesk file server

- Create a Software Distribution Package, Executable type.

     - Point the primary file to the setup.exe, e.g.: \\yourlandeskshare\images\Win10Images\Windows 10 OS\setup.exe

     - At the Install/Uninstall options, add the following switches: /Auto Upgrade /quiet /DynamicUpdate Disable /Copylogs %SystemDrive%\ProgramData\LANDESK\Logs\

To get a full list of command line options please take a look at this Microsoft article:  Windows Setup Command-Line Options | Microsoft Docs

You can now create a scheduled task to deploy. Please note that both the Scheduled task settings and the used Agent Settings must have 'Download and Execute' as configured setting.

The installer is fully silent with the only UI being the one below. If you wish to change this, remove the /quiet from the command line switches.

Of course, you can still make this install part of a Provisioning Template or Package Bundle to follow up on the install with additional new software and/or settings. Be aware though that in testing the installer reports back to the server with successful before it's even managed its first reboot. A Wait might be necessary. in those cases.

A second option (author: marcel ) using the same XML file, but instead of using a .EXE, it uses Powershell to directly call the ISO:

$scriptPath=split-path-parent$MyInvocation.MyCommand.Definition

$unattend=""""+$scriptPath+"\unattend.xml"+""""

$mount=Mount-DiskImage-ImagePath ($scriptpath+"\YOUR.ISO") -PassThru

$driveLetter= ($mount|Get-Volume).DriveLetter

$setup=$driveLetter+":\setup.exe"

$param="/Auto:Upgrade /Unattend:$unattend /DynamicUpdate Disable"

Start-Process-FilePath$setup-WorkingDirectory ($driveLetter+":\") -ArgumentList$param

Description

When using LANDESK PXE it may be desired to remove some of the options listed on the PXE menus. There are also cases where too many options cause problems for some network cards. Whether removing them for convenience or to resolve an issue with the menu not showing up there are a number of ways to accomplish this. Three options are shown here:

Manually Changing the PXE Representative

The first option is to manually change the options onthe PXE Representative. On the PXE Representative, set the registry keys to 1 for the items that are to be disabled.

• HKLM\SOFTWARE\INTEL\PXE\ProxyDHCP\DisablePredefinedWinPE
• HKLM\SOFTWARE\INTEL\PXE\ProxyDHCP\DisablePredefinedDosPE
• HKLM\SOFTWARE\INTEL\PXE\ProxyDHCP\DisablePredefinedLinuxPE
• HKLM\SOFTWARE\INTEL\PXE\ProxyDHCP\DisablePredefinedProvisioningLinuxPE
• HKLM\SOFTWARE\INTEL\PXE\ProxyDHCP\ /v DisablePredefinedProvisioningWinPE

Note that on a 64-bit OS you will need to go to the 32 bit subsystem of the registry, which is found by adding Wow6432Node after Software as shown below.

• HKLM\SOFTWARE\Wow6432Node\INTEL\PXE\ProxyDHCP\DisablePredefinedWinPE
• HKLM\SOFTWARE\Wow6432Node\INTEL\PXE\ProxyDHCP\DisablePredefinedDosPE
• HKLM\SOFTWARE\Wow6432Node\INTEL\PXE\ProxyDHCP\DisablePredefinedLinuxPE
• HKLM\SOFTWARE\Wow6432Node\INTEL\PXE\ProxyDHCP\DisablePredefinedProvisioningLinuxPE
• HKLM\SOFTWARE\Wow6432Node\INTEL\PXE\ProxyDHCP\ /v DisablePredefinedProvisioningWinPE

Customizing the PXE Deployment Script

The second option is to use a custom PXE deployment script that calls a batch file to update the menu options. There is a custom script and associated batch file attached to this community article called UpdatePxeMenu.zip. The new script includes two additional lines that will download and execute the batch file. The batch file is commented and has details on how to disable each menu option within it. The DosPE option is set to disabled within the batch file. This new script allows the deployment of PXE reps with the configured options without having to modify the msi transform file as outlined below.

1. Download the UpdatePxeMenu.zip file
2. Extract the files
3. Place Pxe Representative Deployment w Menu Disable.ini in the \ManagementSuite\scripts directory. This will add an entry to the OS Deployment > OSD Scripts > All Other Scripts directory that can be used for PXE Representative deployment
4. Place UpdatePxeMenu.bat in the \ManagementSuite\landesk\files directory. This is the directory where the PXE Representative deployment script will access the file
5. Run the new script to deploy your PXE Representatives

Deploying the PXE Rep with Modifications in a Transform File

The third option available in 8.7 Service Pack 1 and later this can be done during the PXE Representative deployment by using a TRANSFORM file with OSDRep.msi. It is also necessary to create a new PXE Representative Deployment Script that uses the Transform File.

To create an MST do the following:

1. Install ORCA
2. Note: The Orca.msi can be found after installing the Windows Installer feature of the  Microsoft Platform SDK.
3. Open OSDRep.msi with Orca (OSDRep.msi can be found on the Core server at <drive>:\Program Files\LANDESK\ManagementSuite\LANDESK\files)
4. In Orca, click on Tranforms | New Transforms.
5. Click to highlight the Registry option on the left pane.
6. On the right pane, click the Name heading to sort by name.
7. Locate the following values.
   • DisablePredefinedWinPE
   • DisablePredefinedDosPE
   • DisablePredefinedLinuxPE
8. To disable the desired values, change the value from 0 to 1.
9. In Orca, click on Transforms | Generate Transform.
10. Save the Transform as name it OSDRepF8Options.mst. Save it in the same directory as OSDRep.msi.

Modify the PXE Representative Script

The PXE Representative Deployment Script must now be copied and the copy must be modified.

1. Make a copy of the "PXE Representative Deployment Script.ini" and name it "PXE Representative Deployment with MST to Disable F8 Options.ini".
2. Make the following changes:
   • Add a new line that downloads the OSDRepF8Options.mst.
   • Modify the installation line to add the TRANSFORMS property to the MSI switches. An example of the new line and the edited line are given below:

REMEXEC20=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/files/OSDRepF8Options.mst"
REMEXEC21=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /p="http://%CUSTJOBHOSTIP%/landesk/files/osdrep.msi" /msi /N /An /Ac /cmds=TRANSFORMS="""%LDMS_CLIENT_DIR%\sdmcache\OSDRepF8Options.mst"""

More information on PXE boot errors

PXE Boot errors and descriptions.

How to trouble shoot LANDESK PXE

Troubleshooting PXE boot (OSD)

Description

Hardware Independent Imaging allows drivers to be injected during the imaging process specific to the destination hardware. During hardware migration planning, driver decisions must be made.  In order to assist with that migration planning a preview option has been added to HII, enabling IT to review driver assignments prior to upgrading to a new OS.

Running HIIClient in Windows

1. On the Client machine, create the directory C:\Windows\LDDriverStore\
2. Copy HIIClient.exe to the new directory (LDDriverstore) on the client, from the core. The file can be found in the %LDMS_HOME%\landesk\files directory.
3. Copy driver.db3 file to newly created folder on the client (C:\Windows\LDDriverStore) from the core. The file can be found in the HII library path. The default path is C:\Program Files\LANDesk\ManagementSuite\landesk\files\drivers
4. Run HIIClient with the appropriate preview options (See below).
5. Review the logs for driver assignment and detection found in the directory where HIIClient was run.

• HIIClient.log
  
• HIIPreview.log

*****************  Starting HIIClient Preview *****************

Running in Windows

Running HIIClient in WinPE

1. In WinPE HIIClient.exe already exists in x:ldprovision.
2. The driver.db3 will need to be downloaded from the core. Use the "net use" command to map a drive to your HII library location on the core.
3. Run HIIClient with the appropriate preview options (See below).
4. Review the logs for driver assignment and detection found in the directory where HIIClient was run.

HIIClient options

hiiclient [/?] [/uncpath] [/taskid <taskid>] [/preview | /previewall] [/os <os> /arch <architecture>]

/? - Shows standard help and syntax information

/uncpath - Specifies if HII should use unc based paths to drivers

/taskid - Specifies the <taskid> to use to ask for SWD snippet when processing packaged drivers

/preview - Specifies if HII should run in preview only mode.

/previewall - Specifies if HII should run in preview only mode with debug information.

/os - Only valid with both /preview and /arch.

          Specifies which OS the preview should be run for.

          Valid options are: winxp, win7, win8, server2003, server2008r2, server2012

          If not specified the currently detected OS will be used.

/arch - Only valid with both /preview and /os.  Specifies which architecture the preview should be run for.

          Valid options are: x86, x64.

          If not specified the currently detected Architecture will be used for the preview.

HII Preview - Natural Driver Selection

Hardware device discovered. Device number 149:

Device name: Intel(R) 82574L Gigabit Network Connection

Primary device ID: PCI\VEN_8086&DEV_10D3&SUBSYS_07D015AD&REV_00

Additional device ID: PCI\VEN_8086&DEV_10D3&SUBSYS_07D015AD

Additional device ID: PCI\VEN_8086&DEV_10D3&CC_020000

Additional device ID: PCI\VEN_8086&DEV_10D3&CC_0200

Additional device ID: PCI\VEN_8086&DEV_10D3&REV_00

Additional device ID: PCI\VEN_8086&DEV_10D3

Automatically detected INF match discovered using device id PCI\VEN_8086&DEV_10D3.

Matching File: Windows 10 vm\Net\Intel(R) 82574L Gigabit Network Connection\net1ic64.inf

Additional device ID: PCI\VEN_8086&CC_020000

Additional device ID: PCI\VEN_8086&CC_0200

Additional device ID: PCI\VEN_8086

Additional device ID: PCI\CC_020000&DT_0

Additional device ID: PCI\CC_020000

Additional device ID: PCI\CC_0200&DT_0

Additional device ID: PCI\CC_0200

HII Preview - Driver Assignment

Hardware device discovered. Device number 149:

Device name: Intel(R) 82574L Gigabit Network Connection

Primary device ID: PCI\VEN_8086&DEV_10D3&SUBSYS_07D015AD&REV_00

Manually assigned INF match discovered using primary device id (PCI\VEN_8086&DEV_10D3&SUBSYS_07D015AD&REV_00).

Matching File: Hp OSD\network\hp\sp65585\Win7X64\ew_busfilter.inf

Provisioning Template Actions to assist in debugging HII issues

The Actions within this template are designed to run HIIClient.exe /previewall and consolidate the results into a C:\Logs folder so that they can be viewed after the device reboots during CTOS. With HIIClient in preview mode, it will list the device ID's that are discovered and what drivers in the HII Library associate with those ID's. This information is passed to DISM and DISM determines which driver to install. Looking at these logs will help you to determine which drivers are needed and help you build your HII library accordingly.

Note: With HIIClient in preview mode will not call DISM so an HII action is still needed.  After copying these actions to your template, make sure that the drive letter on the Create Logs Directory and the Copy actions match the active drive that Windows is installed on.

Problem/Issue/Symptoms

• Booting a UEFI machine via PXE fails, reporting the following error message: winload.efi file is missing or contain errors
• The PXE boot tries to load WinPE 32 WIM image from the Representative (BIOS mode) rather than the 64 bit one (UEFI mode)

Cause

• The PXE Representative has not been updated with the latest Service Pack or component patch installed on the Core Server
• The PXE Representative installation file is not updated on the core

Solution

Redeploy the PXE Representative to make it is the same version as the core.

If this the problem persists, make sure the following file on the is the same as the one from a fresh Core installation at the same version.
If needed, replace the file with one taken from the fresh installation and redeploy the PXE Representative:

%LDMS_HOME%\landesk\files\osdrep.msi

Issue

Receiving the error "The user name or password specified is not correct.   Provide new credentials" when authenticating using the Provisioning Client UI.

Cause

First, double-check that the credentials used are correct and that they have not been typed in incorrectly.  If the core server is installed on Server 2008 R2, it is likely that the Basic Authentication feature of IIS 7 was not installed.

Resolution

To install the Basic Authentication component for IIS 7 on Server 2008 R2, follow the steps below on the Core Server:

1. On the taskbar, click Start, point to Administrative Tools,  and then click Server Manager.
2. In the Server Manager hierarchy pane, expand Roles,  and then click Web Server (IIS).
3. In the Web Server (IIS) pane, scroll to the Role  Services section, and then click Add Role Services.
4. On the Select Role Services page of the Add Role  Services Wizard, select Basic Authentication, and then click Next.
   
5. On the Confirm Installation Selections page, click Install.
6. On the Results page, click Close.

For more information on Basic Authentication, refer to the following link:

http://technet.microsoft.com/en-us/library/cc772009%28WS.10%29.aspx

This document describes how to deploy an image to multiple computers using multicast.

LANDESK Provisioning can take advantage of a feature called "self-organizing multicast".  Please review this presentation to learn more about this feature.

The following are the steps that you need to take to ensure that multicast is being used so that you can efficiently deploy images to multiple devices while saving both bandwidth and time.

Create a template

1. Open the OS Provisioning tool from within the Provisioning tool group.
2. Either go to "My templates" and then "All my templates" to create a template only you are going to be using or go to "Public" and then "All public templates" to create a template others can use.
3. After highlighting one of those groups click on the "New Template" drop-down above the "Provisioning templates" tree.
4. Select "Deploy Template"
   
5. Give your template a name.
6. Select the type of image you will be using. 
   
   Choices are:
   
   
   • LANDESK ImageW V2
   • Symantec
   • ImageX
   • Other  (Note: When using other you must have a tool that supports command line options.  When selecting "Other" you will need to provide those command line options for LANDESK Provisioning to process.
     
     
7. Enter the full path and filename for your image or browse to and select it.
8. Select an Agent Configuration name if you want a specific LANDESK Agent Configuration to be installed after deploying the image.
9. Check the box for Hardware Independent Imaging if you have that setup and want to deploy an image to differing hardware.  For further information about Hardware Independent Imaging, start here.
10. If you have sysprepped your image in order for it to be an unattended install select the drop-down under "Script Name" and select an unattend file and click "Create"

You will then see your newly created image in the right-hand pane of the Operating System Provisioning tool.

Ensure that your default Distribution and Patch setting has the Multicast option selected

1. Within the "Configuration" tool group select the "Agent Settings" tool.
2. Go to "All Agent Settings" and look at the properties for the default Distribution and Patch setting.   This is the setting that will have the green checkbox next to it.
   

   The other option is to make a setting your default setting by going to the Properties of the setting and in the lower left select "Set as default"

3. Under the "Network Settings" section in the right-hand pane check the box next to "Use Multicast and then click "Save".
   
   

Distribute the Deploy Image template to client computers

1. Back in the "OS Provisioning" tool within the "Provisioning" tool group right-click the newly created template and select "Schedule Template"
   This will cause the Scheduled Tasks tool to open with the newly created template highlighted.
2. Drag the desired computers to the newly created task.  These computers will need to have been turned on and will need to have attempted to network boot so that their mac addresses have been sent to the core server.
   If this has happened the MAC addresses should show up in the list of computers.
3. Right-click the task and select "Properties".
4. Go to the "Schedule Task" section and choose when you would like to start the task and then click "Save".

Issue

How to installed software using "Run from source (execute on share)".

Resolution

1. Open the Agent Settings Tool under the Configuration or Security and Compliance tool groups.
2. Select Distribution and Patch Settings under the section you want to modify (Either My Agent Settings, Public Agent Settings or All Agent Settings.
3. Under Distribution-only settings select Download Options.
4. Select the "Run From Source" download option.
5. If including the Distribute Software action in an "end to end" Provisioning Template (Installing the OS, followed by the agent, etc) you will need to assign the configured Distribution and Patch Setting to the Agent Configuration you are including in your template.

Issue

When running a provisioning template, the template fails on the Deploy Image action.

This occurs in Windows PE when running imagew.exe.

The error is "68".

The full error is "-2147477501".

Error as seen in Windows PE:

The ldprovision.log file on the client (X:\ldprovision\ldprovision.log in WinPE) will show this error:

2008-02-15 21:32:19(692-696) ldProvision:Launching action handler http://DeployImageHandler.exe with parameters

2008-02-15 21:32:26(1500-1988) DeployImageHandler.exe:execute failed with 68

The following error is seen in the Provisioning History in the LDMS console when viewing the history for the device:

Cause

The disk driver has not been fully loaded and/or the hard drive is still locked when the imaging command is run.

Resolution

• Add a Wait action before the Deploy Image action.
• Start with 30 seconds.
• If that is not enough to fix the problem, gradually increase the wait time until the issue is resolved.

Issue

Ivanti Antivirus or Policy Invoker Service is not installing with the agent during the sysprep process on OS deployment

Cause

The network drive to the LDLogon folder is being deleted before the Agent installation completes.

Resolution

1. The file that needs to be edited is a XML file, so execution may vary depending on how your computer is configured to handle viewing XML files. The instructions are written as if you need to manually find the file and open it with notepad.
2. Browse to <coreserver>\LDmain\LANDESK\files
3. Locate the .XML file with the name of your OSD deployment script.
4. Open the .XML with notepad.
5. Locate the and change the following as shown.

<SynchronousCommand>  <CommandLine>net use \\core90v2\ldlogon /d /y</CommandLine>  <Description />  <Order>6</Order>  </SynchronousCommand>
- <SynchronousCommand>  <CommandLine>cmd /q /c del /q c:\ldiscan.cfg</CommandLine>  <Description />  <Order>76</Order>  </SynchronousCommand>

Issue

The following error occurs when attempting PXE boot:

PXE-E74 bad or missing PXE menu and or prompt information

           

This issue can be caused by a variety of different problems.  The following describes these different scenarios, causes, and resolutions.

For more information on PXE boot errors please see:

PXE Boot errors and descriptions.

For more information on troubleshooting PXE boot please see:

Troubleshooting PXE boot (OSD)