Microsoft’s Jason Langridge wrote an interesting blog item related to recurring meetings earlier this week…

Having Problems With a Calendar With Lots of Recurring Meetings?

The problem, it turns out, occurs because Microsoft creates recurring meetings out to 400 years if no end date is set. Um, who was the big brain who decided on that I wonder? I suspect many of us set recurring events that go on forever even if we don’t expect to live for another 400 years. And, I wonder if birthdays and anniversaries are set using the same recurrence algorithm? That might explain some of the bizarre behavior there. Many WiMo users have seen birthday events multiply inexplicably. Some have even seen birthdates split across two days after Microsoft issued a patch to deal with the fact that Daylight Savings’ start and end dates were changed in the US this year. And, then, there is the problem of changing just a single occurrence of a recurring event that I’ve described earlier…

Here’s the scenario for that problem: Set a recurring appointment (e.g., weekly staff meeting) with no end date in Outlook on the PC. Sync the PC with a WiMo device. Detach the WiMo device from the PC. Change just one of the meetings in the series on the WiMo device while leaving the other recurring events in place. Sync the WiMo device with the PC. When I do this, the single event changed on my WiMo device reverts back to the original date/time after syncing with the PC. It does not happen 100% of the time. But, I would say it happens at least 50% of the time for me.

Brighthand and ZDNet both recently had blog items commenting on Microsoft reorganizing the Windows Mobile group and focusing the division on Windows Live service. I’m a little worried about this me-too strategy that seems to follow on the heels of Apple’s iPhone (and to a lesser extent iPod touch). Windows Mobile’s greatest strength has always been the rich set of client software available for it that gave it a good disconnected experience. And, what about Windows Live anyway? It is a bunch of barely connected web services that doesn’t seem to have a strategy of its own. How can it be the basis of a Windows Mobile strategy?

I hope history doesn’t repeat itself. Take a look at the photo above. See that big white thing behind the T-Mobile Dash (Windows Mobile Smartphone AKA Standard Edition)? That is not a PC. It is an MSN Companion that like Windows Mobile was based on Windows CE. Its only function was to connect to the web (by phone line or Ethernet) and was based on Interent Explorer 4. It was barely web-ready even when it was introduced though I thought it was a good first start and used it quite a bit as stand up terminal for quick web browsing. The problem is that it was orphaned and never had more that 2 firmware updates (which took a month to roll out to customers). Today, with its lack of a modern browser, it is essentially useless. Even the first Handheld PC or the earlier MS-DOS based handhelds, on the other hand, are still useful with their built-in client applications and third-party software. But, try using a GPS in your current day Windows Mobile device with only Microsoft applications and no phone service (when you are out of a service area for example). Now imagine that there were no 3rd party client-side GPS applications. What would you do?

Microsoft’s strategies have not been firing on all cylinders for the last couple of years. Their stock price and the general reception of major products like Windows Vista (Office being a rare exception) are two prominent examples. I think Windows Live needs a strategy before it can be used a strategy for Windows Mobile. Microsoft should focus on the broken aspects of Windows Mobile like ActiveSync/WMDC (Windows Mobile Device Center), email, and Office Mobile before looking at Windows Live services.

I tend to listen to the podcast version of Leo Laporte’s Tech Guy radio program when I want to listen to something interesting while driving but don’t want to pay attention to very single word (which I tend to do when listening to something like the Security Now podcast). I have a backlog of these files on my iPod. Today, I was listening to Show 363 from June 23 and noted the segment about someone who has an old Jornada Pocket PC who can’t sync with Windows Mobile Device Center (WMDC) on Windows Vista.

The issue is that WMDC only supports devices going back to Windows Mobile 2003. The last Jornada model was a 2002 device. So, you can’t sync it on a Vista PC. The caller seemed aware of the issue and asked if a Windows XP virtual machine running on Vista might be able to sync with the Jornada if ActiveSync was installed on the Windows XP Guest OS. Leo correctly suggested using either VMware Workstation or Parallels Desktop for Windows. However, the caller asked if Microsoft Virtual PC (which is free) might work too. Leo agreed. Alas, that is not the case. Microsoft Virtual PC has virtually (pun intended) no USB device support. So, it wouldn’t see a Pocket PC or Smartphone and partner it to ActiveSync. VMware Workstation and Parallels Desktop for Windows, on the other hand, have pretty decent USB device support and should be able to run ActiveSync in a Windows XP Guest OS and partner with an older Pocket PC or Smartphone. I haven’t tested this myself. So, you might want to verify this using a 30-day trial before plunking down your hard earned dollars. I have VMware Workstation 6 though. So, I’ll get around to testing this idea one of these days.

FYI: You aren’t limited to virtual machine running on Windows Vista. If you use a Mac, Parallels Desktop for Mac and VMware Fusion have good USB device support too. The wrinkle in this story is Apple is releasing a major upgrade (Mac OS X 10.5 Leopard) next week Friday. All this should still work under Leopard. But, it wouldn’t hurt to check first. I’ve got my upgrade copy pre-ordered and plan to install it next weekend.