I've got a hefty provisioning template that i initially built to only apply to 32 bit machines but either way the step is to copy a file from A to B. When running on a 32-bit machine this completes and copies the file however when running on a 64-bit machine, the step fails. Why is it failing it's using only a Windows directory to copy the file into?

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

LDMS 9.6 SP3

Hi, I get this error while trying to provision a machine.

Any ideas?

Best.

We have been trying to get a image made with Windows 10 1709 to provision on a computer. It causes a blue screen during Ctos.

We tried 3 different computers.

Recaptured the image twice.

I can get a 1703 image to provision ok.

I'm wondering if its a DISM incompatibility.

I'm wondering if there is any good documentation or other advice that can help us optimize our PXE booting.  In the past we've always used DHCP scope options 60, 66, 67, and 43 to point our clients to the PXE server.  If the PXE representative is also the DHCP server then only option 60 is needed, but if we want PXE to point to a PXE rep that is not the DHCP server we have used options 66, 67, and 43 to point it to the correct server and boot file.  This solution works great if we just stick to 32 bit PXE booting, but doesn't allow any flexibility if we want to use both 64 and 32 bit booting.

I am aware that we can accomplish our goal by using the self-elected subnet service on clients in the same subnet, but this has proven unreliable for us.  We much prefer to use servers as our PXE representatives, which reside on a different subnet than the clients.  Are there any best practices out there to make PXE booting across subnets happen without the use of DHCP scope options?  We've tried putting the IP address of the PXE rep in the IP helper table, but it doesn't help.  We are running version 2017.3.

Overview

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

Capture Windows 10 Image

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

How to Capture a Windows 10 image with IMAGEX

Import the UNATTEND.XML file

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

How to Deploy a Windows 10 Image with ImageX

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 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 DeployWin10ImageX.xtp to a folder on the Core Server. The template is in the ProvImageX.zip file attached to the following Community article:

How to Deploy a Windows 10 Image with ImageX

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 DeployWin10ImageX 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 ImageX 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 .WIM 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.

ImageX 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.

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 All,

                I have a Dell XPS 13 9365 I’m trying to PXE boot and Image. It starts to PXE boot but then errors out asking for a device.. Is there a driver that needs to be installed or our core??

Error message:

"The selected software distribution package is invalid. Specify a valid software distribution package." Error occurs when you try to save a provisioning template.

The troubleshooting steps below can also be used to troubleshoot issues with Packages not saving in a template even after they have been mapped.

Solution / Workaround:

     1) Look through the template and find a install software action that is missing a "Selected Package":

     2) Select the correct package for that action. Once the template saves, edit the template again and verify that the selected package was maintained after saving.

     3) In rare instances, you will run into a bad package that will not save in the template. If you do:

• Attempt to export the package, and then import the same file back into the console. This will re-enter the distribution package into the database and fix issues that can be caused when updating to newer versions of the software.
  • How to Import/Export Software Distribution Packages
• If exporting and Importing does not fix the issue, the package is most likely not repairable. Recreate the package and map the new package to the template.

Hello, community!

I just recently updated my Ivanti Endpoint Manager from 2017.1 to 2017.3 after learning (from the Ivanti Bootcamp) that 2017.3 has integrated the Profile Capture / User Migration Assistant from AppSense.

According to the official Ivanti Endpoint Manager 2017.3 users guide, we should have access to this "UMA" (User Migration Assistant). However, after selecting the Capture Profile action in the Capture Template within OS Provisioning, we are completely unable to find any folder named "UMA" or find any indication that the tool is there.

In fact, the actual guide doesn't offer much insight to the actual tool.

My question is whether or not this tool was actually implemented in 2017.3 as we were told within our Ivanti Bootcamp course. If it was, I'd like to know how to find it and use it. We have a massive Windows 10 deployment project underway, and we cannot migrate to Windows 10 until we have a secured and confirmed working method of backing up user data.

Does anyone have any insight on this?

Hi all,

I am currently facing an issue in which I can't view the Change ticket. When I click on the ticket, it'll displays below error as per screenshot:

The first thing I did was executing a script against its pm_guid. Script as below:

