Does anybody know about this error:[5H]

When loading a template to restore an image

Action #1

Vboot

FAILED

error:[5H] An unknown error occurred. If the problem persists, contact the LANDESK administrator.

After that the rest of the template works fine and the image is restored.

Just curious if anybody knows how to fix Action #1

Thanks,

Pete

We've been using the profile backup and restore features in LDMS for quite a while and it has been working well for us until we updated to 9.6.  How this has been done till now is that if someone needs to replace a computer or reimage an existing one they run a backup provisioning task, then reimage the computer, and then run a restore provisioning task to restore profiles.  The backup was placed in a network share under the computer name, so as long as they were using the same computer name it would grab the correct restore and put it back.  After the 9.6 update it still backs up the profiles using the computer name, but it appends the computer ID to the end of the file as well.  So where before the file was <COMPNAME>.sma, it is now <COMPNAME>-prov<COMPID>.sma.  The problem with the is that when the computer is replaced it gets a new computer ID and looks for the backup filed named with the new computer ID.  We can look up the new computer ID and rename the file with it and it works fine, but I'd like to change it so that it doesn't append the computer ID so we don't have to do that.  For the life of me I can't find where to do this.  Does anyone know where to do this, or is there a new way that I can use to do this without the manual step of changing that computer ID?

Thanks!

- Bryan

Has anyone had any luck editing the LANDesk PE to use a Static IP Address instead of DHCP once within PE? If so how did you accomplish this task?

Issue

Imaging a device with a LANDESK Management Agent installed can cause the devices that receive the image to overwrite each other in the database.

Cause

LANDESK inventory looks at a Unique ID/Device ID when inserting the scan. This ID is created when the agent installed on the device.

Resolution

It is strongly recommended that the LANDESK agent not be included in an image.  The recommended way to install the LANDESK Agent with imaging is to use LANDesk Provisioning and include a Configure Agent action in your provisioning template.  Besides causing duplicate devices, the LANDESK agent is often updated and adding it to the image will quickly cause your image to be outdated. 

If the agent must be included in an image or Non-Persistent VDI image, the unique identifiers must be deleted out of the registry prior to the capture of the image.  Before creating an image of the machine do the following:

LANDesk Mangement Suite 9.0 and later

1. Install the LANDESK agent, then STOP all LANDESK related services
2. Delete the following Registry Keys for 32bit clients:

           HKLM\SOFTWARE\Intel\LANDesk\Common Api\UniqueID
          HKLM\SOFTWARE\LANDesk\Common Api\UniqueID

          HKLM\SOFTWARE\LANDesk\Inventory\LogonHistory\Logons
          HKLM\SOFTWARE\LANDesk\ManagementSuite\WinClient\SoftwareMonitoring\MonitorLog contents

          Delete the following Registry Keys for 64 bit clients:

          HKLM\SOFTWARE\Wow6432Node\Intel\LANDesk\Common Api\UniqueID

          HKLM\SOFTWARE\Wow6432Node\LANDesk\Common Api\UniqueID

          HKLM\SOFTWARE\Wow6432Node\LANDesk\Inventory\LogonHistory\Logons

          HKLM\SOFTWARE\Wow6432Node\LANDesk\ManagementSuite\WinClient\SoftwareMonitoring\MonitorLog contents

     3. On Windows XP delete C:\Documents and Settings\All Users\Application Data\LANDESK (delete the entire directory and subdirectories)

     4. On Windows 7, 8, and 8.1 delete C:\ProgramData\LANDesk (delete the entire directory and subdirectories)

     5. From the command line (as administrator) in the \LDCLIENT directory run the following

"clientdbutil.exe /create"

     6. Verify that a new database, (LDClientDB.db3) was created in the same path as you deleted above

In addition it is a good practice to ensure that the image does not contain any DRIVERS.DB3 file.

See Community discussion for additional tips and information:

http://community.landesk.com/support/message/61210

Issue

