Configuration profile settings are not applied to the device (not distributed / not applied)

There are several possible causes, so check the following.
The device must be powered on and connected to the internet.

◆ Check communication between the device and the server
First, check in the admin console whether the device is communicating with the server normally.
Open the device detail screen in the admin console, run the following sync operation, and check that Last Access is updated.

• Device Detail > Command > Sync

When you perform the sync operation, Operation Time is updated. Then, within several seconds to several tens of seconds, the device communicates with the server and the Last Access time is updated.
Note: Operation Time is the time of the operation in the admin console, and Last Access is the time of communication from the device.

• Device Detail > Device (tab) > Device Status > Request Device Information (Operation Time)
• Device Detail > Device (tab) > Device Status > Last Access

If Last Access is not updated, the device may not be communicating with the server.
The lack of communication may be the reason the settings are not applied, so resolve the issue by referring to the following FAQ.

• Last Access is not updated
  The date and time of the device's Last Access is not updated

◆ Check the cause of the settings not being applied
If Last Access is updated and communication with the device is confirmed, identify the cause from the log contents and take action.

• Device Detail > Sync Status (tab) > Check Log

Typical causes are as follows.

• The same setting exists in multiple profiles and conflicts
  Remove profile "***" before installing this profile is displayed

• Blocked by a passcode
  InstallProfile: (4027) Profile <profile name> may require a passcode change, but the passcode cannot be changed

• The same profile is already installed by a method other than MDM
  Profile "***" is not managed by MDM is displayed

Back to FAQ top

Last updated: January 15, 2026

---