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.

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

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.

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