System Center Configuration Manager · PDF file1.1 Overview ENGL Driver Manager simplifies the...

ENGL Driver Manager™ 6.0

for

System Center Configuration Manager

Table of Contents

Table of ContentsTable of Contents 3

1 Getting Started 5

1.1 Overview 6

1.2 System Requirements 7

1.3 Installation 9

1.4 Prerequisites 12

1.5 Walkthroughs 16

2 Configuration 21

2.1 Tour of the Workspace 22

2.2 Options 26

2.3 Machines View 30

2.4 Driver Pack Properties View 37

3 Implementation 41

4 Reference 43

4.1 DMScanner 44

4.2 Driver Installer 45

5 Support 46

6 ENGL Software Licence (Version 4) 47

- 3 -

1 Getting Started

1 Getting StartedThis section introduces you to Driver Manager, system requirements, prerequisites and walkthroughs.

n Overview

n System Requirements

n Installation

n Prerequisites

n Walkthroughs

- 5 -

1.1 OverviewENGL Driver Manager simplifies the discovery and deployment of Windows device drivers with Microsoft System Center Configuration Manager (SCCM).

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 10 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 for use in a SCCM OS deployment.

- 6 -

1.2 System RequirementsThe following system requirements must be met in order to use Driver Manager.

n Windows Versions for Administration Machine

n Windows Versions for Driver Searches

n System Center Configuration Manager

Windows Versions for Administration MachineThe following Operating Systems may be used for the Administrative machine. Where a service pack is specified it is the minimum supported version.

n Windows 10

n Windows 8.1

n Windows 8

n Windows 7

n Windows Server 2012 R2

n Windows Server 2012


The following are the minimum supported display settings required to run Driver Manager.

n Resolution 1024 x 768 pixels or higher

n Colour depth 16-bit or higher

Windows Versions for Driver SearchesDriver searches can be performed for the following Windows versions:

n Windows 10

n Windows 8.x

n Windows 7


n Windows Server 2012


System Center Configuration ManagementThe following versions of SCCM are supported for driver integration.

n System Center 1602

n System Center 1511

n System Center 2012 R2 Configuration Manager

n System Center 2012 Configuration Manager


Note: n Windows 10 drivers can only be integrated if Cumulative Update 1 (or above) for System Centre 2012 R2 Configuration

Manager SP1 or System Center 2012 Configuration Manager SP2 is detected.

n Windows ADK for Windows 10 is required on the SCCM server in order to add Windows 10 drivers to boot images.

- 7 -

n Windows 8 and Server 2012 drivers can only be integrated if System Center 2012 Configuration Manager SP1 or above is detected.

For the latest information on supported System Center Configuration Management versions, please visit the compatibility web page.

- 8 -

https://www.engl.co.uk/products/drivermanager/compatibility

1.3 InstallationThis 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.

n Downloading

n Installing

n Upgrading from a previous version

n Welcome Wizard

DownloadingThe 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 6.0 link then click Download.

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.

InstallingThe 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 6.0 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: n Select I Accept the Terms of the License Agreement then click Next.

OR

n Select I Do Not Accept the Terms of the License Agreement then click Next.

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.

UpgradingThe following tasks must be completed to upgrade from a previous version of Driver Manager.

- 9 -

https://www.engl.co.uk/

Warning: Driver Manager 6.0 installation is not supported on Windows XP, Server 2003 or Server 2008 (however, Server 2008 R2 is still supported). Attempts to perform a fresh installation or upgrade on Windows XP, Server 2003 or Server 2008 will cause the installation/upgrade process to fail.

1. Login to the machine with administrative permissions.

2. Run the Driver Manager 6.0 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

Note: If following an upgrade, the Welcome Wizard is displayed, follow the on-screen instructions to complete the wizard.

4. Select Tools > Update Driver Installer to search for SCCM Software Packages and replace the Driver Installer executable and license. SCCM Packages must then be redistributed to Distribution Points.

Welcome WizardThe 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:

Note: During evaluation the machine library can contain a maximum of 2 machines and searching for drivers can be performed a maximum of 5 times.

n Username Specifies your ENGL website username.

Note: If you have not previously registered a username on the ENGL website, click Create Account.

n 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. n Paste in the licence key.

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.

c. Click Next.

d. If licence activation was successful a confirmation message will appear, then click OK.

3. At the Deployment Solution page, for the Windows deployment solution select System Center Configuration Manager, then click Next.

Note: See the integration global options for further details.

4. Specify Connection settings, Target Path and Package Creation settings, then click Next.

Note: See the integration global options for further details.

5. At the Folders page, change default folder paths as required, then click Next.

- 10 -

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.

6. At the Completed page, click Finish.

Driver Manager console starts.

- 11 -

1.4 PrerequisitesThe following prerequisites must be met before using Driver Manager with System Center Configuration Manager:

n Driver Manager requires an Internet connection to search for and download drivers.

Note: Driver source files can also be manually imported.

n Driver Manager can be installed on a client machine or the SCCM server.

Note: The SCCM Console is not required to perform SCCM integration.

n The user credentials used to access the SCCM server must be configured within SCCM an granted appropriate permissions: o For SCCM 2012 or later:

