Install.htm - Installation Guide

  • Article

Note  This content applies to the Windows Logo Kit (WLK). For the latest information using the new Windows Hardware Certification Kit (HCK), see Windows HCK User's Guide on the Windows Hardware Dev Center.

Windows Logo Kit Installation Guide

This document provides an overview of the Microsoft Windows Logo Kit (WLK) with Driver Test Manager (DTM) and provides essential installation information. Read this document to learn how to set up your computer(s) before installation, as well as how to complete a manual installation of the Device Test Manager (DTM) Controller, Studio, and Client.

Images displayed throughout these documents are for illustration purposes only, and might appear differently on your screen.

Note   The DTM Controller is currently only supported on the English language version of Microsoft Windows Server 2008 R2 64-bit.

Table of Contents

Legal Information

Release Notes

Overview

DTM Deployment Scenarios

System Requirements

Install the DTM

Install DTM Studio and DTM Client

Appendix: Optional Command-line Pre-Install directions for DTM Controller

Appendix: Command-line options to install DTM Controller

Appendix: Upgrading a DTM Controller

Appendix: Changing a Controller for a DTM Client

Configure DTM Client Kernel Debugger Settings

Supplemental Information

Technical Support

This document is provided for informational purposes only and Microsoft makes no warranties, either express or implied, in this document. Information in this document, including URL and other Internet Web site references, is subject to change without notice. The entire risk of the use or the results from the use of this document remains with the user. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

© 2009 Microsoft Corporation. All rights reserved.

Microsoft, MS-DOS, Windows, Windows NT, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

All other trademarks are property of their respective owners.

To print out the license terms, open the license.rtf file in the DTM folder of the DTM installation media.

Release Notes

Read the release notes for last-minute changes and additions to the DTM. The release notes provide late-breaking information, including last-minute changes to the DTM that could affect driver compatibility among different versions of the Windows operating systems.

Overview

The WLK provides tools and documentation to test, sign, and logo drivers for the following operating systems:

  • Windows 7

  • Windows Server 2008 R2

  • Windows Vista

  • Windows Server 2008

  • Windows XP

  • Windows Server 2003

The WLK includes the Driver Test Manager (DTM). DTM is an application and collection of tools that manage tests for development teams who create Windows hardware, drivers, and validate Windows configurations. DTM provides support for automating Windows-based driver and hardware testing and is directed at those who use the WLK to test, validate, and certify drivers.

DTM is comprised of three installation components:

  1. DTM Controller - The DTM Controller manages tests that are run on available clients. The DTM Controller is installed from the DTM installation media and contains separate installers to install the DTM Studio and DTM Client components. You must install DTM Controller first from the DTM installation media. You can then install DTM Studio and DTM Client.

  2. DTM Studio - You use DTM Studio to select and schedule tests to be run on available clients that are connected to, and controlled by, the DTM Controller computer. You will not see an option to install the DTM Studio from the DTM installation media. Instead you install DTM Studio directly from a shared network location on the DTM Controller.

  3. DTM Client - Each client computer can have a different configuration, appropriate for your testing scenario(s) including different hardware, operating systems, service packs, drivers, and so forth. You will not see an option to install the DTM Client from the DTM installation media. Instead, you install DTM Client directly on your individual test computers from a shared network location on the DTM Controller.

DTM Security Warning

DTM might transmit user account names, domains, and passwords in plain text (unencrypted) through logs sent from clients to their DTM Controller. If you create a custom job in DTM that requires a user account, create a specific user account with only the permissions necessary for the job, with the understanding that the account information will be transmitted in plain text between the client and its DTM Controller.

DTM Deployment Scenarios

There are two scenarios in which you can deploy DTM:

  • In a domain-joined environment. A domain-joined environment is an environment in which a domain controller is present, and all computers on which DTM components will be installed are joined to the domain controller.

  • In a workgroup environment. A workgroup environment is one in which no domain controller is present.

Undocumented deployment scenarios, such as installing DTM Controller on a domain-joined computer and DTM Client on a workgroup-based computer, are not supported.

Supported Domain-joined Deployments and Configurations

If you plan to deploy DTM in a domain-joined environment, you need a minimum of three computers. One is a Windows domain controller, one is the test server on which you install DTM Controller and DTM Studio, and one is a test computer on which you install DTM Client. You must make sure that Microsoft Active Directory is configured and running on the domain controller. Alternately, if you have an additional computer, you can install DTM Studio on it instead of on the test server.

