Use one of the following methods to run the agent:
Run the BIOS Verification agent using scheduling
To schedule BIOS Verification agent to run at set intervals or to trigger execution by events, see Microsoft Task Scheduler documentation here.
The following table details optional command-line arguments.
| Parameters | Meaning |
|---|---|
| -imagecapture | Copies the captured BIOS image to the default or specified location |
| -export <FolderLocation> | Exports the most recent image to a specified location |
| -exportall -export <FolderLocation> | Exports all images to a specified location. |
| -headless | Suppresses browser result and display results in the Command-Line window |
| -noncefile <filename> | Load the file as a binary file and the contents become the nonce. If the file is larger than 1024 bytes, an ArgumentException error is thrown. |
| -noncestring <nonce> | The <nonce> parameter is a base64 encoded nonce. The string is base64 decoded, and the result becomes the nonce. If the decoded nonce is larger than 1024 bytes, an ArgumentException error is thrown. |
Running the BIOS Verification agent in repeated intervals ensures that devices remain in a protected state. Third-party utilities are commonly used to run and report back on a schedule. It is recommended targeting specific collections of devices to avoid a high volume of noise from unsupported platforms.
It is recommended that you run the BIOS Verification feature with its headless property as SYSTEM on devices to avoid interrupting users while ensuring the proper return codes.
C:\Program Files\Dell\TrustedDevice\Dell.TrustedDevice.Service.Console.exe -headlessAfter running the utility, query %ERRORLEVEL% to return the status of the device in question. The %ERRORLEVEL% return value can be compared against the list of error code definitions in Results, Troubleshooting, and Remediation.
Scheduling is used to automate the collection of BIOS results. Microsoft's Endpoint Configuration Manager custom task sequence can collect status reports for scheduled tasks. For more information about managing the schedule of the task sequence, see https://docs.microsoft.com/en-us/previous-versions/system-center/packs/hh967525(v=technet.10)#BKMK_Mandatory_Assignment.
To limit return results to computers supported by Trusted Device, it is recommended to use a collection that is created with Microsoft Intune. For information about the options to target specific devices, see https://docs.microsoft.com/en-us/mem/configmgr/core/clients/manage/collections/create-collections.
Third-party utilities use similar retrieval mechanisms. For information about PDQ Deploy's options for creating collections, see https://support.pdq.com/knowledge-base/1752-viewing-and-creating-collections-in-pdq-inventory.