TPM OOBE Provisioning
This automated test validates that Windows Setup and TPM provisioning happen in the correct order. This test ensures that the TPM does not get provisioned before OOBE finishes, thereby ensuring that the OEM imaging process results in the TPM being in the correct state when a user logs in. The test checks for the TPM provisioning event to be seen within a few minutes of OOBE being completed.
Test details
Associated requirements |
System.Fundamentals.TPM20.TPM20 |
Platforms |
Windows RT (ARM-based) Windows 8 (x64) Windows 8 (x86) Windows Server 2012 (x64) Windows RT 8.1 Windows 8.1 x64 Windows 8.1 x86 Windows Server 2012 R2 |
Expected run time |
~10 minutes |
Categories |
Certification Functional |
Type |
Automated |
Running the test
Before you run the test, review the prerequisites in TPM System Fundamentals Testing Prerequisites.
This test requires that the system be imaged through the OEM manufacturing process (that clears the TPM as part of the deployment). This test should only be run on systems that have gone through an OEM-style imaging process.
Note
While running this test, the time zone should not be changed in OOBE.
To run this test on pre-production devices
Set the HKLM\System\CurrentControlSet\Services\Tpm\WMI\NoAutoProvision registry setting to 1.
Clear the TPM. For more info, see Clear the TPM.
Reinstall the operating system and complete OOBE.
Note
If you forgot to clear the TPM before you reinstall the operating system, you have 5 minutes after OOBE to do this.
The Sysprep OOBE option to prevent an operating system reinstall is not currently supported.
Troubleshooting
For troubleshooting information, see Troubleshooting System Fundamentals Testing.
If this test fails but the other TPM HCK tests pass, the TPM was not cleared before the operating system was reinstalled. If the TPM was not cleared, the status of the TPM will be The TPM is ready for use, with reduced functionality. You can check the status by using the Trusted Platform Module Management console.
This test returns Pass or Fail. To review test details, review the test log from Windows Hardware Certification Kit (Windows HCK) Studio. To provide more information for troubleshooting failures in this test, you can enable tracing of the TPM. Refer to the steps provided under the Troubleshooting section in TCG TPM Integration Test (Manual). Investigations also need log files with name like ‘tpm*.txt’ and console.txt from the ‘Documents’ folder
Related topics