4 Comments

Summary:

I know, this week has been covered with news about the new version of Windows Mobile.  So you owners of Windows Mobile 2003, 2003SE or 5.0 don’t feel left out, Microsoft has released an important update that you should apply to your device as soon as […]

I know, this week has been covered with news about the new version of Windows Mobile.  So you owners of Windows Mobile 2003, 2003SE or 5.0 don’t feel left out, Microsoft has released an important update that you should apply to your device as soon as possible.  Government leaders in the US and Canada have enacted legislation that changes when Daylight Savings Time starts and ends in those countries.  Unfortunately, this change means that consumer electronic devices that are programmed to automatically change the clock by one hour for CST must be updated or they will erroneously change the clock at the old dates.  Microsoft has released an update to change the WM devices to the new dates so the clocks will change properly.  The update is available in two flavors, a PC installer that requires hooking the device to the PC and as a CAB file that can be downloaded directly to the device and installed without a PC.  The update web page has detailed information and instructions which should be followed exactly to make sure the update gets applied properly.  Note that once the update is installed on your device you MUST manually change your time zone once to make the update kick in. Then just change the time zone back.  I intend to update all my WM devices today so I don’t forget.

UPDATE: in going through the update process I noted there are three components to this update- a Windows XP component, Outlook component, and the Windows Mobile component.  According to the update docs, Vista has already incorporated the change so nothing needs to be applied on those systems running Vista.  Outlook 2007 is not listed as a version needing the Outlook component so apparently the change has already been rolled into that too.  That means if you’re running Vista and Outlook 2007 you only need to apply the WM update to your device.

  1. No such thing from Palm, dammit! (For *PalmOS*, that is!)

    Share
  2. One bit of information that I can’t find anywhere is whether this is a permanent update or if it’s lost following a hard reset. Does this update the device ROM or will I need to install this on any device following a hard reset?

    I am currently trying to work through the logistics of updating the various devices in my organization (as well as having to run the Outlook tool on about 400 computers in our non-Exchange environment) and it would be nice to know if we need to have this update around when we hard reset a user’s device.

    Can anyone who has installed this confirm whether this update survives a hard reset? Also, any advice anyone has for updating hundreds of users’ calendars would be appreciated, too, because I am really stressing out about all this. I can’t understand why it’s less than a month before the change actually happens, and so many products are still unpatched. As an IT person, I am highly annoyed by this because it now becomes my problem.

    Share
  3. Mike:

    For the Palm OS its a manual change. I received a bunch of emails on this I commented on how to do it here:

    http://www.bostonpocketpc.com/CommentView,guid,961e1909-10cf-4d86-8b38-2391f47a6017.aspx

    Dave:
    It is currently a program that changes registry values. So if a unit is remote wiped or hard reset the CAB file will need to be run again. If you have access to the extended ROM on your device or have some third party utilites you can have it autoinstall. Some carriers may be issuing ROM updates to include the 2K7 fix, but none haven’t been announced officially yet.

    For updating hundreds of calendars I haven’t seen a best practice document yet. However we will be testing it later this week. Since running the client-side Outlook patch requires user confirmation, I don’t recommened issuing the patch manually. If you are using an Exchange server there is an Exchange server patch:
    http://support.microsoft.com/kb/926666/

    Note: The server-side tool is merely a wrapper around the client-side tool. Therefore, the server-side tool provides no semantics that are not also exposed by the client-side tool for the actual job of updating a user’s calendar. In short, any calendar or reminder update that can be made through the Exchange tool can be made exactly as in the Outlook tool.

    Typically, it makes sense to run the server-side tool only in “quiet” mode. The main difference between the server-side tool and the client-side tool is the fact that when the client-side tool is in “quiet” mode, the tool displays no user interface (UI). Therefore, the tool provides no method by which anyone can specify nondefault behavior. Nondefault behavior can include updating data that is not in the Calendar folder or in the reminder queue of the default store of the given MAPI profile.

    Any other differences between the server-side and client-side tools relates to how they are configured and run. The differences do not relate to how the tools identify or update appointments that have to be updated.

    Hope this helps. :)

    Share
  4. That was helpful Steven. Disappointing, but helpful. :-) So not looking forward to “fixing” this on Palms OS, either. I will look forward to your test results for bulk-deployment of the client-side Outlook tool.

    Share

Comments have been disabled for this post