The following diagram shows supported domain-joined deployments and configurations.

The following diagram shows supported workgroup deployments and configurations.

Setup procedure overview

  1. Install Windows Server 2008 R2 64-bit on the intended DTM Controller machine.

  2. Install fresh operating systems on all DTM Studio and all DTM Client computers.

  3. Join all computers to the appropriate domain.

  4. On the DTM Controller, run KitSetup.exe from the DTM installation media, as described in Install the DTM Controller.

    Note  Completing this step using Kitsetup.exe will automatically install .NET Framework 2.0 and Microsoft SQL Server 2008 R2 Express 32-bit.

  5. On the DTM Controller, run KitSetup.exe to install the various logo kits appropriate to your requirements.

  6. On each computer that you want to install DTM Studio on, install Microsoft .NET Framework 2.0.

  7. On each computer that you want to install DTM Studio on, click Start, click Run, type \\ControllerName\DTMInstall\Studio\Setup.exe, and then click OK.

  8. On each computer that you want to install DTM Client on, click Start, click Run, type \\ControllerName\DTMInstall\Client\Setup.exe, and then click OK.

Note  Replace ControllerName with the name of your DTM Controller computer.

Supported Workgroup Deployments and Configurations

If you plan to deploy DTM in a workgroup, you need a minimum of two computers. One is the test server on which you install DTM Controller and DTM Studio, and one is a test computer on which you install DTM Client. You should not install DTM Controller or DTM Studio on any computer that you install DTM Client on.

Setup procedure overview

Note  Do not use the Default Administrator account.

  1. Install Windows Server 2008 R2 64-bit on the intended DTM Controller computer.

  2. Install fresh operating systems on all DTM Studio and all DTM Client computers.

  3. On each computer, create a new user account and add it to the Administrator group.

  4. On each computer, log on with the username you just created in step 3, and enable the Guest account.

  5. On the DTM Controller, run KitSetup.exe from the DTM installation media, as described in Install the DTM Controller.

    Note  Completing this step using Kitsetup.exe will automatically install .NET Framework 2.0 and Microsoft SQL Server 2008 Express 32-bit.

  6. On the DTM Controller, run KitSetup.exe to install the various logo kits appropriate to your requirements.

  7. On the DTM Controller computer, click Start, click Run, type \\ControllerName\DTMInstall\Studio\Setup.exe, and then click OK.

  8. To grant users access to the database, add them to the dtm_DSOwners group in DTM Studio by clicking Tools, Management Console, and then Users.

    Note  Only the account that installs DTM Controller has initial access to add additional users.

    Note  Each unique user must be added one at a time.

  9. On each computer that you want to install DTM Client on, click Start, click Run, type \\ControllerName\DTMInstall\Client\Setup.exe, and then click OK.

Note  Replace ControllerName with the name of your DTM Controller computer.

System Requirements

DTM has the following system requirements.

DTM Controller System Requirements

Note   The DTM Controller is currently only supported on the English language version of Windows Server 2008 R2 64-bit.

Component Minimum Optimum

Processor

Single x86-based processor running in x64 mode, with a speed of 2.0 GHz

Multicore or multiple x64-based processors running in x64 mode, with a speed of 2.0 GHz or faster

System Memory

2 GB main memory

4 GB main memory

Hard Disk Capacity

300 GB. This value is considered a minimum because of the volume of logs that can be generated and their storage requirements.

JBOD array

Network Connection

100 megabits per second (Mbps)

Operating System

x64-based version of Windows Server 2008 R2.

Notes:

  • DTM Controller is not supported on Windows Server 2003, Windows Server 2008, Windows Vista, Windows XP, or Microsoft Windows 2000.

  • DTM Controller is not supported on a Windows Server 2008 R2 installation that has already been set up as a domain controller.

  • DTM Controller is not supported in a virtual PC environment.

 

DTM Studio System Requirements

Component Minimum

Processor

x86-based, or

x64-based architectures

Operating System

  • Windows 7 (all versions) for x86-based or x64-based architectures, or

  • Windows Server 2008 R2 x64-based architectures, or

  • Windows Vista (all versions) for x86-based or x64-based architectures, or

  • Windows Server 2008 for x86-based or x64-based architectures, or

  • Windows XP with Service Pack 2 (SP2) for x86-based or x64-based architectures

  • Windows Server 2003 with Service Pack 1 (SP1) for x86-based, or x64-based, or

