We have 5 additional polling engines and one main poller. Especially during the upgrade process it is hard to control services on each one of them.
There should be central service manager that controls all the polling engine services.
I feel your pain... A central service manager that runs on the main poller would be perfect. I would love to see an installer that does this automatically.
Let me change the idea name as you suggested. Thanks
I really need to look at ideas more often...This is fantastic. I have 4 polling engines.
It should also control the WPM service on the players. It would be nice to have a one stop shop for all. Makes it simpler if you have to take down your primary you wouldn't have to log into every box. With 4 pollers and 3 players thats 7 systems I have to RDP into just to stop/start services.
Excellent suggestion!!!
Is this something that should be part of the enterprise management product? If you are doing that many controllers then you most likely have or are tying to set up HA instances of NPM with the Enterprise managment doing all the "high" level work - we are not doing this but just a thought.
anyone have a powershell script for this in the meantime?
Resurrection time! I would like to bring this back from the dead and hope something can be done to detect additional pollers and manage services from the primary server (or any server really). I do not think it would be overly difficult to design a MMC snap-in to perform these functions. You could easily add additional servers in manually and then save the MMC similar to all of the standard MMC snap-ins. We are running distributed poller model and we will be up to 8 Additional Pollers plus the Application Server. It is a bear to have to log into each server to manage services (mostly to verify they are down, you could obviously write a powershell script to turn down services, but it's verifying that SWIS believes they are down too.) this woudl also be great for if we stand up additional instances as well separate from the centralized deployment. I could see where this would be more inclined to be a part of EOC, but in a distributed poller model, EOC doesn't provide any function.
This was implemented in Orion Core 2016.1 as the Orion Service Manager. It can be found in the Orion web interface under [Settings -> All Settings -> Orion Service Manager]
