Originally Posted by samharna. How to fix factory reset protection (1) do hard reset (2) setup pone you will notice it doesn't ask for wifi to setup (3) hit the window key 2 or 3 times (provision this device) it will ask for nfc or removable media. Reset Protection is enabled on a device by provisioning UEFI secure boot keys and is a two-step process: Anti-Rollback provisioning - The DBX variable must be updated to contain the hashes for the builds that did not support Reset Protection. Nov 13, 2019 This key may be stored in your Microsoft account, printed or saved as a file, or with an organization that is managing the device. The requirement for a recovery key in these cases is a critical component of the protection that BitLocker provides your data.
-->Reset Protection helps you secure a device in case it is stolen. It must be enabled on the device during manufacturing time.
Reset Protection consists of the following parts:
To turn on Reset Protection, you must configure two secure UEFI variables:
There are two ways to turn on reset protection in your images:
Option 1: Enable it by using oeminput.xml
Adobe acrobat x key generator. On retail devices, you enable Reset Protection by adding the RESET_PROTECTION feature to the OEMInput.xml file. When you include this feature, the device’s UEFI secure boot keys for Reset Protection are provisioned as a scheduled task that will run once at first boot into main operating system and will not run again. For more info on the optional features that are available, see OOptional features for building images.
Note If you’re building a test image, use RESET_PROTECTION_INTERNAL instead.
Option 2: Enable when provisioning secure boot keys
Reset Protection is enabled on a device by provisioning UEFI secure boot keys and is a two-step process:
Anti-Rollback provisioning -- The DBX variable must be updated to contain the hashes for the builds that did not support Reset Protection. Specifically, the sample scripts that create PK, KEK, DB and DBX variables will be modified to add in the DBX variable the list of hashes provided by Microsoft. The list of hashes will be supplied by Microsoft in a file called OEM_RollbackHashes.bin. The DBX variable must be signed with the OEM certificate.
The following excerpt includes the changes to the script that creates the DBX variable:
Reset and Reactivation Protection provisioning -- After setting the DBX variable, you must also set the ANTI_THEFT_ENABLED authenticated variable. The content of this variable will be provided by Microsoft in the OEM_ResetProtection_Enable_Resource.bin file. The name of the variable is ANTI_THEFT_ENABLED and the namespace GUID is 1A597235-6378-4910-9F8B-720FEE9357A3. You can set this in the same way as the secure boot keys.
When you submit an update, Reset Protection should not be included as part of the update. However, when you build image, Reset Protection should be included in the oeminput.xml file. We recommend the following steps to update a retail image with Reset Protection enabled:
When using Reset Protection on a device, the MMOS or bootable WIM files that support this device must be built on a version of the tools that support Reset Protection. We recommend that the version of the device image and the version of MMOS match.
With reverse logistics, you can get information about the status of Reset Protection on a device, such as the device IMEI, or check if Reset Protection is currently enabled on the device. You can also use this to remove Reset Protection if you have the appropriate recovery key for that device. Reverse logistics can help you in refurbishment scenarios where Reset Protection is turned on, but you don’t have the Microsoft Account credentials that are required to turn it off. We’ve provided sample code on how to use reverse logistics in the Portable Devices COM API Sample.
In order to use Microsoft's automated reverse logistics program, organizations need to sign up for an account with the Microsoft Dashboard and perform the following tasks:
Your company may already have an account with the Microsoft Dashboard. In that case, you will need to find the administrator of your account with the Dashboard. To find the administrator, click Administration and then click My Administrators. We recommend adding a reverse logistics manager as an additional administrator so it's easier to approve users' reverse logistics requests. The administrators responsibilities include approving requests to join the company, approving request for permissions, and removing users after they leave the company.For more information, see Manage users and permissions.
If your company does not yet have an account with then Dashboard, here is how to get started:
Make sure you save this certificate and that it is accessible. You will need to install it on multiple computers later in this section. We recommend that you save a copy of the certificate on a thumb drive, or something easily accessible.
After you register your company, add other users who need reverse logistics permission:
For more information about signing in to the Dashboard, see Before you sign in.
mmc
and press ENTER.The next step is to create a client tool on a provisioned workstation to submit reverse logistics requests. You will need to create a third-party app with Microsoft account. The app will use a browser to allow a user to enter credentials using a Microsoft account website. That will grant access to your tool to get the appropriate token to call the Reverse Logistics API. For more information about how to build the app, see Mobile and Windows desktop apps, and use 'dds.reverse_logistics' scope (instead of 'wl.basic') to get the appropriate token.
After your tool has the token, it can call the Reverse Logistics API with that token, your client certificate, and the target IMEI in order to retrieve the recovery key for the target device.
Reverse Logistics API endpoint:
POST https://cs.dds.microsoft.com/Command/ExternalClientCert/AdministrativeUnprotect/%7BPartnerName%7D/%7BDeviceId%7D
{PartnerName} should be replaced with an end-user readable string that will be included in an email to the user whose Microsoft account is protecting the phone.
{DeviceId} should be replaced with a string in one of the following formats (leaving the square brackets and replacing the text inside and including the curly braces):
Include the Microsoft account user token in the “Authorization” header of the request.
The certificate provisioned with the Dashboard for your organization must be used as the client certificate for mutual HTTPS.
Response codes: