Video Screencast Help

Using Driver Management from DS console to Manage Device Drivers and Best Practices

Created: 20 Jun 2011 • Updated: 13 Oct 2011 | 10 comments
Language Translations
yogeshsadhu's picture
+15 15 Votes
Login to vote

Deployment Solution provides a provision to add drivers to the driver database to ensure the successful completion of Windows scripted OS installation and Windows image deployment tasks. By adding drivers to the driver database, you eliminate the need for manual driver installations. When you add drivers to the driver database, missing drivers and newly discovered drivers are automatically added to the image.

In the driver management console , with some practices user can maintain the driver database and can keep it up-to-date.

Driver management console has driver listing of two driver database types DeployAnywhere and Preboot,  DeployAnywhere driver database is used to make imaging and Scripted OS installation hardware independent ; Whereas preboot driver database is used for WinPE environment , which insures that you can reboot the client computer successfully to automation or PXE.

Some best practices and points which you should know while managing the device driver database

  • It’s good to update the driver database with the new version of drivers or for the devices which are newly added in the environment ;
  • Add / Import critical device drivers in the driver database , which will make sure after new image deploy or new OS installation the target machine is up and accessible ;
  • The critical driver are basically Storage and Network , Storage drivers , i.e. MSD drivers are very essential to make the machine up and running, unavailability of these drivers results target machine to give BSOD (Blue screen of Death) or can go in to continues reboot mode and never boots in to Operating System. The other critical device driver is Network drivers , lacking of which the target machine will not be accessible from the NS console or remotely , and user has to go to the target machine manually to make it accessible from the network.
  • Device drivers may not be same for all the OS’s as the device vendor provides the drivers with respect to supported  OS types ;  make sure you have the correct OS version of drivers , When you add the driver in to the DS driver management , the driver list can give the information about the supported OS types .
  • To check the number of drivers present in the driver database select the scroll bar and drag.
  • If the required driver is missing , then get the driver form vendor site or from the driver CD provided by the vendor and import in to the Driver database.
  • Make sure the driver present in the driver database is matching the device ids, From the list of drivers go to more info tab which will give the details about the applicable device ids . this simple check will make sure the required device driver is present in the driver database.
  • Following figure shows more info page which gives the device id’s applicable for the selected device driver , Device id is the combination of basically three fields Vendor id (VEN) , Device ID (DEV) and Subsystem ID (SUBSYS) ; You can find the same information in the drivers source inf file , While matching / applying the driver, DeployAnywhere chooses the most appropriate matching driver , In the drivers inf file there are some more fields present , that is CC , REV , but at present driver manager does not add this details and also DeployAnywhere does not consider these values while retargeting of the drivers.

Driver Manager – More Info

  • The driver list displays the driver as : Vendor name . Device name . Driver Version
  • Driver list displays the type of the device and supported OSs,
  • Drivers can be searched using the vendor name , device name  or device id.
  • If the target machine has some Operating system already installed and if you need to find out the device ids of the device , you can find these details by going in to the device manager from : My Computer -> Manage -> Device manager ; Then select the device for which you want to find the device details , e.g. Let’s say you need to find out the information about Modem device , Select device type ‘Modem’ and from the tree select the modem , Open Properties page and go to the tab ‘Details’ and from the list select option ‘Hardware ids’ , Which will give you the device id details for the selected modem device

  • Driver Manager also supports addition and deployment of Non critical device drivers , I could find the following different non critical devices as –  BIOS , Bluetooth , Camcoder , Card Reader-Writer ,CD ROM ,CD RW, Chipset, Copier, Digital Camera, Digital Media, DVD-ROM / RW, FAX, IrDa, Joystick, Keyboard, Modem, Monitor, Motherboard, Mouse, MP3 player, Multifunctional , plotter, print server, Printer, Projector, Scanner, Sound, Telephone, TV Tuner Card, UPS , USB, Video Capture  ,Video Card ,Web Cam.
  • Driver manager’s driver list displays all the information including type of the device , but for some devices like , printer , scanner , image driver manager shows the device type as unclassified , but there should not be any problem while matching and retargeting of the device driver.
  • The device driver can be accessible or evoked from the NS server  at C:\Program Files\Altiris\Altiris Agent\Agents\Deployment\Task Handler\DriverDB ; User can go to the driver directory for more information , which contains the driver inf file .
  • Make sure the device drivers added are digitally signed , You may face the problem while retargeting of the drivers when they are unsigned.
  • If the unsigned drivers show an exclamation mark for the devices, use the following tag entry in the unattended answer file:  DriverSigningPolicy.

 

  • By using Microsoft utility sigverif you can check if driver file is digitally signed , Go to Windows : Run and type sigverif , to open the tool , go to Advanced page , Check option – Look for other files that are not digitally signed , And select the driver folder.