Create an SCCM user under the Administration\Security\Administrative Users folder and assign the Operating System Deployment Manager role.

o For SCCM 2007:

Create an SCCM user under the site Security Rights\Users folder with full rights over Devices, Driver Packages and Packages.

n The user credentials used to access the SCCM server must have full read/write file system permissions to the specified shares.

n The shares used to import drivers and create driver packages must be accessible to the SCCM server and the Driver Man-ager console.

Note: The SMS Provider must have must have full read/write file system permissions on the shares used for drivers and driver packages.

n In order to query the SCCM inventory to import machines into Driver Manager the hardware inventory reporting must be con-figured as follows:

o For SCCM 2012 or later configure the hardware inventory

o For SCCM 2007 update the sms_def.mof

- 12 -

Configuring SCCM 2012 (or Later) Hardware InventoryHardware 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.

- 13 -

Configuring SCCM 2007 Hardware InventoryThe sms_def.mof file must be configured as follows to support importing machines from SCCM 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_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_Group_Name ("Computer System"),

SMS_Class_ID ("MICROSOFT|COMPUTER_SYSTEM|1.0") ]

- 14 -

class Win32_ComputerSystemProduct : SMS_Class_Template

{

[SMS_Report (TRUE), key]

string Name;

[SMS_Report (TRUE)]

string Vendor;

[SMS_Report (TRUE), key]

string Version;

};


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)]


[SMS_Report(TRUE)]

string Name;

[SMS_Report(TRUE)]

string PNPDeviceID;

};


SMS_Group_Name ("System Enclosure"),

SMS_Class_ID ("MICROSOFT|SYSTEM_ENCLOSURE|1.0") ]

class Win32_SystemEnclosure : SMS_Class_Template

{

[SMS_Report (TRUE)]


[SMS_Report (TRUE)]

string SerialNumber;

[SMS_Report (TRUE)]

string SMBIOSAssetTag;

}

- 15 -

1.5 WalkthroughsThe following step-by-step walkthroughs have been created to help you create and deploy driver packages as part of your Windows deployment process.

n System Center 2012 (or Later) Configuration Manager


- 16 -

System Center 2012 (or later) Configuration Manager Driver IntegrationThis System Center 2012 (or later) Configuration Manager (SCCM) walkthrough will complete the following steps:

n Specify Windows deployment solution

n Discover drivers

n Driver integration

n Distribute Packages

n Configure task sequences

Specify Windows Deployment SolutionThe following are steps to specify the Windows deployment solution.

1. Start the ENGL Driver Manager console.

2. Select Tools>Options or in the global toolbar by clicking .

3. Select Integration.

4. Ensure the Windows deployment solution is set to System Center Configuration Manager.

5. Select Integration>SCCM then complete the form.

6. Click OK to save the changes.

Discover DriversThe 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 IntegrationThe following are steps to integrate drivers into SCCM.

1. Select Driver Integration in the Task view.

2. Select machine models and driver packs.

Note: n Windows 10 driver packs will be disabled for integration unless SCCM 2012 R2 SP1 CU1 or above is detected.

n Windows 8 and Server 2012 driver packs will be disabled for integration unless SCCM 2012 SP1 or above is detec-ted.

3. For the options beneath Select the types of driver to integrate, select Driver package drivers (INF configured) and Soft-ware package drivers (command line configured).

4. Click OK to perform the integration.

- 17 -

Distribute PackagesDriver 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 SequencesOnce the Integration process has completed update the appropriate OSD Task sequences.

- 18 -

System Center 2007 Configuration Manager Driver IntegrationThis System Center 2007 Configuration Manager (SCCM) walkthrough will complete the following steps:

n Specify Windows deployment solution

n Discover drivers


n Distribute Packages

n Configure task sequences

Specify Windows Deployment SolutionThe following are steps to specify the Windows deployment solution.

1. Start the ENGL Driver Manager console.

2. Select Tools>Options or in the global toolbar by clicking .

3. Select Integration.

4. Ensure the Windows deployment solution is set to System Center Configuration Manager.

5. Select Integration>SCCM then complete the form.

6. Click OK to save the changes.

Discover DriversThe 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 IntegrationThe following are steps to integrate drivers into SCCM.

1. Select Driver Integration in the Task view.

2. Select machine models and driver packs.

Note: n Windows 10 driver packs will be disabled for integration unless SCCM 2012 R2 SP1 CU1 or above is detected.

n Windows 8 and Server 2012 driver packs will be disabled for integration unless SCCM 2012 SP1 or above is detec-ted.

3. For the options beneath Select the types of driver to integrate, select Driver package drivers (INF configured) and Soft-ware package drivers (command line configured).

4. Click OK to perform the integration.

- 19 -

Distribute PackagesDriver 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 SequencesOnce the Integration process has completed update the appropriate OSD Task sequences.

- 20 -

2 Configuration

2 ConfigurationThis section contains information about using the Driver Manager console to manage drivers.

n Tour of the Workspace Introduction to the user interface.

n Options Changing global settings.

n Machines View Importing machine inventory and managing drivers.

