CoMo Error – You must update your version of Communicator Mobile

So, long story, short version: I was trying to hook up Communicator Mobile 2007 on my HTC S710 running WM 6.1. I downloaded the latest version from the Microsoft download site and installed it. So far so good.

I then entered all of the important information in the client, you know, like the address info and my log on info. I clicked on sign in and after a couple of minutes, I got this ugly error message that said:

“You must update your version of Communicator Mobile before you can sign in…” Well, I just downloaded the latest and greatest. How could I have too old of a version?

A little research gave me the following steps to fix it.

1. Check the Client Version Filter defined in your OCS environment
 – Expand Standard/Enterprise Edition Servers node
 – Right Click on the pool or server name. Choose Application Properties > Client
 – Select the Application Properties and then Client Version Filter
 – Click on the line for CPE
2. Update the version number to block a lower number than the current version

Repeat the process on the Access Edge. You may need to restart the RTCSRV service, but I didn’t seem to need to take that step.

Upcoming Mindsharp Summits and Unified Communications

We have been working really hard these last few weeks completing our courseware for Unified Communciations. OK, it is really just the first round.

Our first course will focus on Core Technologies in Office Communications Server 2007. In this course, we will talk about how OCS fits into Unified Communications, the different server roles, and how to implement basic instant messaging as well as conferencing and voice.

The second course will be focused on using OCS 2007 and Exchange 2007 Unified Messaging to provide Enterprise Voice. I am really excited about the voice side of it all as we will get to play with media packs and set up routing rules. I can’t wait!

I love this technology stuff!

New MVP Award

I received the formal announcement this morning that I am awarded the MVP again for my work in Windows High Availability (Server Clustering). No, that is not the title, but that is the way that I try to treat the subject.

As an contributor to the different communities around the world, I try to provide some objective information to questions and issues. One of the hardest things for me to respond to are those that want to implement Failover Clustering (that is the term in Windows Server 2008), but they don’t want to invest in good hardware, or enough hardware, to do it well. However, my real pet peeve is that too many people think that High Availability is just putting together a cluster and then magic happens.

OK, it is true. Magic does happen. Failover clustering is so much easier today that it has ever been, and it is also much less expensive than ever before in the past. However, we have to remember to stick to the basics. Don’t forget change control. Don’t forget your backout plans. Don’t forget your DR plans. Most importantly, don’t forget to test everything.

Anyways, I spent my last plane flight working on several blog ideas. I hope to refine them and get back to giving you more and more information about some of the topics that came to mind Monday morning while I was flying to the office.