We have started ordering Dell Precision T7820's.  We downloaded the driver cab for it and put the drivers in the driver store, rebuilt the driver database, and did an auto-detect and assign drivers for the T7820's.  All good so far.  Then we went to image the first machine (Windows 10, 64 bit), and once it begins to load windows, it blue screens.  The problem is with amdkmpfd.sys (system thread exception not handled).  OK, so we go into assign driver, find where that driver is assigned (in this case, PCI Exrpess Root Complex), and remove that one driver.  Then we try imaging again, and windows still blue screens on that same driver.  I am at a loss as to how it is blue screening on a driver that isn't even being used at this point.  Am I missing something with removing the driver?  How do I get Endpoint Manager to stop loading this bad driver into the image?  Should I remove the driver entirely from the driver store?  I am just worried that may cause issue with other PC models.

We are on ivanti Management Console version 11.0.0.164

Thanks

Purpose

This article will walk through resolving the issue of the first action after CTOS failing (usually installing the agent) when deploying Windows 10 (Build 1703).

Problem

Provisioning fails at first action in system configuration area of template when deploying a Windows 10 (Build 1703) image.

Cause

This appears to be an issue specific to Windows 10 Creator's Edition and may be a bug with that build. It is not affecting any Windows version other than build 1703.

A link to a discussion on a Microsoft website for more information is below:

Windows 10 v1703 - Provisioning Package - Microsoft Partners Forum

Solution

There are currently two working solutions:

1.) Include "<SkipMachineOOBE>true</SkipMachineOOBE> <SkipUserOOBE>true</SkipUserOOBE>" in the oobeSystem part of the unattend file being used (this is included by default in the LD_Default_Unattend.xml).

2.) Add a reboot with 100 second delay as first action in system configuration area

• 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:

I have been searching for a way to turn on network discovery for all profiles during provisioning but I have yet to find a way,  information I can find is either old or has spotty results.  I have tried various methods in unattend.xml they are not working, and usually making things worse by keeping the agent from running after CTOS.  Does anyone know if there is a way to turn on file and print sharing during provisioning so that the OSD doesn't pop up asking for network visibility?  We have found that if someone isn't there to answer that, then file and print sharing remains off and provisioning fails. 

Hello everyone,

I've got a problem here with OS deployment. As we updated to version 2017-3 this year I decided to clean up our OS templates a little bit. Before the update, we had a single template for desktops and for notebooks with nearly the same settings

except one or two exceptions.

Now I've build a Windows 10 template with an if-else configuration. I created a variable that looks if the device got a battery or not. It works fine without any problem.

Sadly it doesn't seem to work with a Windows 7 template. The settings are, in most parts, equal to the Windows 10 template and it has the same if-else configuration.

The deployment stops at "Configure Target OS". The Task runs into the error 1163.

It think there is a problem with the if-else configuration, but it has the same settings like the Windows 10 one.

I hope you've got a quick solution for that. Thank you so far.

Problem

On the self-elected PXE Representative chosen in 2016.3+, the "Landesk PXE MTFTP Service" is either not started or is long to start but the "Landesk PXE service" is running. You can also see on the LDMS Console, that the PXE service on this subnet is enabled.

Cause

Here are some information which might help you to understand what's going on:

1. A PXE rep cannot have a WIFI adapter and cannot have multiple NICs. If they do, they will not be elected.
2. If the LANDESK PXE service is started and the LANDESK PXE MTFTP service is not started, the BOOT.WIM and BOOT_x64.WIM files have not been downloaded to the PXE rep or are being downloaded. The MTFTP service will not start until both WIM files have been downloaded to the PXE rep. The WIM files are downloaded to the C:\Program Files (x86)\LANDESK\PXE\System\Images\Boot folder on the PXE rep.
3. Check the following log files on the PXE rep in the C:\ProgramData\LANDESK\\Log folder to see what it is doing:

• pxesvc.log
• tmcsvc.log
• selfelectcontroller.log

Solution / Workaround