Notes:

  • Windows Vista and Windows XP are supported when DTM is deployed in the domain-joined scenario. However, in the workgroup deployment scenario, you must install DTM Studio directly on the DTM Controller.

  • DTM Studio is not supported in a virtual PC environment.

 

DTM Client System Requirements

Component Minimum Optimum

Processor

x86-based, or

Itanium-based, or

x64-based architectures

System Memory

128 MB main memory (for free builds)

256 MB or more (for checked builds)

Operating System

  • Windows 7 (all versions) for x86-based or x64-based architectures, or

  • Windows Server 2008 R2 x64-based, or Itanium-based architectures, or

  • Windows Server 2008 for x86-based or x64-based, or Itanium-based architectures,

  • Windows Vista (all versions) for x86-based or x64-based architectures, or

  • Windows Server 2003 with Service Pack 1 (SP1) for x86-based, x64-based, or Itanium-based architectures, or

  • Windows XP with the latest release Service Pack

  • To test and obtain a Windows Server 2008 logo, you must use Windows Server 2008 Datacenter (x64-based) or Windows Server 2008 for Itanium-based systems (IA-64). x64-based systems may be AMD64 or Intel64. IA64-based systems must be Itanium 2 or later because Windows Server 2008 does not support Itanium 1 (Merced) processors.

Notes:

  • When selecting a computer name for the client, you must choose a unique name with 15 or fewer characters.

  • Windows 2000 is supported for testing -purposes only. There is no logo support for Windows 2000.

  • DTM Client is not supported in a virtual PC environment.

 

Automatically Install the DTM

Use KitSetup.exe to automatically install prerequisite software and then the DTM. When you run KitSetup.exe, you will be presented with a tree-list of components you can install, as shown in the following screen shot.

By using KitSetup.exe, you can change the configuration of your installation of the WLK/DTM, including which logo kits you wish to install or uninstall.

Manually Install DTM Studio and DTM Client

You can only run the DTM Studio and DTM Client installers after the DTM Controller installation has completed successfully.

Follow the procedures below to manually install DTM Studio and DTM Client.

Step 1: Install the DTM Controller

To correctly install the DTM Controller, you must be logged on to the computer as a user who is a member of the local Administrators group, and you must be able to access the DTM installation media from Windows, either locally or through a network.

If, at any time, you encounter difficulties, consult the troubleshooting guide and the release notes.

To install the DTM Controller

The following procedure describes an express installation by using the DTM Controller Setup Wizard. You can manually install DTM Controller from the command line. See Appendix: Command-line options to install DTM Controller for more information about manual installations.

  1. From the automated installer program (KitSetup.exe), select Driver Test Manager, and then click OK.

    Note  If any DTM Pre-install requirements are not detected, they will automatically be installed first (Microsoft .NET 2.0 and Microsoft SQL Server 2008 R2 Express 32-bit).

  2. The End-User License Agreement page appears.

  3. After you have read the software license agreement, click I Agree, and then click OK.

  4. The Microsoft WLK Install Progress dialog box appears.

  5. After the DTM Controller installation is finished, the Microsoft WLK Configuration 100% complete dialog box appears.

  6. Click Finish.

Note   After the Microsoft Driver Test Manager (DTM) Controller has been installed, any logo kit tests that you selected will be installed.

Step 2: Install the Logo Kit(s) you have selected

The DTM installation program will continue to install the logo kit tests that you selected from KitSetup.exe. These may include, for example, the Devices Logo Kit and the Display Logo Kit (if you intended to logo a display product).

The procedure for installing each logo kit is similar to the following:

  1. From the automated installer program (KitSetup.exe), select Devices Logo Kit and Display Logo Kit. The following screen shot of the Logo Kit dialog box shows two logo kits and the Driver Test Manager check boxes selected.

    Note  You may select as few or as many Logo Kits as you want to install or uninstall at any given time.

  2. To start the installation, click OK.

  3. The Microsoft WLK Install Progress dialog box appears.

  4. After the installation has finished, the Microsoft WLK Configuration 100% complete dialog box appears.

  5. Click Finish.

Note   After you have installed the logo kit tests that you selected from KitSetup.exe, you can install DTM Studio and DTM Client.

Step 3: Install .NET Framework 2.0 on DTM Studio