When machines are attempting to PXE boot they are failing with one of the following errors:

BOOT SERVER IP: x.x.x.x MFTP...PXE-T00 Undefined error code

PXE-T01 Undefined error code

PXE-E36: Error received from TFTP server

PXE-M0F: Exiting (NIC Manufacturer) PXE ROM

Cause

PXE Representative is failing to give a valid multicast address for Startrom.0 file.

This is being caused by the PXE Representative attempting to redirect the Client machine to a PXE rep in another subnet for file download.

Resolution

Currently there are 3 solutions:

1. Remove all PXE Representatives except the one you are attempting to use.
2. Install a PXE representative on the same subnet as the computer being PXE booted.
3. Disable the Multicast option for the MTFTP service on the PXE Representative.

There is only one supported option for disabling Multicast on the MTFTP server.

Disabling Multicast on the MTFTP server will not have a significant effect on the process of imaging machines even if using the Multicast option is in the script or template.

Instructions for how to manually disable Multicast

This will need to be performed on all PXE Representatives:

1. On the PXE Rep, go to C:\Program Files\LANDESK\PXE\System, double click to run PxeConfig.exe.       
2. Right click "Boot Server", then click "Configure Boot Server", select the "MTFTP Options" tab, and un-check the Multicast option checkbox.       
3. Restart both LANDESK PXE services on the PXE Rep and boot into WinPE

Further information on PXE boot errors:

PXE Boot errors and descriptions.

How to troubleshoot PXE boot:

Troubleshooting PXE boot (OSD)

Applies to LANDESK Management Suite 9.0[, 9.5

In LANDESK Management Suite 9, LANDESK introduced new Hardware Independent Imaging (HII) tools. These tools can be used in conjunction with OSD or Provisioning to apply drivers for particular hardware devices when deploying a generic Windows image.

Hardware Independent Imaging Components

HII Driver Repository

This is where the actual driver files are stored. This can be ANY machine with a UNC and HTTP share available to client machines. It is recommended that the HII Driver Repository be located with a high-speed, low-latency connection to the Core Server. The drivers can be organized in any manner and should include the inf files and all supporting files. The location of the HII Driver Repository is configured in the LANDESK Management Console.

The "master" HII Driver Repository can be replicated to Preferred Servers as needed. The Preferred Servers do not have to have both UNC and HTTP shares available as long as clients are configured to use the available share.

For more information on the HII Driver Repository see HII Driver Repository

HII Driver Database

Once drivers are placed in the HII Driver Repository, and the HII Driver Repository Manager configured to point to the drivers, the HII Driver Repository Manager will generate the HII Driver Library Database. A progress bar will indicate the progress of the database creation and when the database is complete. The HII Driver Database is not updated automatically so it should be updated anytime new drivers are added to the HII Driver Repository

The driver library is created at the root of the HII Driver Repository and is named drivers.db3. This file is distributed to clients and used to determine the correct drivers and the associated files necessary for any given hardware device and the corresponding driver.

For more information on the HII Driver Library Database see HII Driver Database

HIIClient

HIIClient is the client side application that is run in order to get drivers installed on target devices. HIIClient will use HTTP by default, but can be configured to use UNC. No other configuration is necessary.

When HIIClient runs it will automatically detect the Windows® version (Windows XP®, Windows 7®) that is installed, the architecture that is installed (x86, x64) and all the individual devices connected to the client (Hard drive controller, video card, sound card, chipset etc.). HIIClient will then use the HII Driver Database to find the best matching drivers available in the HII Driver Repository. The best drivers are determined by a number of factors and should match the drivers that Windows would choose. Only the best matching and most recent driver for each device is downloaded.

The drivers are downloaded from Preferred Servers (if configured) and then installed on the device. The installation method for the drivers varies depending on the Windows version being deployed. For more information about HII Client see HIIClient

Preferred Servers

With LDMS 9 SP3, HII has been improved to allow the use of Preferred Servers via HTTP or UNC and download speed has been improved. All Preferred Server configuration requirements are the same as for LANDESK features that use Preferred Servers.

Because HII runs in WindowsPE, some special considerations are worth noting. Windows PE will assign a random hostname to the device when it boots. Also WindowsPE will not have any domain access or credentials natively. This means that it is very important that any Preferred Server that will be used by HII have the client Read-only credentials configured. For more information on Preferred Server configuration see:

LANDESK Content Replication - Preferred Server (Target) Configuration

How to Configure a Preferred Package Server

How to set up a HTTP share for a Preferred Package Share

Important Information

The HII tools use information contained in driver files and information obtained from devices in order to match up the right drivers and devices without requiring the user to manually configure or match up anything. In order to do this, LANDESK pulls information from drivers files in accordance with standards published by Microsoft. Occasionally device manufacturers will take shortcuts or have an error in a driver file. When this happens it can cause LANDESK to match the wrong drivers to a machine and can result in problems. In every case if the Windows were pointed to the driver, it would also incorrectly identify the driver as applicable and install the driver.

To reduce the potential impact of such errors, it is recommended that drivers be obtained from official sources whenever possible and any errors should be reported to the device manufacturer or vendor. Large packages of drivers (aka driver packs) have been found to often contain many errant and corrupt drivers that can cause problems. Additionally driver harvesting utilities often do not gather all the necessary information or files for a driver and can produce problematic drivers as well.

Hi,

Is there anyway to make the HII process quicker when it's looking for and loading the drives through the template? Does the HII process look through every folder and file in your drivers folder you have on your Core server? My core points to a specific drivers folder where i have all my drivers for OS provisioning.

I'm just curious if only keeping the exact .inf, .sys, .ini files for the specific hardware device will speed up the HII process and me deleting all the other folders and files that come with a full driver install will have no effect on HII?

I noticed another document (How to add drivers to WinPE for LANDESK OS Provisioning) had some discussions on the newer Thinkpad models and which drivers are needed to be pre-loaded in order for the PE environment to work. However I have spent 4 hours testing and researching the various drivers and have had no such luck getting any to work. Any help in which .inf files are needed would be great. We are using the 32bit format since we are using the legacy bios setups currently.

Also Lenovo support provided me these links to use these drivers and they still did not work:

WinPE Driver Packs

http://download.lenovo.com/luc_test/eval/TP_X250-T550-W550s-S5Yoga15-X1Carbon_MT20BS-20BT_PE3132_201501.exe

http://download.lenovo.com/luc_test/eval/TP_X250-T550-W550s-S5Yoga15-X1Carbon_MT20BS-20BT_PE3132_201501.txt

http://download.lenovo.com/luc_test/eval/TP_X250-T550-W550s-S5Yoga15-X1Carbon_MT20BS-20BT_PE3164_201501.exe

http://download.lenovo.com/luc_test/eval/TP_X250-T550-W550s-S5Yoga15-X1Carbon_MT20BS-20BT_PE3164_201501.txt

http://download.lenovo.com/luc_test/eval/TP_X250-T550-W550s-S5Yoga15-X1Carbon_MT20BS-20BT_PE564_201501.exe

http://download.lenovo.com/luc_test/eval/TP_X250-T550-W550s-S5Yoga15-X1Carbon_MT20BS-20BT_PE564_201501.txt

Hello everyone

I'm hoping i'm just tired and this is a simple answer.. I've been tasked with setting up a virtual machine from one of our old XP images in VMWare workstation 10 using landesk 9,5 sp2

I can get all the way to right before you get the actual PXE Menu and then the command window does the searching for IP address from 127.0.0.1 and fails on me. I've done some research and it says that it can use the e1000 nic driver which I've added to the drivers but I can't get this guy to connect.

anyone have any idea what I'm doing wrong?

thanks in advance for any help!!

Mark

Hello,

I am having trouble using HII deployment with 9.5 SP3. I create and deploy my images using OSD and ImageWV2 tool. I have already assigned my drivers and build my database. The main machine model that I am having an issue with is a Dell Optiplex 7010. It keeps blue screening while starting Windows. I know the drivers are good because they work with a fresh Windows install. Please let me know what other information is needed to fix this issue.

Hi, I am having a problem with HII not installing the driver for a usb3.0 hub in Windows 7 x86.

HII detects the usb root and installs the driver, but not the usb hub.

It is an intel motherboard with usb 3.0 onboard.

SQL lite view of the drivers.db3 (select * from devices where inffiles_idn = 82)

If you build a fresh install of Windows 7, a single unknown usb device is shown, give it the usb3.0 driver and it installs a usbroot device. Then another unknown device appears, give it the usb driver and it installs a usb hub.

How do I troubleshoot this to fix it? attached is the driver .inf file for the usb3.0 hub.

Thanks!

Problem:

OS Deployment template actions are failing.  To determine the cause of the failures it's helpful to take a look at the log files, but WinPE is loaded onto a RAM drive and the logs disappear when the device reboots.  If you log a support case, LANDesk will ask you for these logs.

Solution:

When you start a provisioning template, the computer boots into WinPE and will stay in WinPE until you get to the Configure Target OS action.  After CTOS, the computer reboots and all logs and files generated in WinPE are lost.  We need to pause the process prior to the CTOS action.  Edit your template and insert a wait action just prior to CTOS.  Specify a wait time in seconds.  Usually 600 seconds (5 minutes) is sufficient.  In LDMS 9.6+, you can continue from the wait action early if you desire.  In LDMS 9.5 you will need to wait out the entire timer, so choose your duration accordingly.

Run your template again, and view the computer you are provisioning.  If it's a remote computer you can use LANDesk Remote Control to view the WinPE environment.  This document shows you how:

Use LANDesk remote control to view a computer in WinPE provisioning

Next we will open a console window to locate and copy the logs to a remote computer:

1. Click the green icon on the bottom left and select New Console
2. Type cd\
3. Type cd ldprovision
4. Type dir *.log to view the log files in this location.  This is the main log location for provisioning within WinPE
5. If you would like to view these logs within WinPE, type "notepad nameoflog.log"
6. We need to map a network drive to copy the files to a shared folder on a remote computer.  Do so using the NET USE command:
       Use the Net Use command to map or disconnect a drive
7. Copy the files to the drive letter you just mapped.  We will assume you mapped the E drive to your remote computer.  The command is:
   xcopy *.log E:
8. You can now access these logs from the remote computer which you mapped as the E: drive.  If you are working with LANDesk support, email these logs to your support representative or attach them to your case.

Troubleshooting OS Provisioning using the log files

Each OS Provisioning template action has a log file.  In addition, the overall template process has a log, called "ldprovision.log".  This should be your first stop.  Open the log file and scroll through.  You are looking for a section of the log similar to this:

     2015-04-17 14:35:38(1404-1408) ldProvision_x64:********************************** Begin processing actions **********************************

This indicates the beginning of the template actions.  You will see the start of each action called out in the log similar to this:

     2015-04-17 14:35:38(1404-1408) ldProvision_x64:*********  Begin an action - Map_toPreferred

You will also see that each action has it's own action handler.  You will see the ldprovision.exe action handler calling additional handlers, similar to this:

     2015-04-17 14:35:39(1404-1408) ldProvision_x64:Launching action handler [MaptoPreferredHandler_x64.exe] with parameters ["]

     2015-04-17 14:35:39(1404-1408) ldProvision_x64:handler launched.

At the end of each action you will see an indication of success or failure, and then the next action starts.  Keep in mind that some actions show failed but do not affect the success of the entire template.  For example the vboot action, or in some cases HII may show failed but the template can continue and ultimately succeed.  Locate the failed action that you are troubleshooting.  Each action handler has it's own log file, so next pull up the log for the specific action handler that failed.  If the name of the handler is "myactionhandler.exe" the log file will be "myactionhandler.log".   If you have difficulty identifying the failed action, press CTR+F to open the Find box, and search for "failed".

The log file specific to the action which failed will give you greater detail into the cause of the failure.  You will also see a failure error code.  Sometimes these codes can be very generic, other times they are quite specific.  Search the LANDesk community for your failure reason and error codes and you should find discussions and documents that help you resolve the failure.  If you are not able to determine the cause of the failure, log a support case with LANDesk and provide the log files to your support rep. 

Hello,

We're on Landesk 9.5 SP2 and have a weird issue during provisioning.  What we're seeing on some models is that after running CTOS, Landesk doesn't wait for the first startup(after sysprep) to finish.  It just keeps moving on to the next tasks as soon as the network drivers are installed.

Our images are sysprepped and captured as TBI files.  Our provisioning tasks removes the disk partitions, deploys the image, run HII, then CTOS, and then supposed to run some more tasks after it starts up and auto logs into an administrator Windows account.  But it's not waiting for the first startup to finish.  I can see by refreshing the Landesk task that it moves onto the System Configuration section even before all the drivers have finished installing and whatever it is doing is interrupting that first startup, causing it to fail with the message "The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install Windows, click 'OK' to restart the computer. and then restart the installation."

Restarting doesn't help.

We've now added Wait 300 seconds as the first task in the System Configuration section as a workaround so Windows can finish and reboot.  Has anyone else seen this happening in their environment?  Our call to Landesk support ended up with them saying the same thing - just add a wait time.  We didn't have this issue in Landesk 9.0.  It always waited until after the first startup to finish and reboot before continuing any tasks,.

Thanks,

Peggy

Does anyone have a working method to change the screen resolution for windows 7 within a provisioning template?

I have tried utilities like Qres.exe,  which does work fine OUTSIDE of a provisioning template.

If you are provisioning computers in another office or on another floor, it's very helpful to view the WinPE environment while the provisioning template is running.  Follow these steps to use LANDESK Remote Control to view the remote computer:

1. From your core or a computer with a LDMS console installed, open a RUN command and type ISSCNTR.exe.  This launches the LDMS remote control platform.
2. Enter the IP address of the device in question.  The device must have booted into WinPE before it can be remote controlled.
3. Once connected, click the magnifying glass icon on your toolbar to start viewing and interacting with the remote screen.

This guide is design to assist users as a general overview in pushing a file to a specific destination:

1. Go to the Distribution directory.
2. Select OS Deployment.
3. Go to My Templates
4. Create new Template
   1. Provide name
   2. Select Not Applicable for Boot Environment
   3. Select the appropriate Target OS
   4. Provide Description
5. Locate your new template, right click, and then select edit.
6. Click on Action List
7. Select System Configuration and select Add
   1. Provide Name
   2. Provide Description
   3. Under Type select “Copy file”
   4. Press OK
8. Copy and Paste the Source path
   1. This can be UNC or HTTP path
9. Copy and Paste the Destination Path

Proceed with standard deployment.

Ensure deployment has proper authentication to source and deployment folders.

Hi all,

Wondering if anyone has had this problem before and can help me.  I am trying to find a NIC driver that will work in WinPE on a Dell R210 II server.  The Hardware ID of the NIC is B06BDRV\L2ND&PCI_163B14E4&SUBSYS_04DD1028&REV_20 and the target OS is Windows Server 2008 R2.

I am running the Core on Server 2012 R2, LANDesk 9.6 SP1.

I downloaded Dell's WinPE driver CAB as well as this driver most recently: http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=W1XTR

I stuck them on a flash drive and ran the DRVLOAD <driver_inf> command, which several said they loaded successfully YET, there is no network adapter.

Thanks in advance for any help you can offer.

Cheers,

Kevin Beattie

We use a Hardware Independent Image process at my company.  With the use of a few scripts to identify what model machine, and where the correct drivers are shared from, we are able to get almost every model we have in production to full provision without an error.

Of course, there is one exception.  The Dell T7600, using the on-board SAS connections.  With our standard build template, the machine accepts and starts to provision, runs the scripts, downloads drivers and then reboots to begin the Windows Setup portion...but then, the wonderful blue-screen flash, and a reboot to no-good install of Windows.  It seems that Windows can not find or access the SAS-connected SSD.  If I plug that same SSD into the SATA connector, it works like any other machine.  The reason I'm trying to use SAS is the speed difference, 6Gbs versus 12Gbs.  And considering the only department that uses the only 15 T7600's we have, routinely works with files that can be over 10Gb, the transfer speed is very important.  Right now, my users have no clue there is a SAS option, and seem to be happy.  But if I can make the SAS work, it could extend the life the T7600 for them, saving the company from buying new machines too early.  The T7600s are only a few years old.

I know I have the correct driver, because if I boot off of our Windows Enterprise CD, it says no HDD detected.  But then I tell it where to look for the driver, it finds it, loads it, and then finds the drive.  So I know it's possible have that configuration in place.  I just can't seem to get the driver injected, or the drive recognized for some reason.

I have tried pre-staging the driver on the HII, and made a reference to the location in the Unattend.XML answer file..no good.

I put the driver in our normal driver store for that model...no good.

I had the machine fully ready to go, sysprepped, and then created a WIM file, using DISM to mount the image and inject the file, then return the WIM to the reference to capture as a TBI...no good.

I'm running out of ideas, and seeing as Dell had someone tell me the on-board SAS was just a 'gang-plug' and not a boot-able option, they are of no help right now.

It has to be possible, but I can't figure out how to specifically tell Windows to use the driver for the model using SAS any other method.

Any ideas?

Thanks,

Rick S

Issue

When attempting to PXE boot, the following error appears:

• PXE Boot fails.
• No F8 option is recieved by clients.
• Unable to PXE Boot machines.
• Unable to network boot machines.

Cause

• No PXE representatives are deployed.
• Deployed PXE Representative is turned off.
• PXE representative is not in the same broadcast domain as target machine.
• Firewall on PXE representative is blocking requests from target machine.
• PXE services are not running.
• Windows Deployment Services (WDS) are installed on the PXE representative.
• Another service on the server is using port 67

Resolution

• Update BIOS on device
• Ensure that a PXE representative is on and is deployed in the same broadcast domain as the target machine.
• Ensure that no firewall is blocking requested packets from PXE booted machines.
• Ensure PXE services are running.  The two services are "LANDESK® PXE Service" and "LANDESK® PXE MTFTP Service".
  If they are running, restart the services.
• Redeploy the PXE Representative.
• If PXE services repeatedly stop on PXE representatives, download and install the latest service pack on the core, then remove and redeploy PXE representatives.
• Disable the Windows Deployment Services (WDS) on the PXE representative.
• Run the "netstat -abn" command to find the service which is using port 67 and disable/reconfigure this service.

Note: The PXE Representative may need to be rebooted if the services are running, the firewall is off, but it still does not respond.

More information on PXE boot errors:

PXE Boot errors and descriptions.

How to troubleshoot PXE boot:

Troubleshooting PXE boot (OSD)

It is taking about 20 minutes, sometimes more, to get through the HII step in Provisioning.  It hasn't always been that way, but as we've added more and more hardware models (currently 42) to our driver database it has slowed down the process significantly. 

I am wondering what the best practices are for uploading drivers into the drivers folder.  Currently when we notice that a driver is missing after imaging it, we download it from HP, extract the SPxxxxx.exe and upload the entire contents of that extraction into our Drivers folder, organized by model.  Those extracted folders can be very large, which is probably at least part of the reason why HII is so slow. 

The hope is that we could just grab the .inf, .ini, .cat, or .sys files and exclude the rest.  Is that possible, and how do I know which files are necessary?  What is the best way to go about cleaning up an existing driver library?

Thanks!