- 21 -

2.1 Tour of the WorkspaceThe Driver Manager user interface consists of the following sections:

n Menus

n Global toolbars

n Window panes

n Status bar

n Customising the workspace

n Keyboard navigation

MenusDriver 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 Sets the global toolbar icon size (normal or large).

Theme Sets user interface theme (black, blue or silver).

Status Bar Toggles display of the status bar.

Drivers

Import Hardware Imports hardware inventory from DMScanner output or SCCM inventory server.

Driver Integration Integrates drivers into the current deployment solution.

Cancel Cancels the current operation.

Tools

Options Displays the global options panel.

Update Driver Installer Searches a server path containing SCCM Software Packages, replacing the Driver Installer executable and license.

Note: n SCCM Packages must be redistributed to Distribution Points.

n Only SCCM packages for supported Windows versions will be updated.

Remove Unused Files Searches the machine library and removes files that are no longer in use.

- 22 -

Help

Documentation Displays help.

Release Notes Displays release notes for Driver Manager.

ENGL on the Web Displays the ENGL web site.

Register Driver Manager Starts product activation where a valid license key can be entered.

Check for Updates Forces a check for software updates, driver analysis rule updates, deployment solution support, and Windows OS driver search support.

Driver Management Statistics Displays driver search usage statistics.

Display Log File Displays the Driver Manager log file.

About Driver Manager Displays the Driver Manager version and license details.

Global ToolbarDriver 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 inventory import, 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 PanesDriver Manager has numerous window panes in the interface that are used for a variety of purposes.

- 23 -

Status BarAt the very bottom of the interface is a status bar. The most notable use for the status bar is to see the current integration type and progress of driver download, analysis, and integration.

Customising the WorkspaceSimply 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.

n Moving window panes You can move a window pane by clicking the title bar and dragging the window pane where you want it.

n Floating window panes If you drop the window pane at a random location in the program window or outside the program win-dow boundary.

n 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.

n 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.

- 24 -

n 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 NavigationThe keyboard can be used to navigate between window views.

Key Sequence Description

Ctrl + TAB Switch between available views.

- 25 -

2.2 Options

The following Driver Manager options can be configured by selecting Tools>Options or by clicking .

n Folders

n Proxy

n Integration

n Notifications

n Updates

n Logging

FoldersThe following default folder settings are available.

n Import/Replace Driver Specifies the default folder used when browsing for device drivers.

n Machine Import Specifies the default folder used when browsing for machine hardware scans created by DMScanner.

n Machine Library Specifies the folder where imported hardware inventory, driver packs, and downloaded drivers will be stored.

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.

n Temporary Workspace Specifies a local folder to be used when analysing and preparing driver and software packages.

ProxyThe following proxy settings are available.

n Use Internet Explorer Settings Specifies whether Internet Explorer settings will be used.

n Hostname Specifies the proxy server address.

n Port Specifies the proxy server port.

n Username Specifies the proxy username.

n Password Specifies the proxy password.

IntegrationThe following general integration settings are available.

n Deployment Solution Specifies the Windows deployment solution that Driver Manager will integrate with.

n Enable Log File (Driver Installer) Specifies whether the Driver Installer log file will be enabled.

n Log Path (Driver Installer) Specifies the Driver Installer log file path (default C:\DriverInstaller.log).

The following SCCM integration settings are available.

n Server Name (Connection) Specifies the name of the SCCM server.

n Use Alternate Credentials (Connection) Specifies whether alternative credentials are used instead those of the currently logged in user.

n Username (Connection) Specifies the name of the SCCM Administrator including domain name where appropriate, e.g. LAB\Administrator.

Note: The user must have full Administrative rights to SCCM in order to be able to import drivers and create packages.

- 26 -

n Password (Connection) Specifies the SCCM user password.

n 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.

n 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.

n File / Folder Exists (Package Creation) Specifies the action to take when copying a file or folder that already exists.

Option Action

Prompt Prompt the user for the action to take.

Skip copy Do not copy the file / folder.

Copy, do not delete target first Copy the files without deleting the target files first. Note that this may leave files that are no longer required on the target.

Copy, delete target first Delete the target folder before copying files. This will ensure that the target is identical to the source being copied.

n 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 Action

Prompt Prompt the user for the action to take.

Create a new revision A new package will be created with the same name and a revision number appended.

Delete and recreate The existing package will be deleted and a new pack-age with the same name will be created.

Add to existing Use the existing package and attempt to add drivers / software to it.

n 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 inform-ation, e.g. "Dell Latitude E6500".

Note: If a driver is used by more than one machine type the driver will have multiple categories assigned.

n Create Manufacturer Folder (Package Creation) Specifies whether a folder for each manufacturer is created for driver and software packages.

For SCCM 2012 (or later) the manufacturer folder is created beneath the Software Library\Operating Systems\Driver Pack-ages 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 Soft-ware 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.

n 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.

- 27 -

Option Action

Prompt to add drivers to boot media

Prompt the user for the action to take

Add drivers to boot media Display the list of compatible drivers and boot images during the SCCM integration process

Don't add drivers to boot media 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.

NotificationsThe following notification settings are available.