Install .NET Framework 2.0

  1. Open a command prompt and change the directory to the NET2.0 folder on the DTM installation media.

  2. Run the .NET Framework 2.0 Redistributable installation package that is appropriate for your architecture:

    • For x86-based platforms, run Dotnetfx.exe from the X86 subfolder of the DTM installation media.
    • For x64-based platforms, run NetFx64.exe from the X64 subfolder of the DTM installation media.
    • For Itanium-based platforms, run NetFx64.exe from the IA64 subfolder of the DTM installation media.

  3. Accept all of the default selections during installation.

Step 4: Install DTM Studio

To install DTM Studio, the computer must be able to connect to the installation folder that is shared from the DTM Controller computer. Therefore, before you can install DTM Studio, you must have already installed DTM Controller. For more information, see Install the DTM Controller.

  1. Click Start, click Run, and then type \\YourDtmController\DTMInstall\Studio\Setup.exe.

    Note  Replace YourDtmController with the name of the computer on which you installed the DTM Controller. Attempting to install DTM Studio directly from the %programfiles% directory is not supported and may block any future QFE updates.

    The following screen shot of the Run dialog box shows an example of what the path might look like.

  2. Click OK to start the installation.

    The Welcome to the Microsoft Windows Logo Kit - DTM Studio Setup Wizard appears.

  3. To start the wizard, click Next.

  4. The Custom Setup page appears.

  5. To accept the default component and installation location, click Next.

    The Ready to Install page appears.

  6. To begin DTM Studio installation, click Install.

    The Installing Microsoft Windows Logo Kit - DTM Studio page appears.

  7. After the installation of DTM Studio is finished, the Completing the Microsoft Windows Logo Kit - DTM Studio Setup Wizard page appears.

  8. Click Finish. The Office XP Primary Interop Assemblies dialog box appears.

After the Office XP PIA is finished installing, an entry named Windows Logo Kits\Microsoft Driver Test Manager\Studio is added to the list of programs in the Start menu.

Note   If you want to run DTM Studio, you must be added to the Administrators group on the DTM Controller. Otherwise, you will not be able to successfully use DTM Studio.

To add a user to the DTM Controller

  1. Open the Control Panel on the DTM Controller.

  2. Click Administrative Tools.

  3. Click Computer Management.

  4. Expand Local Users and Groups.

  5. Click Groups.

  6. In the right pane, right-click the Users group, and select Add to Group...

  7. In the Users Properties dialog box, click Add.

  8. In the Select Users, Computers, or Groups dialog box, type the user account to add.

Step 5: (Optional): Configure Internet Connection Firewall (ICF)

If you choose to install DTM Studio on a computer other than the DTM Controller, you must configure the Internet Connection Firewall correctly on the DTM Controller, otherwise DTM Studio will be unable to connect to the DTM database.

To configure ICF, complete one of the following tasks on the DTM Controller.

Option 1: Disable ICF on the computer

  1. In the Control Panel, click System and Security, and then clickWindows Firewall.

  2. On the left pane, click Turn Windows Firewall on or off.

  3. Click Turn off Windows Firewall for each selection, and then click the OK.

-Or-

Option 2: Add an exception to ICF

  1. In the Control Panel, click System and Security, and then clickWindows Firewall.

  2. On the left pane, click Advanced settings.

  3. On the left pane under Windows Firewall with Advanced Security on Local Computer, click Inbound Rules.

  4. On the right pane, under Actions, click New Rule. This launches the New Inbound Rule Wizard.

  5. Make sure that Program is selected, and then click Next.

  6. The program path should be selected. Click Browse and browse to the location where SqlServ.exe is located. Usually that is the following location: %ProgramFiles(x86)%\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlservr.exe .

  7. Click OK, and then click OK again.

Step 6: Install .NET Framework 2.0 on the DTM Client

Install .NET Framework 2.0

  1. Open a command prompt and change the directory to the NET2.0 folder on the DTM installation media.

  2. Run the .NET Framework 2.0 Redistributable installation package that is appropriate for your architecture:

    • For x86-based platforms, run Dotnetfx.exe from the X86 subfolder of the DTM installation media.
    • For x64-based platforms, run NetFx64.exe from the X64 subfolder of the DTM installation media.
    • For Itanium-based platforms, run NetFx64.exe from the IA64 subfolder of the DTM installation media.

  3. Accept all of the default selections during installation.

Step 7: Install the DTM Client

To install DTM Client, the client computer must be able to connect to the shared installation folder on the DTM Controller computer. Therefore, before you can install DTM Client, you must have first installed the DTM Controller.

