DST Update and SCOM e-mail notifications
Hi! Russia canceled daylight saving time at this fall, and MS releases some updates http://support.microsoft.com/gp/cp_dst. We have installed all required pathes on our servers, but our SCOM 2007 R2 CU 5 writing wrong time in e-mail notifications: From: scom@domain.com [mailto:scom@domain.com] Sent: Friday, November 11, 2011 9:40 AM To: Denis Osipov Subject: Alert: AD: User account modified Resolution state: New Alert: AD: User account modified Source: ra-dc01.some.domain Path: Last modified by: System Last modified time: 11.11.2011 8:39:55 Alert description: Event Description: The name of an account was changed: Subject: Security ID: DOMAIN\kupriyanovdy Account Name: kupriyanovdy Account Domain: DOMAIN Logon ID: 0x233cf748a Target Account: Security ID: DOMAIN\zelencova.kseniya Account Domain: DOMAIN Old Account Name: zelencova New Account Name: zelencova.kseniya Additional Information: Privileges: - Alert view link: "http://RA-MON01:51908/default.aspx?DisplayMode=Pivot&AlertID=%7b283683a2-3cca-4c03-9e0b-b6c64261b07d%7d" Notification subscription ID generating this message: {C7ADA98E-CA33-312F-1F91-F7065AEF776E} This problem exists only in e-mail notifications, all alerts in console has correct time. My collegue from another organization confirm this issue! Please help ;)
November 11th, 2011 12:53am

Hi! I have the same problem :( Incorrect time is not only in e-mail, but in the SMS to. Anybody knows, where SCOM take the date and time from? In the system of the server SCOM time is normal. I use in notification channel variable "$Data/Context/DataItem/TimeRaisedLocal$" How to correct this thing?
Free Windows Admin Tool Kit Click here and download it now
November 21st, 2011 1:59am

I fix that just recreate the subscriptions :)
November 25th, 2011 1:45am

agree. that's because subscriptions cache timezone information. If we look into Microsoft.SystemCenter.Notifications.Internal.xml, we will see why this happens. <LanguageCode>ENU</LanguageCode> <ExcludeNonNullConnectorIds>false</ExcludeNonNullConnectorIds> <RuleId>$MPElement$</RuleId> <TargetBaseManagedEntityId>$Target/Id$</TargetBaseManagedEntityId> <TimeZone>6801000000000000C4FFFFFF00000B0000000100020000000000000000000300000002000200000000000000|Central Standard Time</TimeZone> </AlertChangedSubscription> these digits is a cache from windows registry. these digits provide information for windows when to switch from summer to winter time and back. So, we have two options: recreate subscription or export Microsoft.SystemCenter.Notifications.Internal.xml MP, find you subscription, update TimeZone value.
Free Windows Admin Tool Kit Click here and download it now
November 25th, 2011 2:39am

Sorry guys, it doesn't works in my case.
November 25th, 2011 2:55am

We can close this thread, server was repaired by clean install procedure :( OperationsManagerDB was recreated too.
Free Windows Admin Tool Kit Click here and download it now
November 25th, 2011 2:57am

. . м. .
December 5th, 2011 4:38am

. . м. . , м ?
Free Windows Admin Tool Kit Click here and download it now
December 14th, 2011 5:59am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics