Business Community > Wireless > EAP787 stuck in Adopting status after Omada Controller converted to Windows service
< Wireless

EAP787 stuck in Adopting status after Omada Controller converted to Windows service

EAP787 stuck in Adopting status after Omada Controller converted to Windows service

EAP787 stuck in Adopting status after Omada Controller converted to Windows service
EAP787 stuck in Adopting status after Omada Controller converted to Windows service
2026-01-02 18:18:51 - last edited 2026-01-14 06:53:34
Tags: #Wi-Fi 7
Model: EAP787  
Hardware Version: V1
Firmware Version:

I run Omada Controller on a Windows 11 25H2 PC. I recently turned it into a service using the official instructions. After rebooting, I can access the Omada Controller instance just fine but my EAP787's status is stuck on Adopting.

 

Any ideas?

 

UPDATE: Solution.

EAP787 | Omada Controller on Windows 11
  0      
 
  0      
 
#1
Options
1 Accepted Solution
Re:EAP787 stuck in Adopting status after Omada Controller converted to Windows service-Solution
2026-01-14 06:53:30 - last edited 2026-01-14 06:53:34

Hi  @jdrch 

 

Thanks for sharing.

 

 

UPDATE: Solution.

Wish you a happy life and smooth network usage!  >Omada US Enterprise Beta Program Launch< >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
Recommended Solution
  1  
  1  
#2
Options
1 Reply
Re:EAP787 stuck in Adopting status after Omada Controller converted to Windows service-Solution
2026-01-14 06:53:30 - last edited 2026-01-14 06:53:34

Hi  @jdrch 

 

Thanks for sharing.

 

 

UPDATE: Solution.

Wish you a happy life and smooth network usage!  >Omada US Enterprise Beta Program Launch< >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
Recommended Solution
  1  
  1  
#2
Options

Information

Helpful: 0

Views: 251

Replies: 1

Tags

Wi-Fi 7
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.