Cloning Windows installations may lead to suspended device issue
An orange Suspended device banner may appear on your site if LogMeIn Resolve MDM cannot reliably identify some of the devices enrolled in your LogMeIn Resolve MDM site.
This is a safety measure that occurs as a result of device linking failure and is intended to prevent further problems in device management and/or billing.
Suspended device
This issue usually happens if there are two or more devices on your LogMeIn Resolve MDM site that have been installed using a cloned image, containing traces of earlier LogMeIn Resolve MDM enrollment.
LogMeIn Resolve MDM's MDM profile
and Miradore client can both leave permanent system identifiers to Windows devices and entries to the devices' Windows Registry and system settings even if the components would have been removed from the device. Some identifiers are created when an MDM profile is installed on a Windows machine for the first time. Removing the MDM profile or re-enrolling the device again to LogMeIn Resolve MDM does not change the identifiers.
These existing device identifiers make it impossible to identify the device reliably. Therefore, LogMeIn Resolve MDM may accidentally consider multiple similarly installed devices to be one and the same device, and it tries to link the different physical devices to the same Device entity in LogMeIn Resolve MDM.
Preventing the problem
Always use generalized (sysprepped) Windows images, which do not contain any computer-specific information.
See more from Microsoft documentation.
Do not enroll the device to LogMeIn Resolve MDM when you're creating a new Windows image. Instead, enroll devices in LogMeIn Resolve MDM after their deployment.
Unsuspending a device
After identifying and trying to fix the issue, contact LogMeIn Resolve MDM support through your site and explain the situation.