Alarm List
This is the list of alarms displayed under [LOG] → [ALARM] in the admin console.
| Displayed Message | Description | Action | Severity |
|---|---|---|---|
| The device has been withdrawn | Occurs when a managed device is withdrawn and removed from BizMobile Go! management. | No action is needed if this is the result of an Withdraw operation by an administrator.Click the trash can icon in the Action column of the alarm list to delete the device information.You can check whether the withdrawal was performed by an administrator or by the device user in "Reason for Withdrawal" on the device detail screen. Reason categories: Request from administrator / Operation on the device / Re-enrollment performed If the withdrawal was performed by an administrator, you can check the operator in the log for up to 90 days after the operation. | Warning |
| The device was re-enrolled with a different identifier | Occurs when the same device is registered twice with different identifiers. | No action is needed if this is the result of an intended enrollment operation. The previous device information is withdrawn immediately afterward, so follow your operating procedures, such as deleting the withdrawn data. After checking, you can delete the alarm by clicking the trash can icon in the Action column of the alarm list.If the result was not intended by the administrator, you need to take action such as checking the situation with the device user. | Warning |
| No response from the device | Occurs when the number of consecutive days without confirmed communication with the device exceeds the set value.
The set value is managed by
| If the device is simply powered off, no action is needed. As long as the device enrollment is valid, device management resumes when communication with the managed device is restored. The device may have been withdrawn. If you are not sure whether the enrollment is valid, connect the managed device to the network and check whether this notification disappears. If you no longer need to manage this device, delete it. To change the set value, use the admin console. - SETTING → Unit Detail → Duration Change of "Not Responding" | Major |
| The device token has expired | Occurs when the token in use has expired at the time the server sends a push notification to the device. | In this case, the device must be re-enrolled. | Warning |
| The device enrollment has expired | Occurs when the device enrollment expiration date has passed. | Click the edit icon in the Action column of the alarm list to jump to the device edit screen, where you can extend the enrollment expiration date.You also need to take action such as reminding the device user to enroll. | Minor |
| The device cannot be enrolled because it violates the device enrollment restrictions | Occurs when enrollment is attempted by a device whose information does not match the Enrollment Restrictions set when the device was created. | The device is withdrawn automatically. If the enrollment restriction information was entered incorrectly, you need to re-create the device information. Otherwise, you need to take action such as checking whether the correct device user is enrolling. | Warning |
| The device administrator setting is disabled on the device | Occurs when it is detected that the device administrator app setting of the MDM agent app is disabled on an Android device. | Ask the user to enable the device administrator app setting. | - |
| The user locked the device | (Only when the Personal service is used) Occurs when the device user issues a lock command. | You can delete this alarm by clicking the trash can icon in the Action column of the alarm list. | Warning |
| The user performed a selective wipe on the device | (Only when the Personal service is used) Occurs when the device user issues a selective wipe command. | You can delete this alarm by clicking the trash can icon in the Action column of the alarm list. | Warning |
| The user wiped the device | (Only when the Personal service is used) Occurs when the device user issues a wipe command. | You can delete this alarm by clicking the trash can icon in the Action column of the alarm list. | Warning |
| No passcode is set on the device | (iOS only) Occurs when no passcode is set on the managed device. | (iOS only) The managed device displays a message prompting the user to set a passcode, and a passcode is enforced within 60 minutes, so no action is needed. | Warning |
| The device passcode does not meet the policy | Occurs when the passcode set on the managed device does not meet the passcode requirements set by the profile. | (iOS) The managed device displays a message prompting the user to set a passcode, and a passcode is enforced within 60 minutes, so no action is needed. (Android) Apps installed on the managed device are grayed out and cannot be used, so ask the user to set a passcode that meets the policy. | Warning |
| Device users are sharing an Apple VPP account | Occurs when two or more VPP users share the same iTunes account. This alarm applies when per-user VPP is used. | You can delete the alarm by stopping the shared use of the account. | Warning |
| The iTunes Store account on the device is disabled | Occurs when the Apple ID linked when purchasing per-user VPP app licenses is disabled at the time of installation and the device returns an iTunes account disabled error. | Register the correct Apple ID that was linked for per-user VPP app distribution on the device. | Warning |
| The iTunes account on the device is different from the Apple VPP registered account | Occurs when the Apple ID linked when purchasing per-user VPP app licenses is not assigned or is different. | Register the correct Apple ID that was linked for per-user VPP app distribution on the device. | Warning |
| The SIM card of the device was changed | Occurs when replacement or removal of the SIM card of a managed device is detected. | You can clear this alarm by authorizing the changed SIM card or by reinserting the removed SIM card. | Critical |
| Signed in with a Managed Apple Account that is not assigned to the device | Occurs when, on a Shared iPad, a user signs in with a Managed Apple Account that is not assigned to the user profile. | Check that the user of the Shared iPad and the Managed Apple Account assigned to the user are correct. | Warning |
| The book is not installed | Occurs when a book cannot be installed. | On the [LOG] screen, search with Command turned ON and check whether there are any command errors from the device. | Warning |
| Data could not be deleted by selective wipe | Occurs when data in the folder specified for deletion in the profile cannot be deleted. | A possible cause is that the target folder does not exist. Check whether the target folder exists and whether the folder is specified correctly. After checking, you can delete this alarm by clicking the trash can icon in the Action column of the alarm list. | Warning |
| Admin Lock could not be executed. The command was sent to the device, but the device returned an error | Occurs when an Admin Lock command is sent to a managed device that is not supervised. Normally, an Admin Lock command cannot be sent to a device that is not supervised. However, if Notify by alarm and apply Admin Lock to the device is selected as the action to execute when a SIM card change is detected, an Admin Lock command is sent to the managed device that is not supervised. | The alarm is displayed as an action by the device user. After checking, you can delete this alarm by clicking the trash can icon in the Action column of the alarm list.Note: Even if you delete the alarm, the SIM card change detection alarm is not cleared until the changed SIM card is authorized. | Warning |
| The profile is not supported by the OS version | Occurs when the profile contains settings that are not supported by the OS version of the device. | Remove the profile settings that are not supported by the OS version of the device from the template. For details on the profiles that can be applied for each Android OS version, see the Android profile. | Warning |
| The installed MDM agent is not supported | Occurs when the device uses a version of the MDM agent app that was used with the former BizMobile MDM. | Install the latest version of the agent app from the Google Play Store. | Warning |
| The profile is not supported by the MDM agent version | Occurs when a device running Android 5.x or later is enrolled using the Android MDM agent app currently distributed on Google Play, and a profile setting that can be applied only to Android 4.x or later is applied. | You need to update to the latest version of the Android MDM agent app. Contact us to obtain the latest version of the Android MDM agent app. | Warning |
| The profile is supported only on devices in Device Owner mode | Occurs when, among the profile settings that can be applied only to Android 5.x or later, a profile that can be applied only in Device Owner mode is applied to a device in standard mode. | Remove the profile that can be applied only in Device Owner mode from the template. | Warning |
| An app that is not permitted is installed on the device | Occurs when an app registered in Banned App Detection as a prohibited target is installed on the device. | Contact the device user and ask them to delete the prohibited app. | Warning |
| There are not enough licenses that can be assigned to the app | Occurs when the number of licenses to distribute exceeds the number of licenses purchased. | Log in to Apple Business (formerly Apple Business Manager) and purchase additional licenses. The alarm is cleared when the number of purchased licenses is equal to or greater than the number to be distributed. | Warning |
| An app with the same identifier is already installed on the device | (iOS only) Occurs when the same app is already installed on the device at the time you try to distribute the app from BizMobile Go! (conflict). This applies, for example, when the app was downloaded directly from the App Store. | Enable the Auto Management setting for the app in the template and change the installed app to Managed. | Warning |
| The app is unavailable because it was removed from iTunes | Occurs when an App Store app registered in BizMobile Go! is removed from the App Store (iTunes). Apps already installed on devices are not deleted and can still be used. | This alarm is cleared when you delete the app from BizMobile Go! or when the app is registered in iTunes again. | Major |
| The app is unavailable because it was removed from the Google Play Store | Occurs when a Google Play Store app registered in BizMobile Go! is removed from the Google Play Store. | This alarm is cleared when you delete the app from BizMobile Go! or when the app is registered in the Google Play Store again. | Major |
| The application could not be changed from "Unmanaged" to "Managed" | (iOS only) Occurs when overwriting an app that is already installed on the device as a managed app with Auto Management: Enabled in the template fails. | Auto Management: Enabled can be used only on devices running iOS 9 or later. On devices running iOS 9 or earlier, this feature cannot be used. If this applies, delete the installed app from the device. | Warning |
| Location settings are turned off on the device | Occurs when the location option is enabled and sharing location with administrators is enforced, but the location acquisition function of the managed device is not enabled. | This alarm is cleared when the location function is enabled by an operation on the managed device and BizMobile Go! then acquires the location. | Warning |
| The location services setting on the device is set to "While Using" | Occurs when the location setting of the BizGo! Air app is set to While Using.In this state, the location cannot be acquired as the device moves. | You can delete the alarm by setting the location setting of the BizGo! Air app to Always. | Warning |
| The Apple Push Certificate will expire in 7 days | Occurs when the Apple Push Certificate required to manage Apple devices will expire within 7 days. | If the Apple Push Certificate expires, Apple devices can no longer be managed, so you need to renew the Apple Push Certificate. For the steps, see Renew the Apple Push Certificate. | Warning |
| The Apple Push Certificate will expire in 30 days | Occurs when the Apple Push Certificate required to manage Apple devices will expire within 30 days. | If the Apple Push Certificate expires, Apple devices can no longer be managed, so you need to renew the Apple Push Certificate. For the steps, see Renew the Apple Push Certificate. | Warning |
| Apple devices cannot be enrolled because no Apple Push Certificate is registered or the certificate has expired | Occurs when device enrollment is performed in a unit where no Apple Push Certificate has been registered yet. | Apple devices cannot be managed in this state. If no Apple Push Certificate has been registered, see Obtain and register an Apple Push Certificate. If one is already registered and has expired, see Renew the Apple Push Certificate. | Warning |
| The Apple Push Certificate has expired | Occurs when the Apple Push Certificate required to manage Apple devices has expired. The certificate has expired. | Apple devices cannot be managed in this state, so renew the certificate as described in Renew the Apple Push Certificate. | Critical |
| The Apple Push Certificate is invalid | Occurs when the Apple Push Certificate required to manage Apple devices becomes invalid for some reason. | Apple devices cannot be managed in this state, so renew the certificate as described in Renew the Apple Push Certificate. If the certificate cannot be renewed, you need to register the Apple Push Certificate again and then re-enroll the devices. | Critical |
| License management cannot be performed correctly because the Apple VPP token is also registered on another management server | Occurs when the VPP account is also used by another MDM service. | The alarm is cleared when the VPP token is renewed or deleted. | Warning |
| The Apple VPP token will expire in 30 days | Occurs when the registered Apple VPP token will expire within 30 days. | The alarm is cleared 5 minutes after the VPP token is renewed. | Warning |
| The Apple VPP token will expire in 7 days | Occurs when the registered Apple VPP token will expire within 7 days. | The alarm is cleared 5 minutes after the VPP token is renewed. | Warning |
| The Apple VPP token has expired | Occurs when the Apple VPP token of the unit has expired. | The alarm is cleared 5 minutes after the VPP token is renewed. | Warning |
| The Apple VPP token is invalid | Occurs when the Apple VPP token of the unit becomes invalid. | The alarm is cleared 5 minutes after the VPP token is renewed. | Warning |
| The DEP device was re-enrolled | Occurs when a DEP device is re-enrolled. | Check the status of the device. You can delete this alarm by clicking the trash can icon in the Action column of the alarm list. | Warning |
| The Apple DEP token will expire in 30 days | Occurs when the DEP token will expire within 30 days. | The alarm is cleared when the DEP token is renewed and the DEP sync is completed. | Warning |
| The Apple DEP token will expire in 7 days | Occurs when the DEP token will expire within 7 days. | The alarm is cleared when the DEP token is renewed and the DEP sync is completed. | Warning |
| The Apple DEP token has expired | Occurs when the DEP token has expired. | The alarm is cleared when the DEP token is renewed and the DEP sync is completed. | Warning |
| The zero-touch device was re-enrolled | Occurs when an Android zero-touch device is re-enrolled. | Check the status of the device. You can delete this alarm by clicking the trash can icon in the Action column of the alarm list. | Warning |
| The distributed provisioning profile has expired | Occurs when the provisioning profile registered in the template has expired. | In-house apps can no longer be used, so promptly distribute the renewed provisioning profile from the admin console, or rebuild and re-register the in-house app using the renewed provisioning profile. | Minor |
| The provisioning profile embedded in the app has expired | Occurs when the provisioning profile embedded in the in-house app has expired. | In-house apps can no longer be used, so promptly distribute the renewed provisioning profile from the admin console, or rebuild and re-register the in-house app using the renewed provisioning profile. | Minor |
| The distributed provisioning profile will expire in 7 days | Occurs when the provisioning profile registered in the template will expire within 7 days. | In-house apps will become unavailable, so distribute the renewed provisioning profile from the admin console, or rebuild and re-register the in-house app using the renewed provisioning profile. | Minor |
| The provisioning profile embedded in the app will expire in 7 days | Occurs when the provisioning profile embedded in the in-house app will expire within 7 days. | In-house apps will become unavailable, so distribute the renewed provisioning profile from the admin console, or rebuild and re-register the in-house app using the renewed provisioning profile. | Minor |
| The distributed provisioning profile will expire in 30 days | Occurs when the provisioning profile registered in the template will expire within 30 days. | In-house apps will become unavailable, so distribute the renewed provisioning profile from the admin console, or rebuild and re-register the in-house app using the renewed provisioning profile. | Minor |
| The provisioning profile embedded in the app will expire in 30 days | Occurs when the provisioning profile embedded in the in-house app will expire within 30 days. | In-house apps will become unavailable, so distribute the renewed provisioning profile from the admin console, or rebuild and re-register the in-house app using the renewed provisioning profile. | Minor |
| The Microsoft Azure Client Secret Key has expired | Occurs when the key expiration date under SETTING → Unit → Windows 10 Store Settings has passed. | The alarm is cleared 5 minutes after the key is renewed. | Warning |
| 10 or more Android devices are assigned to this user. Reduce the number to 10 or fewer | Occurs when 10 or more Android devices are assigned to one user. | The alarm is cleared when the number of Android devices assigned to the user becomes 10 or fewer, or when the EMM account is deleted. | - |
| The EMM organization was deleted or is temporarily unavailable | Occurs when the EMM organization is deleted or becomes temporarily unavailable. | The alarm is deleted when the organization is re-created or when a sync completes while the organization is valid. | Warning |
| There is a problem with the device integrity (safety) or compatibility | Occurs when the device does not meet the specified "Minimum Device Integrity". | Check the verdict in "Device Integrity" on the device detail screen. For details on the verdict levels, see Device Integrity Verdict. | Major |