update pm_process set usr_description_html=pm_description where pm_guid ='5223B2C1-F66B-4A22-BB42-BE6859C56C5F'

As the Change module integrate with Release module, the Release ticket also facing the same problem.
Hopefully you guys might be able to help me on this.

Thanks.

Regards,

Faiz

ZeN Computer Systems

I have a few questions and problems with Mac provisioning. We are currently using LD 2016.3 SU3. Our NetBoot image is based on macOS 10.12.6.

1. Do preferred servers work with Mac provisioning, or do I need a separate template for each of our locations?

2. Does NetBoot work with preferred servers? We have our NBI hosted on our source preferred server which is defined in "Mac Netboot Image Mappings". This is replicated to our preferred servers at each location with a matching HTTP share. NetBoot seems very slow at all locations, almost like it's downloading over the WAN.

3. Is there a way to prevent the NBI from going to sleep? It might just be the display that's going to sleep. Sometimes when it goes to sleep, it will hang on the agent install and only finish after it's been woken up.

4. We have our building techs assigned to a specific device scope. When they go to image a new Mac out of the box, it will schedule the template in the console, but never run on the Mac. The only way we've found around this is to have them refresh the scope after the device is booted into NetBoot, then choose the template. Is this expected behavior, or is there something I need to add to their device scope to allow them to "see" new Mac devices? It doesn't happen with new Windows devices.

I think that's all... thanks for any help you can provide!

I have followed the steps in the link below to create a Provisioning Template to capture a profile using USMT.   However, I'm not sure how to implement this.  I've tried to PXE Boot and select the template but it times out with 40 of 40 when I select it directly.  I've added it to a working Provisioning template that does a full image of our devices and the same thing happens.  Times out after 40 of 40 tries.  I've deleted the device from inventory.  I've even added each step one by one and every time it fails.  Is there something special that needs to be done for actions in the "System Migration" section of a template?

I've checked the provisioning log and the same message occurs until the tile out and the task fails.

DEBUGGING ProvisioningWebService 12/19/2017 10:16:31 AM : GetTaskXmlInternal

VERBOSE ProvisioningWebService 12/19/2017 10:16:31 AM : Identifiers to use - Mac Address: True, Serial Number: True, AMT GUID: True

VERBOSE ProvisioningWebService 12/19/2017 10:16:31 AM : Identifiers:

VERBOSE ProvisioningWebService 12/19/2017 10:16:31 AM : MACAddress: D481D7D464C7

VERBOSE ProvisioningWebService 12/19/2017 10:16:31 AM : SerialNumber: 5FSX2H2

WARNING ProvisioningWebService 12/19/2017 10:16:31 AM : Unable to find template for computer IDN 63155

Provisioning - Steps to use User State Migration Tool (USMT) to capture a profile

I'm using  Ivanti Endpoint Manager 2017.1 SU2

Regards,

Jim

Hello, we have a company of about 260 and just recently upgraded to the latest version of LANDesk/Ivanti. We had an Ivanti certified third party software vendor come in and install the new instance for us. They noted that you can use the default install.wim file from a standard Windows .iso to create the image and not have to actually go through the process of sysprepping the laptop to be imaged. Is this true and how would we go about this if anyone has any information?

Thanks!

In order to upgrade the Win10 version and fix issues on certain machines, I created a provisioning template that reboots the laptop and performs the OS upgrade/refresh form the install media.  I run setup.exe from the installation with the command line strings "/Auto Upgrade /Unattend /Copylogs %SystemDrive%\ProgramData\LANDESK\Log\" as a software distribution package.  These actions are being performed in the system configuration pass.  I created a Provisioning Package referencing the provisioning template to create the distribution task. 

I pushed this task on about 30 some odd machines and had 25 BSOD's "A required device isn't connected or can't be accessed".  A few were repaired by hitting F9 to choose a different operating system, but most had to be swapped out.  Not a good few days afterward.

I had previously done this process on about 100 machines prior to this using the install source and manually running the commands.  In order to speed the process of the remaining machines in need, I created the provisioning template to run this.  I often ran into people that said they would reboot their machines before they left, but had done nothing but walked away at the end of the day with all their apps left running.  To combat this, I created the template with the reboot as the first action to overcome this issue. 