You need to wait until the WIM files are entirely downloaded onto the self-elected representative.

The WIM files might not be downloaded for some reasons, and the IIS logs might inform you either.

I created an OS Provisioning template to deploy Win10 1709 to UEFI systems.  I used a VM to create the master image.  First, with almost no applications, I captured a .wim file to make a thin image.  Then I rolled back to a snapshot before I sysprepped the VM, added MS Office, etc., and then captured a .wim file to make a thick image.  I configure the template to deploy the thin image, and it works just fine.  I copy the template and change it to apply the thick image instead of the thin image, leaving everything else alone.  This second template succeeds in partitioning the hard drive, downloading the thick image, and applying it to the local hard drive.  It appears to successfully use HII to download and apply drivers, and complete the configuration.  After it reboots, it tries to install the Landesk (2016.3) agent (same agent as works with the thin image), and fails.  So I modified the thick template and moved the Join Domain step above the Install Landesk Agent step.  And it failed on the Join Domain step!

Is it possible that there's something not right with this thick image?  If so, what?  Where should I start looking to figure out why this template works fine with one .wim file, but not with the other?

Thanks.

Issue

The computer name does not match what was entered in the Device Name Prompter during Provisioning.

Cause

This is commonly caused by:

• A different unattend file being processed by windows
• The name from the prompter not being placed into the Unattend file

Steps

When using the Device Name Prompter, make sure it is positioned BEFORE the Inject Script action.

The Device Name Prompter will append the injected script, and update <ComputerName>%ldHostname%</ComputerName>  to reflect what is entered in the prompter.

Note: This means the unattend being used

must use the %ldHostname% variable in the ComputerName field.

Example: If you enter "Workstation7" in the Device Name Prompter, it will attempt to change modify the script from <ComputerName>%ldHostname%</ComputerName>  to <ComputerName>Workstation7</ComputerName>

After verifying that the actions are in the right order, add a wait action after the inject script action, and use the 'wait' time to open the script as it was injected at c:\windows\panther\unattend.xml.

Verify that the name that was put in the prompter appears in the xml here:<ComputerName>VALUE_FROM_PROMPTER</ComputerName>

Once the name has been verified as correct in the xml that was injected to the Panther folder, allow the machine to process through the CTOS action and reboot into windows.

Once in windows, check if the name matches the prompter.

If no, check this log: "C:\Windows\Panther\UnattendGC\setupact.log"

In this log it will tell you what unattend.xml file it uses:

2015-06-02 14:53:24, Info [windeploy.exe] Found unattend file: [C:\Windows\Panther\unattend.xml]

It will also tell you about windows reading the unattend to name the computer:

2015-12-18 07:45:29, Info [Shell Unattend] ComputerName set to VALUE_FROM_PROMPTER

If more than one unattend is found on the computer, Windows may be selecting an unintended file to process. If this is found to be the case, it is recommended to:

• Delete the extra unattend files and recapture the image.

or

• Add logic in the provisioning template to delete the extra templates
  • This method is less desirable as it may result in other unattends still being missed, which could cause the issue to recur but on another unattend that windows finds on the hard drive.

How To:

In this scenario, we have several NEW machines including different models to be provisioned and we need to deploy a different image according to the model. This scenario will show us how to collect the model of the computer in the registry within WinPE environment which will be reported back to the Core Server in the temporary inventory of this machine.

We will then use this value in the inventory to create some conditions in the provisioning template to deploy 1 image or another based on this value.

Step by Step:

     Step 1: Create a batch file with the following code