n Machine Exists Specifies whether importing an existing machine manufacturer/model will display a Prompt, silently perform a Merge, or Skip the merge.

n Machine Import Specifies whether importing a machine displays a Prompt or silently performs the Import.

n Display a message when driver download completes Specifies whether a message will be displayed following driver down-load.

n Display a message when analysis completes Specifies whether a message will be displayed following driver analysis.

n Set custom properties on unanalysed Specifies whether changing properties on drivers that have not be analysed will dis-play a Prompt, Allow the request, or Deny the request.

UpdatesThe following update settings are available.

n Check for software and driver analysis rule updates Specifies that Driver Manager software updates, driver analysis rule updates, deployment solution support, and Windows OS driver search support will be checked for on a Daily or Weekly basis.

n Include BETA Updates Specifies whether pre-release BETA updates will be included.

n Do Not Check for Updates Specifies that check for updates is disabled.

- 28 -

LoggingThe following log file settings are available.

n Enable Debug Output Specifies whether debug (verbose) output is written to the status view and log file (DriverManager.log).

- 29 -

2.3 Machines ViewThe 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 Task Sequence, drivers will be installed with the added benefit of real-time hardware compatibility checking for each driver.

- 30 -

Navigation Buttons and Identification Icons

Button / Element Description

Manufacturer / Machine / Driver Pack 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 NavigationThe keyboard can be used to perform some basic tasks.


Up / Down Select item above / below.

Left / Right Collapse / Expand selected item.

Delete Delete the selected item including child items.

Application / Context Menu Displays context menu for selected item (same as mouse right-click).

The following tasks can be performed within the Machines view.

n Importing SCCM inventory

n Importing DMScanner inventory

n Manually adding a machine

n Renaming a machine model

n Search for drivers

n Download drivers

n Manually add driver file

n Analyse drivers

n Integrate drivers

n Open Folder in Windows Explorer

n Deleting

Importing SCCM InventoryThe following are steps to import machine hardware inventory from SCCM into the Machine Library.

1. Do one of the following:

n Click the Import Hardware button in the Tasks view.

OR

n 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.

- 31 -

Note: The Inventory Collection Method page will only be displayed if SCCM is the currently configured deployment solution.

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 InventoryThe following are steps to import machine hardware inventory from DMScanner into the Machines view.



OR



2. If the Inventory Collection Method page is displayed, select DMScanner Inventory Report then click Next.

3. Select Machine hardware scan then click Next.


n Click Import a single DMScanner XML file.

OR

n 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 MachineThe following are steps to manually add a machine to the Machine Library



OR



- 32 -

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 ModelThe following are steps to rename a machine model.


n Right-click the Machines>[Model] and select Rename.

OR

n 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 DriversThe following are steps to search for drivers for a previously imported hardware inventory scan.

1. Do one of the following in the Machines view:

n Right-click Machines.

OR

n Right-click Machines>[Manufacturer].

OR

n Right-click Machines>[Manufacturer]>[Model].

OR

n 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.

- 33 -

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 right-click 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 DriversThe following are steps to download available drivers for existing driver packs.

1. Do one of the following in the Machines view:

n Right-click Machines.

OR

n Right-click Machines>[Manufacturer].

OR

n Right-click Machines>[Manufacturer]>[Model].

OR

n 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 FileThe following are steps to manually add a driver file to a previously imported hardware inventory scan.


n Right-click the Machines>[Manufacturer]>[Model]>[Driver Pack] in the Machines view then select Manually add driver file.

OR

n 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.

- 34 -

9. At the Import into Machines view prompt, click Yes to import the driver.

Driver is imported.


Analyse DriversThe 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 DriversThe following are steps to create driver and software packages in the configured deployment solution for an existing driver pack.


n In the global toolbar, click or select Driver Integration from the Tasks view to launch the Driver Integration Wiz-ard.

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.

Note: n Driver packs will only be selectable for integration if the version of SCCM supports the target oper-

ating system.

n During SCCM Software Package creation, 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.

OR

n Right-click the Machines>[Manufacturer]>[Model]>[Driver Pack] in the Machines view then select Integrate Drivers.

Warning: An error message will be displayed if the version of SCCM in use does not support the target operating system. See System Requirements for the latest compatibility information.

Open Folder in Windows ExplorerThe 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.

Windows Explorer opens.

DeletingThe following are steps to delete machine models and driver packs from the Machines view.


n Right-click the Machines>[Manufacturer]>[Model]>[Driver Pack] and select Delete.

OR

- 35 -

n Right-click the Machines>[Manufacturer]>[Model] and select Delete.

OK

n Right-click the Machines>[Manufacturer] and select Delete.

OK

n Right-click the Machines and select Delete.

- 36 -

2.4 Driver Pack Properties ViewThe 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 integ-ration.

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 com-mand line that driver analysis recommended.

Settings Indicates the driver has been analysed to determine the most appropriate install-ation method.

Settings Indicates the driver will be installed using Windows mini-setup hardware dis-covery.

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 Status Indicates the driver was discovered through a driver scan and has been down-loaded.

Imported Status Indicates an additional driver that has been manually imported.

