- Device activation
- Steps to activate devices
- Requirements: Activation
- Turn on user registration with the BlackBerry Infrastructure
- Managing activation passwords
- Specify the default settings for activation passwords
- Allowing users to activate multiple devices with different activation types
- Manually expire an activation password
- 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
- 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
- Activation step-by-step for users
- 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 using a managed Google Play account
- Activate an Android Enterprise device without a Google Play account
- 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
- Activate a Windows 10 Mobile device
- Activate a BlackBerry 10 device
- Activating Android devices
- Activate multiple devices using zero-touch enrollment for Android Enterprise devices
- Activate multiple devices using Knox Mobile Enrollment
- Automatically activate the first BlackBerry Dynamics app on Apple DEP and User Enrollment devices
- 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
- Activating BlackBerry 10 devices using the BlackBerry Wired Activation Tool
- 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.13
- Administration
- Activating devices
- Tips for troubleshooting device activation
- Error 3007: Server is not available
Error 3007: Server is not available
Description
This error can appear on the device during activation because of the following:
- The certificate thatBlackBerry UEMuses to sign the MDM profile that it sends toiOSdevices is not trusted by the device. The user is asked to trust this certificate when they activate the device.
- If you configure a transparent proxy such asBlue Coatand it monitors port 443 for non-standard traffic, theBlackBerry UEM Clientcannot make the required HTTP CONNECT and HTTP OPTIONS calls toBlackBerry UEM.
Possible solutions
Possible solutions include:
- In an on-premises environment, install the root certificate for the CA that issued the certificate thatBlackBerry UEMuses to sign the MDM profile to theiOSdevice. For more information about this certificate, see the on-premises Configuration content.
- Verify that your proxy configuration is not blocking theBlackBerry UEM Clientfrom making HTTP CONNECT and HTTP OPTIONS calls toBlackBerry UEM. For more information, visit support.blackberry.com/community to read article 38644.