Video Screencast Help

DeployAnywhere not importing 64 bit drivers DS 7.5 HF5

Created: 10 Apr 2014 • Updated: 30 Apr 2014 | 7 comments
This issue has been solved. See solution.

When I attempt to import network drivers in to the DeployAnywhere database I get the following report:

27 driver(s) were attempted for import. 9 driver(s) were successfully imported.
Detailed Results :
Failed to import driver: \\SMP_Server\nscap\bin\win32\x86\deployment\temp\drivers\network_driver_intel_a08_win_vcny8-setup_zpe\e1c\w2k12-x64\e1c63x64.inf [Failed to find any drivers to add.]
Failed to import driver: \\SMP_Server\nscap\bin\win32\x86\deployment\temp\drivers\network_driver_intel_a08_win_vcny8-setup_zpe\e1c\w2k12r2-x64\e1c64x64.inf [Failed to find any drivers to add.]
Failed to import driver: \\SMP_Server\nscap\bin\win32\x86\deployment\temp\drivers\network_driver_intel_a08_win_vcny8-setup_zpe\e1c\w2k8r2-x64\e1c62x64.inf [Failed to find any drivers to add.]
Failed to import driver: \\SMP_Server\nscap\bin\win32\x86\deployment\temp\drivers\network_driver_intel_a08_win_vcny8-setup_zpe\e1c\windows7-x64\e1c62x64.inf [Failed to find any drivers to add.]
Successfully imported driver: Intel.e1cexpress.12.10.28.1688
Failed to import driver: \\SMP_Server\nscap\bin\win32\x86\deployment\temp\drivers\network_driver_intel_a08_win_vcny8-setup_zpe\e1c\windows8-x64\e1c63x64.inf [Failed to find any drivers to add.]
Successfully imported driver: Intel.e1cexpress.12.10.28.1688_1
Failed to import driver: \\SMP_Server\nscap\bin\win32\x86\deployment\temp\drivers\network_driver_intel_a08_win_vcny8-setup_zpe\e1c\windows8.1-x64\e1c64x64.inf [Failed to find any drivers to add.]
Successfully imported driver: Intel.e1cexpress.12.10.28.1688_2
Failed to import driver: \\SMP_Server\nscap\bin\win32\x86\deployment\temp\drivers\network_driver_intel_a08_win_vcny8-setup_zpe\e1d\w2k12-x64\e1d63x64.inf [Failed to find any drivers to add.]
Failed to import driver: \\SMP_Server\nscap\bin\win32\x86\deployment\temp\drivers\network_driver_intel_a08_win_vcny8-setup_zpe\e1d\w2k12r2-x64\e1d64x64.inf [Failed to find any drivers to add.]
Failed to import driver: \\SMP_Server\nscap\bin\win32\x86\deployment\temp\drivers\network_driver_intel_a08_win_vcny8-setup_zpe\e1d\w2k8r2-x64\e1d62x64.inf [Failed to find any drivers to add.]
Failed to import driver: \\SMP_Server\nscap\bin\win32\x86\deployment\temp\drivers\network_driver_intel_a08_win_vcny8-setup_zpe\e1d\windows7-x64\e1d62x64.inf [Failed to find any drivers to add.]
Successfully imported driver: Intel.e1dexpress.12.11.77.1
Failed to import driver: \\SMP_Server\nscap\bin\win32\x86\deployment\temp\drivers\network_driver_intel_a08_win_vcny8-setup_zpe\e1d\windows8-x64\e1d63x64.inf [Failed to find any drivers to add.]
Successfully imported driver: Intel.e1dexpress.12.11.77.1_1
Failed to import driver: \\SMP_Server\nscap\bin\win32\x86\deployment\temp\drivers\network_driver_intel_a08_win_vcny8-setup_zpe\e1d\windows8.1-x64\e1d64x64.inf [Failed to find any drivers to add.]
Successfully imported driver: Intel.e1dexpress.12.11.77.1_2
Failed to import driver: \\SMP_Server\nscap\bin\win32\x86\deployment\temp\drivers\network_driver_intel_a08_win_vcny8-setup_zpe\e1r\w2k12-x64\e1r63x64.inf [Failed to find any drivers to add.]
Failed to import driver: \\SMP_Server\nscap\bin\win32\x86\deployment\temp\drivers\network_driver_intel_a08_win_vcny8-setup_zpe\e1r\w2k12r2-x64\e1r64x64.inf [Failed to find any drivers to add.]
Failed to import driver: \\SMP_Server\nscap\bin\win32\x86\deployment\temp\drivers\network_driver_intel_a08_win_vcny8-setup_zpe\e1r\w2k8r2-x64\e1r62x64.inf [Failed to find any drivers to add.]
Failed to import driver: \\SMP_Server\nscap\bin\win32\x86\deployment\temp\drivers\network_driver_intel_a08_win_vcny8-setup_zpe\e1r\windows7-x64\e1r62x64.inf [Failed to find any drivers to add.]
Successfully imported driver: Intel.e1rexpress.12.7.28.0
Failed to import driver: \\SMP_Server\nscap\bin\win32\x86\deployment\temp\drivers\network_driver_intel_a08_win_vcny8-setup_zpe\e1r\windows8-x64\e1r63x64.inf [Failed to find any drivers to add.]
Successfully imported driver: Intel.e1rexpress.12.7.28.0_1
Failed to import driver: \\SMP_Server\nscap\bin\win32\x86\deployment\temp\drivers\network_driver_intel_a08_win_vcny8-setup_zpe\e1r\windows8.1-x64\e1r64x64.inf [Failed to find any drivers to add.]
Successfully imported driver: Intel.e1rexpress.12.8.26.0

