Time zone issues when copying SCOM alerts

Background

When trying to copy-paste (ctrl+c, ctrl+v) alerts from the SCOM console to an Excel worksheet or just a text file, we noticed that the Created field values where different from the ones displayed in the console. There was a two-hour difference.

1

2

As it turns out, the server was configured in a GMT+2 time zone, and the values got pasted in UTC. Hence the two-hour difference.

Solution

On each of the servers/workstations with SCOM console installed where you want to fix this, simply create the following registry key and value:

Key: HKEY_CURRENT_USERSOFTWAREMicrosoftMicrosoft Operations Manager3.0ConsoleViewCopySettings

Value: InLocalTime (DWord)

Data: 1

(Where 1 means that you want to have the values in your local time, and 0 means the default behaviour of UTC)

3

 

Conclusion

With some digging done by me and my colleagues using Procmon we where able to find out that the copy mechanism is trying to reach a non existing registry key and value.

So.. “When in doubt, run process monitor” – Mark Russinovich.

 

Hope this helps,

Oren Salzberg.

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.