The issue only manifests in IDS 10.00.TC4 and earlier. Tech support are actively working on it and I'll update this post when we have more info. Expect a tech alert on this soon too.
Here is a summary of the current findings..
|10.00.TC4||Upgrade to 10.00.TC5|
|9.40.TCx||Uncheck Windows DST box and adjust OS time manually|
|7.31.TDx||Uncheck Windows DST box and adjust OS time manually|
Update 3/10/09: It has been determined that the problem is related to the version of the Microsoft Platform SDK that was used when IDS was built. This is good news for patch engineers.. the fix is simply to rebuild IDS with a later version of the SDK. If you have IDS 9.x or 7.31 and a valid support contract, contact tech support for a patch. If you have IDS 10.x, upgrade to TC5 or later.
Update 3/19/09: Versions of IDS that were having the Time Zone problem are now working correctly. All IDS versions switched back to the correct time on Sunday March 15th - corresponding to the DST start date for the previous year. Therefore if you have one of the above versions that had a problem, you now have a choice of upgrading/getting a patch, or doing nothing until March 2010 when there is a chance that the 1 hour difference will occur again for a few days if DST starts before the 2008 DST again.