@AdminCat 

The reason is that you migrated them to a new controller which has a new CID (controller ID) and a new secret password etc.  You then tried to re-manage them with the older controller info which isn't going to work.  It sounds like you did not take a backup of the new controller or that when you built it you replace the admin account info in the new controller.  Having just experienced some failed migrations myself, I know that the new controllers will refuse to run if the data is corrupted.

I don't think you have any choice but to factory default all your devices and allow them to be re-adopted by the controller you've just restored.

Huge reason to immediately backup any controller once you've migrated it!

Also a reason to suggest to TPlink that some kind of a 'recovery' utility be created, even if it involves a paid license and somebody from the factory connected online to use it, because that was my first experience with this 'issue'...having to climb a 12' mast on the peak of a snowy roof at -20'C to reset my EAP225-outdoor basestation.  Fun times.

AdminCat wrote

  @d0ugmac1 

 

Okay we are now resetting one after another EAP. Is there any possibility to prevent faults like these? 

We are adopting like this procedure:

1) Install a local DHCP server in same subnet.
2) Connecting all EAP devices.
3) Login to web server of each device and changing default credentials from admin/admin to own credentials.
4) Using the discovery tool to connect to software controller on other subnet in VPN.

5) Changing the Administrator account in site settings to own credentials.

6) Trying to Batch Adopt all devices. This has never worked before (?!?).
7) Adopting one after another with own credentials manually after using the Retry button.

8) ------ Are now the credentials on the EAP devices changing to random? --------
9) If i shut ddown the controller i cant login to EAP's web server. Because credentials are wrong. But why?

 

  @AdminCat 

Ok, it feels like you might be making this more painful than necessary, I could be wrong, but let's try a few things.  First please review this KB:

https://community.tp-link.com/en/business/kb/detail/632

It sounds like you are using Option 2 from the KB right now.  It should really be as simple (assuming DHCP is present on the local network ie Step 1) as resetting each device to factory and running the batch config tool with admin/admin (Step #4).  In general the controller is smart enough to try admin/admin when adopting any device, so (Step #3 and #5) above should be unnecessary.  Once adopted each device will replace admin/admin with the Device Account as set in the local site (Site Settings->Site->Device Account).  Once adopted and managed by a controller, you are blocked from entering the device's Web interface to prevent you from changing the settings needed by Omada (this is normal).