Validating OEM Packages

**THESE PAGES HAVE BEEN DEPRECATED **

PLEASE REFER TO https://docs.microsoft.com/en-us/azure/azure-stack/partner/

Overview

New OEM Package should be run when there has been a change to the firmware or drivers for an already validated solution and the goal is to get a new signed OEM Extension package from Microsoft. This run must contain the updated OEM Extension package with the drivers and firmware that have passed Windows Server logo and PCS testing.

Instructions

1. Ensure that the current monthly update has been applied.
2. Check system health status by running Test-AzureStack as described here. Fix any warnings and errors before launching any tests.
3. Go to the VaaS portal and add a new Solution using the "New solution" button or select an existing Solution.
4. Navigate to the "Package Validation" tile and "Start" a new workflow.
   Note: Diagnostic logging must be enabled for validation runs. Instructions on how to enable logging are here.
5. Complete the required fields and click "Submit".
   Note: An OEM Extension package must be specified for every Package Validation run. You should specify the OEM package that was installed on the solution at the time of AzureStack deployment. Instructions for generating the package blob URI are here.
   Note: A JSON with the environment variables must be used to complete the input for required fields for the run to avoid mistakes in data entry. Information on how to create that JSON file is available here.
6. Run the tests.
7. When all tests have completed successfully, send the name of your Solution and Package Validation to vaashelp@microsoft.com to request package signing.

All tests should complete in around 24 hours and with "pass" as the result. If any of the tests "fail", file a bug in MS Collaborate and notify Microsoft by sending an e-mail to the vaashelp@microsoft.com alias.