The "Last Access" date and time is not updated
The device status Last Access shows the date and time of the last access from the device to the MDM server.
If Last Access is not updated by the daily automatic sync or a manual sync from the admin console, check the following in order.
This page covers cases that occur on some specific devices.
First, confirm that no alarm that affects all Apple devices (Push certificate expired) or all Android devices has occurred.
1. First, check the common items
These are checks common to all OSs.
The device is correctly enrolled in BizMobile Go!
Check that the management status of the device is not Withdrawn.
If the device is withdrawn, you can check the Withdrawn Reason on the device detail screen in the admin console to see whether it was caused by an operation from the admin console or by the device leaving on its own.
After checking the reason for withdrawal, re-enroll the device.
- For devices deployed using Apple ADE or Android Zero-touch
Reset the device and follow the on-screen instructions to activate it. This completes everything through re-enrollment. - For devices deployed using other methods
Depending on the deployment method, you may or may not need to re-create the device information. Check Deployment methods, and then re-enroll the device.
The device is connected to the internet
Check that the device is powered on and connected to the network.
Also check the Network configuration requirements and make sure that connections to the required destinations are not blocked.
The date and time on the device are correct
If the date and time on the device are significantly off, communication with the server may not work correctly.
→ If there are no problems, proceed to "2. Check by OS".
2. Check by OS
iOS / iPadOS / macOS / tvOS
For unsupervised devices, check that the MDM profile exists on the device.
Settings > General > VPN & Device Management > Remote Management > Signer: mdm.bizmobile.co.jp
Even if the signer shows Not Signed because of expiration, it is not the cause of Last Access not being updated. Even if Not Signed is displayed, device management by BizMobile Go! remains in effect.
For details, see Update the MDM profile.
Android
If you are using a Work Profile, check the following.
- Personal apps and
Workapps are displayed separately - Work apps are not
Paused
Windows
In the device details in the admin console, check the status of the push channel.
If Push channel is invalid is displayed, check the following.
Why "Push channel is invalid" is displayed
The push channel is a mechanism used for Windows push notifications and is set up at MDM enrollment.
This mechanism uses Windows Notification Services (WNS), and the push channel (Channel URI) that is obtained has an expiration period (usually about 30 days).
The Channel URI is normally renewed automatically in the background while the device is running. However, if the device is powered off or not connected to the network for a long time, it is not renewed and may expire.
If the MDM server sends a push notification while the channel is expired, an error is returned from the Microsoft server, so the MDM server treats the push channel of that device as Invalid.
If there has been no communication with the server for 30 days or more since Last Access, this is likely the case.
Why there is no communication with the server for 30 days or more
In BizMobile Go!, the server normally syncs with the device once a day by sending a request (push notification).
Windows MDM also has a periodic sync process, separate from push notifications, that communicates with the MDM server in the background, and a new push channel is re-registered with the MDM server when this periodic sync runs.
The following device states are generally possible reasons why no communication took place for 30 days or more.
- The device was in a network environment that could not connect to the server
- The device remained powered off for 30 days or more
- MDM enrollment has been canceled
(If the provisioning package is deleted while the device is offline, the server cannot detect it.) - Impact of an OS update
(There are no reports on Windows, but there are cases on other OSs.)
How to recover
Normally, when the device is powered on and connected to a network environment that can reach the server, the push channel is re-registered automatically and the device recovers.
If you need to recover quickly, running a manual sync (MDM sync) on the device may re-register the push channel sooner.
Settings > Accounts > Access work or school > Connected to BizMobile MDM > Info > Sync
3. If it is still not updated
If there are no problems with the common items or the OS-specific items, the cause is likely an internal problem on the device.
There is no way to prevent internal problems on a device from occurring.
As a remedy, try steps 1) to 4) below in order. This may refresh the MDM-related state on the device and resolve the problem.
If step 4) does not resolve the problem, perform step 5).
1) Restart the device
2) Check the communication status such as Wi-Fi / SIM
Applies to: SIM models of iOS / iPadOS
After restarting the device, before entering the passcode, turn Wi-Fi off in Control Center so that the device communicates over the SIM only.
In that state, send a command such as Lock to the device from the admin console.
3) Update the MDM profile
Applies to: iOS / iPadOS
This is not related to certificate expiration. It is a way to refresh the state.
In Safari on the device, enter https://go.bizmo.in/apple/upgrade.
For details, see Update the MDM profile.
4) Apply an OS update
5) Re-enroll the device
The procedure differs depending on the management mode.
Apple unsupervised devices / Android Work Profile devices
Re-enroll the device.
Apple supervised devices / Android Device Owner devices
Reset the device and then re-enroll it.
- Apple supervised iOS / iPadOS devices
If resetting on the device is restricted by a profile, you need to reset it using a Mac.
For the procedure to reset a device using a Mac, see the information from Apple.
https://support.apple.com/en-us/HT201252
If pairing with a host is restricted, you need to reset the device in recovery mode.
https://support.apple.com/en-us/HT212787 - Android Device Owner devices
A forced reset using recovery mode or similar is required.
The procedure for a forced reset differs by model, so check the device manufacturer's website.
Related keywords:
No response, Not-Responding, Push channel is invalid
Last updated: September 15, 2026