KNOWN ISSUE: DeployAnywhere with DS 7.1 does not always apply the drivers needed.
Last Updated September 17, 2012
DeployAnywhere is used to apply missing drivers on target client computers after restoring an image but before booting into Windows Production.
In some cases, some drivers can be entered at the Symantec Management Console, but they do not apply successfully to the target computers.
Start with the link below. If there is still a problem, continue with the information below.
DOCUMENT: How can you tell if a driver is compatible with DeployAnywhere?
Things to check:
- Drivers can typically be added by browsing to the folder where the .INF and .CAT files are located. There have been issues when trying to load the drivers from a parent folder.
- Make sure that the VEN and DEV numbers for the new driver in the .INF file match those same values in the .NFO file produced by running MSINFO32.EXE on the client computer involved.
- Make sure that the OS type for the new driver matches exactly what is on the target machine.
- Do the new drivers show up on the NS under \Program Files\Altiris\Altiris Agent\Agents\Task Handler\DriversDB\drivers.manifest? If not, then the drivers did not get added to the drivers database correctly.
If you still have trouble, there are a few things that you can do to try to work around the issue:
- You could build a special copy of the model computer that already has all drivers that are needed.
- Add the contents of the driver download that include .INF and .CAT file in to the DriversDB folder ( as documented above ) using a unique folder name.
- Typically, driver downloads include .EXE components designed to be run to automatically update a driver. You could, from the NS, build a 'Copy File' task that copies such an .EXE and runs it. This can be done in WinPE before the target boots. NOTE: If the target machine is 64 bit, use the 64 bit version of WinPE in this case.
- If you need help from Symantec, contact Technical Support. They will need the following information:
- The output from MSINFO32.EXE on a client computer that will not take the driver. This should be an .NFO file, not a .TXT file.
- The driver itself. This must be an exact match of vendor and device numbers that are shown in the .NFO file from the same client computer.
- The driver.manifest file as documented above.
Imported Document ID: HOWTO79452
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe