Symptom

When attempting to UEFI PXE boot ThinkPad notebook systems that have Intel Kabylake chipsets, the PXE process will fail and potentially return PXE-E16 errors.

This document has since been deleted/removed (Reference Lenovo's Document ID: HT503674 - https://support.lenovo.com/us/en/solutions/ht503674 System Is Configured With: UEFI PXE booting Kabylake Chipsets)

You can reference this forum post (PXE Boot error code E16 No Offers Received - Lenovo Community )

This issue has been resolved by Lenovo by updating to the latest BIOS version for these devices. If you run into this the first step would be to confirm you are on the latest BIOS version.

Affected Systems

• T470
• T470s
• L470
• T470p
• T570
• P51s
• X270
• X1 Carbon
• X1 Carbon Yoga
• Yoga 370
• P51
• P71
• L570

PXE boot fails at getting the BOOT.SDI file.

LANDESK PXE and LANDESK PXE MTFTP services will not stay running on the PXE representative.

CauseThe TFTP block size for the subnet is too big.

Solution

1. Open the Self-electing subnet services tool in the LANDESK Console.

2. Click on PXE service on the left side.

3. Right-click the subnet for the PXE representative and select the Service settings option.

4. In the PXE Settings window, change the TFTP block size to 1456 for ia32 and x64 then save it.

5. Reinstall the LANDESK Agent on the PXE representative.

6. If this resolves the issue, you can try higher settings for the block size to see what works on the subnet. The higher the block size the faster the client will download files from the PXE representative.

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 computer's 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 shut down.

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 computer's 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 log in 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 shut down when the template is done. Refer to the screenshots in the previous section to see various stages of the provisioning process.

• Description
  • Core Logs
  • Client Logs
  • Steps to disable removal of the client provisioning folder
  • Understanding Action Handler Flow (Client)
  • Action Handler Logs
    • Related Video: How to Troubleshoot Provisioning Template Actions

Description

This document is intended to explain provisioning action handlers so that failures seen in individual actions within a provisioning template can quickly be found and corrected.

Core Logs

Logs on the core will help with why a task is not starting, but do not provide a lot of detail about why a certain action failed.

The following are the core logs:

• %LDMS_HOME%\log\prov_schedule.exe.log
• %LDMS_HOME%\log\provisioning\provisioning.log

Client Logs

Device logs can be found in the following locations on the client:

• x:\ldprovision
• systemdrive:\windows\temp

Steps to disable removal of the client provisioning folder

1. Right-click desired provisioning template and go to "Properties".

2. In the left-hand pane, select "Options" and uncheck the box next to "Remove Client Provisioning folder".

Understanding Action Handler Flow (Client)

Each action that is run in a provisioning template is done by an action handler. An action handler may launch multiple other action handlers as part of its task. These other tasks could be considered to be child actions. The deploy image action in 9.5 and higher is an example of this. The Deploy Image action hander may automatically download the appropriate tool for imaging using a Download Action handler. The Deploy Image action then maps a drive to the network location where the image file is using the Map to Preferred Server action handler. Finally it will complete its own job of deploying the image using itself. The launch of each of the additional action handler used by deploy image will be logged in the DeployImageHandler.log along with the result code from the additional handler.

This sample DeployImageHandler.log shows the launch of two additional action handlers (DownloadHandler.exe and maptopreferredhandler.exe) as well as the exit codes for those handlers.

ExecuteCmd DownloadHandler.exe /source="http://mycore/ldlogon/provisioning/windows/imagew.exe" /dest="x:\ldprovision\imagew.exe"

created process, file handle 60 with non-readonly parameter

Process Exit Code: 0

Verifying file was successfully downloaded.

The file (x:\ldprovision\imagew.exe) was successfully downloaded

Getting free drive letter

Free drive letter: f

ExecuteCmd maptopreferredhandler.exe /path="\\mycore\images\win7.tbi" /driveletter=f /pathisfile

created process, file handle 68 with non-readonly parameter

Process Exit Code: 0

 

If a failure occurred in either of the additional actions (DownloadHandler and maptopreferredhandler) launched by deployimage the errors would be shown in the DeployImageHandler.log with a corresponding exit code. Zero indicates the task succeeded. If a failure occurred the DeployImageHandler.log may not contain enough detail to determine the root cause of the failure. Instead the log from the additional action handler (DownloadHandler.log or maptopreferredhandler.log) should be reviewed. The additional action handler may even launch its own child handlers before returning so those logs may also need to be reviewed.

If the failure seen in the DeployImageHandler.log was an error mapping the drive to the image, the MaptoPreferredHandler.log would provide additional details about the failure. Sometimes the error will be spelled out. Other times only an error code will be shown. The error codes shown will often correspond to the windows error codes listed at http://msdn.microsoft.com/en-us/library/windows/desktop/ms681381(v=vs.85).aspx. This allows a simple lookup to get additional information about the failure. Viewing the primary action handler log and following the failure through to the action handler log where the failure actually occurred will save time and frustration while troubleshooting provisioning templates.

Action Handler Logs

Related Video: How to Troubleshoot Provisioning Template Actions

Error Message

DrvLoad: Unable to load X:\InstalledDrivers\...\e1d6432.inf (Error 0x80070002)

Issue

When WinPE is attempting to load a driver, it fails.

Cause

When going through an OSD or Provisioning task, WinPE uses drvload.exe to access drivers. If drvload.exe is unable to load a driver successfully for use, different actions can fail, including making network connections which are required for performing OSD and Provisioning tasks.

Resolution / Workaround

• Load the drivers' .inf file onto a thumb drive and attach to the machine that is booting into WinPE.
• Identify the thumb drives assigned drive letter
  • Open a New Console

• Type diskpart then press Enter.

• Type list volume then press Enter. This will display assigned drive letter.

• Identify the drive letter for the thumb drive.
• Type exit and press Enter.

• Next try mounting the driver from the thumb drive using the command: X:\Windows\System32\drvload.exe [usbDriveLetter]:\[path_to_driver]\[driver_name].inf

Example:The driver in this example is located in the root of C:\

X:\Windows\System32\drvload.exe C:\e1c6432.inf

• If the driver is compatible, the console will display: DrvLoad: Successfully loaded [usbDriveLetter]:\[path_to_driver]\[driver_name].inf

Example:

DrvLoad: Successfully loaded C:\e1c6432.inf

• If the driver is not compatible, the console will display an error.

Example:

DrvLoad: Unable to load c:\BadDriver.inf (Error 0xe0000100)

• If manually attempting to use drvload.exe to load a driver fails, this must be corrected before OSD or Provisioning tasks can work.

Initializing the network stack after installing NIC drivers

• After loading a NIC driver successfully, you will need to initialize the network stack.

netcfg -WinPE

• Run IPconfig after this completes verifying an IP address has been acquired.

Possible causes of a failure

• The test may have selected the wrong file.
• Dependent files may be missing that are needed as a reference by the *.inf file.
  • .dll, .cab, and .sys files may be dependencies for the driver. Try adding them if available.
• The driver file added may be corrupted. Try re-downloading and testing.
• The driver selected may be incorrect. Try a different driver.
  • Windows Blue drivers have been seen to work in some circumstances where Windows 8.1 x86 drivers did not.

has anyone else had the issue when performing provisioning tasks even though the task box is unchecked where it says to stop if task fails, the task fails and the provisioning stops. I then have to relaunch the ldprovision.exe to get it to continue. sometimes the tasks just stop responding and I have to reboot and relaunch ldprovision to get it to finish. This has been an ongoing problem since 2017.1. No one seems to really have an answer. It seems as if the connection from the task to the computer just stops. It is random. It is not always the same task. Surely this is working as designed?

So despite having touched nothing on our server, out WinPE environment no longer loads drivers.  The interface says "Driver Folder List is empty"

Now when I go into the Management Console and go to "Manage drivers in Windows PE image" it opens the image just find and lists all the drivers.  So suspecting something got messed up, I backed up the image and replaced the active boot.wim with the backup "clean" boot.wim file we saved back when we rebuilt our boot.wim file.  When using that, it doesn't even attempt to load drivers.  It just runs WinPE init, and then sits at the command line interface doing nothing.  Of course, since there are no keyboard drivers, we can't type anything.  This is extremely frustrating as WinPE seems to break on it's own every 6 months.

Anyone have any ideas?

Hi Ivanticommunity,

may be someone else out there had the same issue than me and knows how to solve it. I`m deploying Win10 upgrade from Win7 to clients via UEM. That normally works fine, but now there`s a client which don`t wants to upgrade. The Job starts and the download of the ISO file works fine, but when the Installation starts there`s Always this errorcode:.

this is a part of the log for that Job in Ivanti UEM:

Tue, 07 Aug 2018 09:49:12 Processing generic executable
Tue, 07 Aug 2018 10:00:31 Launched application 'C:\Program Files (x86)\LANDesk\LDClient\sdmcache\Softwareverteilung\Microsoft\Win10upgr\deWin10ProX64\setup.exe'('/auto upgrade /noreboot /quiet') result -1047526944
Tue, 07 Aug 2018 10:00:31 Installation result 8DB501E0
Tue, 07 Aug 2018 10:00:31 RunPackageInstall: stop on returncode=8db501e0 of package=W10Ver1803upgr
Tue, 07 Aug 2018 10:00:31 processing of package is complete, result -1917517344 (0x8db501e0 - code 480)

The Problem is I can`t find anything about errorcode 8db501e0, what does it mean?

Mit freundlichem Gruß
i.A. Florian Schriefer

Hello,

I'm using LDMS 207.3.2 and I want to use OS Provisioning.

I have a problem with Self-Electing Subnet Services. The PXE Representative elected is not a device that always

works : its state is often "deactivated" and I can't change it on my own.

I would like to have a single PXE Rep on my subnet (for instance, a computer I have chosen before, with PXE service  activated in client connectivity). How can I do that ?

Thanks for help.

Hello everyone!

I am relativ new on Invanti UEM am I am trying to provision a client for some tests.

I have done that already successfully on our Testserver, but it fails permanently on our live system.

Everytime I boot up into WinPE, I log in with my admin account and select my public template (which is an exact copy from the test core server).

But as soon as WinPE starts to look for the template, I can see the taskhandlerproxy.exe crashing on the core server. This is reproduceable,

Faulting application name: TaskHandlerProxy.exe, version: 11.0.0.1089, time stamp: 0x5ad8bd8f

Faulting module name: KERNELBASE.dll, version: 10.0.14393.2189, time stamp: 0x5abdad60

Exception code: 0xc06d007e

Fault offset: 0x0000000000033c58

Faulting process id: 0x181c

Faulting application start time: 0x01d4436bf8a73920

Faulting application path: D:\LANDesk\ManagementSuite\TaskHandlerProxy.exe

Faulting module path: C:\Windows\System32\KERNELBASE.dll

Report Id: 215c3d69-f688-48ba-84aa-acbef03c8712

Faulting package full name:

Faulting package-relative application ID:

I have already followed procedures from here: Issue: Provisioning task failing after try 40 of 40

But nothing helps. The posted workaround does also say, that there would be a taskhandlerproxy.exe.log file. But that logfile isn't even being generated on

my live system.

I have check differences in setup on both cores but haven't find any, except for OS, which is 2012 R2 on the test core and 2016 on live core.

Anyone got an idea what else I could check or do?

Thanks,

Ray

I have a problem with HII on the Dell Optiplex 5050.

With four out of ten identical computers, the HII ran smoothly.

Then in provsisioning no USB driver was installed.

(After aborting, the existing driver on the core could be easily installed)

Also the driver assignment in the HII-drivermanagement brought no improvement

Annotation:

Im using Ivanti 2017.3 SU3 (SU5) and i have to use USB-boot - for a variety of reasons

There are ten identical computers, no changes were made to the template or the driver location or otherwise, the drivers are the same from the beginning. 

Troubleshooting:

The log files from the HII and Provisioning show that all required drivers were successfully copied to C:\Windows\LDDriverStore\DELL_Optiplex_5050\chipssatz\...

BUT the driver was missing.

Workaround: 

Before the step HII in the provisionig template, I now manually copy the USB driver to C:\Windows\LDDriverStore\chipset\...

It is no longer HII, but I can finish the provisioning    

Does anyone have an idea what this may be?

and how to fix it?

Description

When PXE Booting you receive an error before booting into WinPE.

- TFTP Boot Issues

- PXE-032 Error

- NBD failing to load (freezes)

Cause

Starting in Windows 10 1709 build windows firewall has been updated to Windows Defender Firewall.

If you have your firewall enabled and you used to be able to PXE Boot it was because the PXE Services was set as an exception.

Solution

Windows 10 1709 requires that you specify the open ports for PXE into the Inbound Rules if you have your Windows Firewall enabled.

Ports used by LANDESK Management Suite - Full List

Open Windows Defender Firewall.

1. Test disabling it to see if this resolves your issue with PXE Booting. If it does then continue to add the Specific Ports into the Firewall Inbound Rules.

2. Windows Defender Firewall	Inbound / Outbound Rules

   
   
   
3. You can use the following document to reference Ports that LANDesk uses - Ports used by LANDESK Management Suite - Full List
   
   

4. General Tab	Advanced Settings	UDP Ports 67, 68, 69, 1758, 1759 and 4011

I have two devices that work with our 2016 core but one does not work with the new 2017 core. With the computer shown to the right, it states that  X:\ldprovision\ldprovision_x64.exe is not compatible with the Windows you're running.

Any thoughts?

Issue

Chinese character can't show on the UI of provisioning in WinPE.

This is most easily done with the Deployment Image Servicing and Management tool, commonly known as DISM.

DISM is also the utility LANDESK Hardware Independent Imaging employs to install drivers during the HII step of Provisioning Templates and OSD Scripts

Here is the screenshot:

Resolution

1. Download the attachment , Extract the attachment to D drive
2. Extract all the files to D:\OSD folder, if this folder not exist, please create D:\OSD
3. if the client machine is booting with BIOS, Copy  \Program Files(x86)\LANDESK\ManagementSuite\landesk\vboot\boot.wim to D:\OSD folder
4. Download Windows ADK packages from here:
   http://download.microsoft.com/download/8/1/9/8197FEB9-FABE-48FD-A537-7D8709586715/adk/adksetup.exe
5. Install Windows ADK on windows 10 (Do not install ADK on windows 2012, it will fail, this is verified)
   
6. Copy below two files to D:\OSD folder
   
   C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\WinPE-FontSupport-ZH-CN.cab
   C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\lp.cab
7. Right click on CMD as administrator, run echo.bat
8. Copy the newly updated Boot.wim file from the mount folder to the \Program Files(x86)\LANDESK\ManagementSuite\landesk\vboot\ folder
9. Redeploy your PXE Rep.
10. PXE Boot your client and verify all the "??????" is showing Chinese character correctly now.

PS: If the client machine is booting with UEFI, please repeat above steps from step 6 to 9, and replace boot.wim with boot_x64.wim, copy below two files to D:\OSD folder

C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-FontSupport-ZH-CN.cab

C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\lp.cab

About Windows PE versions used in Ivanti Endpoint Manager

You could  check your core server version, and find the corresponding winPE version from this article, then download corresponding ADK from Download and install the Windows ADK | Microsoft Docs . Different versions of ADK file has to be installed on corresponding level of windows OS.

Description

Experiencing issues when running SysPrep that it takes a long time or when Windows 10 loads for the first time it takes a 20-60 minutes to come up to the login screen.

Cause

You may see an error similar to this one in your SetupACT.log

[msoobe.exe] TASK: End failed running task ProvisionPackageCreate with hr=0x800705B4.

Solution

This is being caused by the "WAP Push Message Routing Service (dmwappushservice)".

To resolve this issue you need to set the service to its default startup type of Automatic (Delayed Start). Follow these steps:

1.  On the reference computer, open an administrative command prompt

2.  Type the following command to set the startup type:

                sc config dmwappushservice start= delayed-auto

3.  Type the following command to start the service:

                sc start dmwappushservice

4.  Once this has been done, you will need to recapture your image and deploy using the updated image.

Additional Information

• You can locate your SetupACT.log in the following directories.

     "C:\Windows\Panther" and "C:\Windows\Panther\UnattendGC"

• Microsoft TechNet Forum Post
• The "WAP Push Message Routing Service (dmwappushservice)" service is used for Windows Mobile / Phone management.

Scenario:

In some environments, computer name should remain the same after the reimaging of the device. This article shows how to configure Provisioning template to achieve it and use one template for existing and brand new devices.

Configuration steps:

1. Create a new template or modify existing one
2. Add "IF" condition to Pre-OS Installation stage of Provisioning job
3. Add "Compare Variable" to "IF" condition
4. Set Variable to ldDeviceID and its value to Unassigned

5. Add "Device Name Prompter" action
6. Choose "Name Template" or "LDHostName Variable"

7. Add "ELSE" condition to Pre-OS Installation stage of Provisioning job
8. Add "Device Name Prompter" action
9. Choose "LDHostName Variable"

How to use Conditionals in LANDESK 2016 Provisioning: https://community.ivanti.com/docs/DOC-40464

LDMS 2016 v. 10.0.1.78

Scenario:

Windows XP machine in remote site with agent installed. I have a working OS provisioning template to push W10 image. I've added vboot as a reboot/shutdown task as I have done many times before.

I can watch the job kick off, creates ldprovisioning folder and quickly populates with downloaded files, then it starts downloading boot.wim to C:\

I can watch the file being downloaded and increasing in size - shortly before the d/l finishes, the job fails. "Preparing for virtual boot failed, the action failed" - so based on that it would appear to be timing out before the d/l finishes from the core.

It appears the process is timing out and I just can't figure out a way to increase the timeout or some workaround for this issue.

Here is the log.

2018-09-07 13:49:23(3772-448) ldProvision.exe:Create process (C:\Program Files\LANDesk\Shared Files\httpclient.exe) with args (  -f "c:\boot.wim" http://*server*/landesk/vboot/boot.wim)

2018-09-07 13:59:23(3772-448) ldProvision.exe:Waiting for process result: 258.

2018-09-07 13:59:23(3772-448) ldProvision.exe:Waiting for process timed out. Waited 600000 seconds

2018-09-07 13:59:23(3772-448) ldProvision.exe:Process exit code:259

2018-09-07 13:59:23(3772-448) ldProvision.exe:Entering downloadbyproxy.

2018-09-07 13:59:23(3772-448) ldProvision.exe:Create process (C:\Program Files\LANDesk\Shared Files\httpclient.exe) with args (  -f "c:\boot.wim" http://*server*/landesk/vboot/boot.wim)

2018-09-07 13:59:24(3772-448) ldProvision.exe:Waiting for process result: 0.

2018-09-07 13:59:24(3772-448) ldProvision.exe:Process exit code:1

2018-09-07 13:59:24(3772-448) ldProvision.exe:Entering downloadbyproxy.

2018-09-07 13:59:24(3772-448) ldProvision.exe:Create process (C:\Program Files\LANDesk\Shared Files\httpclient.exe) with args (  -f "c:\boot.wim" http://*server*/landesk/vboot/boot.wim)

2018-09-07 13:59:24(3772-448) ldProvision.exe:Waiting for process result: 0.

2018-09-07 13:59:24(3772-448) ldProvision.exe:Process exit code:1

2018-09-07 13:59:24(3772-448) ldProvision.exe:Entering downloadbyproxy.

2018-09-07 13:59:24(3772-448) ldProvision.exe:Create process (C:\Program Files\LANDesk\Shared Files\httpclient.exe) with args (  -f "c:\boot.wim" http://*server*/landesk/vboot/boot.wim)

2018-09-07 13:59:24(3772-448) ldProvision.exe:Waiting for process result: 0.

2018-09-07 13:59:24(3772-448) ldProvision.exe:Process exit code:1

2018-09-07 13:59:24(3772-448) ldProvision.exe:Entering downloadbyproxy.

2018-09-07 13:59:24(3772-448) ldProvision.exe:Create process (C:\Program Files\LANDesk\Shared Files\httpclient.exe) with args (  -f "c:\boot.wim" http:/*server*/landesk/vboot/boot.wim)

2018-09-07 13:59:25(3772-448) ldProvision.exe:Waiting for process result: 0.

2018-09-07 13:59:25(3772-448) ldProvision.exe:Process exit code:1

2018-09-07 13:59:25(3772-448) ldProvision.exe:Downloading the file (c:\boot.wim) failed!

2018-09-07 13:59:25(3772-448) ldProvision.exe:Preparing for virtual boot failed.

2018-09-07 13:59:25(3772-448) ldProvision.exe:Caught exception in main: code=80001803H, file=ldProvision.cpp, line=2095

2018-09-07 13:59:25(3772-448) ldProvision.exe:Call web service GetStatusString()

2018-09-07 13:59:25(3772-448) ldProvision.exe:Start TryallWebService Attempt:0.

2018-09-07 13:59:25(3772-448) ldProvision.exe:Calling Program:C:\Program Files\LANDesk\Shared Files\httpclient.exe  -b ncs -H"c:\ldprovisioning\header.txt" -o"c:\ldprovisioning\body.txt" -f"c:\ldprovisioning\result.xml" https://*server*/LANDesk/ManagementSuite/Core/ProvisioningWebService/WebService.asmx

2018-09-07 13:59:25(3772-448) ldProvision.exe:End TryallWebService Attempt:0. ExitCode:0

2018-09-07 13:59:25(3772-448) ldProvision.exe:StatusString = The action failed.

2018-09-07 13:59:26(3772-448) ldProvision.exe:Call web service SetActionStatus()

2018-09-07 13:59:26(3772-448) ldProvision.exe:Start TryallWebService Attempt:0.

2018-09-07 13:59:26(3772-448) ldProvision.exe:Calling Program:C:\Program Files\LANDesk\Shared Files\httpclient.exe  -b ncs -H"c:\ldprovisioning\header.txt" -o"c:\ldprovisioning\body.txt" -f"c:\ldprovisioning\result.xml" https://*server*/LANDesk/ManagementSuite/Core/ProvisioningWebService/WebService.asmx

2018-09-07 13:59:26(3772-448) ldProvision.exe:End TryallWebService Attempt:0. ExitCode:0

<br class="Apple-interchange-newline"><div></div>

I can replace out boot wim with the clean one, but I cannot locate an exe called osd.upgrade.exe, like the instructions say to do. I've searched the whole core server, but I cannot find it. Can I just replace the wims and be good to go?

Bonjour,

Je souhaite provisionner des PC portables depuis un modèle déconnecté sur une clé USB.

Lorsque je lance l'opération de création de la clé j'obtiens un échec avec cette erreur dans le log :

J'ai fait l'essai avec 3 clés USB de 4 Go, 8 Go et 16 Go ainsi qu'un disque dur externe de 500 Go.

J'obtiens toujours le même log.

Merci pour votre aide.

Hello,

So, we have a OS provisioning job for windows 10 but the job doesn't seem to pass the LDhostname that is entered during the imaging process.  The machines come online with names like "Desktop-298UNOC42398734", which is bad because that is what gets added to the Domain.

Now, the unattended file has an entry for %LDHostname% but it apparently doesn't actually do anything.

Any pointers would be greatly appreciated.

Thanks,