ENGL Driver Manager 4.1 Documentation
Table of Contents Table of Contents Table of Contents 3 1 Getting Started 5 1.1 Overview 6 1.2 System Requirements 7 1.3 Installation 8 1.4 Prerequisites 10 1.5 Walkthroughs 14 2 Configuration 23 2.1 Tour of the Workspace 24 2.2 Options 28 2.3 Machines View 32 2.4 Driver Pack Properties View 39 3 Implementation 43 3.1 System Center Configuration Manager 44 3.2 Microsoft Deployment Toolkit 46 4 Reference 48 4.1 DMScanner 49 4.2 Driver Installer 50 5 Support 51 6 ENGL Software Licence (Version 4) 52-3 -
1 Getting Started 1 Getting Started This section introduces you to Driver Manager, system requirements, prerequisites and walkthroughs. Overview System Requirements Installation Prerequisites Walkthroughs - 5 -
1.1 Overview ENGL Driver Manager simplifies the discovery and deployment of Windows device drivers with Microsoft System Center Configuration Manager (SCCM) and Microsoft Deployment Toolkit (MDT). Driver Manager takes care of all of the deployment challenges presented by OEM drivers. In order for a machine to deploy without requiring manual intervention, all of the hardware drivers must install successfully and silently. Driver Manager will match drivers to a specific piece of hardware based on the machine's manufacturer and the version of Windows being deployed. This approach combined with the analysis process ensures that drivers are installed and configured correctly during deployment. Figure 1 1. Hardware inventory is gathered using the Driver Manager hardware inventory scanner (DMScanner) or directly from SCCM inventory, then imported into the Driver Manager console. 2. Once the inventory has been imported a driver search can be initiated for the Windows version and platform that will be deployed, for example Windows 8 64-bit. 3. Driver Manager will then download all of the required drivers. 4. The analysis process checks each driver package and establishes the best deployment method for that driver. 5. The drivers are then packaged up and integrated into either SCCM or MDT for use in an OS deployment task sequence. - 6 -
1.2 System Requirements The following system requirements must be met in order to use Driver Manager. Windows versions for Administration machine System Center Configuration Manager Versions Microsoft Deployment Toolkit Versions Windows Versions for Administration Machine The following Operating Systems may be used for the Administrative machine. Where a service pack is specified it is the minimum supported version. Windows 8.1 Windows 8 Windows 7 Windows Server 2012 R2 Windows Server 2012 Windows Server 2008 R2 Windows Server 2008 SP2 The following are the minimum supported display settings required to run Driver Manager. Resolution 1024 x 768 pixels or higher Colour depth 16-bit or higher System Center Configuration Manager Versions The following versions of SCCM are supported for driver integration. Note: Windows 8 and Server 2012 drivers can only be integrated if System Center 2012 Configuration Management SP1 or above is detected. System Center 2012 R2 Configuration Manager System Center 2012 Configuration Manager System Center 2007 Configuration Manager Microsoft Deployment Toolkit Versions The following versions of MDT are supported for driver integration. Note: Windows 8 and Server 2012 drivers can only be integrated if Microsoft Deployment Toolkit 2012 or above is detected. Microsoft Deployment Toolkit 2012 Microsoft Deployment Toolkit 2010-7 -
1.3 Installation This section describes the steps required to install Driver Manager on an Administrator machine. Before performing these steps you should familiarise yourself with System Requirements. The following tasks are used to install Driver Manager. Downloading Installing Upgrading from a previous version Welcome Wizard Downloading The following tasks must be completed to download the latest version of Driver Manager. 1. Visit the ENGL web site at www.engl.co.uk. 2. New users should click Login then Register Me and following on screen instructions to activate their ENGL user account. 3. Login to the ENGL web site 4. Select My ENGL>Product Downloads. 5. Select the Driver Manager 4.1 platform link that is suitable for your Administration machine then click Download. Note: If the Administration machine is running Windows 64-bit select x64 otherwise select x86. The installation will display an error message if the incorrect platform installer is used. 6. Carefully read the licence agreement. Click Yes to accept the terms of the licence agreement or No to cancel the download. 7. Click an available link to begin the download. Installing The following steps are required to install Driver Manager. 1. Install.NET Framework 4.0. 2. Login to the machine with administrative permissions. 3. Run the Driver Manager 4.1 setup EXE and follow these steps. a. At the Welcome page, click Next. b. At the License Agreement page, read the licence agreement and do one of the following: Select I Accept the Terms of the License Agreement then click Next. OR Select I Do Not Accept the Terms of the License Agreement then click Next. Upgrading Note: If the licence agreement is not accepted the setup will exit. c. At the Choose Destination Location page, click Change to specify a different installation path then click Next. d. At the Ready to Install the Program page, click Install. Setup Status will be displayed during installation. e. At the Installation Wizard Complete page, click Finish. f. Run Driver Manager and complete the Welcome Wizard. The following tasks must be completed to upgrade from a previous version of Driver Manager. - 8 -
Warning: Driver Manager 4.1 installation is not supported on Windows XP and Server 2003. Attempts to perform a fresh installation or upgrade on Windows XP or Server 2003 will cause the installation/upgrade process to fail. 1. Login to the machine with administrative permissions. 2. Run the Driver Manager 4.1 setup EXE and follow these steps. a. At the Welcome page, click Next. Setup Status will be displayed during upgrade. b. At the Update Complete page, click Finish. 3. Run Driver Manager and complete the Welcome Wizard. Welcome Wizard The following tasks must be completed the first time Driver Manager is run in order to complete the Welcome Wizard. 1. At the Welcome page, click Next. 2. At the Licensing page, do one of the following: a. Select Request Evaluation License to request a restricted evaluation licence then complete the following: Username Specifies your ENGL website username. Note: If you have not previously registered a username on the ENGL website, click Create Account. Password Specifies your ENGL website password. Note: If you have a previously registered user account but have forgotten your password, click Forgot Password. b. Select Enter License Key if you have received a licence code from ENGL. Paste in the licence key. c. Click Next. Note: To display your ENGL purchased licenses click Display licenses owned by your organisation. You will need to have been previously registered on the ENGL site and your email address must have been assigned as the ENGL licence contact. d. If licence activation was successful a confirmation message will appear, then click OK. 3. At the Folders page, change default folder paths as required, then click Next. Note: A significant amount of disk space may be required by Driver Manager depending upon the number of different machines and Windows versions you require drivers for. ENGL recommend that the Machine Library is not placed on the Windows system drive. 4. At the Deployment Solution page, select a Windows deployment solution, then click Next. a. If you selected System Center Configuration Manager as the Windows deployment solution, specify Connection, Target Path and Package Creation settings, then click Next. Note: See the SCCM Integration global options for further details. b. If you selected Microsoft Deployment Toolkit as the Windows deployment solution, select a Deployment Share and optional Database settings, then click Next. Note: See the MDT Integration global options for further details. 5. At the Completed page, click Finish. Driver Manager console starts. - 9 -
1.4 Prerequisites The following prerequisites must be met before using Driver Manager: Common MDT Integration SCCM Integration Common 1. Driver Manager requires an Internet connection to search for and download drivers. Note: Driver source files can also be manually imported. Microsoft Deployment Toolkit Integration 1. Driver Manager must be installed to a machine that has the MDT Workbench and PowerShell 2.0 installed. 2. An MDT Deployment Share must have been created. 3. The MDT database must be configured if Make and Model information is to be added using Driver Manager. System Center Configuration Manager Integration 1. Driver Manager can be installed on a client machine or the SCCM server. Note: The SCCM Console is not required to perform SCCM integration. 2. The user credentials used to access the SCCM server must be configured within SCCM an granted appropriate permissions: a. For SCCM 2012: Create an SCCM user under the Administration\Security\Administrative Users folder and assign the Operating System Deployment Manager role. b. For SCCM 2007: Create an SCCM user under the site Security Rights\Users folder with full rights over Devices, Driver Packages and Packages. 3. The user credentials used to access the SCCM server must have full read/write file system permissions to the specified shares. 4. The shares used to import drivers and create driver packages must be accessible to the SCCM server and the Driver Manager console. Note: The SMS Provider must have must have full read/write file system permissions on the shares used for drivers and driver packages. 5. In order to query the SCCM inventory to import machines into Driver Manager the hardware inventory reporting must be configured as follows: a. For SCCM 2012 configure the hardware inventory b. For SCCM 2007 update the sms_def.mof - 10 -
Configuring SCCM 2012 Hardware Inventory SCCM 2012 hardware inventory must be configured to as follows to support importing machines. 1. From the SCCM Console select Administration. 2. Expand the Overview and select Client Settings. 3. Right-click Default Client Settings and select Properties. 4. Select Hardware Inventory then click the Set Classes button. 5. Ensure the following Classes and Properties are enabled: a. Baseboard (Win32_Baseboard) i. Manufacturer ii. Product iii. SerialNumber iv. Version b. Computer System (Win32_ComputerSystem) i. Manufacturer ii. Model iii. Name c. Computer System Product (Win32_ComputerSystemProduct) i. Name ii. Vendor iii. Version d. PNP Device Driver (Win32_PnpEntity) i. Device ID ii. Class Guid iii. Manufacturer iv. Name v. PNPDevice ID e. System Devices (CCM_SystemDevices) i. Name ii. Compatible IDs iii. Device ID iv. Hardware IDs 6. Click OK twice to save the changes. Note: Once the changes to the hardware inventory have been made a Hardware Inventory Cycle must run on every machine to gather the additional inventory data. - 11 -
Configuring SCCM 2007 Hardware Inventory The sms_def.mof file must be configured as follows to support importing machines from SCCM 2007 inventory. Pre-requisite properties are highlighted in red. The default location for the sms_def.mof file is: <SCCM Installation Directory>\inboxes\clifiles.src\hinv Note: The sms_def.mof file may already contain all of the properties listed below, check each class and property and specifically the SMS_Report() value. Not every property within the class is displayed. [ SMS_Report (TRUE), SMS_Group_Name ("BaseBoard"), SMS_Class_ID ("MICROSOFT BASEBOARD 1.0") ] class Win32_BaseBoard : SMS_Class_Template { [SMS_Report (TRUE)] string Manufacturer; [SMS_Report (TRUE)] string Product; [SMS_Report (TRUE)] string SerialNumber; }; [SMS_Report (TRUE)] string Version; [ SMS_Report (TRUE), SMS_Group_Name ("System Devices"), SMS_Namespace (TRUE), SMS_Class_ID ("MICROSOFT System_Devices 1.0") ] class CCM_SystemDevices : SMS_Class_Template { [SMS_Report(TRUE), key] string Name; [SMS_Report(TRUE)] string DeviceID; [SMS_Report(TRUE)] string CompatibleIDs[]; }; [SMS_Report(TRUE)] string HardwareIDs[]; [ SMS_Report (TRUE), SMS_Group_Name ("Computer System"), SMS_Class_ID ("MICROSOFT COMPUTER_SYSTEM 1.0") ] - 12 -
class Win32_ComputerSystemProduct : SMS_Class_Template { [SMS_Report (TRUE), key] string Name; [SMS_Report (TRUE)] string Vendor; }; [SMS_Report (TRUE), key] string Version; [ SMS_Report (TRUE), SMS_Group_Name("PNP DEVICE DRIVER"), SMS_Class_ID("MICROSOFT PNP_DEVICE_DRIVER 1.0") ] class Win32_PnpEntity : SMS_Class_Template { [SMS_Report(TRUE), key] string DeviceID; [SMS_Report(TRUE)] string ClassGuid; [SMS_Report(TRUE)] string Manufacturer; [SMS_Report(TRUE)] string Name; }; [SMS_Report(TRUE)] string PNPDeviceID; [ SMS_Report (TRUE), SMS_Group_Name ("System Enclosure"), SMS_Class_ID ("MICROSOFT SYSTEM_ENCLOSURE 1.0") ] class Win32_SystemEnclosure : SMS_Class_Template { [SMS_Report (TRUE)] string Manufacturer; [SMS_Report (TRUE)] string SerialNumber; } [SMS_Report (TRUE)] string SMBIOSAssetTag; - 13 -
1.5 Walkthroughs The following step-by-step walkthroughs have been created to help you create and deploy driver packages as part of your Windows deployment process. System Center 2012 Configuration Manager System Center 2007 Configuration Manager Microsoft Deployment Toolkit 2012 Microsoft Deployment Toolkit 2010-14 -
System Center 2012 Configuration Manager Driver Integration This System Center 2012 Configuration Manager (SCCM) walkthrough will complete the following steps: Specify Windows deployment solution Discover drivers Driver integration Distribute Packages Configure task sequences Specify Windows Deployment Solution The following are steps to specify the Windows deployment solution. 1. Select Tools>Options or in the global toolbar by clicking. 2. Select Integration. 3. Ensure the Windows deployment solution is set to System Center Configuration Manager. 4. Select Integration>SCCM then complete the form. 5. Click OK to save the changes. Discover Drivers The following are steps to discover machine drivers. 1. Run DMScanner on the hardware platform(s) to be deployed. 2. Click Import Hardware in the Task view. 3. Select DMScanner inventory report then click Next. 4. Click Import a single DMScanner XML file. 5. Specify a path to the DMScanner hardware scan XML file and ensure Search for drivers is selected then click Next. 6. When prompted click Yes to import the machine into the Machine Library. 7. Select the Windows Operating System then click Next. 8. Click Next to search for drivers. 9. Select all available drivers then click Next to download the driver source files. Note: This may take some time. 10. Click Finish. Driver Integration The following are steps to integrate drivers into SCCM. 1. Select Driver Integration in the Task view. 2. Select machine models and driver packs. Note: Windows 8 and Server 2012 driver packs will be disabled for integration unless SCCM 2012 SP1 or above is detected. 3. For the options beneath Select the types of driver to integrate, select Driver package drivers and Software package drivers. - 15 -
Note: Selecting Driver package drivers (INF configured) and/or Software package drivers (command line configured) controls which package types will be integrated into SCCM. 4. Click OK to perform the integration. Distribute Packages Driver Manager will create Driver Packages and Software Packages during the integration process. In order to use the packages in SCCM OS Deployment Task Sequences these packages must be distributed to the appropriate SCCM Distribution Points. The following are steps to distribute packages in SCCM. 1. Right click the appropriate package then select Distribute Content. 2. Complete the wizard to assign the package to the relevant distribution points within SCCM. Configure Task Sequences Once the Integration process has completed update the appropriate OSD Task sequences. - 16 -
System Center 2007 Configuration Manager Driver Integration This System Center 2007 Configuration Manager (SCCM) walkthrough will complete the following steps: Specify Windows deployment solution Discover drivers Driver integration Distribute Packages Configure task sequences Specify Windows Deployment Solution The following are steps to specify the Windows deployment solution. 1. Select Tools>Options or in the global toolbar by clicking. 2. Select Integration. 3. Ensure the Windows deployment solution is set to System Center Configuration Manager. 4. Select Integration>SCCM then complete the form. 5. Click OK to save the changes. Discover Drivers The following are steps to discover machine drivers. 1. Run DMScanner on the hardware platform(s) to be deployed. 2. Click Import Hardware in the Task view. 3. Select DMScanner inventory report then click Next. 4. Click Import a single DMScanner XML file. 5. Specify a path to the DMScanner hardware scan XML file and ensure Search for drivers is selected then click Next. 6. When prompted click Yes to import the machine into the Machine Library. 7. Select the Windows Operating System then click Next. 8. Click Next to search for drivers. 9. Select all available drivers then click Next to download the driver source files. Note: This may take some time. 10. Click Finish. Driver Integration The following are steps to integrate drivers into SCCM. 1. Select Driver Integration in the Task view. 2. Select machine models and driver packs. Note: Windows 8 and Server 2012 driver packs will be disabled for integration unless SCCM 2012 SP1 or above is detected. 3. For the options beneath Select the types of driver to integrate, select Driver package drivers and Software package drivers. - 17 -
Note: Selecting Driver package drivers (INF configured) and/or Software package drivers (command line configured) controls which package types will be integrated into SCCM. 4. Click OK to perform the integration. Distribute Packages Driver Manager will create Driver Packages and Software Packages during the integration process. In order to use the packages in SCCM OS Deployment Task Sequences these packages must be distributed to the appropriate SCCM Distribution Points. The following are steps to distribute packages in SCCM. 1. Right click the appropriate package then select Manage Distribution Points. 2. Complete the wizard to assign the package to the relevant distribution points within SCCM. Configure Task Sequences Once the Integration process has completed update the appropriate OSD Task sequences. - 18 -
Microsoft Deployment Toolkit 2010 Driver Integration This Microsoft Deployment Toolkit 2010 (MDT) walkthrough will complete the following steps: Specify Windows deployment solution Discover drivers Driver integration Distribute Packages Configure task sequences Specify Windows Deployment Solution The following are steps to specify the Windows deployment solution. 1. Select Tools>Options or in the global toolbar by clicking. 2. Select Integration. 3. Ensure the Windows deployment solution is set to Microsoft Deployment Toolkit. 4. Select Integration>MDT then complete the form. 5. Click OK to save the changes. Discover Drivers The following are steps to discover machine drivers. 1. Run DMScanner on the hardware platform(s) to be deployed. 2. Click Import Hardware in the Task view. 3. Select DMScanner inventory report then click Next. 4. Click Import a single DMScanner XML file. 5. Specify a path to the DMScanner hardware scan XML file and ensure Search for drivers is selected then click Next. 6. When prompted click Yes to import the machine into the Machine Library. 7. Select the Windows Operating System then click Next. 8. Click Next to search for drivers. 9. Select all available drivers then click Next to download the driver source files. Note: This may take some time. 10. Click Finish. Driver Integration The following are steps to integrate drivers into MDT. 1. Select Driver Integration in the Task view. 2. Select machine models and driver packs. Note: Windows 8 and Server 2012 driver packs will be disabled for integration unless MDT 2012 or above is detected. 3. For the options beneath Select the types of driver to integrate, select Driver package drivers and Software package drivers. - 19 -
Note: Selecting Driver package drivers (INF configured) and/or Software package drivers (command line configured) controls which package types will be integrated into MDT. 4. Click OK to perform the integration. Configure Task Sequences Once the Integration process has completed update the appropriate OSD Task sequences. - 20 -
Microsoft Deployment Toolkit 2012 Driver Integration This Microsoft Deployment Toolkit 2012 (MDT) walkthrough will complete the following steps: Specify Windows deployment solution Discover drivers Driver integration Distribute Packages Configure task sequences Specify Windows Deployment Solution The following are steps to specify the Windows deployment solution. 1. Select Tools>Options or in the global toolbar by clicking. 2. Select Integration. 3. Ensure the Windows deployment solution is set to Microsoft Deployment Toolkit. 4. Select Integration>MDT then complete the form. 5. Click OK to save the changes. Discover Drivers The following are steps to discover machine drivers. 1. Run DMScanner on the hardware platform(s) to be deployed. 2. Click Import Hardware in the Task view. 3. Select DMScanner inventory report then click Next. 4. Click Import a single DMScanner XML file. 5. Specify a path to the DMScanner hardware scan XML file and ensure Search for drivers is selected then click Next. 6. When prompted click Yes to import the machine into the Machine Library. 7. Select the Windows Operating System then click Next. 8. Click Next to search for drivers. 9. Select all available drivers then click Next to download the driver source files. Note: This may take some time. 10. Click Finish. Driver Integration The following are steps to integrate drivers into MDT. 1. Select Driver Integration in the Task view. 2. Select machine models and driver packs. Note: Windows 8 and Server 2012 driver packs will be disabled for integration unless MDT 2012 or above is detected. 3. For the options beneath Select the types of driver to integrate, select Driver package drivers and Software package drivers. - 21 -
Note: Selecting Driver package drivers (INF configured) and/or Software package drivers (command line configured) controls which package types will be integrated into MDT. 4. Click OK to perform the integration. Configure Task Sequences Once the Integration process has completed update the appropriate OSD Task sequences. - 22 -
2 Configuration 2 Configuration This section contains information about using the Driver Manager console to manage drivers. Tour of the Workspace Introduction to the user interface. Options Changing global settings. Machines View Importing machine inventory and managing drivers. - 23 -
2.1 Tour of the Workspace The Driver Manager user interface consists of the following sections: Menus Global toolbars Window panes Status bar Customising the workspace Keyboard navigation Menus Driver Manager's user interface includes a menu bar at the top of the program window, containing several menu options. File Exit Exits the Driver Manager application. View Toolbars Theme Status Bar Sets the global toolbar icon size (normal or large). Sets user interface theme (black, blue or silver). Toggles display of the status bar. Drivers Import Hardware Driver Integration Cancel Imports hardware inventory from DMScanner output or SCCM inventory server. Integrates drivers into the current deployment solution. Cancels the current operation. Tools Options Update Driver Installer Displays the global options panel. Searches a server path containing SCCM Software Packages or MDT Application Packages, replacing the Driver Installer executable and license. Note: SCCM Packages must be redistributed to Distribution Points. Remove Unused Files Searches the machine library and removes files that are no longer in use. - 24 -
Help Documentation Release Notes ENGL on the Web Register Driver Manager Check for Updates Display Log File About Driver Manager Displays help. Displays release note for Driver Manager. Displays the ENGL web site. Starts product activation where a valid license key can be entered. Forces a check for software and driver analysis rule updates. Displays the Driver Manager log file. Displays the Driver Manager version and license details. Global Toolbar Driver Manager has a single global toolbar ("global" meaning it is always available at the top of the user interface, regardless of the window pane you are working on at the time). Tools in the Global toolbar let you perform tasks for managing import inventory, drivers, options and help. Button / Section Description Imports hardware inventory from DMScanner output or SCCM inventory server. Integrates drivers into the current deployment solution. Cancels an operation. Displays the options panel. Displays help. Window Panes Driver Manager has numerous window panes in the interface that are used for a variety of purposes. - 25 -
Status Bar At the very bottom of the interface is a status bar. The most notable use for the status bar is to see the progress of driver download, analysis, and integration. Customising the Workspace Simply because a window pane is attached to the left or right side of the program window by default, this does not mean it has to stay there. Moving window panes You can move a window pane by clicking the title bar and dragging the window pane where you want it. Floating window panes If you drop the window pane at a random location in the program window or outside the program window boundary. - 26 -
Docking window panes "Docking" a window pane means to "attach it" to a particular part of the program window. To do this, move the floating window pane by clicking in the title bar of the window pane, drag it to the edge where you want to dock it, and drop it on top of an existing window. Hiding window panes In the top-right corner of some window panes, you will see a small button that looks like a pin. If you click this button, the window pane is hidden (or "pinned" to the edge of the program window). However, you can still see the title of the window pane along the edge of the program window. When you hover over the title, the window pane temporarily displays again until you move the mouse off the window pane. Click the button again to "un-pin" the window pane. Close window panes In the top-right corner of some window panes, you will see a small button that looks like a cross. If you click this button, the window pane is closed. Select View>[Window] to display the window pane. Keyboard Navigation The keyboard can be used to navigate between window views. Key Sequence Ctrl + TAB Description Switch between available views. - 27 -
2.2 Options The following Driver Manager options can be configured by selecting Tools>Options or by clicking. Folders Proxy Integration Notifications Updates Logging Folders The following default folder settings are available. Import/Replace Driver Specifies the default folder used when browsing for device drivers. Machine Import Specifies the default folder used when browsing for machine hardware scans created by DMScanner. Machine Library Specifies the folder where imported hardware inventory, driver packs, and downloaded drivers will be stored. Proxy Note: Changing the Machine Library path will cause all content to be moved. This includes machine hardware inventory scans, driver packs, drivers (downloaded and replaced), and custom driver settings. Temporary Workspace Specifies a local folder to be used when analysing and preparing driver and software packages. The following proxy settings are available. Use Internet Explorer Settings Specifies whether Internet Explorer settings will be used. Hostname Specifies the proxy server address. Port Specifies the proxy server port. Username Specifies the proxy username. Password Specifies the proxy password. Integration The following general integration settings are available. Deployment Solution Specifies the Windows deployment solution that Driver Manager will integrate with. Valid options are Microsoft Deployment Toolkit (MDT) or System Center Configuration Manager (SCCM). Enable Log File (Driver Installer) Specifies whether the Driver Installer log file will be enabled. Log Path (Driver Installer) Specifies the Driver Installer log file path (default C:\DriverInstaller.log). The following SCCM integration settings are available. Server Name (Connection) Specifies the name of the SCCM server. Use Alternate Credentials (Connection) Specifies whether alternative credentials are used instead those of the currently logged in user. Username (Connection) Specifies the name of the SCCM Administrator including domain name where appropriate, e.g. LAB\Administrator. - 28 -
Note: The user must have full Administrative rights to SCCM in order to be able to import drivers and create packages. Password (Connection) Specifies the SCCM user password. Driver Path (Target) Specifies the path where the.inf (mini-setup) driver files will be copied to. These files will be added to the SCCM Driver store and will be used to create driver packages in the same location. Note: The path must be accessible to the SCCM server and cannot be the same as the Package target path. Package Path (Target) Specifies the path where software (non-mini-setup) drivers will be copied and packages created. Note: The path must be accessible to the SCCM server and cannot be the same as the Driver target path. File / Folder Exists (Package Creation) Specifies the action to take when copying a file or folder that already exists. Option Prompt Skip copy Copy, do not delete target first Copy, delete target first Action Prompt the user for the action to take. Do not copy the file / folder. Copy the files without deleting the target files first. Note that this may leave files that are no longer required on the target. Delete the target folder before copying files. This will ensure that the target is identical to the source being copied. Package Exists (Package Creation) Specifies the action to take when creating a driver or software package and a package with the same name already exists. Option Prompt Create a new revision Delete and recreate Action Prompt the user for the action to take. A new package will be created with the same name and a revision number appended. The existing package will be deleted and a new package with the same name will be created. Add to existing Use the existing package and attempt to add drivers / software to it. Assign Driver Categories (Package Creation) Specifies whether a driver category shown be assigned to each driver that is imported into the SCCM driver store. If enabled, the category will be set to reflect the machine manufacturer and model information, e.g. "Dell Latitude E6500". Note: If a driver is used by more than one machine type the driver will have multiple categories assigned. Create Manufacturer Folder (Package Creation) Specifies whether a folder for each manufacturer is created for driver and software packages. For SCCM 2012 the manufacturer folder is created beneath the Software Library\Operating Systems\Driver Packages and Application Management\Packages nodes in the SCCM console. For SCCM 2007 the manufacturer folder is created beneath the Operating System Deployment\Driver Packages and Software Distribution\Packages nodes in the SCCM Console. Note: Manufacturer folder will be named using the short version of the manufacturer's name e.g. Dell, HP rather than the long version e.g. Dell Inc., Hewlett-Packard. - 29 -
Add Drivers (Boot media) Specifies whether mass storage or network interface drivers are added to SCCM boot images. When enabled Driver Manager will list mass storage and network interface drivers that are compatible with WinPE and list the Boot Images that are available in SCCM. Option Prompt to add drivers to boot media Add drivers to boot media Don't add drivers to boot media Action Prompt the user for the action to take Display the list of compatible drivers and boot images during the SCCM integration process Do not prompt or add drivers to boot images. Note: Driver Manager will assign the appropriate drivers to the boot image but it will not initiate a distribution of the boot image(s). In order to include the new drivers in the boot image the Update Distribution Points process must be run for each boot image. The following MDT integration settings are available. Path (Deployment Share) Specifies a deployment share that has been previously opened in MDT Deployment Workbench. Use Database Specifies whether the MDT database will be used to populate machine make and model details. Note: These settings must match those specified in the MDT Workbench's Database node. SQL Server Name Specifies the SQL server name. SQL Instance Specifies the SQL instance. Note: This setting is required if using Microsoft SQLExpress for the MDT database. If using Microsoft SQL Server (MSSQL) only specify the instance if is not the default, i.e. MSSQLSERVER. Database Name Specifies the database name. Notifications The following notification settings are available. Machine Exists Specifies whether importing an existing machine manufacturer/model will display a Prompt, silently perform a Merge, or Skip the merge. Machine Import Specifies whether importing a machine displays a Prompt or silently performs the Import. Display a message when driver download completes Specifies whether a message will be displayed following driver download. Display a message when analysis completes Specifies whether a message will be displayed following driver analysis. Set custom properties on unanalysed Specifies whether changing properties on drivers that have not be analysed will display a Prompt, Allow the request, or Deny the request. Updates The following update settings are available. Check for software and driver analysis rule updates Specifies that Driver Manager software and driver analysis rule updates will be checked for on a Daily or Weekly basis. Include BETA Updates Specifies whether pre-release BETA updates will be included. Do Not Check for Updates Specifies that check for updates is disabled. - 30 -
Logging The following log file settings are available. Enable Debug Output Specifies whether debug (verbose) output is written to the status view and log file (DriverManager.log). - 31 -
2.3 Machines View The Machines view contains imported machine hardware inventory and discovered driver packs that can be used with your Windows deployment. The Machine Library is located on the machine where Driver Manager was installed and can be moved by changing the Machine Library path in Options > Folders. To create a deployable driver package, hardware inventory is required for each machine and can be imported into Driver Manager. The hardware inventory scan can be generated by DMScanner or imported from SCCM inventory. Each machine model will appear in the Machines view as follows: Machines>[Manufacturer]>[Model]. The latest drivers for a given machine and Windows operating system platform can be searched for by sending the hardware scan to the ENGL Driver Repository. Once search results have been received by Driver Manager, a Driver Pack for the Windows operating system platform will appear below the machine model in the Machines view. Devices and drivers in the driver pack can be managed from the Driver Pack Properties view. Recommended drivers can be downloaded to the Machines view and if required additional drivers can be manually imported. Analysis can then be performed that opens the driver archive and using analysis rules will determine the best installation method to install the driver. Driver and Software packages can be created from a driver pack. When the software package is deployed as part of your OS deployment Task Sequence, drivers will be installed with the added benefit of real-time hardware compatibility checking for each driver. - 32 -
Navigation Buttons and Identification Icons Button / Element Manufacturer / Machine / Driver Pack Description Indicates hardware inventory has been updated and a new search for drivers is required to refresh the Driver Pack. Typically this occurs after a machine inventory import merge. Identifies an imported machine hardware inventory scan. Identifies a machine Driver Pack. Keyboard Navigation The keyboard can be used to perform some basic tasks. Key Sequence Up / Down Left / Right Delete Application / Context Menu Description Select item above / below. Collapse / Expand selected item. Delete the selected item including child items. Displays context menu for selected item (same as mouse right-click). The following tasks can be performed within the Machines view. Importing SCCM inventory Importing DMScanner inventory Manually adding a machine Renaming a machine model Search for drivers Download drivers Manually add driver file Analyse drivers Integrate drivers Open Folder in Windows Explorer Deleting Importing SCCM Inventory The following are steps to import machine hardware inventory from SCCM into the Machine Library. 1. Do one of the following: Click the Import Hardware button in the Tasks view. OR Right-click the Machines folder in the Machines view and select Import hardware. The Import Drivers Wizard opens. 2. At the Inventory Collection Method page, select SCCM Inventory Import then click Next. - 33 -
Note: The Inventory Collection Method page will only be displayed if the currently configured deployment solution is SCCM 2012 or SCCM 2007. 3. At the SCCM Machine Selection page, do the following: a. Select a manufacturer / model folder in the SCCM Inventory view. b. Select one or more source computers in the Computers view, then right-click the selected computers and select Add. c. Repeat the above steps for all required machine models. Note: If there are no machines in the Computers view then review the pre-requisites for SCCM inventory 4. Click Finish to import the selected machines and close the Import Wizard. 5. Proceed with steps in Searching for Drivers Importing DMScanner Inventory The following are steps to import machine hardware inventory from DMScanner into the Machines view. 1. Do one of the following: Click the Import Hardware button in the Tasks view. OR Right-click the Machines folder in the Machines view and select Import hardware. The Import Drivers Wizard opens. 2. If the Inventory Collection Method page is displayed, select DMScanner Inventory Report then click Next. 3. Select Machine hardware scan then click Next. 4. Do one of the following: Click Import a single DMScanner XML file. OR Click Import all DMScanner XML files in a folder. 5. Select Search for drivers to search and download drivers immediately after import. 6. Click Next. Note: If you are prompted to confirm the import click Yes. To prevent future confirmation prompts from appearing ensure Import without prompting is checked. 7. If Search for drivers was selected continue to the step Searching for drivers, otherwise click Finish to close the Import Wizard. Manually Adding a Machine The following are steps to manually add a machine to the Machine Library 1. Do one of the following: Click the Import Hardware button in the Tasks view. OR Right-click the Machines folder in the Machines view and select Import hardware. The Import Drivers Wizard opens. - 34 -
2. Select Manually create machine. a. Specify the machine Manufacturer and Model. b. Click Finish. Note: You cannot Search for Drivers for a manual machine entry. Drivers can be added using Manually add driver file Renaming a Machine Model The following are steps to rename a machine model. 1. Do one of the following: Right-click the Machines>[Model] and select Rename. OR Select the Machine>[Model] then click the description to edit. Note: To restore the default description perform the rename using an empty string. Searching for Drivers The following are steps to search for drivers for a previously imported hardware inventory scan. 1. Do one of the following in the Machines view: Right-click Machines. OR Right-click Machines>[Manufacturer]. OR Right-click Machines>[Manufacturer]>[Model]. OR Right-click Machines>[Manufacturer]>[Model]>[Driver Pack]. 2. Select Search for Drivers. 3. Click the Windows Operating System down arrow and select a Windows version and platform to search for compatible drivers. 4. Select Download drivers to automatically download all missing drivers after driver searching completes. 5. Click Next. 6. Click Next again to begin the search process. Note: Your driver search request will be sent to an ENGL web server. If this is the first search you have performed since starting Driver Manager, you may notice a delay before the driver list is displayed. The ENGL driver service will return the latest available version of a driver as made available by the manufacturer. 7. If a list of drivers are displayed, select the drivers to download then click Next. 8. Click Finish to close the Import Wizard. Driver Pack's for the Windows operating system and platform will appear below manufacturer models in the Machines view. Drivers will be downloaded if the Download drivers option was selected. - 35 -
Note: There may be devices listed under the No Drivers section in the Driver Pack properties. This does not necessarily mean that a required driver is missing because the device may be handled natively by Windows. If there are no Unknown Devices listed in Windows Device Manager then no further drivers are required. If there are unknown devices then rightclick the device and select Report Issue to notify ENGL that a driver is required. Also review the section below for steps to Manually Add a driver. Download Drivers The following are steps to download available drivers for existing driver packs. 1. Do one of the following in the Machines view: Right-click Machines. OR Right-click Machines>[Manufacturer]. OR Right-click Machines>[Manufacturer]>[Model]. OR Right-click Machines>[Manufacturer]>[Model]>[Driver Pack]. 2. Select Download drivers to download all available drivers. Drivers will download. Note: Drivers that have already been downloaded or disabled will be skipped. To force a driver to be re-downloaded, use the Driver Pack Property View download menu option. Selecting to download drivers from a level in the Machine view that includes multiple manufacturer models and Driver Packs may take many hours to complete. Manually Add Driver File The following are steps to manually add a driver file to a previously imported hardware inventory scan. 1. Do one of the following: Right-click the Machines>[Manufacturer]>[Model]>[Driver Pack] in the Machines view then select Manually add driver file. OR Right-click the Machines>[Manufacturer]>[Model] in the Machines view then select Manually add driver file. Import Wizard opens. 2. Click the Windows Operating System down arrow and select a Windows version and platform to which the driver will be added. Note: If the Windows Operating System down arrow is disabled, continue to the next step. 3. Click the Driver class down arrow and select a driver class matching the driver file being added. 4. Enter a brief Driver description. 5. Enter a Driver version. 6. Click Next. 7. Click the Browse button and select a.7z,.cab,.exe,.msi,.rar, or.zip file containing the driver to import. Use the original driver package as supplied by the OEM or driver manufacturer, do not extract or modify the original package in any way. 8. Click Next. - 36 -
9. At the Import into Machines view prompt, click Yes to import the driver. Driver is imported. 10. Click Finish to close the Import Wizard. Analyse Drivers The following are steps to analyse drivers in an existing driver pack. 1. Right-click the Machines>[Manufacturer]>[Model]>[Driver Pack] in the Machines view then select Analyse drivers. Driver pack analysis will be performed. Integrate Drivers The following are steps to create driver and software packages in the configured deployment solution for an existing driver pack. 1. Do one of the following: In the global toolbar, click or select Driver Integration from the Tasks view to launch the Driver Integration Wizard. a. At the Driver Integration page, select whether the display of driver packs will be sorted by Machine type or Windows version. b. Select the types of driver to integrate, by selecting Driver package drivers and/or Software package drivers. c. Select the driver packs to integrate. OR Note: Windows 8 and Server 2012 driver packs will be disabled unless SCCM 2012 R2, SCCM 2012 SP1, or MDT 2012 is detected. Note: If SCCM 2012 R2 is detected during the creation of Software Packages, client platform requirements for Windows 8.0 will include Windows 8.1, and Windows Server 2012 will include Windows Server 2012 R2. d. Click OK to perform the integration. Right-click the Machines>[Manufacturer]>[Model]>[Driver Pack] in the Machines view then select Integrate Drivers. Warning: An error message will be displayed if SCCM 2012 SP1 or MDT 2012 could not be detected when attempting to integrate Windows 8 or Server 2012 driver packs. Open Folder in Windows Explorer The following are steps to open the folder of previously searched for driver pack. 1. Right-click the Machines>[Manufacturer]>[Model]>[Driver Pack] and select Open Folder in Windows Explorer. Deleting Windows Explorer opens. The following are steps to delete machine models and driver packs from the Machines view. 1. Do one of the following: Right-click the Machines>[Manufacturer]>[Model]>[Driver Pack] and select Delete. OR - 37 -
Right-click the Machines>[Manufacturer]>[Model] and select Delete. OK Right-click the Machines>[Manufacturer] and select Delete. OK Right-click the Machines and select Delete. - 38 -
2.4 Driver Pack Properties View The Driver Pack Properties view includes a list of drivers and the devices each driver services. Devices that have been associated with a driver through a driver search or driver replacement will be listed below the Drivers folder. Devices that do not have an associated driver will be listed below the No Drivers folder. The Driver Pack Properties view can be displayed by selecting a Driver Pack from the Machines view. Navigation Buttons and Identification Icons Button / Element Description Expands all items in the view. Collapses all items in the view. Driver name Indicates the driver has been disabled and will not be included in analysis or driver image creation. Represents a hardware device. Represents a hardware driver. Indicates the driver properties have been modified. Indicates the installation command line has been modified and is different from the command line that driver analysis recommended. Settings Indicates the driver has been analysed to determine the most appropriate installation method. Settings Indicates the driver will be installed using Windows mini-setup hardware discovery. Settings Indicates the driver will always be installed regardless of hardware compatibility. Settings Indicates the driver source file will be extracted and stored in the driver image. Order Driver installation order (software / non-inf drivers). Status No driver file exists in the driver library. Downloaded Imported Replaced Status Indicates the driver was discovered through a driver scan and has been downloaded. Status Indicates an additional driver that has been manually imported. Status Indicates the driver has been replaced with a user supplied file. This status is used for all devices where a driver has been added specifically to it regardless of whether a driver was discovered or not. Keyboard Navigation The keyboard can be used to perform some basic tasks. Key Sequence Up / Down Left / Right Application / Context Menu Description Select item above / below. Collapse / Expand selected item. Displays context menu for selected item (same as mouse right-click). - 39 -
The following tasks can be performed from the Driver Pack properties view. Download driver Replace driver Enabled / Disable driver Analyse driver Properties of a driver Delete driver Report Issue Open Folder in Windows Explorer Download Driver The following are steps to download a driver. 1. Right-click the Drivers>[Driver] in the Properties view then select Download. Driver will download. 2. Click Finish to close the wizard. Replace Driver The following are steps to replace an ENGL discovered driver with another driver. Note: Replacement drivers are always used if they exist regardless of changes to the discovered drivers for the devices they relate to. 1. Do one of the following: Right-click the Drivers>[Driver] in the Properties view then select Replace. OR Right-click the No Drivers>[Device] in the Properties view then select Replace. 2. Click the Driver class down arrow and select a driver class matching the driver file being added. Note: If the Driver Class down arrow is disabled, continue to the next step. 3. Enter a Driver version. 4. Click Next. 5. Click the Browse button and select a.7z,.cab,.exe,.msi,.rar, or.zip file containing the driver to import. 6. Click Next. 7. At the Import into File Library prompt, click Yes to import the driver. Driver is imported. 8. Click Finish to close the Import Wizard. Enable / Disable Driver The following are steps to enable or disable a driver. 1. Right-click the Drivers>[Driver] in the Properties view then select Enable. Driver enabled status will be changed. - 40 -
Note: Performing an integration after disabling all drivers of a specific type (INF or non-inf) in the Driver Pack Property View, will not remove any previously created drivers or packages in MDT or SCCM. Integrated drivers and packages must be manually removed and Task Sequences updated using the SCCM Console or MDT Workbench. For example, if previously a Lenovo W530 Windows 8 (x64) driver pack contained both INF and non-inf drivers, integrating the driver pack into SCCM would create a Driver Package for INF drivers and a Software Package for the non-inf drivers. If all INF drivers were disabled in the Driver Pack Property View, then attempting to intergrate the driver pack into SCCM would cause Driver Manager to skip Driver Package creation as there would be no INF drivers enabled. However, the Driver Package in SCCM will not be removed. Analyse Driver The following are steps to analyse a driver. 1. Right-click the Drivers>[Driver] in the Properties view then select Analyse. Driver analysis will be performed. Properties of a Driver The following are steps to change the properties for a driver. 1. Right-click the Drivers>[Driver] in the Properties view then select Properties. 2. If the driver has not been downloaded or analysed a warning will be displayed. Click Yes to continue or No to exit. Note: It is recommended that you analyse drivers before changing properties. The Custom Driver Processing Properties window opens. 3. Following options are available: Install using setup file instead of adding to Driver Store (Don't use INF file) Select to force driver installation using a custom command line, otherwise the driver will be installed using Sysprep hardware discovery. Do not filter driver based on discovered hardware (always install) Select to force driver to install regardless of whether the hardware is compatible with the driver, otherwise the driver will only be installed on compatible hardware. Do not extract source file (.EXE only) Select to prevent the driver being extracted contents being stored in the driver image. Install order Specifies the driver installation order for software/non-inf drivers. This setting can be used to control the order that drivers are installed. Drivers will be installed in the order of 1-99, followed by drivers which have an install order of 0 (default). Drivers with the same install order will be grouped and installed alphabetically based on the original driver filename. For example, based on the following table the driver installation order will be B, C, D, A, E, F. Driver Install Order Setting A 3 B 1 C 1 D 2 E F 0 (default value) 0 (default value) - 41 -