To install DTM Client

  1. Click Start, click Run, and then type \\YourDtmController\DTMInstall\Client\Setup.exe.

    Note  Replace YourDtmController with the name of the computer on which you installed DTM Controller.

    The following screen shot of the Run dialog box shows an example of what the path might look like.

  2. Click OK to start the installation.

    The Welcome to the Microsoft Windows Logo Kit - DTM Client Setup Wizard appears.

  3. To start the wizard, click Next.

  4. The Internet Connection Firewall Agreement page appears.

    Note   If the Internet Connection Firewall Agreement page does not appear, the Windows Software Firewall is not installed. Or, a hardware firewall, or another software firewall is installed on the DTM Controller computer. If another firewall is installed, you must manually open TCP port 1778 to proceed with installation. Refer to the instructions that came with your firewall product to manually open a TCP port. Otherwise, the installation will fail.

  5. Select Yes I will allow a port to be opened, and then click Next.

    The Custom Setup page appears.

  6. To accept the default components and installation location, click Next.

    The Drive Selection page appears.

    Note   DTM Client is designed to identify itself to the controller through the hardware signature. Therefore, having multiple separate installs, even across OS installs, is not supported. If DTM client detects a previous installation of the client, it will use that information in lieu of any specified directories.

  7. Make sure the Use Default Drive check box is selected, and then click Next.

    The Ready to Install page appears.

  8. To begin DTM Client installation, click Install.

    The Installing Microsoft Windows Logo Kit - Client page appears.

    Note  To cancel the installation before it completes, click Cancel.

  9. After the installation of DTM Client is finished, the Completing the Microsoft Windows Logo Kit - DTM Client Setup Wizard page appears.

  10. Click Finish.

Note   After you install and set up DTM Client, the client computer will appear in the Job Monitor window in DTM Studio. You must wait until the client becomes fully registered with DTM Controller before you can see the client appear in the Job Monitor window. This process might take five or more minutes.

Appendix: Optional Command-line Pre-Install directions for DTM Controller

DTM Controller Pre-install: Install Microsoft SQL Server 2008 R2 Express 32-bit

Note   This step is an optional manual step. If you are using Kitsetup for installation, the following steps will be performed automatically for you.

DTM supports Microsoft SQL Server 2008 R2 Express 32-bit, as well as Microsoft SQL 2005 and Microsoft SQL 2008. The Windows Logo Kit (WLK) includes Microsoft SQL Server 2008 R2 Express 32-bit as the default supported SQL engine. DTM is not supported with any other SQL products and only recognizes 32-bit instances of SQL.

To install Microsoft SQL Server 2008 R2 Express 32-bit

  1. Open a command prompt and change the directory to the SQL folder on the DTM installation media.

  2. If the computer has language packs other than English installed, run the following command:

    SQLEXPR_x86_ENU.exe /QUIET /HIDECONSOLE /ACTION=install /FEATURES=SQL,RS /SQLSVCACCOUNT="NT AUTHORITY\SYSTEM" /AGTSVCACCOUNT="NT AUTHORITY\SYSTEM" /ASSVCACCOUNT="NT AUTHORITY\SYSTEM" /RSSVCACCOUNT="NT AUTHORITY\SYSTEM" /ADDCURRENTUSERASSQLADMIN /INSTANCENAME=MSSQLSERVER /SAPWD=p,assword1 /TCPENABLED=1 /NPENABLED=1 /IAcceptSQLServerLicenseTerms=1 /SQLCOLLATION=SQL_Latin1_General_CP1_CI_AS

    Otherwise, run the following command:

    SQLEXPR_x86_ENU.exe /QUIET /HIDECONSOLE /ACTION=install /FEATURES=SQL,RS /SQLSVCACCOUNT="NT AUTHORITY\SYSTEM" /AGTSVCACCOUNT="NT AUTHORITY\SYSTEM" /ASSVCACCOUNT="NT AUTHORITY\SYSTEM" /RSSVCACCOUNT="NT AUTHORITY\SYSTEM" /ADDCURRENTUSERASSQLADMIN /INSTANCENAME=MSSQLSERVER /SAPWD=p,assword1 /TCPENABLED=1 /NPENABLED=1 /IAcceptSQLServerLicenseTerms=1

    Note  Replace AdminPassword with a strong SQL database administrator password. Make sure to include the set of double quotation marks around the password, as the previous command instructs.

