The following reconfiguration has been identified as part of the preparation needed to perform the upgrade to Okta Identity Engine (OIE). Note that additional Okta features may require reconfiguration or be disabled in order to complete the upgrade. This article describes the required steps to upgrade to Okta Identity Engine (OIE) when Okta Mobility Management (OMM) is enabled. The OIE upgrade cannot proceed while OMM is active.

• Okta Mobility Management (OMM)

Okta Mobility Management (OMM) is a deprecated feature from Okta Classic Engine that allowed for mobile device management. This feature is not available in Okta Identity Engine (OIE). Because OMM is incompatible with OIE, it must be disabled before the upgrade can proceed.

Okta Mobility Management - End of Life August 2023

An administrator must disable the Okta Mobility Management (OMM) feature before scheduling the upgrade to Okta Identity Engine (OIE).

1. In the Admin Console, navigate to the OIE Upgrade Hub.

2. Follow the on-screen instructions to disable the OMM feature.

Disabling OMM also disables the following dependent features:

• ENG_OMM_DEVICE_TRUST_ANDROID_DEVICE_CERTIFICATE
• WIFI_OMM_INTEGRATION
• OMM_DEVICE_TRUST_IOS_DEVICE
• OMM_ENROLLMENT_RESTRICTION
• HOSTED_APPSTORE
• ENG_NOT_NOW_ANDROID
• OMM_DEVICE_TRUST_ANDROID_DEVICE
• ANDROID_FOR_WORK
• ENG_OPTIMIZED_MOBILE_DEVICES_AGGREGATOR
• ENG_IOS_USE_ITUNES_STORE_ID
• OMM_DEVICE_TRUST_IOS_DEVICE
• ENG_OPTIMIZED_NATIVE_APPS_PERFORMANCE
• ENG_GENERIC_ENROLLMENTS_CLEANUP
• CERTIFICATE_BASED_EAS
• OMM_ENROLLMENT_RESTRICTION
• VPN_CONFIG
• MOBILE_MIM

Related References

• Okta Mobility Management - End of Life August 2023