Condividi tramite

TCG TPM Integration Test (Manual)

  • Articolo

This test validates that the integration of the Trusted Platform Module (TPM) on the system motherboard meets the BitLocker Drive Encryption feature requirements for Windows.

This test is run after a full boot and exercises the TPM and BIOS base, including the setting of physical presence, taking ownership of the TPM, and ACPI interfaces.

The test will restart the system several times during the test, requiring interaction with the machine to verify physical presence according to the BIOS vendor.

Test details

Associated requirements

System.Fundamentals.TrustedPlatformModule.TPMEnablesFullUseThroughSystemFirmware System.Fundamentals.TrustedPlatformModule.Windows7SystemsTPM

See the system hardware requirements.

Platforms

Windows 7 (x64) Windows 7 (x86) Windows Server 2012 (x64) Windows Server 2008 R2 (x64) Windows Server 2012 R2

Expected run time

~2 minutes

Categories

Certification

Type

Manual

 

Running the test

Before you run the test, review the prerequisites in TPM System Fundamentals Testing Prerequisites.

This test has no additional test parameters.

The test will prompt you with a certificate. Click OK to accept.

Troubleshooting

For troubleshooting information, see Troubleshooting System Fundamentals Testing.

This test returns Pass or Fail. To review test details, review the test log from Windows Hardware Certification Kit (Windows HCK) Studio. You can enable TPM logging to diagnose implementation issues.

To enable TPM logging

  1. Make sure the following resources are installed on the test client.

    • TraceView.exe be available in the execution path. This program is available from the Windows WDK.

    • Windows Symbol Packages for formatting of the log files. The following instructions assume that the debug symbols for the appropriate operating system have been installed to C:\Symbols.

  2. Turn on the TPM driver tracing from the registry. This following will log multiple boot cycles to one log file per boot cycle.

    reg add HKLM\System\CurrentControlSet\Control\WMI\Autologger\Tpm /v Start /t REG_DWORD /d 1 /f
reg add HKLM\System\CurrentControlSet\Control\WMI\Autologger\Tpm /v LogFileMode /t REG_DWORD /d 0x10000004 /f
reg delete HKLM\System\CurrentControlSet\Control\WMI\Autologger\Tpm /v FileMax  
reg delete HKLM\System\CurrentControlSet\Control\WMI\Autologger\Tpm /vFileCounter.

    If you log many boot cycles, you may want to increase the 'MaxFileSize' value (given in MB).

  3. Restart the test client to start logging.

  4. Run your TPM scenario or TPM tests.

To view TPM logs

  1. Open an elevated command prompt.

  2. Change to the log directory: cd %SystemRoot%\System32\LogFiles\WMI

  3. Stop the logging: logman stop tpm -ets

  4. Format the trace file: TraceView -process <tpm.etl> -pdb <SymbolPath>\tpm.pdb\<ID>\tpm.pdb

    Where <tpm.etl> identifies the specific .etl file if FileMax was set in the registry (otherwise, just 'tpm.etl'), <SymbolPath> is the directory to which the symbols were installed (usually 'C:\Symbols'), and <ID> is a subdirectory of the tpm.pdb symbol directory. If there is more than one subdirectory of the tpm.pdb symbol directory, use the one that reports the fewest events as "Unknown".)

    The formatted trace is in the file FmtFile.txt.

To turn off TPM logging

Set the following registry.

reg add HKLM\System\CurrentControlSet\Control\WMI\Autologger\Tpm /v Start /t REG_DWORD /d 0 /f

Note  

When supplying log files to Microsoft, it is recommended you provide the .etl file, to avoid potential loss of information during the formatting process. Also specify the operating system on which the log file was obtained.

 

System.Fundamentals Tests

 

 

Send comments about this topic to Microsoft