I could never pinpoint what had caused the BSOD's and chalked it up to a massive freakout that hit the VMWare environment that runs the core server on the night that the task was push out the the 30+ machines.  Yesterday, I rolled up another task to upgrade to 1709 in same provisioning template mold.  First test run of it gave me the BSOD.  To test if it were the source install causing this (which was different from the 30+ machines) I copied the install locally and ran it with the same command line.  This went through fine.  The only difference really between the two runs in that there was an initial reboot in the template and the setup was run as the System account, not as a local admin as in the second run. 

So, since the second run indicated it wasn't an issue with the install source, I tried moving the reboot into the Pre-OS installation pass.  This test ran fine.

Why would having a reboot action in the same configuration pass in the template cause a BSOD?  This really does not make any sense to me.

I have attached the working templates and packages and the template that caused the BSOD's initially (Windows 10 1703 Refresh.xtp)

So I am trying to deploy a Windows 10 Enterprise LTSB image via PXE booting. It is failing during the final system configuration page.

ConfigHandler.log shows

017-12-21 13:54:39(7312-9212) ConfigHandler.exe:Attempting traditional agent install.

2017-12-21 13:54:39(7312-9212) ConfigHandler.exe:LDLogon Path: \\{THECOREFQDN}\ldlogon

2017-12-21 13:54:40(7312-9212) ConfigHandler.exe:Mapping drive using preferred server credentials

2017-12-21 13:54:46(7312-9212) ConfigHandler.exe:Could not get credentials for \\{THECOREFQDN}\ldlogon

2017-12-21 13:54:46(7312-9212) ConfigHandler.exe:Check to make sure preferred server credentials are correct. May need FQDN and shortname entries.

2017-12-21 13:54:46(7312-9212) ConfigHandler.exe:Could not connect to \\{THECOREFQDN}\ldlogon,

2017-12-21 13:54:46(7312-9212) ConfigHandler.exe:Connecting to path returned: 100003

2017-12-21 13:54:46(7312-9212) ConfigHandler.exe:config tool \\{THECOREFQDN}\ldlogon\wscfg32.exe was not found.

2017-12-21 14:01:43(1476-2728) ConfigHandler.exe:Could not find tag request

2017-12-21 14:02:01(5056-5924) ConfigHandler.exe:Could not find tag request

and HIICLIENT.log shows

2017-12-21 13:54:49(9088-9084) HIIClient:*****************  Starting HIIClient *****************

2017-12-21 13:54:49(9088-9084) HIIClient:Command line args: /uncpath /forceunsigned /taskid 947

2017-12-21 13:54:49(9088-9084) HIIClient:Running in Windows

2017-12-21 13:54:49(9088-9084) HIIClient:GetImageSystemDirectory: c:\Windows

2017-12-21 13:54:49(9088-9084) HIIClient:GetImageSystemDirectory: c:\Windows

2017-12-21 13:54:49(9088-9084) HIIClient:HII Proxy Location: http://{THECOREFQDN}/LANDesk/ManagementSuite/Core/Core.WebServices/hii.asmx

2017-12-21 13:54:50(9088-9084) HIIClient:Driver path found: \\{THECOREFQDN}\Images\Drivers

2017-12-21 13:54:50(9088-9084) HIIClient:Determining OS version and architecture.

2017-12-21 13:54:50(9088-9084) HIIClient:Found key "CurrentMajorVersionNumber".  Assuming this is Windows 10 or greater.  Will check for "CurrentMinorVersionNumber".

2017-12-21 13:54:50(9088-9084) HIIClient:OS Major version: 10

2017-12-21 13:54:50(9088-9084) HIIClient:OS Minor version: 0

2017-12-21 13:54:50(9088-9084) HIIClient:OS Product type: 0

2017-12-21 13:54:50(9088-9084) HIIClient:Major and Minor version and product type gathered.

2017-12-21 13:54:50(9088-9084) HIIClient:GetImageSystemDirectory: c:\Windows

2017-12-21 13:54:50(9088-9084) HIIClient:Architecture is: AMD64

2017-12-21 13:54:50(9088-9084) HIIClient:source path to download: \\{THECOREFQDN}\Images\Drivers\drivers.db3

