Managing Drivers by model

For recent hardware, the WinPE WMI script cannot always automatically detect all drivers. This option allows you to create a directory in which all drivers pertinent to a specific hardware model are copied and to be used by OSD projects for this model type.

Following are some examples how you can find the hardware model name:

• You can use a test project: A single active test project run on the representative set of hardware devices automatically creates the model name folders on the OSD Manager ( <driver cache root>/bymodel/<model name>/ ) and it displays the model name in the test project success window.
• You can use a standalone VB script: You can find a .vbs script in the < CM agent >\data\OsDeployment\modelname\modelname.vbs location to run. It results in a popup stating the model name to create the folder manually with.
• You can use the hardware inventory of Client Management : You can find the model name in the hardware inventory section under Computer System > Model and use it to create the folder manually.

The Drivers by Model node provides a list of all existing driver model name folders with the following information:

Column	Description
File Name	This column lists the names of all files and directories that are located in the selected driver directory.
Size	This column displays the size of the respective file. The field is empty for directories.
Access	This column displays the access types defined for the file or directory in the standard notation of r , w , x and - .
Last Modification Time	The date and time at which the driver file or directory was copied into this folder.

Operations on drivers by model

You can execute the following operations on the drivers by model and their content:

• Creating new directories for model drivers
• Transferring the driver files to the model directories
• Scanning model drivers for changes

Creating new directories for model drivers

You can manually add directories to the file structure for the model drivers. To do so, proceed as follows:

1. In the left pane select Drivers by Model node or a subdirectory under which the new directory is to be placed.
2. Click Edit > Create Directory .
    The Create a New Directory pop-up dialog box opens.
3. Enter a name for the new directory then click OK to confirm your addition, otherwise click Cancel .

Transferring the driver files to the model directories

You can directly transfer the driver files from their original location to the model driver directory on the OSD Manager from the respective directory.

1. Go to the driver directory under the Drivers by Model node.
2. Select File Transfer .
    The File Transfer window opens on the screen. This window allows you to copy files from another device to the OSD Manager.
3. Find the driver files to be copied in the tree hierarchy of the remote device and select it.
4. Select the target directory, that is, <driver cache root>/bymodel/<model name>/ on the OSD Manager.

5. Click the arrow between the two boxes to start the transfer.

   Information

   The transfer can be stopped and thus the file copy being canceled by clicking Cancel the current transfer .

6. Select Close at the bottom of the window when all required files were transferred.

Scanning model drivers for changes

If changes were made to the model drivers, the directories need to be scanned to make the projects aware of these changes. This is done either automatically, when the OSD module is started, or whenever any project is (re-)built. However, to make sure you can also manually scan the model drivers for any changes as follows:

1. In the left pane select Drivers by Model node or a subdirectory under which the new directory is to be placed.
2. Click Edit > Scan Drivers by Model .
3. Click Yes in the Confirmation dialog box.
    The scan of all existing directories is directly started.