Check the timezone for the management servers and the SQL server to make sure it's correct. If they're getting date/time info from a domain controller (they should be), make sure that the DC has the correct time as well.
Might want to turn on time debugging as well in case something is going wrong https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/turn-on-debug-logging-in-windows-time-service
Management Configuration Service Group - Alerts for Future Date.
Hi ,
Alerts for the "Management Configuration Service Group" getting for the future date in SCOM Console. Where as all the SCOM servers date\time same. Also, all the Management Configuration Service task is sucessfully executing everydays.
Any support will be appreaciated.
3 answers
Sort by: Most helpful
-
Andrew Tabar 271 Reputation points
2021-11-18T03:48:50.983+00:00 -
sushil Kumar 1 Reputation point
2021-11-18T05:15:36.057+00:00 We have cross verified "Time Zone" and Time setting in Management Servers and SQL servers is same. Also, its locally configured.
Also, generated other alerts from SQL server is coming correctly. Only alerts related to Management Configuration Service Group is coming to future date with Delayed status.
Our SCOM DB is configured on SQL Always ON.
-
Adam Hulek 1 Reputation point
2022-07-08T10:55:46.753+00:00 Hi,
The data that you see in the monitor state change context is coming from OperationsManager database where datetime is in UTC timezone. Your computer where the console is installed is probably in UTC+2. Therefore the datetime that you see in Alert Generated field minus two hours equals $Context/DataItem/time$
Adam Hulek