2017-12-21 13:54:50(9088-9084) HIIClient:dest path for download: c:\Windows\LDDriverStore\drivers.db3

2017-12-21 13:54:51(9088-9084) HIIClient:Failed to download the driver.db3 file - HII will not continue

2017-12-21 13:54:51(9088-9084) HIIClient:Failed to get driver files list.

2017-12-21 13:54:51(9088-9084) HIIClient:ProcessDrivers failed.

2017-12-21 13:54:51(9088-9084) HIIClient:GetImageSystemDirectory: c:\Windows

The odd thing is that if after the template fails and leaves me at the desktop, if I open a command prompt as Administrator (I am not on the domain yet, just a local, non domain joined pc) and run hiiclient.exe /preview, it connects fine and shows me all of the drivers that it would download.

I have tried taking a working Windows 10 Pro template, cloning it and just pointing it to this Win10 Enterprise LTSB captured .WIM file, just in case I had an error when I created my template, however I get the same problem, where the Win 10 Pro template executes with no errors.

I have went through all the steps to mount my boot.wim file, and check the FQDN of the core, and make sure the right keys are in the boot.wim. I don't think this was ever an issue, because I do have templates that work.

I will attach my logs, thank you for any help.

Message was edited by: Paul Hoffmann

we have Precision 5520 unable to boot from network through Type - C adapter

• Issue
  • In prov_schedule.exe.log - This log is located in \\core\ldmain\log
  • In provisioning.log - This log is located in \\core\ldmain\log\provisioning. 
  • or
  • or
• Resolutions
  • Issue - Scheduler service being stopped
  • Resolution
  • Issue - Computer is not showing up under All Devices in the Console
  • Issue - Corrupt Template
  • Resolution
  • Issue - Template is trying to perform an invalid action
  • Resolution
  • Issue - LANDesk is trying to find a provisioning task from a failed distribution
  • Resolution
  • Issue - Too many PXE Reps to update with the Provisioning information for the device
  • Resolution
  • Issue - Templates may include Distribute Software actions to packages that contain a large amount of additional files
  • Resolution
  • Issue - User cannot see the devices in the console
  • Resolution

Note: In LANDESK Management Suite 9.6 or 2016 the software distribution architecture has been completely redesigned, and the case of templates taking a long time to start should be improved or eliminated.

Issue

The provisioning task is failing to load. It will attempt to load the template and retry for 40 attempts and then the job hangs and the client stays in the WinPE screen or brings back the template section window.

In 2016, the LDPROVISION.LOG file in WINPE has the following error:

“Not able to obtain a client certificate. Aborting provisioning”

Logs on the core may indicate a few different errors:

In prov_schedule.exe.log -This log is located in \\core\ldmain\log

Template is not flattened, will attempt to flatten.
Flattening  template failed.

In provisioning.log - This log is located in \\core\ldmain\log\provisioning. 

Unable to find the history task

or

Unable to find template for computer idn ###

or

Unable to find computer

Resolutions

Issue - Scheduler service being stopped

• If the scheduler service is not running, provisioning jobs will not start.
• DCOM errors can cause the scheduler service to stop.

Resolution

• Change the service to run as a Domain Administrator and start the Scheduler service. Once this is done, the provisioning task should work.
• Reset the password for the admin account that was running the LANDesk and LANDesk1 COM+ objects. This prevents the scheduler service from failing which prevents the provisioning template from running.
• Start the scheduler service

Issue - Computer is not showing up under All Devices in the Console

If the LANDESK Inventory Server service is stopped on the Core Server, the device will not show up in the LANDESK Console when the Mini Scan runs when WINPE loads.  If this is happening the Provisioning.log file will show the "Unable to find computer" error.

The Inventory service is set to ignore Mini Scans which will cause new computers to not show up in All Devices in the Console and consequently prevent templates from running.

• Make sure the "Ignore Mini Scans" option is set to 0 in the Advanced Settings for the Inventory service in Configure Services.
• Start/Restart the LANDESK Inventory Server and Managed Planet Core Scan Processor services on the Core Server.

