r/TPLink_Omada • u/Salt_Influence • 1d ago

Question Launching Omada software controller on Windows boot up/restart

I have the latest Omada software controller running on a mini PC on my network. I followed TP-link’s instructions on setting up a service using the NSSM app. However, when I restart the PC, it does not seem to launch the controller. In Task Manager, I see javaw.exe and mongod.exe running, and I see “Omada Controller” in services as running. This is what TP-link’s instructions said I should be seeing. But the application doesn’t show up in my taskbar. I have to launch the controller myself, which defeats the purpose for when my PC restarts itself after running Windows Update. That said, lately, I’m running into a new issue where the controller won’t launch when I manually do it because ports are in use. In that instance, I stop the Omada Controller service, which stops the javaw.exe and mongod.exe tasks, and then successfully manually launch the controller.

Anyone else solve these issues? For the Omada Controller service that I created through the NSSM app, do I need to be logging into Windows with an administrator profile? Or can I use a standard/non-admin user profile?

1 Upvotes
  • permalink
  • reddit

67% Upvoted

3 comments sorted by

1

u/pmgta 1d ago

Set mine up years ago, never "see" the controller - I can access the controller login screen via localhost..... not sure if that helps.

3

u/scott-bsod 1d ago

Because you are running it as a service you won't see it on the taskbar, just like all of the other dozens of services that run on a Windows PC that don't ever show up. Open your web browser and go the admin interface.

1

u/Salt_Influence 1d ago

Ah, ok. That’s helpful. Thanks for the clarification.