v9.5 SP1 HII Driver Manager problem
Having just installed SP1, I'm having a bit of trouble searching for .inf files when assigning drivers in the new HII Driver Management tool. I've tried putting both a UNC and HTTP path in the "Search...
View ArticleRe: v9.5 SP1 HII Driver Manager problem
Good Day, The Device ID from the database may not fully match up with the listing in the driver Library. For example with one of our USB network adapters LAN7500The Device ID reported by the Database...
View ArticleRe: v9.5 SP1 HII Driver Manager problem
It might also be helpful to know how to populate the Library =o) Here is how I have done it (The is probably a better way) Copy the drivers to the following location...
View ArticleRe: WinPE: Could not resolve core server name
StojThe problem is WinPE's paired down network solution does not properly walk the DNS like a full blown Windows build. So even if you do put the FQDN in there it is still not always going to findthe...
View ArticleRe: v9.5 SP1 HII Driver Manager problem
I got it working. I had to delete the drivers.db3 and .dbk files from \ldmain\landesk\files\drivers and then rebuild the driver library. It seems the database I had didn't migrate well from v9.0 SP4....
View ArticleLANDesk pxe boot creates an inventory entry!
I was testing some Bare Metal templates on 4 machines. I deleted the Bare Metal intentory entries for my 4 machines and booted one of the from the NIC and pressed F8 to see the boot options. I left...
View ArticleRe: Scheduling a Provisioning Template
This worked for me as well. Thanks! For those looking, here are the instructions from LANDesk: http://community.landesk.com/support/docs/DOC-25239
View ArticleModel Specific Drivers in a Provisioning Template
We provision several different models of computers through provisioning templates and HII. It seems that some models are not getting the correct drivers or are not installing at all. Example: We are...
View ArticleRe: Model Specific Drivers in a Provisioning Template
Some Drivers dont support inf install. So they musst installed using a setup routine. In 9.5 SP1 there is an option to do this by wmi model. Pre 9.5 SP1 you could use copydrivers and then run a batch...
View ArticleError in provisioning when deploying image
I am getting an error when my image template starts. The template is able to delete the partitions, and map the imaging drive but it fails at deploying the image. I get the error message Deploying...
View ArticleSoftware deployment in a provisioning template
Prior to 9.5 sp1 I was able to deploy an msi file just by putting for example \\servername\installs$\flash\install_flash_player_11_plugin.msi in the target path and file name field and a /qn in the...
View ArticleCannot assign drivers in HII / blue screen trap after imaging with SP1
When we open up the Assign tool in 9.5 SP1, the device tree window is blank for all of our desktops (various HP models), except one (see attachments). All of our other systems are Windows 7...
View ArticleRe: Cannot assign drivers in HII / blue screen trap after imaging with SP1
I would try renaming the drivers.db3 under C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\files\drivers and then rebuild the driver DB.
View ArticleRe: Cannot assign drivers in HII / blue screen trap after imaging with SP1
I should have mentioned that we already tried that.
View ArticleClik here to view.
Re: Cannot assign drivers in HII / blue screen trap after imaging with SP1
Ensure you check ' populate by selected device id 'then you may need to move off the device then back no to it and do some clean up getting to the correct id
View ArticleRe: Cannot assign drivers in HII / blue screen trap after imaging with SP1
We have successfully inventoried other Win7 x64 machines, and it does not populate the device tree for them. Only the older XP x86 ones are showing.
View ArticleRe: Cannot assign drivers in HII / blue screen trap after imaging with SP1
So the question is those other Win7 x64 machines are the same model? Regards
View ArticleRe: Cannot assign drivers in HII / blue screen trap after imaging with SP1
Several different models of Win 7 x64 machines. None of them show a device tree. The model that has XP (and shows a device tree) on it does not have Win7.
View ArticleRe: Cannot assign drivers in HII / blue screen trap after imaging with SP1
OK, I figured out the driver tree part. We had redeployed the 9.5 pre-SP1 ldiscn32.exe to our machines in order to fix an issue we have where the SP1 inventory scanner does not inventory 32-bit...
View ArticleRe: Cannot assign drivers in HII / blue screen trap after imaging with SP1
New scanner breaks SW Inventory ? Can you explain a bit more? Regards
View Article