Issue with OpManager's Windows Service Monitors and Same Dis
I already created a ticket, but I am posting in the forums so everyone is aware.
We are having an issue with OpManager 7, 7102. We have seen a situaton with OpManager's Windows Service Monitors where if the same display name for the service exists on two servers with different windows service names, then OpManager erroneously shows the different service name as down.
Here is the evidence:
2 Exchange Servers. 1 is Exchange 2003, 1 is Exchange 2007. Both run POP3.
Exchange 2007's service display name is "Microsoft Exchange POP3" with an actual service name of "MSEXCHANGEPOP3".
Exchange 2003's service display name is "Microsoft Exchange POP3" with an actual service name of "POP3SVC".
Because, when we deployed OpManager, we monitored Exchange 2007 first, thus bringing the "Microsoft Exchange POP3" service into OpManager's database, when you try to monitor Exchange 2003's POP3 service, OpManager is looking for "MSEXCHANGEPOP3", not "POP3SVC".
OpManager should allow the admin account to be able to change actual service name to realize the differences (I perfer the flexibility to change it).
Is there anything I can do to fix? We use OpManager to monitor hospital networks, so our SLA is high. This issue has been a irritant to our NOC people.
Please help. I sent our log file when I created the ticket.
Jonathan Merrill
MCP, CCA, NET+
Manager, Enterprise Solutions
TpHR, LLP
We are having an issue with OpManager 7, 7102. We have seen a situaton with OpManager's Windows Service Monitors where if the same display name for the service exists on two servers with different windows service names, then OpManager erroneously shows the different service name as down.
Here is the evidence:
2 Exchange Servers. 1 is Exchange 2003, 1 is Exchange 2007. Both run POP3.
Exchange 2007's service display name is "Microsoft Exchange POP3" with an actual service name of "MSEXCHANGEPOP3".
Exchange 2003's service display name is "Microsoft Exchange POP3" with an actual service name of "POP3SVC".
Because, when we deployed OpManager, we monitored Exchange 2007 first, thus bringing the "Microsoft Exchange POP3" service into OpManager's database, when you try to monitor Exchange 2003's POP3 service, OpManager is looking for "MSEXCHANGEPOP3", not "POP3SVC".
OpManager should allow the admin account to be able to change actual service name to realize the differences (I perfer the flexibility to change it).
Is there anything I can do to fix? We use OpManager to monitor hospital networks, so our SLA is high. This issue has been a irritant to our NOC people.
Please help. I sent our log file when I created the ticket.
Jonathan Merrill
MCP, CCA, NET+
Manager, Enterprise Solutions
TpHR, LLP