FOR /F "tokens=3*" %%a IN ('reg query "HKLM\HARDWARE\DESCRIPTION\SYstem\BIOS"  /V SystemProductName  2^>nul') do miniscan.exe /send="Custom Data - Model = %%a %%b"

     NOTE: This code is designed to collect the device model name from a registry key, and then use miniscan.exe available in WinPE to report a custom data back to the Core Server to be available on the inventory of the device being provisioned.

     Step 2: Save this batch file onto a share folder

     NOTE: I called it "\\<CORESERVER>\TEST_SOFTWARE\SystemProductName.bat"

     Step 3: Go on your provisioning template and go in "OS Installation section"

          a. Add a first action "Download Preferred Server" to download the batch file created in Step 1 into WinPE.

               NOTE: Do not forget to specify the Read credentials for the corresponding Preferred server (In my example, I defined a preferred server called "10.1.1.210")

          b. Add a second action "Execute File" to execute the batch file

          c. Now the value appears in the inventory of the new device:

          d. We can use an "if conditional" action to deploy one or another image depending on this inventory data:

          NOTE: see How to use Conditionals in LANDESK 2016 Provisioning to know how to use the conditionals (In this article, it actually explains how to deploy an image based on an inventory value, but for a computer which was already existing on the Core Server, hence the inventory data were already there).

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.

Description

This document is intended to help you determine why and fix the provisioning template not continuing after the CTOS action.

Issue 1

The image is not sysprepped. Check the CONFIGTARGETOSHANDLER.LOG file on the computer in the X:\LDPROVISION folder while the computer is still in WINPE. If the computer has already booted to the OS then the log file will be in the C:\Windows\Temp folder. The following error will be in the log file:

Not able to determine sysprep drive

Solution 1

MDT does not sysprep the OS completely to work with LANDESK.

Following Community article shows how to sysprep and capture the image for use with Management Suite:

How to capture an image using IMAGEW.EXE with provisioning in Management Suite 9.6

This document works for all version of Management Suite up to 2016.x and works for Windows 7, 8, 8.1 and 10.

Issue 2

The image is not sysprepped in mode supported by LANDESK.

Solution 2

Sysprep the image in Audit mode without the Generalize box checked or sysprep the image in OOBE mode with the Geeneralize box checked then recapture the image.

Issue 3

The image being deployed is an OEM version.

Solution 3

The following Community article shows what to look for and how to fix it:

Issue: Provisioning on Windows 8 & 8.1 with an OEM license fails to continue after Configure Target OS action.

Issue 4

The image being deployed has the LANDESK Agent already installed. Check the CONFIGTARGETOSHANDLER.LOG file on the computer in the X:\LDPROVISION folder while the computer is still in WINPE. If the computer has already booted to the OS then the log file will be in the C:\Windows\Temp folder. Beginning of the log file will show if it detected the LANDESK agent.

Solution 4

Remove the LANDESK Agent by running "UNINSTALLWINCLIENT.EXE /forceclean" then recapture the image.

Issue 5

There is a SETUP folder at the second level in a folder of the image being deployed other than C:\Windows\Setup. For example, if there is a C:\Users\Setup folder it will cause the problem.

Solution 5

The following Community article has information on this issue:

Issue: Template is not continuing after the Configure Target OS (CTOS) action

Issue 6

There is already a SETUPCOMPLETE.CMD file in the Windows\Setup\Scripts folder in the image deployed. Check the CONFIGTARGETOSHANDLER.LOG file on the computer in the X:\LDPROVISION folder while the computer is still in WINPE. If the computer has already booted to the OS then the log file will be in the C:\Windows\Temp folder. The log file will have an error about updating the SETUPCOMPLETE.CMD file.

Solution 6

Remove the Windows\Setup\Scripts\SETUPCOMPLETE.CMD file from the image.

Issue:

When Provisioning with a Dell USB-C Network Dongle you are getting Duplicate Device ID's in your Inventory

Cause:

The USB-C Network Dongle is designed to pass through the Internal Device MAC Address, without the correct drivers loaded into WinPE (How to add drivers to WinPE for Ivanti EPM OS Provisioning - How to add drivers to WinPE for Ivanti EPM OS Provisioning ) the device uses its own MAC Address. When loading into WinPE a mini scan runs which creates a basic Inventory entry with the USB-C Network Dongles MAC address. Then later when the device boots into Windows and the pass through begins to work the Agent is installed a second Inventory entries is created since it now has a different MAC Address.

Resolution:

If you load the correct drivers for the USB-C Network Dongle then the pass through functionality will work within WinPE Environment.

Information from Dell - The USB-C Network Dongle is designed to pass through the Device MAC Address, this only occurs if the correct drivers are loaded into the WinPE Environment

Additional Information about WinPE Drivers:

How To Test Drivers Compatibility Within Winpe

How to add drivers to WinPE for Ivanti EPM OS Provisioning

Reviewed 7/23/2015

Problem

You are trying to assign drivers in HII but your device make or model isn't available in the drop down menus:

Cause

Device make, model, OS and architecture, as well as hardware devices are populated in HII through inventory scans.  If your device or an identical device has not ever scanned into the database, it will not show up in HII.

Solution

Install a LANDesk agent on the device in question and run an inventory scan.  This will populate the device details into HII.  Be sure that Data Translation Services (DTS) rules are not normalizing the make and model.  For example, if the make is "Hewlett-Packard" but DTS normalizes this to "HP", it will appear as HP in HII and this will be incorrect.  Disable any such DTS rules while you run the inventory scan, and then enable the rules again once the correct, exact match device is populated into HII.

You can verify the detected make, model, OS and architecture of a device by running HII in Preview mode on the device:

How to use HIICLIENT in preview mode

Here is an example from an actual HIIPreview.log file:

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

Running in WinPE

Device manufacturer discovered as: Hewlett-Packard

Device model discovered as: HP ProDesk 600 G1 SFF

Running preview for OS 6.1 Workstation X86: Windows 7 32-bit

 

Hardware device discovered. Device number 1:

Device name: USB Root Hub (xHCI)

Primary device ID: USB\ROOT_HUB30&VID8086&PID8C31&REV0004

Additional device ID: USB\ROOT_HUB30&VID8086&PID8C31

Additional device ID: USB\ROOT_HUB30

I want users to be able to update drivers and BIOS easily if needed.  Or by request.

My current setup works but doesn't display the GUI when it runs.  Is there a way to elevate the process or redirect the output to the current user?  Or maybe whitelist the thininstaller.exe program to the operating system?

In response to this Community thread, I have created a tool that will modify the ComputerName value in a Sysprep Unattend XML file after being injected during WinPE Provisioning.

The purpose of this tool is to eliminate the need to chose between automatic and manual computer naming when injecting an Unattend XML.

Syntax:

CompName.exe N "C:\Path\To\YourUnattend.xml"

The first command line argument is the number of seconds to wait before the tool exits and makes no modifications to the Unattend XML.

The second argument is the path to the Unattend XML you wish to modify.  You must wrap this string in quotes, even if there are no spaces in the pathname.

Both arguments are mandatory or the tool will default to 300 seconds and "C:\Unattend.xml"

Use:

In a Provisioning template, make a new Action of the type "Execute File" and have it execute CompName.exe.  Supply the number of seconds and the path to the newly injected XML as the command parameters.

Place this action directly after the existing Inject Script action in your template (or any other point after the Inject Script action, but before the system boots to the new image)

** In the ZIP file there is a _Demonstrate.bat that runs the tool against a sample Unattend XML file so you can try it out before putting it into LANDesk.

Warranty:

None

How it works:

1 - In WinPE, a Provisioning action launches the tool and waits a configurable number of seconds before moving on.

2 - Supply a computer name

3 - Script checks the hostname length and illegal characters

4 - Once validated, script displays old name and new name.

Unattend XML before:

Unattend XML after!

Application exit codes:

I look forward to your feedback!

Thanks,

Jesse McCoppin

Hello All,

We are currently using EPM 2017.3.3.

The issue we're having is that we have some users that are unable to Provision and the process fails after 40 of 40 tries while attempting to load the template during PXE/WinPE.

If another user enters their credentials and selects the same template for the same device, it loads properly after 3-5 tries and Provisioning proceeds normally.

