Year: 2007

I installed Windows Mobile Device Center (WMDC) 1.0 on a PC running Windows Vista Ultimate Edition. You can find an illustrated guide through the WMDC partnership creation process at…

Illustrated WMDC Partnership Creation

Couple of quick notes before you click on the link above…

Installing WMDC took a very long time… Many minutes. I have no idea why this process took so long. Other applications have not taken very long to install under Windows Vista. To make matters worse, the installation process instructed me to reboot after it completed. ActiveSync (such as it is) did not require a reboot after installation.

The process of partnering (see Step 4 in the illustrated guide) also took a long long time (many minutes). This is not too unusual for Windows Mobile 5 devices. But, I was synching with a Windows Mobile 2003 device which normally does not take as long to create a partnership.

The menus have a kind of hybrid Xbox/Vista look. Lots of white space (or green space as the case may be). I would prefer a set of legacy pull-down menu lists going across the top or a ribbon navigator like Office 2007 apps. It would be much faster to navigate.

The decision to go with a Xbox-y consumerish WMDC design doesn’t make sense since Microsoft is aiming their Windows Mobile device at the Enterprise (vs. the Apple iPhone consumer market).

That said, the process was reasonably smooth (though very slow). I did, however, get a bunch of duplicate recurring events in my calendar. WMDC did not ask how it wanted me to handle events in the Outlook 2007 calendar in relation to the existing items in the Smartphone’s calendar. I also see a small number of duplicated contacts in my Contacts list.

Microsoft took away ActiveSync over the network (wired and wireless) a few versions ago and did not give it back with Windows Mobile Device Center. But, the sometimes flaky USB connection is not your only alternative.

My K-JAM Pocket PC Phone Edition, for example, syncs on the first attempt over USB. But, it somehow corrupts ActiveSync on the desktop for subsequent syncs unless I reboot my PC (and, yes, I’ve tried terminating and restarting the ActiveSync service). None of my other Windows Mobile devices causes this problem. Just the K-JAM. My solution has been sync the K-JAM using Bluetooth exclusively. This does not corrupt ActiveSync for subsequent sync sessions. The only downside is that I need to initiate ActiveSync from the K-JAM.

The GeekZone has detailed information on setting this up….

Bluetooth ActiveSync Guide for Windows XP Service Pack 2

If you have ActiveSync Bluetooth issues, take a look at this Microsoft Bluetooth FAQ…

Frequently asked questions about Microsoft Bluetooth-enabled devices

In my previous blog entry, I pointed out the two download links for the 32-bit and 64-bit veresions of the Vista replacement for ActiveSync. Here’s a link to its home web site…

Windows Mobile Device Center

It’s interesting that the full name for the software is Windows Mobile Device Center 6. Something to match up with an unreleased Windows Mobile 6, perhaps (we are currently at Windows Mobile 5 release)?

There’s a link to a WMDC troubleshooting page. One interesting note on this page is that while pre-WM2003 devices are not supported as partnered devices, you can still browse the ancient device and copy files.

I haven’t installed WMDC on my Vista PC yet. But, you can read what I have learned from installing Windows Vista Ultimate Edition on a cheap ($500) PC on another personal blog of mine: TO-Tech.com/blog.

Microsoft released the production versions of Windows Mobile Device Center (WMDC) for Windows Vista on January 31. WMDC replaces ActiveSync for Vista users. There are two versions available…
Microsoft Windows Mobile Device Center Driver for Windows Vista (x86)

Microsoft Windows Mobile Device Center Driver for Windows Vista (AMD64)

Please note that you must check which version of Windows Vista you are using. I suspect that many people with AMD Athlon 64 based PCs (like me) are running the 32-bit version of Vista for driver compatibility. So, just having an Athlon-64 CPU does not mean you should download and try to install the AMD64 version of WMDC.