- Device activation
- Steps to activate devices
- Requirements: Activation
- Turn on user registration with the BlackBerry Infrastructure
- Managing activation settings
- Specify the default activation settings
- Allowing users to activate multiple devices with different activation types
- Force activation password expiry
- Set an activation password and send an activation email message
- Send an activation email to multiple users
- Allow users to set activation passwords in BlackBerry UEM Self-Service
- Supporting Android Enterprise activations
- Support Android Enterprise activations using managed Google Play accounts
- Support Android Enterprise activations with a Google Workspace domain
- Support Android Enterprise activations with a Google Cloud domain
- Support Android Enterprise devices without access to Google Play
- Program an NFC sticker to activate devices
- Supporting Windows 10 activations
- Supporting Apple User Enrollment for iOS and iPadOS devices
- Supporting Samsung Knox DualDAR
- Enable user notification when a device has been activated
- Creating activation profiles
- Device activation instructions
- Activating Android devices
- Activate an Android Enterprise device with the Work and personal - user privacy activation type
- Activate an Android Enterprise device when BlackBerry UEM is connected to a Google domain
- Activate an Android Enterprise device with the Work and personal - full control activation type using a managed Google Play account
- Activate an Android Enterprise device without access to Google Play
- Activate an Android device with the MDM controls activation type
- Activating iOS devices
- Activate a macOS device
- Activate an Apple TV device
- Activate a Windows 10 tablet or computer
- Activating Android devices
- Configure support for Android zero-touch enrollment
- Activate multiple devices using Knox Mobile Enrollment
- Restricting unsupervised iOS devices
- Import or export a list of approved device IDs
- Activating iOS devices that are enrolled in DEP
- Steps to activate devices that are enrolled in DEP
- Register iOS devices in DEP and assign them to the BlackBerry UEM server
- Assign an enrollment configuration to iOS devices
- Add an enrollment configuration
- Remove an enrollment configuration that is assigned to iOS devices
- Delete an enrollment configuration
- Change the settings for an enrollment configuration
- View the settings for an enrollment configuration that is assigned to a device
- Assign an activation profile to iOS devices
- Remove an activation profile that is assigned to iOS devices
- Assign a user to an iOS device
- Unassign a user from an iOS device
- View the owner of an activated device
- Activating iOS devices using Apple Configurator 2
- Tips for troubleshooting device activation
- Device activation can't be completed because the server is out of licenses. For assistance, contact your administrator.
- Please check your username and password and try again
- Profile failed to install. The certificate "AutoMDMCert.pfx" could not be imported.
- Profile Installation Failed: The new MDM payload does not match the old payload.
- Error 3007: Server is not available
- Unable to contact server, please check connectivity or server address
- iOS or macOS device activations fail with an invalid APNs certificate
- Users are not receiving the activation email
- User details screen is showing more Windows devices activated with UEM than expected
- BlackBerry Docs
- BlackBerry UEM 12.18
- Administration
- Activating devices
- Tips for troubleshooting device activation
- Profile failed to install. The certificate "AutoMDMCert.pfx" could not be imported.
Profile failed to install. The certificate "AutoMDMCert.pfx" could not be
imported.
Description
This error is displayed on an
iOS
device
during activation when a profile already exists on the device.Possible solution
Go to
Settings > General > Profiles
on the device and verify that a profile already exists. Remove the profile and
reactivate. If the issue persists, you might have to reset the device because data
might be cached.