Capture Profile action is failing with a 259 error.
Capture profile action is getting a timeout error.
Capture Profile action has a 5 minute timeout.
Install SP2 which increases the timeout to 90 minutes.
Hello, I have been trying to get the provisioning to work but it wouldn't get an IP address. It would say "Waiting for IP address" and timed out eventually. When I typed ipconfig /renew, I get an error "The operation failed as no adaptor is in the state permissible for this operation". I tried everything suggested from here http://community.landesk.com/support/message/95932#95932 but gotten nowhere. I updated the bios and using the 32bit Win7 network driver. Please help.
Hi there,
I'm facing a critical issue with HII (LDMS 9.5 sp1) when adding new drivers for different computer models that I have tested and approved for these specific PC's models (Dell Latitude E6x40, DELL Precission T1700, T3610, T5610, T7610). Seems that some older computers with different models of hardware detects the new drivers as adequate for their components (let's say the chip set driver for a DELL optiplex 7010 or HPCompaq 8300), and then HII assign these new drivers to the old computers even to pc's that are from a different maker, for instance HII is assigning DELL drivers to HP computers.
The nightmare for me is that I don't know how to pinpoint what drivers has been assigned to each old computer and which one (or ones) are the offending drivers that produces the blue screen of death when the the new image boots up after HII injects the drivers to the old PC's models.
I have over 40 different PC models and makers in our environment and we add periodically new models. So now I face a difficult situation as every time I add new drivers for new PC's to the HII driver library I don't know what will happen to the existing models when a image is deployed and the HII injects the drivers. Up to now and after adding some new drivers I'm in a terrible situation because computers that were receiving OS images and drivers perfectly alright, and now these fails with the BSOD and I don't have a clue about which drivers are the offending drivers that are breaking the OSD process.
Any ideas about it? Any help will be welcome.
Thanks!
I want to show you how I fixed all of our HII Problems in 9.5 SP1 and dramatically speeded up the provisioning process with a few simple steps.
We working with this method for weeks now without any problems...so I wanted to share it to the community.
Benefits:
No DELL USB 3.0 Driver Problems, No more Blue Screens after StandBy Mode, No mixing of drivers because of generic Hardware IDs, massivly speeded up Provisioning Process
Steps:
Now your Windows Installation has all drivers that are needed right for this computer model.
Kind regards,
Marco Feuerstein
Germany
We are looking into Hii for imaging moving forward.....I can't find a document explaining the process
Is there a lot of issues with 9.5 sp1 hii? I've seen quite a few unanswered posts regarding blue screens and slowness....is it unstable?
Is there a way to import all HP/Dell Drivers
Hello,
After some research about vBoot I found this Script:
http://community.landesk.com/support/docs/DOC-9980
My question is, is there a possibility to change this script so that it download the Image (.wim) from the Core server and you can use this offline version of the image multiple time for the deployment on a PC?
For example: You have a Computer, before the first deployment the Image is downloaded to the Hard disk (an extra Partition) and then you install it. After some days you decide to reinstall the PC (because a Virus or something else). When you start the reinstallation the Landesk-Agent should use the Image from the partition and don’t download it again from the Core server.
I hope I can explain well enough what my question is and that you can help me
Friendly greetings
So, we swapped out to different switches at the end of last week, which caused all kinds of grief, which for the most part has been sorted out. We were having some DHCP errors, and when I'd try to boot off the PXE representitive it would return some appropriate error about not receiving a DHCP reply.
Well, now when I try to image a computer, it says something about the MTFTP Server not having an IP address? The error is up VERY briefly before it kicks me to the Start windows normally option screen. Last time I tried it I notice a bunch of zeroed out IP addresses, like something about subnet mask 0.0.0.0 etc.
I don't even know where to start on this one, a quick google/landesk search hasn't turned anything up for me.
I understand by upgrading to 9.5 SP2 that Winpe requires Windows 8 drivers. My computers are on Windows 7 and a few on XP.
I have searched Dells web site and cannot find Windows 8 drivers except for network and storage.
Can I just put in windows 7 drivers?
A bit of a newbie in OSD, so I need some input as to my issue with OSD.
Are using LDMS 9.5 SP2. Imaging a Dell E7440.
My steps have been:
On source PC configuring with WIn 7, install apps etc. Start sysprep Audit, no geneneralize, shutdown.
I check for partition # of C drive using diskpart
I capture the image using OSD script with Image W V2.
aWhen capture is done, source machine can't boot because no OS
Image capture itself seems to work
I deploy Image onto destination PC using OSD script configured to use sysprep.
Image deploys, PC boots successfully, sysprep OBE runs, Agent installs.
After boot complete desktop resolution is set at lowest level, device manager shows 3 unknown devices,
and the C; parttion is shrunk in half with the balance of space unallocated.
Comparing the source driver files to destination, the actual driver files are missing for the unknown devices.
Is this a sysprep thing, OSD, a combination or am I doing something very wrong.
Thanks in advance.
Issue
After enabling FIPS on the core server, LANDESK OSD scripts and Provisioning templates stop working.
After selecting and trying to launch an OSD script, nothing happens and the screen stays on the LANDESK imaging background.
If you select a Provisioning template to execute, it will attempt to run but will fail with error 80001803H
Cause
This issue occurs after enabling FIPS 140-2 on a core server. When FIPS 140-2 is enabled, a new SHA1 cert is generated on the core and replaces the old MD5 core cert.
The WINPE image does not get updated automatically with the new cert and thus communication from a client being imaged is refused by the core server.
Resolution
On the core server, do the following steps:
This will update BOOT.WIM, BOOTMEDIA.WIM, and BOOT_X64.WIM and inject the newer SHA-1 certificates into the Boot Images.
Issue
Solution
UEFI is still not compliant with the PXE menu specifications, therefore booting a machine in UEFI mode via PXE for provisioning works only when the device is associated to a provisioning task on the core.
The error PXE-E21 appears when the device is not associated to a provisioning task on the core.
LANDesk submitted an enhancement request to the UEFI Forum regarding this issue. Once they add the support needed, LANDesk will be able to support the PXE menu for the devices booting in UEFI mode as well.
At the moment, the only way to have the PXE menu functionality on a device booting in UEFI mode is setting it up to boot in Legacy BIOS mode.
Environment
LANDesk Provisioning
WinPE x64
Target machine booting in UEFI mode
Issue
Trying to deploy an x86 operating system image on a device booting in UEFI mode fails.
More specifically, WinPE x64 is loaded, which is not able to install drivers in HII with DISM to x86 images.
In this situation, the following DISM error is shown:
DISM Error: An error occurred. You cannot service an x86-based image from an x64-based host that does not support WOW64
Resolution
The scenario doesn't work by design, as per Microsoft specifications
There are two possible workarounds to avoid this 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.
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 taskor
Unable to find template for computer idn ###
First, make sure that the latest service pack and the latest component patches are applied to the core.
Resolution
Resolution:
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:
Cannot save changes to the template . Verify that the template name you have chosen is not already used by another template. Database Error.
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.
Question:
How to properly use CSVIMPORT.EXE to import devices.
In order to properly import devices Network view, the proper formatting, syntax, and network information must be supplied.
Answer:
Automating the naming of computers during an OS Deployment task reduces the work load of the IT department, saving time and money. OSD has the ability to work with sysprep to name computers based off Device Name in the database. It uses the Mac Address of a computer to match a device to the computer name associated with that Mac Address in the Database. Newly purchased computers do not exist in the LANDESK database as these computers have never been scanned. Such computers can be manually added to the database before deploying the image allowing the computers to be automatically named as part
of an OS Deployment task.
To accomplish this, LANDESK provides a utility called csvImport.exe to manually add devices to the database. This utility is located in the C:\Program
Files\LANDESK\ManagementSuite directory.
Adding devices to LANDESK using csvImport is a four step process:
1. Create a template
2. Create a .csv file
3. Run csvImport to generate mini-scans
4. Process the mini-scans
Step 1 - Creating a Template File
A template file is required by the csvImport utility. This file contains information about what content will be added to the inventory for a device created with the
csvImport utility.
(NOTE: The template file is a plain text file. This file should be created in a plain text editor such as notepad.) Each line in the template file represents an entry that will be inserted into a miniscan file when csvImport.exe is run. This mini-scan processed by moving it to the ldscan directory, at which point the device is added to the database.
Syntax
The template file must be created following strict syntactical guidelines.
(NOTE: Failure to follow the correct syntax could result in one or more of the following:
The syntax for each desired line is as follows:
[<Heading> - <Heading> - <Head...>] - <Value name> = <Value Data>
(NOTE: The following characters are not used: <,>,[,]. These symbols are used to help clarify the syntax only.)
The following line is an example of correct syntax for a line in the template file:
Network - TCPIP - Subnet Mask = 255.255.255.0
In this line, "Network" is the first heading while "TCPIP" is a sub heading. "Subnet Mask" is the Value Name and "255.255.255.0" is the Value Data.
Heading
Headings are not required as indicated by the square brackets []. There can be multiple headings. Default heading values can be seen in the Inventory of a fully scanned client on the left panel underneath the computer name.
If a heading has a plus sign next to it, then more headings exist underneath the first heading. Expand any heading by clicking on the + sign and the default values for that heading will be displayed. Headings are not limited to the default values. Custom values may be used and will be entered into the database.
Value Name
This is a required field. Most default Value names can be seen in the right pane by highlighting any heading. All headings are visible in the left pane. If a Value Name is given without a heading, it will be entered under the computer name on the very top
of left panel of the Inventory screen. Value Names are not limited to the default values. Custom values may be used and will be entered into the database.
Value Data
Value Data can be any date, string, or integer. It is not required to specify in the template file whether the Value Data will be a date, string, or ineger because this is automatically detected. Value Data can be specified with a variable that gets its value from the .csv file (see Variables as Value Data), or it can be statically entered (see Static Entries as Value Data).
Variables as Value Data
Variables are used to get data from the .csv file. The template file is created so each line contains data to enter into the database. The variable %<number>% describes the column in the .csv file from which the value of the variable will be assigned. %1% is or the first column, %2% is for the second column, %3 is for the third column, and so on.
Static Entries as Value Data
If a line does not have a variable (such asthe second line of the example below), the Value Data is considered static. No Column should be made in the .csv file for this line because the data will be the same for all devices. Only lines with a variable should have a column in the .csv file.
Minimal Information Needed for OS Deployment
OS Deployment will use database information to rename a computer. The minimum inventory a device needs is “Device Name” and “Network – NIC Address.” This means the template file must have at least the following two lines:
Device Name = %1%
Network - NIC Address = %2%
Sample Template File
The following is the text from a sample template file.
Device Name = %1%
Network - NIC Address = %2%
Network - TCPIP - Subnet Mask = 255.255.255.0
BIOS - Serial Number = %3%
BIOS - Asset Tag = %4%
Lines 1, 2, 3 and 5 use variables to get their data value from the .csv file. Line 3 gets its value from the assigned value in the template file.
Step 2 - Creating a .csv File
The .csv file is an information file referenced by the csvImport. It should contain all the information for the computers that are being added to the database. This information can often come for the computervendor or it can be manually gathered from the computers. Remember that by using csvImport, the naming of computers can be automated through the imaging process. The man hours used to gather the data needed for the .csv file is significantly less than the man hours needed to manually rename every computer during or after the imaging process.
Syntax
In order for csvImport to understand the .csv file, it reads the template file. The
template file determines how the .csv file should be created. Every variable in the
template file refers to a column in the .csv file. While the columns are determined
by the number of variables in the template file, the number of rows is determined by
the number of computers; one row is needed for each computer.
The following is the proper syntax
value1,value2,value3,...
value1,value2,value3,...
...
Alternately a space can exist after each comma.
(NOTE: The ellipsis “...” is not part of the syntax. This is used only to represent the
idea that data for more columns and more rows can be added.)
The following two lines are an example of correct syntax for a line in the .csv file:
ComputerName1, 000ABBCCDD01, SN-0001, ASSETTAG-01
ComputerName2, 000ABBCCDD02, SN-0002, ASSETTAG-02
Though the above two lines have four columns, any number of columns is possible. The minimum should include columns for the Device Name and NIC Address. The number of columns and the type of data the column contains is directly related to the Template file.
The Relationship between the Template File and the .csv File
Below is a copy of the template file from the previous step:
Device Name = %1%
Network - NIC Address = %2%
Network - TCPIP - Subnet Mask = 255.255.255.0
BIOS - Serial Number = %3%
BIOS - Asset Tag = %4%
This sample template file has four variables %1%, %2%, %3%, %4%. This indicates that the .csv file will have four columns. Each column should contain the data for which the variable represents. For example, in the template file shown above, %1% standsfor the NIC Address. Column one of the .csv file should contain only NIC Addresses; one NIC Address for each row, or each computer. Similarly, %2% represents the Serial Number for the BIOS. Column two of the .csv file should contain only BIOS Serial Numbers; one Serial Number for each row, or each row for each computer.
Sample .csv File
The following is a sample .csv file. This sample file has been created based on the sample template file using only four machines.
ComputerName1, 000ABBCCDD01, SN-0001, ASSETTAG-01
ComputerName2, 000ABBCCDD02, SN-0002, ASSETTAG-02
ComputerName3, 000ABBCCDD03, SN-0003, ASSETTAG-03
ComputerName4, 000ABBCCDD04, SN-0004, ASSETTAG-04
(NOTE: This can be created in any text editoror in any spreadsheet application. If created in a spreadsheet application, makesure the file is saved as a comma delimited .csv file. Also note that the commas are automatically inserted when creating a file using a spreadsheet application and should not be
manually added in the spreadsheet.)
Step 3 - Running csvImport
The csvImport utility is used to create mini-scan files from a template file and a .csv file. It does not automatically enter these scans or create machines in the database. Instead, it creates mini-scan files that must be placed in the ldscan directory so that the LANDESK Inventory service can process them. It is the LANDESK Inventory service that processes the mini-scans and adds the device to the database.
Syntax
The syntax for csvImport is as follows:
csvImport <template file> <.csv file> <output directory>
[template file = any template file] [.csv file = any .csv file] [output directory = folder where mini-scans are created]
The csvImport utility requires all three options (the template file, the .csv file, and the output directory) to be specified. Ifthese files are not in the directory from
which csvImport is launched, then full paths may need to be specified.
Example:
csvImport c:\path\to\templatefile.txt c:\path\to\computers.csv c:\folder
Running csvImport will result in the generation of mini-scan files, one for each device in the .csv file.
Step 4 - Processing Mini-Scans
Mini-scan files are text files with a .IMS extension that contain information about a device. This is information is in plain text but is formatted so that the LANDESK
Inventory service can read and process it. The LANDESK Inventory service uses the information from the mini-scan to add devices to the database.
Mini-scans are created by csvImport as explained in Step 3.
How to Process Mini-Scans
To process the mini-scans, copy all the mini-scan files (files with a .ims extension) to the \Program Files (x86)\LANDESK\Managementsuite\ldscan directory on the core. These scans will be processed and deleted from the directory by the LANDESK Inventory service. The devices created from the mini-scans will be viewable in the LANDESK Console in the Network View under All Devices.
Note: The core server will not process a mini-scan if it does not have [Network - NIC Address = ] in it. The scans will be placed in the ErrorScan directory and no errors messages will be generated.
Sample Mini-Scan
The following information is the output of a sample mini-scan named csvImp2.ims.
Notice that the mini-scan is in the same format as the template without variables.
Device Name = COMPUTERNAME2
Network - NIC Address = 000ABBCCDD02
Network - TCPIP - Subnet Mask = 255.255.255.0
BIOS - Serial Number = SN-0002
BIOS - Asset Tag = ASSETTAG-02
Creating a Mini-Scan in a Text Editor
Understand that csvImport is a utility that automates the creation of mini-scans. The csvImport utility is not required to create mini-scans. Manual creation of mini-scans can be done in a text editor if created withthe correct syntax. The syntax for a miniscan is the same as for a template file without the variables; all data must be static.)
Test the following:
1. Create a text file with the following syntax. Put in any computer name and any NIC Address not already in the database
Device Name = ANYNAME
Network - NIC Address = 000123456789
2. Save the file as test.ims and copy the file to the ldscan directory for processing by the LANDESK Inventory service.
3. In the LANDESK Console, refresh All Devices under the Network View. The new device will exist.
Sample Use of csvImport
This section will demonstrate the use of csvImport, using example files and example computers.
1. Create a template file by opening a text editor and copying the information below. Save the file to c:\temp\template.txt.
Device Name = %1%
Network - NIC Address = %2%
Network - TCPIP - Subnet Mask = 255.255.255.0
BIOS - Serial Number = %3%
BIOS - Asset Tag = %4%
2. Create a .csv file by opening a text editor and copying the information below. Notice that each column corresponds to a variable from the template file.
Save the file to c:\temp\data.csv.
ComputerName1, 000ABBCCDD01, SN-0001, ASSETTAG-01
ComputerName2, 000ABBCCDD02, SN-0002, ASSETTAG-02
ComputerName3, 000ABBCCDD03, SN-0003, ASSETTAG-03
ComputerName4, 000ABBCCDD04, SN-0004, ASSETTAG-04
3. Open a command prompt and change to the C:\Program Files\LANDESK\ManagementSuite directory. Then run the following command:
csvImport c:\temp\template.txtc:\temp\data.csv c:\temp
4. Once the above command is run, four .ims files (one for each computer), will be created in the c:\temp directly.
Copy those files to the \Program Files (x86)\LANDESK\ManagementSuite\ldscan directory.
5. Open the console and go to the All Devices under the Network View to verify that the devices are added to the database.
Summary
This article has explained the four step process by which computers can be added to the database using csvImport.
Adding devices to the database using csvImport is necessary only before OS Deployment using Sysprep and is used in conjunction with OS Deployment and Sysprep to automate the naming of computers that are not already in the database.
Appendix A – Wake on LAN
For sending a wake on LAN packet, the following is the minimal information needed:
Device Name = %1%
Network - NIC Address = %2%
Network - TCPIP - Subnet Mask = 255.255.255.0
Network – TCPIP - Address = %3%
Network – TCPIP – Subnet Broadcast Address = %4%
Environment
LANDESK Management Suite 9.5 SP1
Issue
After upgrading to 9.5 SP1, some software within a WIM image is not working properly anymore.
You might receive the following error when booting Windows 8 for the first time :
Error 1500. Another installation is in progress. You must complete that installation before continuing this one.
Example
The mail icon in the Control Panel created by Microsoft Office is missing.
Cause
The version of WinPE used by OSD/provisioning is version 4.0 instead of version 3.1 and Microsoft changed the way it formats partitions. The 8.3 file format is not active which causes some files from the WIM file not to be copied or to be corrupted when copied over to the hard drive.
Solution
Format the drive using the following switches :
format C: /fs:<FS> /q /s:enable /y
The /s:enable turns the 8.3 format back on and should resolve issues when files are copied over from the WIM to the partition.
Reference
This document was generated from the following discussion: LDMS 9.5 SP1 PXE Rep Issue
Applies to LANDesk Management Suite 9.5 SP1 and newer
Hardware Independent Imaging allows drivers to be injected during the imaging process specific to the destination hardware. During hardware migration planning, driver decisions must be made. In order to assist with that migration planning a preview option has been added to HII, enabling IT to review driver assignments prior to upgrading to a new OS.
HIIClient.log
HIIPreview.log
hiiclient [/?] [/uncpath] [/taskid <taskid>] [/preview | /previewall] [/os <os> /arch <architecture>]
/? - Shows standard help and syntax information
/uncpath - Specifies if HII should use unc based paths to drivers
/taskid - Specifies the <taskid> to use to ask for SWD snippet when processing packaged drivers
/preview - Specifies if HII should run in preview only mode.
/previewall - Specifies if HII should run in preview only mode with debug information.
/os - Only valid with both /preview and /arch.
Specifies which OS the preview should be run for.
Valid options are: winxp, win7, win8, server2003, server2008r2, server2012
If not specified the currently detected OS will be used.
/arch - Only valid with both /preview and /os. Specifies which architecture the preview should be run for.
Valid options are: x86, x64.
If not specified the currently detected Architecture will be used for the preview.
Applies to LANDESK Management Suite 9.5 SP1 and older
This issue was resolved in Service Pack 2
Issue
When changing the background image WinPE, the changes seem to take effect but when the PXE client boots the background has not changed.
Cause
The reason why this is not working was due to the changes Microsoft made to their WinPE image wallpaper settings. In WinPE 3 the default wallpaper was located here:
x:\windows\system32\winpe.bmp
Which is what the LDMS console is designed to replace, But in WinPE 4/5 the default wallpaper is located here:
x:\windows\systme32\winpe.jpeg
Resolution
Apply the latest service pack for LDMS 9.5
Installed a new Core Server using the existing Core Server database.
Note: The issue can also be caused by moving the existing LANDesk database to a new database server. Also take note that the same symptom can occur for LANDesk(R) Management Suite 9.5 and 9.5 SP1. The solution below is the same.
Resolution
Windows XP clients are not installing the drivers added to HII.
Incorrect drivers are getting installed when using HII.
Forward slashes (/) were used in the path for the drivers instead of back slashes (\).
1. Run the following SQL statement against the HII driver database (drivers.db3) located in the directory specified for HII:
update inffiles set FilePath = replace(FilePath, '/', '\') where FilePath like '%/%'
The database is a SQLITE database. Use any tool that can run SQL statements for SQLITE such as SQLite Browser.
2. Save the changes to the database after running the SQL statement.
Note: The SQL statement will need to be run against the HII database after each time the Save button is clicked in the "HII Driver Repository Manager" window.
Applies to LANDESK Management Suite 9 SP3 and later
The Hardware-Independent Imaging (HII) Driver Database is created after clicking Save in the HII Driver Repository Manager. It contains information about any devices, operating system versions and architectures the drivers in the HII Driver Repository can be used for. This information is retrieved from the .inf driver files and used to find the correct driver for any given device without requiring access by the client to the entire driver repository.
The HII Driver Database is a SQLLite database. It is stored in a single file at the root of the Driver Repository and named drivers.db3. The database contains several tables that enumerate inf files, supporting files as well as Device IDs and Compatible IDs. With this information HIIClient is able to determine which driver best matches the hardware found on the device.
During HII the HII Driver Database is downloaded to the client machine and all lookups and driver matching is performed on the client machine. This means that the HII Driver Library (drivers.db3) can be replicated to Preferred Servers and client will simply download the file from their local Preferred Server. This can provide significant savings in bandwidth as well as processing time since the client will match the drivers on their own.
If the HII Driver Library is being replicated to Preferred Servers, make sure that when the HII Driver Library is updated on the HII Driver Repository it is updated on all Preferred Servers. If the client discovers that the HII Driver Library file (drivers.db3) is out of date on the local Preferred Server, it will go back to the original source on the HII Driver Repository for the download.
Some drivers that are poorly written, corrupt or incomplete can result in incorrect matches on devices. For example, a touchpad driver may have a very generic setting that causes it to match any pointing device so it is installed on desktop machines where there is no touchpad. Also, a Windows XP driver may install on a Windows 7 OS and vice versa. When this happens there are a few options.
If the driver is not needed at all in the environment, simply remove it from the HII Driver Repository and rebuild the HII Driver Database. If it is needed, review the steps below to help improve the driver matching.
In most cases, drivers that have been improperly matched by LANDESK will also be improperly matched by Windows. To test this, copy the offending driver (and all supporting files) to a test device. Then use Device Manager to try and install the driver. For example, if a touchpad driver is installing improperly, open Device Manager, select the Mouse section (Mouse, Pointing Devices or HID devices) and try to update the driver. Point to the driver in question and see if Windows considers it a valid driver for the device.
If Windows also agrees that this driver should be installed for a device, then there is probably something awry with the driver file. In fact, because LANDESK uses DISM to install drivers for Windows 7 and newer, if the driver is installed, Windows already thought the driver was right. DISM will refuse to install drivers that do not apply to a device. Make sure there isn't an updated or alternative version of the driver that may be better. If there is no alternative that functions better, see below on editing the driver database so that the device doesn't get matched by LANDESK.
If Windows does not install the driver or consider it applicable for a device, please report that to LANDESK Support. Make sure to have the driver and device information available so that LANDESK can make changes and improvements to the driver matching process.
In some instances it may be necessary to modify the HII Driver Database in order to prevent a certain driver from being installed on some devices. Any SQLLite browser or tool can be used to do this. One example is this open-source SQLite Database Browser.
DELETEFROM devices WHERE device = ‘<DEVICE ID HERE>’
Note: This will prevent this device ID from being matched at all on any machine. If only parts of the match need to be removed (Windows 7 driver should not match Windows XP) please contact LANDesk Support for assistance
Authors Note: We know this isn't a good solution. Frankly we thought device vendors would be better about writing drivers for their own hardware. We are working on a better solution, so stay tuned.
For more information about HII please see Hardware Independent Imaging (HII)