The following reconfiguration has been identified as part of the preparation needed to perform the upgrade to Okta Identity Engine (OIE). Note, additional Okta features may require reconfiguration or be disabled in order to complete the upgrade..

Org Summary - Device Trust Desktop Registrations
Complexity Level: Medium

Customers who use client-based Device Trust on Windows and macOS to assess if a device is managed or not.

How does this blocker impact the upgrade to OIE?
Sign-on policies work differently. Post upgrade, the customer should roll out OV (Okta Verify), push Certificates from Okta, and decommission Classic MTLS Device Trust.

Support for migration of Client Based Desktop Device Trust has been added to OIE.  This will keep Windows IWA servers running so Windows can work even though IWA is not supported on OIE. Providing time for customers to deploy OV and the new device context feature after the upgrade to move off the v1 device trust model.

How to remediate this blocker?
What can be done to remove Disqualification? Nothing, we have a migration path built for customer upgrades.

Please refer to the link below for the changes in functionality while the classic device trust platform is enabled in OIE.

It is recommended that the customer work towards deploying Okta Verify to all desktops and implement managed devices on OIE. Once this has been completed the migrated Device platform can be removed from Okta.

Is there additional training or information available to assist with this remediation?
YES, visit Migrate from Device Trust to Okta FastPass FAQ for further information, and Troubleshoot Device Trust after upgrade if encountering errors.