For more information about Microsoft SQL Server 2008 R2 Express 32-bit, see the SQL Server 2008 R2 page on MSDN.

To install Microsoft SQL Server 2005 (instead of using bundled SQL Server 2008 R2 Express)

WLK 1.6 is the first release to fully support SQL Server 2008 R2, and it recognizes any pre-installed instance of SQL server 2008 and SQL Server 2008 R2, 32-bit only. If you want to use a pre-installed instance of SQL server 2005 32-bit, you must manually modify the registry to bypass the Kitsetup detection that will otherwise block an attempt to install WLK 1.6.

To do this, follow these steps:

  1. Make sure that the default SQL named instance of “MSSQLSERVER” exists. Refer to the specific SQL instructions on how to check and create this, if necessary.
  2. Manually edit the registry and add the following key: HKLM\SOFTWARE\wow6432Node\Microsoft\Microsoft SQL Server\100\Machines.
  3. Launch Kitsetup normally, select the Logo Kits to install, and complete the Kitsetup installation.

Note  Due to a potential SQL Server 2005 backward compatibility version mismatch between the copy distributed with WLK and the copy that may be preinstalled, we recommend that you uninstall any preinstalled versions of it before launching Kitsetup. To uninstall SQL Server 2005 backward compatibility, click Control Panel, click Uninstall a Program, and then click Uninstall.

Appendix: Command-line options to install DTM Controller

The following table shows ways that you can specify the installation and log file share-names. The share-names are the folders that are created on the DTM Controller during installation. It is from these folders that you later install DTM Client and DTM Studio. Additionally, logs are written to these folders.

Property Description Default value

WTTINSTFS

DTM installation file share name

DTMInstall

WTTINSTDIR

DTM installation directory mapped to file share name

%SYSTEMDRIVE%\Program Files\Microsoft Driver Test Manager\Controller\WTTInstall\

WTTLOGFS

DTM log file share name

DTMLogs

WTTLOGDIR

DTM log directory mapped to file share name

%SYSTEMDRIVE%\Program Files\Microsoft Driver Test Manager\Controller\WTTSystemLogs\

 

The following table shows ways that you can specify information about the log file share user. The log file share user is the account that you create to store logging information.

Property Description Default value

PDUSERNAME

Log file share user name

DTMShareUser

PDDOMAIN

Log file share user name domain

%COMPUTERNAME%

PDPASSWORD

Log file share user password

Randomly generated at installation time

 

The following table shows ways that you can specify information about the installation-user. The installation-user is the account that is created in order to set up and specify the installation and log file share-names.

Property Description Default value

INSTUSERNAME

Installation share user name

DTMInstallUser

INSTMACHINE

Installation computer name where the installation user is created

%COMPUTERNAME%

INSTPASSWORD

Installation user password

Randomly generated at installation time

 

The following table shows ways that you can specify information about the notification-user. The notification-user is the account that DTM Controller uses to communicate with SQL.

Property Description Default value

NOTIFICATIONUSER

Notification user name

DTMServiceAdminUser

NOTIFICATIONDOMAIN

Notification user domain

%COMPUTERNAME%

NOTIFICATIONPASSWORD

Notification user password

Randomly generated at installation time

 

The following table shows miscellaneous options that you can specify during installation of DTM Controller.

Property Description Default value

DBNAME

DTM database name

DTMJobs

DRIVESELECTION

Drive that is used for the WTT directory, using the form "C:\"

WTT is the internal name of the backend infrastructure

DTM

Installation root path (default = %ProgramFiles%\Microsoft Driver Test Manager)

%ProgramFiles%\Microsoft Driver Test Manager

ICFAGREE

Internet Connection Firewall (ICF) exception agreement. Must be ICFAGREE=Yes if ICF is enabled on the system.

"No"

SOURCEINSTALL

Must be SOURCEINSTALL=1 in order to install from command line

"0"

ADDLOCAL

Windows Installer Features. The only featured supported is ADDLOCAL=ALL.

No default value

/l*v %temp%\WLK-Install.log

Enables logging. Without these parameters, no log is created.

No default value

/package

Specifies the location of the MSI installation package

No default value

/qb

Basic installation

/x {ProductGUID}

Uninstall the specified product

 

Installation and Uninstallation Examples

To install either the Logo Kits and/or DTM Controller (Unattended)

  • To install the DTM Controller, use the following command from the root of the DTM installation media:Kitsetup.exe /ui-level express /install {A6E93EA5-52E2-4F16-8AB2-A3A97533FE83}

  • To install the Devices Logo Kit, use the following command from the root of the DTM installation media:Kitsetup.exe /ui-level express /install {EF30275E-5D68-40D2-8AF2-2665AAFCB555}

  • To install the Display Logo Kit, use the following command from the root of the DTM installation media:Kitsetup.exe /ui-level express /install {98EF97A5-C520-498D-8F0F-2C551636E4CC}

  • To install the Network Logo Kit, use the following command from the root of the DTM installation media:Kitsetup.exe /ui-level express /install {8868103C-3527-47FA-A116-84DFD1AE954E}

  • To install the Printing Logo Kit, use the following command from the root of the DTM installation media:Kitsetup.exe /ui-level express /install {A9D61D70-94AD-43FF-B770-B05D4A633C34}

  • To install the System Logo Kit, use the following command from the root of the DTM installation media:Kitsetup.exe /ui-level express /install {14DDB41C-3868-4566-B508-4F20DD649DE4}

  • To install the ALL Logo Kits, use the following command from the root of the DTM installation media:Kitsetup.exe /ui-level express /install {B71A0D52-48C9-45FC-919C-C8F58B009D5C}

    Note  By installing one or all of the Logo kits, you automatically install all prerequisites (DTM Controller, .NET 2.0, SQL), so there is no need to individually install other WLK features.

To uninstall either the Logo Kits and/or DTM Controller (Unattended)

  • To uninstall the DTM Controller, use the following command from the root of the DTM installation media:Kitsetup.exe /ui-level express /remove {A6E93EA5-52E2-4F16-8AB2-A3A97533FE83}

    Note   Removing the DTM Controller will automatically remove all Logo kits that are currently installed.

  • To uninstall the Devices Logo Kit, use the following command from the root of the DTM installation media:Kitsetup.exe /ui-level express /remove {EF30275E-5D68-40D2-8AF2-2665AAFCB555}

  • To uninstall the Display Logo Kit, use the following command from the root of the DTM installation media:Kitsetup.exe /ui-level express /remove {98EF97A5-C520-498D-8F0F-2C551636E4CC}

  • To uninstall the Network Logo Kit, use the following command from the root of the DTM installation media:Kitsetup.exe /ui-level express /remove {8868103C-3527-47FA-A116-84DFD1AE954E}

  • To uninstall the Printing Logo Kit, use the following command from the root of the DTM installation media:Kitsetup.exe /ui-level express /remove {A9D61D70-94AD-43FF-B770-B05D4A633C34}

  • To uninstall the System Logo Kit, use the following command from the root of the DTM installation media:Kitsetup.exe /ui-level express /remove {14DDB41C-3868-4566-B508-4F20DD649DE4}

  • To uninstall the ALL Logo Kits, use the following command from the root of the DTM installation media:Kitsetup.exe /ui-level express /remove {B71A0D52-48C9-45FC-919C-C8F58B009D5C}

To install the DTM Client (Unattended)

\\DtmController\DtmInstall\Client\setup.exe /qb ICFAGREE=Yes

To install the DTM Studio (Unattended)

\\DtmController\DtmInstall\Studio\setup.exe /qb

To uninstall the DTM Client (Unattended)

\\DtmController\DtmInstall\Client\setup.exe /qb /uninstall

To uninstall the DTM Studio (Unattended)

\\DtmController\DtmInstall\Studio\setup.exe /qb /uninstall

Note  Replace DtmController with the name of the computer on which you installed the DTM Controller.

Appendix: Upgrading a DTM Controller

These instructions apply to the WLK version 1.0.c and later.

Note   These instructions do not cover creating a backup of the database before you upgrade the DTM Controller. If you follow only these instructions, any changes you have made to the Jobs, or custom Jobs you have created will be lost forever. For more information about creating a backup of your DTM database, see the DTM Database Options and Maintenance Best Practices Web site.

