Surface Dev Center Manager (SDCM) is a tool that utilizes the REST APIs made available by Microsoft Partner Center (a.k.a. Hardware Dev Center) to automate many common tasks for hardware development and maintenance around driver and firmware management.

SDCM enables you to create Attestation and WHQL products, submissions, download the resulting signed packages, and manage shipping labels to release software on Windows Update.

This tool is based on the Hardware Dashboard API. Detailed options are available with the -?, -h or -help option at the command line.

1. Clone the repo
2. Follow the steps here to setup your app to get credentials
3. Edit authconfig.json to the appropriate values after your app was set up
   • Change clientId, tenantId and key to match the values from your app registration
   • You should not have to change the url or urlPrefix
4. Build the project

Please refer to the Hardware Dashboard API documentation for detailed information on each of the settings below. This sample is targeted for a RS4 HLK submission and shipping label.

{
    "createType": "product",
    "createProduct": {
        "productName": "ProductName_HLK",
        "testHarness": "HLK",
        "announcementDate": "2023-01-01T00:00:00",
        "deviceMetadataIds": null,
        "firmwareVersion": "0",
        "deviceType": "external",
        "isTestSign": false,
        "isFlightSign": false,
        "marketingNames": null,
        "selectedProductTypes": {
            "windows_v100_RS4": "Unclassified"
        },
        "requestedSignatures": [
            "WINDOWS_v100_X64_RS4_FULL"
        ],
        "additionalAttributes": null
    }
}

For an Attestation submission, change testHarness to Attestation.

{
    "createType": "submission",
    "createSubmission": {
        "name": "ProductName_HLK_Submission",
        "type":  "initial"
     }
 }

{
    "createType": "shippingLabel",
    "createShippingLabel": {
        "publishingSpecifications": {
            "goLiveDate": "2023-01-01T00:00:00.000Z",
            "visibleToAccounts": [],
            "isAutoInstallDuringOSUpgrade": true,
            "isAutoInstallOnApplicableSystems": true,
            "manualAcquisition": false,
            "isDisclosureRestricted": true,
            "publishToWindows10s": false,
            "additionalInfoForMsApproval": {
                "microsoftContact": "[email protected]",
                "validationsPerformed": "TBD",
                "affectedOems": [
                    "Your Company"
                ],
                "isRebootRequired": true,
                "isCoEngineered": true,
                "isForUnreleasedHardware": true,
                "hasUiSoftware": false,
                "businessJustification": "Driver Update"
            }
        },
        "targeting": {
            "hardwareIds": [
                {
                    "bundleId": "0",
                    "infId": "empty.inf",
                    "operatingSystemCode": "WINDOWS_v100_RS4_FULL",
                    "pnpString": "empty pnp"
                }
            ],
            "chids": [
                {
                    "chid": "guid",
                    "distributionState": "pendingAdd"
                }
            ],
            "restrictedToAudiences": [],
            "inServicePublishInfo": {
                "flooring": "",
                "ceiling": ""
            }
        },
        "name": "ProductName_HLK_ShippingLabel",
        "destination": "windowsUpdate"
    }
}

Note that SDCM will auto-populate and publish all hardware IDs found in a Submission when creating a Shipping Label.

Create a json file 'Create_ProductName_HLK.json' using the Product json example above.

sdcm.exe -create Create_ProductName_HLK.json

This will output a Product ID (PID) if successful

Verify the product was created by listing the details.

sdcm.exe -list product -productid PID

Create a json file 'Create_ProductName_Submission_HLK.json' using the Submission json example above.

sdcm.exe -create Create_ProductName_Submission_HLK.json -productid PID

This will output a Submission ID (SID) if successful

List all the submissions for the product

sdcm.exe -list submission -productid PID

List a specific submission for the product

sdcm.exe -list submission -productid PID -submissionid SID

Make sure the package (.cab or .hlkx) is signed by the Extended Validation Certificate (EV Cert) registered with your Partner Center Hardware Account

sdcm.exe -upload test.hlkx -productid PID -submissionid SID

When everything is ready to start processing the submission, commit it

sdcm.exe -commit -productid PID -submissionid SID

sdcm.exe -wait -productid PID -submissionid SID

sdcm.exe -download hlksigned.zip -productid PID -submissionid SID

See HLKx.ps1 in the Scripts folder.

See Attestation.ps1 in the Scripts folder.

See ShippingLabel.ps1 in the Scripts folder.

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.