1. Determine the TaskID from the log, Go to your Core and delete that task.
2. Delete client from database
3. PXE boot client, or run a manual inventory scan from the device
   A Manual scan can be initiated from WinPE by running X:/Windows/System32/Startnet.cmd from a command prompt
4. Run the provisioning task

Issue - Corrupt Template

A corrupt template can prevent correct scheduling. One cause if this is if a template is imported, the drop down boxes are not filled in as they were pointing to objects from the previous core. For example, Software Distribution actions do not have a package specified. Same with Configure Agent actions. Also any actions with scripts will have this issue.  Another way to determine if your template is not configured properly is by reviewing the Provisioning.log on the core. If you see the following:

INFO    PROV_SCHEDULE        8/18/2011 5:06:50 PM    : Action LANDesk.Provisioning.Business.PAction_Distribute_software
INFO    PROV_SCHEDULE        8/18/2011 5:06:50 PM    : Got package ID 60, requesting snippet
INFO    PROV_SCHEDULE        8/18/2011 5:06:50 PM    : Requesting snippet for packageId 60
INFO    PROV_SCHEDULE        8/18/2011 5:06:50 PM    : Requesting SWD snippet with task IDN 2214, package ID 60
ERROR    PROV_SCHEDULE        8/18/2011 5:06:50 PM    : Exception encountered trying to get snippet (LANDesk.ManagementSuite.SoftwareDistribution.Business.PackageNotFoundException): This package has been deleted.
ERROR    PROV_SCHEDULE        8/18/2011 5:06:50 PM    : GetSoftwareSnippet failed

Resolution

• Recreate the template, or make sure that all dropdown boxes and options are configured in the template and all included templates.
• If you are getting the error where you are unable to get the Software Snippet, you will need to go into your Provisioning Template and make sure that all software packages are available and working. Determine which package is failing and resolve the software package. Save your template and retry the provisioning task.

Issue - Template is trying to perform an invalid action

Error when attempting to save template - "Cannot save changes to the template . Verify that the template name you have chosen is not already used by another template. Database Error."

Resolution

If you are adding included templates to a main template you will want to start with adding the included templates one at a time until you find the problem template. Then address the specifics of that template and what it is doing. Try to recreate a new template that duplicates the problem template and see if you get any errors while saving the template.

Example Customer Situation:

The problem template was one that used the Update Registry action item and the Registry Operation of Import File. Because the file that was being imported was a combination of different registry export files, and remarked out descriptions had been added to the file, the template would return error: "Cannot save changes to the template . Verify that the template name you have chosen is not already used by another template. Database Error." The initial problem came from the fact that the original template did save when maybe it should not have, which caused the provisioning task to fail and the Prov_Schedule.exe.log file to show "Flattening template failed". Once we isolated the issues with the remarked out lines in the reg file and removed them, the template saved and the provisioning task worked properly.

In the customers environment, having the remarked out comments failed, but in a test lab the customers reg file worked fine. After getting the reg file to import and save, we found that the script failed on the reg file when trying to run it. What we discovered is that in his situation, the header in the reg file that says: "Windows Registry Editor Version 5.0" was causing it to fail, but I was unable to duplicate any of his problems in my lab. This seems to be a unique situation and may or may not apply to other customers that are having the 40 of 40 retries issue.

Issue - LANDesk is trying to find a provisioning task from a failed distribution

• The provisioning log will show  "Unable to find the history task".
  

Resolution

1. Delete client from database
2. PXE boot client, or run a manual inventory scan from the device
3. Run the provisioning task

Issue - Too many PXE Reps to update with the Provisioning information for the device

If there are a large number of PXE representatives in the environment, this error will occur as the core tries to update them all with the needed information. If it cannot complete in time for the 40 retries, the task will not start. However, if you keep waiting the template may start.

Resolution

Reduce the number of PXE reps and remove all PXE Reps that are not active.

Issue - Templates may include Distribute Software actions to packages that contain a large amount of additional files

Software packages that contain a large amount of additional files will require the core to hash the files and prepare manifest files each time a new template is run.
This can cause significant slowdown.  As an example, Microsoft Office 2013 can contain ~ 570 files if the files are included as additional files to the main setup program.
It is recommended to package something like this into a single file or into a few files.  This should significantly speed up the distribution process.