To remove and replace a DTM Controller

  1. Determine installation password. Before you can upgrade your DTM Controller you must determine the existing DTMInstallUser password. If you do not have the existing password and proceed to upgrade the controller, all DTM clients that are connected to the controller will enter Debug mode and will need to be upgraded manually.

    If you must manually upgrade a DTM Client, type the following at the command prompt on the DTM Client computer:

    \\DtmController\DtmInstall\Client\setup.exe /qb /update ICFAGREE=Yes

    Note  Replace DtmController with the name of the computer on which you installed the DTM Controller.

    If you do not know the password, you can determine it in one of two ways:

    1. On a DTM Client, open Notepad.exe and open %ProgramFiles%\Microsoft Driver Test Manager\Client\WTTMaster.ini.
    2. Next, search for "WTTUPDATEPWD" and make a note of the password.

    -Or-

    On the DTM Controller, run RegEdt32.exe and go to HKLM\Software\Microsoft\WTT\2.2\Setup\InstPassword, and make note of the password.

  2. Uninstall the existing DTM Controller.

  3. Open Control Panel.

  4. Double-click Add/Remove Programs, and click Remove next to Microsoft DTM Controller.

  5. Follow the instructions on the screen to uninstall the current DTM Controller.

  6. Install New DTM Controller.

    In WLK versions 1.0.c and later, you must install the DTM Controller from the command line in order to specify custom setup options. The following sample command line specifies the minimum flags and switches:

    WlkMediaDrive**:\DTM\DTMController.msi /qb SOURCEINSTALL=1 ICFAGREE=Yes INSTUSERNAME="UserName" INSTMACHINE="DomainName" INSTPASSWORD="**UserPassword

    Note  Replace WlkMediaDrive with the drive letter that contains the WLK installation media. Replace UserName, DomainName, and UserPassword (do not remove the quotes that surround these variables) with the information that you obtained from the step one earlier in this section. The full list of command-line installation options is described in the Appendix: Command-line options to install DTM Controller section.

  7. Install and accept EULA.

    After you complete the manual DTM Controller installation, you must accept the End User License Agreement (EULA) manually. You must complete this step before you execute KitSetup.exe, or you will see the following pending setup task: "Remove: Driver Test Manager."

    To accept the EULA, execute the following command line:

    WlkMediaDrive:\EULA.exe I SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\WLK_EULA_{6C2D169E-F1E3-419C-B19F-876A4F5982B3} WLK WlkMediaDrive:\license.rtf

  8. Install the Windows Logo Kit Tests and Content.

    From the installation media, launch KitSetup.exe and continue to install Windows Logo Kit Tests. After the tests have been installed, close KitSetup.exe.

  9. Complete the upgrade process and verify.

    All DTM Client systems that were connected to the previous DTM Controller and had current heartbeats (for example, they were communicating with each other) will upgrade automatically to the latest version of DTM in approximately 20 minutes.

    If you do not want to wait for the automatic installation, you can do one of two things to force the client computer to upgrade.

    1. On each DTM Client computer, run net stop WTTSvc, and then net start WTTSvc.
    2. Reboot the DTM Client computer. This has the same effect as stopping and restarting the DTM Client WTTSvc.

All DTM Studio instances will initiate an automatic upgrade the next time they are started. If DTM Studio is open, you must close and re-open it to initiate the automatic upgrade.

You can view the status of DTM Clients in the Default Pool of your upgraded DTM Studio. You can also determine what version of WLK is running on your DTM Client in the Runtime Version column of the Job Monitor Explorer.

Appendix: Changing a Controller for a DTM Client

To change the controller of a DTM Client

Run the following command on the DTM Client computer to associate it with a different DTM Controller, while maintaining all of the DTM Client's current settings.

\\NewDtmController\DTMInstall\Client\setup.exe /update ICFAGREE=Yes SETTINGS="%SystemDrive%\WTT\JobsWorkingDir\settings.txt"

Note  

  • Replace NewDtmController with the name of the new computer on which you installed DTM Controller.

  • If you installed DTM Client to any drive other than the default drive, you must replace %SystemDrive% with the location that you installed DTM Client to.

The client will no longer appear in any machine pool on the original DTM Controller and will subsequently appear in the default machine pool of the newly associated DTM Controller.

Configure DTM Client Kernel Debugger Settings

During driver development, you might want to debug crashes in the kernel. To do so, you must enable kernel debugging on the development computer.

To enable kernel debugging

From the computer on which you installed the debugger:

  1. Click Start, point to Programs, point to Debugging Tools for Windows, and click Debugging Help.

  2. Click the Search tab in the Debugging Tools for Windows window, type "Kernel-Mode Setup" (including quotes), and click Search.

  3. Read the topic Kernel-Mode Setup.

Supplemental Information

Technical Support

For all support inquiries, visit the Microsoft Support Web site.

Copyright © 2001-2009 Microsoft Corporation. All rights reserved.

Version:

 

 

Build date: 9/14/2012