Replaced 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 NavigationThe keyboard can be used to perform some basic tasks.


Up / Down Select item above / below.

Left / Right Collapse / Expand selected item.

Application / Context Menu Displays context menu for selected item (same as mouse right-click).

- 37 -

The following tasks can be performed from the Driver Pack properties view.

n Download driver

n Replace driver

n Enabled / Disable driver

n Analyse driver

n Properties of a driver

n Delete driver

n Report Issue

n Open Folder in Windows Explorer

Download DriverThe 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 DriverThe 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.


n Right-click the Drivers>[Driver] in the Properties view then select Replace.

OR

n 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.


Enable / Disable DriverThe 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.

- 38 -

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 SCCM. Integrated drivers and packages must be manually removed using the SCCM Console.

For example, if previously a Lenovo W530 Windows 10 (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 integrate 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 DriverThe 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 DriverThe 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 (unless disabled in Options). Click Yes to con-tinue 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:

n 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.

n 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.

n Do not extract source file (.EXE only) Select to prevent the driver being extracted.

n 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 ori-ginal 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 0 (default value)

F 0 (default value)

- 39 -

n Command line Enter a command and parameters to install the driver during deployment. The macros %*Driver-Path% and %*DriverFile% can be used which will be substituted during deployment with the driver source path and filename as determined by the analysis process.

4. Click OK.

Custom Driver Processing Properties window closes.

Delete DriverThe following are steps to delete a downloaded or replaced driver.

1. Right-click the Drivers>[Driver] then select Delete.

Driver files will be removed from the File Library.

Report IssueThe following are steps to report an issues to ENGL technical support for a driver or device.


n Right-click the Drivers>[Driver] then select Report Issue.

OR

n Right-click the Drivers>[Driver]>[Device] then select Report Issue.

OR

n Right-click the No Drivers>[Device] then select Report Issue.Report Issue window appears.

2. Click the Issue down arrow and select an issue to report.

3. Enter a Comment describing the issue in detail.

4. If you selected Wrong Driver for the issue, enter a Suggested URL.

5. Enter Full name, Email and Telephone (including country code).

6. Click Save contact details to save your contact details for later Report Issues.

7. Click OK.

8. At the Report Issue Confirmation window click Yes to submit the issue to ENGL technical support.

Reported issue will be sent to ENGL technical support and an incident number will be displayed.

Note: A confirmation email with the incident details will be sent to the specified email address.

9. Click OK to close Report Issue.

Open Folder in Windows ExplorerThe following are steps to open the folder of a previously downloaded driver.

Note: If a driver has been manually imported or replaced then the Open Folder in Windows Explorer menu item will be unavailable.

1. Right-click the Drivers>[Driver] then select Open Folder in Windows Explorer.

Windows Explorer opens.

- 40 -

3 Implementation

3 ImplementationThis section will detail the steps necessary to integrate drivers into System Center Configuration Manager (SCCM) and must be performed in the following order.


n Adding drivers to task sequences

Driver IntegrationDriver Manager will establish the best installation method for each driver.

For drivers that can be installed using Windows hardware discovery (mini-setup):

n Each driver will be imported into the SCCM Drivers store.

n Driver Manager will create a Driver Package for the specified machine model and operating system that contains all relevant drivers within the Drivers store.

For example:

Dell-Latitude-E6500-Win7-x86

For drivers that require an installation process to be run:

n Driver installation source files for each driver will be copied to the specified share on the SCCM server.

n An SCCM Software Package will be created containing all of the driver source files.

For example:

Latitude-E6500-Win7-x86

n A program will be created for the Software Package that runs Driver Installer to install the drivers.

Note: Driver Manager will create one Driver Package (if required) and one Software Package (if required) for each machine model and Windows OS/platform.

The following tasks should be completed.

1. Run the Integration task.

2. Select the required machine models / operating systems then click Next twice.

3. If the Boot Media Add Drivers option is set to Prompt or Add Drivers a. The Add drivers to boot media selection screen will appear.

b. From Select the drivers to add list, select the mass storage and network interface drivers required.

c. From Select the boot media list, select the boot images to update.

d. Click OK.

Adding Drivers to Task SequencesOnce Driver Manager has completed processing drivers you can integrate the drivers into an Operating System Deployment (OSD) Task Sequence.

Note: Driver Manager has the ability to update an existing Driver/Software Package as well as creating a new version of a pack-age. If you update or create new packages with Driver Manager, you must check your Task Sequence to ensure that the right pack-ages are referenced.

You must also ensure that the Driver Packages and Software Packages created by Driver Manager are assigned and distributed to the relevant distribution points within your SCCM infrastructure.

- 41 -

3 Implementation

There are many approaches that could be employed based on your specific task sequence configuration, one of which is documented below.

1. Create a new Group in the Task Sequence within the Install Operating System section.

2. Add an Apply Driver Package step to the group and specify the relevant Driver Package for each machine type.

For example: Dell-Latitude-E6500-Win7-x86

Note: The task sequence may contain an Apply Device Drivers task. To avoid driver conflicts this should be disabled or removed when using the Apply Driver Package method suggested above.

3. To ensure that the driver package is only applied to the required machine type:

On the Options page of the Apply Driver Package step add a Query WMI condition and specify a WMI query.

For example: SELECT * FROM Win32_ComputerSystem WHERE Manufacturer LIKE "DELL%" AND Model LIKE "Lat-itude E6500%"

Note: Review the machine properties view for a full list of the WMI classes and properties that are available for a given model. Depending on the machine manufacturer, different WMI classes are used to store machine product codes and descriptions. For example, Lenovo use the WIN32_ComputerSystemProduct class to store the ThinkPad W530 'friendly' name, which requires the following query:

SELECT * FROM Win32_ComputerSystemProduct WHERE Vendor LIKE "LENOVO%" AND Version LIKE "ThinkPad W530%"

4. Create a new Group in the Task Sequence within the Setup Operating System section.

5. Add an Install Package step to the group and specify the relevant Software Package.

For example: DELL Latitude-E6500-Win7-x86

6. To ensure that the driver package is only applied to the required machine type:

On the Options page of the Install Package step add a Query WMI condition and specify a WMI query.

For example: SELECT * FROM Win32_ComputerSystem WHERE Manufacturer LIKE "DELL%" AND Model LIKE "Lat-itude E6500%"

Note: Review the machine properties view for a full list of the WMI classes and properties that are available for a given model. Depending on the machine manufacturer, different WMI classes are used to store machine product codes and descriptions. For example, Lenovo use the WIN32_ComputerSystemProduct class to store the ThinkPad W530 'friendly' name, which requires the following query:

SELECT * FROM Win32_ComputerSystemProduct WHERE Vendor LIKE "LENOVO%" AND Version LIKE "ThinkPad W530%"

Note: Driver Manager will put the Manufacturer and Model information into the Comment field of both the Driver Package and Soft-ware Package for reference.

- 42 -

4 Reference

4 ReferenceThis section contains information on the following Driver Manager utilities.

n DMScanner

n Driver Installer

- 43 -

4.1 DMScannerDMScanner is a standalone utility that performs a hardware inventory scan on the local machine and outputs the results to an XML file that can be imported into Driver Manager.

Path

<InstallationPath>\DMScanner\<Platform>\DMScanner.exe

Usage

Parameter Description

/? Displays usage.

/log[:<path>] Enables log file (default "dmscanner.log").

/scan[:[wmi | no-wmi]] Specifies whether WMI scanning is enabled (default "wmi").

/target:<path> Specifies the target XML path that will contain the hardware inventory scan results (default "dmscanner-[vendor]-[Model].xml").

/unattend Specifies that DMScanner should be run silently.

Example

REM Run DMScanner silently using defaults

dmscanner.exe /unattend /log

- 44 -

4.2 Driver InstallerDriver Installer is a standalone utility that automates the installation of Windows drivers by processing a configuration file created by Driver Manager. During Driver Manager 'analysis' and 'integration' phases, a DriverInstaller.dat file is created that contains hardware compatibility and installation settings for each driver. This file is created by Driver Manager based on driver analysis and custom driver properties and must not be modified.

During deployment, Driver Installer will perform a hardware inventory scan and install drivers which are compatible with the current hardware. This ensures that machines of the same make and model which contain different hardware will only attempt to install valid drivers. This option can be disabled by changing the custom driver property Do not filter driver based on discovered hardware before integrating drivers and may be required for some devices which do not exist until the driver is installed.

Path

<InstallationPath>\DriverInstaller\<Platform>\DriverInstaller.exe

Usage

Parameter Description

/log[:<path>] Enables log file (default "C:\DriverInstaller.log").

RemarksDriver Installer cannot be used to install INF based drivers.

Example

REM Run Driver Installer with log file enabled

driverinstaller.exe /log

- 45 -

5 Support

5 SupportWalkthroughsStep-by-step guides to common deployment scenarios are included in the Walkthroughs section of these help pages.

KnowledgebaseThe ENGL Knowledgebase includes useful information and examples which have been compiled by ENGL consultants whilst working on customer engagements. Search the Technical Information Documents in the ENGL Knowledgebase for more details.

Reporting Driver IssuesOccasionally there may be issues with a driver, for example, the file downloaded is not correct or it fails to deploy correctly. These issues may be reported directly by right-clicking on the device in question in the driver pack property view and selecting Report Issue. This will display a form with pre-filled information and other fields for more details to be supplied. Please supply as much information as possible, for example, if an incorrect driver URL has been retrieved please supply the valid URL where possible. Depending on the nature of your issue an ENGL support engineer may contact you for further information.

Support IncidentsLicensed customers with an active maintenance agreement can log a support incident which will be answered by one of our engineers.

Contact ENGLIf you are unable to access the news servers or log an incident or you have other difficulties please send an email to the ENGL Support Team at [email protected]. Please provide as much information as possible when you email, including the product name, version, and details of your server and workstation environment.

Alternatively visit our web site for full contact details at www.engl.co.uk.

- 46 -

https://www.engl.co.uk/support/knowledgebase

https://www.engl.co.uk/myengl

mailto:[email protected]

https://www.engl.co.uk/aboutus

6 ENGL Software Licence (Version 4)

6 ENGL Software Licence (Version 4) BEFORE YOU USE AND/OR DOWNLOAD ENGL DRIVER MANAGER (“THE SOFTWARE”), CAREFULLY

READ THE TERMS AND CONDITIONS OF THIS LICENCE. BY USING AND BY DOWNLOADING THE

SOFTWARE YOU ARE CONSENTING TO BE BOUND BY AND ARE BECOMING THE LICENSEE TO

THIS LICENCE. IF YOU DO NOT AGREE TO ALL OF THE TERMS OF THIS LICENCE, DO NOT

USE THE SOFTWARE.

A. PROPERTY OF LICENSOR:

You may obtain a copy of the Software product by downloading it remotely from

our server. The copyright, database rights and any other intellectual property

rights in the programs and data which constitute this Software product (‘the

materials’) are and remain the property of the Licensor (‘the Licensor’). You

are licensed to use them only if you accept all the terms and conditions set

out below.

B. LICENCE ACCEPTANCE PROCEDURE:

By installing and using this software, you indicate acceptance of this

licence agreement and the limited liability set out in this licence agreement.

Such acceptance is either on your own behalf or on behalf of any corporate

entity which employs you or which you represent (‘corporate licensee’). In this

licence agreement, ‘you’ includes both the reader and any corporate licensee.

C. LICENCE REJECTION PROCEDURE:

If you do not accept these terms and conditions, you should uninstall this

software and not attempt to use it.

TERMS AND CONDITIONS OF LICENCE AGREEMENT

1. OWNERSHIP OF MATERIALS AND COPIES

The Materials and related documentation are copyrighted works of authorship.

The Licensor retains ownership of the Materials and all subsequent copies of

the Materials, regardless of the form in which the copies may exist. This

licence is not a sale of the original Materials or any copies, particularly,

(but not by way of limitation) not a sale of the Software or its source code.

2. LICENCE

Provided that you have paid the applicable licence fee and adhere to the terms

and conditions of this licence, the Licensor grants to you a limited,

- 47 -


non-exclusive licence for the duration of the Runtime to:

2.1 Use the Materials for use on only as many single computer systems

(whether owned, leased and/or controlled by you or any member of your

corporate group, which expression includes Corporate Licensee,

Corporate Licensee’s majority-owned subsidiaries, any parent company

having a majority-owned interest in Corporate Licensee, and such

parent’s majority-owned subsidiaries) as you have purchased licenses

for;

2.2 Make copies of the Materials after a licence has been purchased, for

back up, archival or other security purposes, as follows:

One (1) copy of Materials for each licence purchased;

One (1) copy of Materials for back up;

One (1) copy of Materials for disaster recovery purposes;

Provided always that they contain the same copyright materials as

original Materials purchased. For the avoidance of doubt, where the

materials are licensed at no fee for evaluation, you shall not have a

right to make copies of the materials for any purpose.

3. LICENCE RESTRICTIONS

You may not use, copy, modify or transfer the materials (including any

related documentation) or any copy, in whole or in part, except as

expressly provided for in this licence. If you transfer possession of

any copy of the materials to another party except as provided above,

your licence is automatically terminated. You may not translate,

reverse engineer, decompile, disassemble, modify or create derivative

works based on the materials, except as expressly permitted by the law

of this agreement. You may not vary, delete or obscure any notices of

proprietary rights or any product identification or restrictions on or

in the materials.

4. NO TRANSFER

The materials are licensed only to you for use on only so many single

computer systems as you are licensed for. You may not rent, lease,

sublicence, sell, assign, pledge, transfer or otherwise dispose of the

materials, on a temporary or permanent basis, without the prior written

consent of the Licensor.

5. UNDERTAKINGS

- 48 -


You undertake to:

5.1 ensure that, prior to use of the Materials by your employees or agents,

all such parties are notified of this licence and the terms of this

Agreement;

5.2 reproduce and include our copyright notice (or such other party’s

copyright notice as specified on the Materials) on all and any copies

of the Materials, including any partial copies of the Materials;

5.3 hold all drawings, specifications, data (including object and source

codes), Software listings and all other information relating to the

Materials confidential and not at any time, during this licence or

after it’s expiry, disclose the same, whether directly or indirectly,

to any third party without the Licensor’s consent;

5.4 supervise and control, at all times, use of the Materials to ensure

that the Materials are used in accordance with the terms and

conditions of the Licence including specifically:

(i) ensure that your employees, agents and other parties who will

use the Software are notified of, and adhere to, the terms of

this Licence prior to such employee, agent or party using the

same;

(ii) maintain accurate and up-to-date records of the number and

location of all copies of the Software;

(iii) not display the Software on the bulletin board, FTP site,

worldwide website, chat room or by any other means;

(iv) not to use the Software for immoral illegal or any other purpose

which may be determined threatening, abusive or harmful including

but not limited to the creation or transmission of any virus,

worms, trojan horse, cancel bots or other destructive or

contaminating programs.

6. LICENCE FEE

The Licence fee, payable in respect of the Runtime and per computer system may

be varied from time to time and is published on the website at www.engl.co.uk.

The Licence fee is payable to ENGL by direct bank transfer to the Licensor’s

account, or by cheque.

7. NO WARRANTIES

- 49 -


The Software is provided "as is" without any warranty of any kind either

express or implied including but not limited to the implied warranties of

merchantability, fitness for a particular purpose, title and non-infringement.

The Licensor does not warrant that the Software will be error-free or that such

errors will be corrected and you are solely responsible for all costs and

expenses associated with rectification, repair or damage caused by such errors.

The Licensor does not warrant that the materials will meet your requirements

that its operation will be uninterrupted or error free. Exclusion of warranties

may not be valid in certain jurisdictions however, the only applicable laws

under which this licence shall be construed are the laws of England and Wales.

8. EXCLUSION OF LIABILITY

8.1 Except in respect of personal injury or death caused directly by the

negligence of the Licensor, in no event will the Licensor be liable to

you for any damages, including any lost profits, lost savings, loss of

data or any indirect, special, incidental or consequential damages

arising out of the use of or inability to use such materials, even if

the Licensor has been advised of the possibility of such damages.

Nothing in this agreement limits liability for fraudulent

misrepresentation.

8.2 In the event the Licensor incurs any liability whatsoever, such

liability is limited to the licence fee paid by you for the Software

(except for death or personal injury arising from the Licensor’s

negligence).

9. YOUR STATUTORY RIGHTS

This licence gives you specific legal rights and you may also have other rights

that vary from country to country. Some jurisdictions do not allow the

exclusion of implied warranties, or certain kinds of limitations or exclusions

of liability, so the above limitations and exclusions may not apply to you.

Other jurisdictions allow limitations and exclusions subject to certain

conditions. In such a case the above limitations and exclusions shall apply to

the fullest extent permitted by the laws of such applicable jurisdictions. If

any part of the above limitations or exclusions is held to be void or

unenforceable, such part shall be deemed to be deleted from this Agreement and

the remainder of the limitation or exclusion shall continue in full force and

effect. Any rights that you may have as a consumer (i.e. a purchaser for

private as opposed to business, academic or government use) are not affected.

10. TERM

- 50 -


The licence is effective until terminated. You may terminate it at any time by

destroying the Materials together with all copies in any form. It will also

terminate upon receipt of written notice from the Licensor

(i) if you are in material breach of any material term or condition of this

Agreement and fail to remedy the same within 21 days of despatch of a notice

to you specifying the breach and requiring its remedy.

(ii) The License will automatically renew at the end of the Runtime (12 months)

on receipt by the Licensor of the applicable License Fee for the following

Runtime period. Should the applicable License Fee not be received by the Licensor

the License will automatically terminate at the end of the current Runtime.

(iii) The Licence will automatically terminate without further notice after a

period of 14 days from your acceptance of the Licence in the event that this

Licence is for evaluation purposes and at no fee.

(iv) You agree, upon termination on any grounds, to destroy the Materials together

with all copies in any form.

11. MAINTENANCE

In the event that You have purchased Upgrade Protection and Maintenance for the

Licensed Materials from the Licensor you also accept the Licensor’s

Maintenance Terms and Conditions, a copy of which is available on request.

12. GENERAL

12.1 You agree that the Licensor shall have the right, after supplying

undertakings as to confidentiality, to audit any computer system on

which the Materials are installed in order to verify compliance with

this Software licence.

12.2 Each party hereby irrevocably agrees that the courts of England and

Wales shall have exclusive jurisdiction to resolve any controversy or

claim of whatever nature arising out of or in relation to this

Agreement and the place of performance of this Agreement shall be

England that the laws of England shall govern such controversy or

claim.

12.3 This Agreement constitutes the complete and exclusive statement of the

Agreement between the Licensor and you with respect to the subject

matter of this agreement and supersedes all proposals, representations,

understandings and prior agreements, whether oral or written, and all

other communications between us relating to that subject matter.

- 51 -


12.4 Any clause in this Agreement that is found to be invalid or

unenforceable shall be deemed deleted and the remainder of this

Agreement shall not be affected by that deletion.

12.5 Failure or neglect by either party to exercise any of its rights or

remedies under this Agreement will not be construed as a waiver of that

party’s rights nor in any way affect the validity of the whole of part

of this Agreement nor prejudice that party’s right to take subsequent

action.

12.6 This Agreement is personal to you and you may not assign, transfer,

sub-contract or otherwise part with this Agreement or any right or

obligation under it without the Licensor’s prior written consent. The

Materials may only be transferred to another party if the original and

all copies (including back-ups) of the Materials and this Licence are

transferred permanently at no charge to the proposed new licensee and

such party agrees to be bound by all the terms of this Licence and

PROVIDING ALWAYS that the Licensor has agreed to the transfer in

writing in advance of the transfer. You remain liable for any breach of

this Licence by any new licensee if any transfer is attempted without

the consent of the Licensor. Upon such transfer the Licensor may

retain NO copies of the Software or documentation.

- 52 -

Date post:	06-Mar-2018
Category:	Documents
Upload:	phungdiep
View:	220 times
Download:	5 times