If you notice, non of the x64.inf files are being imported.  Ive attempted this with two different systems (HP Probook 640 and Dell Latititude 6440, both are using intel NIC's)

These drivers do import when adding them to boot disk creator.

 

Operating Systems:

Comments 7 CommentsJump to latest comment

Thomas Baird's picture

Look in those folders at the contents.  What is in there?  Are they complete?  compressed?  packaged?

let us know what is in those folders.  Have you tried to do them one at a time - the ones it failed on?

Thomas Baird
Private Consultant & open to full-time opportunities.
That means I CAN help beyond the forum (directly).

 

burndtjammer's picture

I will attempt one at a time.  Drivers are uncompressed and contents of x86 folders and x64 seem similar except for the names of the 64bit inf's.  I am having another issue i think is related.  DeployAnywhere64 isnt using the deploy anywhere driver DB just the windows db.  Had to switch all of my boot disks to x86 late last night.

Thomas Baird's picture

Sheesh - call that in.  Sounds like the "fix" for DA only made it into the 32 bit binaries.  You should collect all the 64 bit logs.  You can actually track what is being copied and see if its simply failing to copy down all the folders.  In fact, post imaging, when using 64 bit, you can actually find a smaller version of DriversDB on the local disk (c:\program files\symantec\driverDB - pretty sure) and see what the contents are.  If it is WAY short of the version you get in 32 bit, you should probably call that in.  DeployAnywhere uses THAT version when it runs the second time, and of course always compares against what is in Windows.  It does this either in 64 or 32 bit mode.  The question though is what files are copied to there to be used?  hmmmm...

Thomas Baird
Private Consultant & open to full-time opportunities.
That means I CAN help beyond the forum (directly).

 

Phil_W's picture

I have seen the same issue with 64 bit drivers and HF4

A quick workaround was to copy an older version of DriverManager64.exe to a separate folder on the server - you can open the original symantec_deploymentsolution_7_5_x64.msi found in the installation folder \Program Files\Altiris\Symantec Installation Manager\Installs\Altiris\ in 7zip to find it.

Run it, and Click the change button to direct the DriverManager to a temporary folder.

Click the Add Driver option, browse and  import the drivers.

In the temporary directory you will now find directories for each of the selected drivers, copy these directories to the Program Files\Altiris\Deployment\DriversDB directory, and delete the drivers.manifest.txt file within it.

Then in the console go to Settings / Deployment / Driver Management, the drivers.manifest.txt will be re-created, including your additional drivers.

 

Phil

burndtjammer's picture

I ran a repair on DS 7.5 HF 5 and that didnt seem to fix the issue.  I do not like this hot fix much at all.  Its the 4th issue i've had with DS since it was released last month.

I've opened a ticket with support and now I wait for initial call back. Fun.

Thomas Baird's picture

What is the download location for those drivers you're importing?  Translation: it might be good to find out if others (e.g. me) try to import those same drivers if they have the same problem?  Also, you can tell your support rep to do the same thing.

<sigh>  It's hard not to be the one in support anymore to connect directly to Dev...

Thomas Baird
Private Consultant & open to full-time opportunities.
That means I CAN help beyond the forum (directly).

 

burndtjammer's picture

I've attempted to import the drivers from various locations but mostly the root of a disk.

 

Im installing HF6 now, which was the recommended course of action from my support call and as detailed in the release notes.

 

Installing HF6 has resolved the issue with adding 64bit drivers to the DeployAnywhere Database.

SOLUTION