Deployment Solution 7.x comes with a relatively small subset of drivers for a majority of known systems at the time of release, but is no where near comprehensive for driver support, and for obvious reasons, will not include drivers that have come out post product release. Additionally, we only include NIC and Mass Storage in the release product, for this is the most important set of drivers needed for imaging. However, because DA also supports Video, Audio, and essentially any other driver that can be used (minus some minor issues with USB3 and SATA devices), you may want to augment our driver database for a number of reasons.
This discusses how to add those drivers.
NOTE: We only support uncompressed drivers in their most basic, raw format. Anything that even hints at an installer will fail (e.g. CAB files, MSI's, or compressed files like sy_ extensions).
Option 1: Import drivers via the Console.
- In the console, go to Settings | All Settings, and then Settings \ Deployment and Migration \ Driver Database Management.
- There are two tabs on this screen: DeployAnywhere and Preboot. Select the tab of your choice.
- The Preboot tab (often overlooked) adds drivers to preboot environments and does essentially the same thing as adding drivers manually into BootWiz (see the next section on adding drivers to 7.0 and 7.1).
- Both tabs write drivers directly to the file system by copying them into custom folders directly. No compilation occurs until they are bundled into the preboot environment.
- Add each driver one at a time and be sure they're added to the list.
- NOTE: All versions and types of drivers are included here (Linux and WinPE) but that the column headings can be clicked on to sort the various columns. For example, you might sort first on name by clicking that column heading, and then type by clicking on that one, and then look for your driver.
Option 2: Import drivers via command-line
Alternatively, you may have several drivers you want to import at the same time. The console only supports adding drivers one-at-a-time, so if you've downloaded a driver package from a manufacturer and want to import them all at the same time, you'll have to run DriverManager.EXE from command line. Here are some important things to note:
- DriverManager.EXE should be run on the SMP not on the site servers!
- DriverManager.EXE is in the \\SMP_ServerName\Deployment\Task Hander\Ghost folder.
- Run with /? for a list of options.
- You will need at a minimum:
- /ddb= to specify the database location, which is \\SMP_ServerName\Deployment\Task Hander\driversDB
- /add= with the path to the UNCOMPRESSED folders you have and want to import.
- It will give you an output of what it did, or did not do.
- This is an unsupported method, that is, support for doing this outside the console is "best effort" and your drivers are, as usual, not supported.
- The use of DriverManager to import drivers though IS supported, so if a driver is failing to import and you are confident it can in fact be used, we will take problems like this to development. The only thing that is NOT supported is getting the command line correct, finding your folders, making sure your drivers are correct, etc.
After Import, Rebuild Automation:
Now, to get the SBS server to actually pick up the change, BootWiz has to recompile WinPE on the server (and all site servers which have been updated. To accomplish this, you will need to perform a few more tasks:
- In the console, go to Settings | All Settings\Deployment and Migration\Symantec Boot Services (PXE)\Preboot Configurations.
- Highlight the menu option you would like to recreate and select 'Recreate Preboot Environment'. (Do not click the 'Save changes' button)
- Update the policies on the Symantec Management Agent for the server(s) on which you wish to recreate the configuration.
- This can be done manually by opening the Symantec Management Agent settings on the system and selecting 'Update'
- This will also automatically be done next time the Agent checks for policy updates on schedule (default is every hour).
- Boot Disk Creator will run on the server, recreating the configuration with the added drivers. While it is running:
- Bootwiz.exe will show as an active process on the Windows Task Manager
- A folder called "cfg-tmp\<Configuration Name>" will be created in the ".\Altiris\Altiris Agent\Agents\Deployment\Task Handler\Bootwiz". (The "cfg-tmp" folder should be auto-deleted after bootwiz finishes running)
This is the only way to add drivers in the early versions of this product. This process will still work in later versions if necessary for troubleshooting or other reasons.The method involves work inside and outside the NS7/DS7 console. It should be noted here that each SBS/PXE site server (DS 7.1) will need to go through this process. This is because the drivers are not replicated to the site servers.
The DA interface is launched from the file system with a relatively long string, as follows:
"\\your_server\Deployment\Task Handler\Ghost\Ghost Boot Wizard.exe" /managedrivers /path="\\your_server\Deployment\Task Handler\DriversDB"
Add drivers and exit. The drivers are automatically replicated to all package servers. No more work is required.
For Preboot Configurations
- Find BootWiz.exe in the Symantec Management Agent installation location ".\Altiris\Altiris Agent\Agents\Deployment\Task Handler\Bootwiz".
- Run BootWiz and go to the interface and select Tools | Add Preboot Device Drivers. Note: This is a new option added to BootWiz as of DS 7.1's release.
- If you have more than one SBS/PXE server (i.e. NS + Site Server), you will either have to
- Repeat this process on each SBS server -OR-
- Use a SWD job to copy the files added during this process off to other servers. Doing this is not documented or supported, but essentially it involves finding the folders added via BootWiz (custom folder with drivers), creating a package for them (pattern them after the DeployAnywhere package) and then setting up replication to the correct locations on the other package servers.
You will then need to rebuild the preboot configuration as indicated above.
Imported Document Id