Sigverif

 

  • Device drivers can be added to the driver database by using the drivermanager.exe which is a backend standalone utility , you need to provide the correct driver database path for that ,
  • Drivermanager.exe (x86/x64) utility can be found at : C:\Program Files\Altiris\Altiris Agent\Agents\Deployment\Task Handler\ghost.
  • You can add drivers to the Preboot database. You can use these drivers for your preboot PXE configurations needs.
  • If a Preboot configuration that you already created needs a new driver, you must regenerate that Preboot configuration.
  • Only Storage (MSD) and Network drivers can be added to the Preboot driver database , this does not supports Non critical drivers.
  • BootWiz.exe also can be used for addition of drivers in to the Preboot driver database, Which is a standalone utility , It is stored in the \Program Files\Altiris\Altiris Agent\Agents\Deployment\Task Handler\bootwiz directory.
  • After addition or deletion of the driver if you want to check the logs , you can check the driver DB logs at : C:\ProgramData\Symantec\Ghost\DA_DriverDatabase or  go to :  C:\Users\Public\Documents\Altiris\Altiris Agent\Logs
  • The running logs can be viewed from ‘Altiris Log viewer’

 

Yogesh Sadhu

Comments 10 CommentsJump to latest comment

Nitin's picture

Yogesh,

Nice and informative article. I strongly believe it would be useful to the customer. Thanks for writing this.

Regards,
Nitin

If you feel your issue has been addressed to, please use the "Mark as Solution" link for the relevant thread

0
Login to vote
olliegee's picture

Hey. Thanks for the article, it's helped claify the new features of DeployAnywhere in DS 7.1.

One problem though (for me anyway) - I don't have Drivermanager.exe ! Is it available on DS 7.1 on CMS 7.0?

0
Login to vote
yogeshsadhu's picture

Drivermanager.exe was present in 6.9 and 7.0 had Ghost boot Wizard which was similar to Drivermanager, and 7.1 has its new version which is Drivermanager.exe

Ghost boot wizard utility can be found in ghost folder where the DS is installed.

Drivermanager.exe is available in DS 7.1 at C:\Program Files\Altiris\Altiris Agent\Agents\Deployment\Task Handler\ghost

Yogesh Sadhu.

If you feel your issue has been addressed,please use the "Mark as Solution" link for the relevant thread.

+5
Login to vote
olliegee's picture

Hey

I don't know who installed DS 7.1 here, but they've made a real mess of it! I don't have Drivermanager.exe in that directory. All I've got gdisk32, ghDplyAw32.exe, etc. Nothing about Drivermanager.exe.

With the amount of issues I'm having I'd really like to blat the thing and start again!

Thanks for your help.

Ollie

0
Login to vote
yogeshsadhu's picture

Once you add the driver in to Preboot driver database you may want to verify if the driver is properly added or not , following points will be useful.

  • You check if the newly added drive is appearing in the Preboot driver database , to check this Go to NS Console: Settings -> Deployment -> Driver management -> open tab Preboot , from the list check if the driver is present ; 
  • You can also verify if the driver is present at the location : \\<NS Server>\Deployment\Task Handler\bootwiz\Platforms\Winpe2\x86\Drivers\CUSTOM\Drivers , if the driver is successfully added then it should present at this location.
  • Once you added the driver in to the preboot driver database in to the DS 7.1 you need to reconfigure the preboot environment , Go to settings -> Deployment -> Create Preboot configuration select PEinstall configuration (For Windows) which is the default Preboot configuration (If you are using LinuxPE then select Linux default preboot configuration) click on 'Recreate Preboot Environment' ; And save changes;
  • Once you reboot the client machine in to Automation (WinPE) you can also check the driver installed in the Automation ,Go to X:\Windows\System32\DriverStore\FileRepository which will have all the drivers source applied in to WinPE.

Yogesh Sadhu.

If you feel your issue has been addressed,please use the "Mark as Solution" link for the relevant thread.

+5
Login to vote
yogeshsadhu's picture

A Driver database can be managed by command line utilities , check this Article which mentions about the driver manager and bootwiz programs - https://www-secure.symantec.com/connect/articles/c....

Yogesh Sadhu.

If you feel your issue has been addressed,please use the "Mark as Solution" link for the relevant thread.

+5
Login to vote
vikasj's picture

Hi Yogesh

Nice Information that you going to provide.

We using DS 7.1 I am facing issue when we going to add drivers throgh Drivers Database Management when we click on add and browse the folder where we store the drivers its not showing any file it shows all blank. Which file exactly we need to add over here

 

Best Regards

Vikas Jagtap

+1
Login to vote
yogeshsadhu's picture

Vikas,

When you browse for driver you will only see a driver folder and not driver files like INF or Sys ; As an input you need to provide a Driver source folder ; you can even provide a source folder which has multiple drivers and / or multiple sub folders in it ; Try adding driver folder and see if they got imported.

Yogesh Sadhu.

If you feel your issue has been addressed,please use the "Mark as Solution" link for the relevant thread.

+4
Login to vote
Victor @ Toronto's picture

Hi Yogesh, I appreciate you documents, and they are really helpful.

I am on DS 7.5, my scripted WinXP installation stuck at reboot to production step, after XP is installed.  I found there were no drivers for network card, and guessing that was the problem. So I  added network drivers, run this job again, it still stuck at same steps, and no network driver.  What could be wrong?

Best Regards

Victor Ma

0
Login to vote