Performs a cross check between the injected product key and the target operating system for edition match. We highly recommend partners use this switch when testing OA 3.0 CBR reporting and hardware hash tolerance.Įxample: OA3Tool.exe /Report /Configfile=C:\OA30\OA3.cfg /LogTrace=C:\OA30\OA3.log The path must be valid for OA3Tool.exe to write to. Logs OA 3.0 hardware hash generation diagnostic tracing data into a file specified in. It is not supported in MDOS.Įxample: OA3Tool.exe /Return /Configfile=C:\OA30\OA3.cfg This command-line option is generally used after the Computer Build Report is generated. For example, you may use this option if you replace a previously injected hardware association with a new association for the same computer. Returns an existing product key for reconciliation. But CBR submission will fail if missing a product key in firmware.Įxample: OA3Tool.exe /Report /Configfile=C:\OA30\OA3.cfg /NoKe圜heck If the machine has no product key in firmware, you can run /report /NoKe圜heck to generate a Hardware Hash for the offline validation. The report file will be sent to the reporting server on the factory floor the next time that you run the /report option when the computer is connected.Įxample: OA3Tool.exe /Report /Configfile=C:\OA30\OA3.cfg In addition, if you run the /report option without a server connection, the resulting report is saved to the same location as the OA3.xml file that your configuration file specifies. ImportantWhen you use the /report command line option together with an internal wireless network adapter, you must run the full operating system. This command-line option is generally used on the factory floor after the product key is injected into the new computer.
After assembly, the OEM-supplied firmware injection tool can inject the OA3.bin file into the firmware of the computer.Įxample: OA3Tool.exe /Assemble /Configfile=C:\OA3\OA3.cfgĬreates the hardware hash value for a specific computer, associates the value with the product key ID, and then sends the OA3.xml file to the reporting server on the factory floor. Retrieves a product key that has a state of Fulfilled from the factory floor database, and then assembles the OA3.bin file and the OA3.xml file for a specific computer. The end user OOBE experience must be consistent with running the OA tool in Audit Mode and not deviate from the standard. When the first prompt appears in the OOBE, press Shift + F10 to open an admin command prompt and run the OA3.0 tool, and then shutdown the machine.
For more information about running the OA 3.0 tool in audit mode, see Audit Mode Overview in the Windows ADK.īy using OOBE mode on the fully assembled client computer. You can run the OA 3.0 tool in two ways:īy using audit mode on the fully assembled client computer. The OA 3.0 tool is a command-line tool that supports assembling, reporting, and returning a unique identifier for the computers on the factory floor.