Ghost Solution Suite

 View Only

How do I use DeployAnywhere with Ghost Standard Tools 3.x? 

Apr 26, 2017 10:58 AM

DeployAnywhere is a utility that is used after image deployment to attempt to identify and inject missing drivers into a deployed Windows image. The DeployAnywhere executable files are included with Ghost Standard Tools, as is the driver database management utility (DriverManager.exe and/or DriverManager64.exe) but there is no default Driver Database.

You can use DeployAnywhere in Evaluation mode without a driver database to identify missing drivers. 

For DeployAnywhere to inject any drivers it must have a DriversDB folder. To get a DriversDB folder you can either copy the DriversDB folder from an existing Ghost Solution Suite installation (From this location: \Program Files (x86)\Altiris\eXpress\Deployment Server\DriversDB, to DriversDB folder you are about to create below.), or create your own DriversDB.

To add a DriversDB folder to your Standard Tools boot disk, on the machine running the Boot Disk Creator, create the DriversDB folder under the OEM folder, like this:
\Program Files (x86)\Symantec\Ghost\bootwiz\OEM\DriversDB\winpe\x64\Base\DriversDB

If you are using the existing DriversDB folder copy the contents of that DriversDB to the path above.

If you want to create your own DriversDB follow these steps:

  1. Launch the Driver Database Manager:
    C:\Program Files (x86)\Symantec\Ghost\DriverManager64.exe  (assuming you have a 64 bit installation)
  2. Click the Change... button in the upper right corner.
  3. Choose the folder you created earlier:
    \Program Files (x86)\Symantec\Ghost\bootwiz\OEM\DriversDB\winpe\x64\Base\DriversDB
    drivermanager.JPG
  4. Click Add Driver, then select the custom driver you want to add.
  5. Repeat step 4 as needed.

Now that you have a DriversDB folder, follow the steps in this document: HOWTO124429 to create a new boot configuration. 

The key point during that process is that you select the OEM extension "ALL" during the creation of your new configuration.  While you are there you should verify that "DriversDB" appears in the OEM extensions list, as well as "GSS" - you want both so you choose "ALL".

After the boot media is created you can boot a machine to that media and the DriversDB folder will be present on the disk and you can follow the steps in DeployAnywhere in Evaluation mode to see if it is able to match the missing drivers to the DriversDB that you provided. 

If you run DeployAnywhere in Evaluation mode and, having evaluated the logs, you determine it does indeed find a match for all of the missing drivers, you can run DeployAnywhere again - this time without the /eval switch - which will cause it to actually inject the matching drivers that it finds in the DriversDB folder.

Statistics
0 Favorited
1 Views
0 Files
0 Shares
0 Downloads

Tags and Keywords

Related Entries and Links

No Related Resource entered.