Managing the changes to Daylight Saving Time with mobile devices and GroupWise Mobile Sync.
If you sync your GroupWise with Mobile Devices, including Blackberry or Smartphone, using Windows Mobile 5.x, you need to update your device's registry in order to keep the accurate time for the new Daylight Saving Time table.
Since 1966, most of the United States has observed Daylight Saving Time from at 2:00 a.m. on the first Sunday of April to 2:00 a.m. on the last Sunday of October. Beginning in 2007, most of the U.S. will begin Daylight Saving Time at 2:00 a.m. on the second Sunday in March and revert to standard time on the first Sunday in November. This year, DST (for most states which observe it) starts on 3/11/07 and ends on 11/4/07, extending the DST by 4 weeks.
Your mobile device needs to receive a new patch or a complete new OS upgrade, depending on the type of the phone or device. This article covers all the Smartphones running the Microsoft Mobile 5.x 2005 operating system.
First, you need to check the Microsoft site regarding this issue and read about their registry fix solution at:
Should you want to compile the file yourself, you can copy the registry into a .INF file and run cabwiz.exe in order to create a .CAB file to run on your mobile device. Cabwiz.exe is part of Visual Studio.
If you are looking for a pre-compiled .CAB file, the following Blog site contains the file and a good thread of discussions regarding this issue:
1. Copy the .CAB file to your Smartphone and run it.
2. Once you apply the patch, manually change your timezone to something else and click Apply.
3. Change it back to your correct time zone. This forces the phone to re-read the registry file.
Most carriers should have this fix available to their customers, but they have been very slow testing and releasing the fix. If you have any other device which may require a different patch or upgrade, please contact your carrier as soon as possible. March 11th is right around the corner!
- GroupWise 7.01
- BES 4.x or Intellisync Mobile Server
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.