# Problem moving ePMP Force 300-19 from Cloud to On-Premises

**URL:** https://community.cambiumnetworks.com/t/problem-moving-epmp-force-300-19-from-cloud-to-on-premises/109097
**Category:** cnMaestro
**Created:** [October 13, 2026, 1:51pm UTC](https://community.cambiumnetworks.com/t/problem-moving-epmp-force-300-19-from-cloud-to-on-premises/109097 "2026-10-13T13:51:31Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![densitynetworks](https://d10gw3vjmzyp8.cloudfront.net/letter_avatar_proxy/v4/letter/d/e480ec/32.png) [@densitynetworks](https://community.cambiumnetworks.com/u/densitynetworks)
#### Post date: [October 13, 2026, 1:51pm UTC](https://community.cambiumnetworks.com/t/problem-moving-epmp-force-300-19-from-cloud-to-on-premises/109097/1 "2026-10-13T13:51:31Z")

</div>

Hi there!

We are trying to migrate our ePMP Force 300-19 SM/AP radios from the cloud to our on-premises server; I have already successfully moved several e500 units at this same location using overrides.

I’ve tried various template types, but we can’t get them to show up in the on-premises console. When we configure the template, the device goes offline for 10 minutes but never actually appears in the on-premises console.

Is anyone else experiencing this issue, or does anyone know how to configure it?

Many thanks!

---

<div class="post-metadata">

### Author: ![1top-it](https://d10gw3vjmzyp8.cloudfront.net/letter_avatar_proxy/v4/letter/1/edb3f5/32.png) [@1top-it](https://community.cambiumnetworks.com/u/1top-it)
#### Post date: [October 13, 2026, 3:04pm UTC](https://community.cambiumnetworks.com/t/problem-moving-epmp-force-300-19-from-cloud-to-on-premises/109097/2 "2026-10-13T15:04:06Z")

</div>

We have migrated several 300-19 and 300-16 devices using the templates. Save the device configuration in Cambium Cloud as a template and add/edit the following lines:

“cambiumDeviceAgentEnable”: “1”,  
‘cambiumDeviceAgentCNSURL’: “[https://cnmaestro.domain.tld](https://cnmaestro.domain.tld)”,

…you may double-check the DNS server can resolve your controller.