After adding a lot of drivers, and DeployAnywhere isn't working as it should. Alternatively, Driver Manager in the console may not be working. Finding the offending driver(s) may be difficult or impossible.
Also, you may simply want to start over "from scratch" or with a clean drivers database.
First, it should be noted that DeployAnywhere doesn't really care if you have extra drivers. It wont increase the image size. At worse, extra drivers may slow the process by a few seconds (not minutes) but it doesn't increase how many drivers get copied to the destination system. The only time you really "need" to clean things up, is if something isn't working. If a driver is breaking Driver Manager, obviously we need to isolate that driver, let support know what the driver is, and get our app fixed, if the driver itself is good. If a driver is being used in DeployAnywhere that you don't want to be used, it can either be removed, or another driver increased in priority to be used instead. Either is sufficient.
Individual driver removal can be done in one of two ways:
In the console from Driver Manager (Settings | Deployment | Driver Management), highlight the driver you want to remove and click the X on the bar.
Browse to DriversDB, and remove the folder with the driver you don't want (see the 1st bullet below for the location). When done, you should re-launch Driver Manager from the console.
If however, you simply want a "clean start", here is how you can do this.
First, make a backup of your current Drivers Database. Back up the entire DriversDB folder located in program files\altiris\altiris agent\agents\deployment\task handler, OR \\smp_server_name\deployment\task handler. This is the folder that is used by Driver Manager in the console.
Delete the entire folder.
Find a clean copy of the folder and copy it to the SMP to replace what was just removed. This can be done in one of two ways:
install a new DS site server. In installation, we create a default copy of DriversDB on the site server. This is updated by package replication eventually, but on install, it is our default package, exactly like it started on the SMP when the product was installed the first time.
Find another system that has not been modified. This might be a parent NS, or maybe someone from Customer Support. If the copy is remote to your location, you may need to have it compressed to be sent.
Launch Driver Manager in the console to re-generate the manifest files. This is found under Settings | Deployment | Driver Management. Once it displays something on the screen in the pop-up window, the process is complete.
Imported Document ID: TECH207157
Subscribing will provide email updates when this Article is updated. Login is required.