Due to the Software Distribution architecture changes in LDMS 9.6, this issue and most other issues with templates taking a long time to start should be eliminated.

Resolution

Issue - User cannot see the devices in the console

The user that is selecting the template cannot see the devices in the Console that are being imaged.

Resolution

Give the user that is running the template the All Devices scope or create a scope that sees the devices and assign it to the user in the User Management tool.

Overview:

This document provides the steps necessary to capture a Windows 10 image using IMAGEW.EXE v2 for use in a provisioning template. The screenshots and steps in this document show Windows 10 but the same steps will work for Windows 7, 8 or 8.1.

Create a provisioning template to capture the image

1. Open the Operating System Provisioning tool in the LANDESK Console by clicking Tools | Provisioning | OS Provisioning.

2. In the Operating system provisioning tool, click on the All my templates folder.

3. Click New Template and select the Capture Template option.

4. Enter a name for the template.

5. Enter a description for the template which is optional.

6. Select LANDESK ImageW V2 for the Image Type.

7. Enter the UNC path including the filename to the location where the image file will be saved. The filename extension will be .tbi.

8. If the image share does not exist, create it before trying to capture the image. You will also need to 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

Note: You must have Write Credentials specified in the preferred server section, the account used must have modify rights to the image share in order to capture the image.

9. Click Create.

10. The template created will show up in the Operating system provisioning tool under All my templates.

Install a PXE Representative

If PXE representatives have not already been installed, install a PXE representative on the same subnet as the Windows 10 computer. Instructions for installing PXE representatives is available in the following Community article:

How to configure Self Electing PXE services in LDMS 2016.3 or higher

Note: PXE representatives cannot have multiple NICs/LANs and they cannot have WIFI.

Prepare the Windows 10 Computer for Capturing the Image

1. Install Windows 10 on a computer or get a computer that already has Windows 10 installed. Make sure the LANDESK Agent is not already installed on the computer or it will need to be removed before capturing the image.

Note: Install the OS on the smallest partition possible so it can be deployed to as many different hard drives in the environment. ImageW captures all partitioned space and will only deploy to hard drives big enough to hold the captured partitions. It will expand the last partition to fill the drive if there is free space left over.

2. After the OS is installed, configure the OS with any Company requirements.

3. Install all OS patches currently available because this will save time in the long run so that the computers do not have to be patched later.

4. Install all applications that are common for all users in the company that this image will be deployed for their use.

Run SYSPREP.EXE to Prepare the OS for Capturing

SYSPREP.EXE is located in the Windows\System32\Sysprep folder on the Windows 10 computer.

For use in LANDESK, the computer can be sysprepped in Audit mode without the Generalize box checked or it can be sysprepped in OOBE mode with the Generalize box checked.

Select the options for sysprep then click OK to run it. When sysprep is complete, the computer will shutdown.

Note: Do not let the computer boot into the OS until after the image is captured or you will have to run sysprep again.

Add a Bare Metal Server Entry

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. Name it whatever you like because the name does not matter for the capture.

6. Make sure the Identifier type has MAC address selected then enter the MAC address of the Windows 10 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.

Create a Scheduled Task for the Capture Template

1. Drag and drop the Bare Metal device on the Capture Template that was created previously.

2. Click Save.

3. Right-click the task created in the Scheduled tasks tool and select Start now | All.

4. Expand the task and click on All devices under the task.

5. Give the task a minute to completely initialize and verify the task Status shows Waiting.

Network Boot the Windows 10 Computer to Capture the Image

1. Network boot the computer. Refer to the computers documentation, if you need help with how to network boot the computer.

2. WINPE is downloading from the PXE representative. The IP address shown is the IP address of the PXE representative that the client is communicating with which is useful to know for troubleshooting.

3. WINPE has finished downloading and is now initializing to run the template.

4. The provisioning template is running.

5. ImageW is now running and capturing the image.

6. When ImageW finishes, it will report a success or failure. Hopefully, it will report a success as shown in the screenshot above. The template progress window will only remain open for short time before closing. Check the status in the scheduled task to make sure it was successfully.