# \[Mender Configure\] Configure is empty after cloning OS image

**URL:** <https://hub.mender.io/t/mender-configure-configure-is-empty-after-cloning-os-image/8267>\
**Category:** General Discussions\
**Tags:** mender-client\
**Created:** [May 11, 2026, 8:22am UTC](https://hub.mender.io/t/mender-configure-configure-is-empty-after-cloning-os-image/8267 "2026-05-11T08:22:36Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Yohei](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/yohei/32/2701_2.png) [@Yohei](https://hub.mender.io/u/Yohei)\
**Post date:** [May 11, 2026, 8:22am UTC](https://hub.mender.io/t/mender-configure-configure-is-empty-after-cloning-os-image/8267/1 "2026-05-11T08:22:36Z")

</div>

Hi everyone,

I am working with Mender Configure for an IoT project. It works perfectly on my “master” device, which I manually configured from a clean Debian installation.

However, I am running into an issue after cloning the OS image from the master device to other machines. While the cloned devices register with the Mender server successfully, the Configure add-on remains empty, displaying the message:

“The device appears to either have an empty configuration or not to have reported a configuration yet.”

I understand this happens because a configuration update hasn’t been triggered yet, which would normally prompt the device to report its current state. However, triggering a dummy update via API for every single device is not ideal for our manufacturing process.

Is there a way to force the device to report its current configuration to the server without performing a configuration update?

Thanks in advance!