Rickey Whitworth's Blog

I recently switched from a Blackberry device to the Cingular Blackjack running Windows
Mobile 5.0. Because I have been on Blackberry for so long, there has been a learning
curve for me on the Windows mobile device, especially since I am also running Vista
on my desktop.

The first big test I have had is getting Office Communicator Mobile installed. Before
you can install any software to your phone in Vista, you must have the Windows
Mobile Device Center installed. Otherwise, Vista treats your phone just like a usb
memory stick, meaning you can browse folders and copy files.

I had a Windows Mobile Device Center icon in Control Panel after plugging up my device,
but if I double clicked on it I only had a couple of configuration options. So I searched
on the internet and found a Beta
3 version of Windows Mobile Device Center for Windows Vista. After installing
this, I could launch the control panel icon and see more options, like Programs and
Services, File Management, Pictures Music and Video, and Mobile Device Settings.

My next problem is detailed in a post by
Dennis Thomsen at msgoodies. The Details:

When launching Communicator Mobile on
Vista RTM with Windows Mobile Device Center Beta 3 you get this message

Current version of ActiveSync is not supported. Please install Microsoft ActiveSync
4.1 ….

The workaround is to create an administrative install of Office Communicator like
this –

msiexec /a CommunicatorMobile_SP50.msi

And then launch the PCinstaller.exe from e.g. C:\Microsoft\Communicator Mobile\Windows
Mobile 5 Smartphone\Setup.

Dennis’s original instructions were for pocket pc 5.0, and I found out that the Cingular
Blackjack is a Smartphone, so I updated the instructions above to reflect this.

After the install, there was an error on my Blackjack that the home page could not
be displayed and that I could correct this by going to Options, home page. I did this
and saw that my home page display had been changed to one called “Office Communicator”.
I changed it back to Windows Standard and I was fine. I’m not sure what in the page
was causing the problem, just wanted to share in case anyone else saw it.

Of course, I realized after all of this that we have not setup an outside proxy for
our Live Communications Server, so I can’t use it yet.

Random Posts