The Provisioning.log on the core shows "Unable to find template for computer IDN " repeatedly for the device (the MAC Address in the log matches the MAC Address of the device).

We have configured the accounts exactly the same; they are all in the same Security Group on the Core Server and have all the same Permissions, Roles and Scopes.

We have deleted their profile and it is recreated after they login, however, that does not correct the issue.

We've ensured that prior to each attempt, all previous tasks for the device have been deleted and there is no Device Record in the system matching the name or MAC Address.

The only work around has been to create a Bare Metal Device in advance and then it will proceed and load the template.

Therefore, it appears to be a permissions issue and the credentials for the users that are having the problem aren't able to create the device if they just PXE Boot first.

Can anyone offer any guidance as to what exact permissions are needed?

A comparison of the Effective Rights between the accounts that work and don't work look the same, so we're a bit stumped.

Any info would be appreciated.

Thanks

Jeff

When using provisioning packages for complex software deployments, I am seeing an issue where some of the devices are failing to install any of the software packages that I have included in the template.  After closer inspection, I can see that none of the files for the software packages in the template are being downloaded, so when it tries to execute, it fails immediately.  I found an error in the ldprovisioning.log file -> Failed to download (C:\ldprovisioning\SDClientHandler.sig) <- that appears to be the issue, but I'm not sure how to go about resolving this.  Wondering if anyone else has seen this, or has any ideas how to troubleshoot further?  LDMS 2016.3 SU3

2017-11-07 16:41:00(8660-4724) ldprovision.exe:Looking for existing file (C:\ldprovisioning\SDClientHandler.sig)

2017-11-07 16:41:00(8660-4724) ldprovision.exe:Entering downloadbyproxy.

2017-11-07 16:41:00(8660-4724) ldprovision.exe:Create process (C:\Program Files (x86)\LANDesk\Shared Files\httpclient.exe) with args (  -f "C:\ldprovisioning\SDClientHandler.sig" http://mylandeskserver.com/LdLogon/Provisioning/windows/SDClientHandler.sig)

2017-11-07 16:41:01(8660-4724) ldprovision.exe:Waiting for process result: 0.

2017-11-07 16:41:01(8660-4724) ldprovision.exe:Process exit code:-1

2017-11-07 16:41:01(8660-4724) ldprovision.exe:Failed to download (C:\ldprovisioning\SDClientHandler.sig)

2017-11-07 16:41:01(8660-4724) ldprovision.exe:Informational: No sig file downloaded.

2017-11-07 16:41:01(8660-4724) ldprovision.exe:Done with download handler.

2017-11-07 16:41:01(8660-4724) ldprovision.exe:Launching action handler [SDClientHandler.exe] with parameters ["]

2017-11-07 16:41:04(8660-4724) ldprovision.exe:handler launched.

2017-11-07 16:41:04(8660-4724) ldprovision.exe:End of action - Distribute_software

2017-11-07 16:41:04(8660-4724) ldprovision.exe:Reporting action status: 5 to core.

Hello to the community

Recently we have deployed Ivanti 2017.3 in our company (replacement of old Landesk 9.0).

We make provisionning on it of our Surface Pro Windows 10 since 2 months without problem

Today, impossible to do it, i have a white screnn instead of the screen Ivanti asking my domain account to select the template.

Boot PXE and loading WIM OK:

All seems OK after :

Then, white screen and nothing else (at this step, it should open an ivanti page with step count and a popup asking my domain account to select the template to install) :

Our server has been rebooted this noon, but still the same.

Can someone help me ?

I'm novice with Ivanti, no knowledge of it.

Thanks for help.

Sébastien

HI all,

I am currently on a Landesk trial and experimenting with provisioning and am hving some problems with the 'Join Domain' action.

I have created a few different templates and I have had this working in the past, but for some reason it no longer works.

Instead of joining the domain, the client joins a workgroup with the same name as my domain.

Below is my Join Domain action:

I have checked and double checked the username/password and everything is correct.  I have also tried using variables and it also fails.

Any ideas?