Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
To set up the device
Plug in to an AC power source the Device Under Test (DUT) and turn it on.
Enter the firmware settings page (e.g., press F2 while booting).
On the firmware settings page, do the following:
Restore all default settings.
Ensure that the DUT is configured to boot using UEFI without CSM.
Install the OEM image to the DUT. If the OEM image is already installed, skip this step.
Running Sysprep specializes on the factory floor and other processes should be part of the OEM deployment process.
Complete the First Boot Experience.
Use <system model>-<hardware stage (EV, DV, or PV) >-<revision number> as the Computer Name (for example, Frabrikam-ModelXYZ-PV-REV1). Always use the same computer name when testing any given model.
For testing, you can use a local admin account instead of a Microsoft account.
Policies for setting up the device
Use wired or OEM-provided network adaptors instead of USB adapters.
If you use local testing with WAC or prepackaged jobs, wired LAN doesn't apply.
If you use WAS, we recommended that you deploy assessments through a wired LAN. If that isn't possible, use wireless.
Don’t enable sharing when connecting to a network.
UEFI should be enabled on all DUTs.
All DUTs should have all signed/certified Windows 8 drivers before you run the assessments.
External devices should not be plugged in unless they are provided with the system.
Testing the device
To test the device
Activate the system using the appropriate product key.
Some operating system components change their behaviors based on some WinSAT metrics. Verify that the WinSAT datastore is populated in the following path:
%WINDIR%\performance\winsat\datastore\
Run Winsat prepop on an elevated command line or follow the deployment guidance.
Run Windows Update and install all driver and Windows updates (even optional ones).
Disable Automatic Updates by selecting Never check updates in the Windows Update settings. You can automate this step by running the following command from an elevated command prompt:
reg "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update" /v AUOptions /t REG_DWORD /d 1 /f
Use Device Manager to verify that the DUT has no problems with drivers or devices.
Investigate and fix all devices marked with a "!".
Download the latest virus definition files and perform a scan using the default antimalware app.
Force execution of IdleTasks once a day (when system is under test) to ensure that no maintenance tasks interfere with ADK assessment execution. Run the following command from an elevated command prompt:
rundll32.exe advapi32.dll,ProcessIdleTasks
Disable Microsoft Store updates, after applying all available updates.
a. Open the Store settings and go to App updates.
b. Set Automatically download updates for my apps to No.
c. You can automate this step by running the following command from an elevated command prompt:
reg add "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsStore\WindowsUpdate" /v AutoDownload /t REG_DWORD /d 2 /f
Enable autologon.
Certain assessments reboot the PC and require the user to log on before continuing the assessment run. Because the assessments are often measuring the boot time, delays caused by the user logging on to the PC can cause unpredictable variance in the metrics.
A best practice is to enable automatic logon for the user account running the assessments. You can configure automatic logon in the registry under the following key:
HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon
Configure the following five values:
Value name Value type Data DefaultUserName REG_SZ <TestUserName> DefaultPassword REG_SZ <LOCALPASSWORD> AutoAdminLogon REG_SZ 1 If the system has access to a timer server, verify the clock has been synchronized with the server time. If the clock time changes during assessment execution, it might cause failures.
Run the following commands to disable Windows system restore to prevent System Restore point creation during the test, which will skew test results:
reg add "HKLM\Software\Microsoft\Windows NT\CurrentVersion\SystemRestore" /v RPSessionInterval /t REG_DWORD /d 0 /f
reg DELETE "HKLM\Software\Microsoft\Windows NT\CurrentVersion\SPP\Clients" /f
Run the following command to disable scheduled hard drive defragmentation:
schtasks /change /tn "Microsoft\Windows\Defrag\ScheduledDefrag" /disable
Verify all .NET compilation targets are up to date:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\ngen.exe executequeueditems
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe executequeueditems
Restart the DUT.