DirectPush with Windows Mobile 5. What to look for to not use Text Messaging

tmintner — Wed, 05 Jul 2006 07:50:00 GMT

Ok. After the slack I took for my last my post: http://blogs.technet.com/tmintner/archive/2006/07/03/440029.aspx

I did some research as to why I was being charged for Text messages on my phone when I thought I was using DirectPush with Exchange Server 2003 SP2 and Windows Mobile 5.

Well after doing some research it turns out that there are two methods of doing Always up to date with Windows Mobile 5. The first method is for devices that do not have the Messaging and Security Feature Pack and sends a text message to the phone to tell the phone to get a new message. The second method uses a persistant HTTP connection to the Exchange Server that does not use Text Messaging. Both methods are described in detail here:

http://msexchangeteam.com/archive/2006/04/03/424028.aspx

After doing some digging I have found that the Motorola Q which is the phone that I am using does not have the latest version of the Exchange Messaging and Security Feature Pack installed which means that with the Motorola Q for the time being the only way to have DirectPush is to use the Text Messaging method. Check out this article:

http://www.mobilekick.com/mobile-os/52/motorola-q-with-windows-mobile-50.html

The bottom line is that if in you do not have the Exchange Messaging and Security Feature Pack, then setting your ActiveSync to "as messages arrive" uses Text Messaging. If it is installed then it doesn't.

Check out this video on the proper way to configure your phone:

http://msexchangeteam.com/archive/2006/05/09/427608.aspx

So in my case with the Motorola Q I can only use the Text Messaging method for the time being until Verizon releases an update for the phone.

I have to say that we have some very passionate users out there who were quick to correct my original statement. This has been a great learning experience for me and now I can speak intellegently on the differences between the phones and what to look for to make DirectPush work correctly with Exchange 2003 SP2.

It just shows that even on an American holiday (July 4). There are still hundreds of readers around the globe that are passionate about what they do. Thanks everyone for keeping me honest!

Update: Wrong Setting: Beware of Text Messaging and Direct Push email with Windows Mobile 5

tmintner — Tue, 04 Jul 2006 01:36:00 GMT

***Quick Update***

Thanks to all who posted comments and emailed me. It turns out that the wrong setting was turned on with my phone. I was using a pre-Windows Mobile 5 feature that used Text Messaging. Sorry for the confusion and thanks to everyone for the correction!

I will post the full details of the correct settings and what was configured incorrectly in a new post tomorrow.

I have created a blog entry on the correct settings here: http://blogs.technet.com/tmintner/archive/2006/07/04/440182.aspx

**********************************

A little off topic here, but I just wanted to give everyone a heads up that if you are using Direct Push with Windows Mobile 5 you need to make sure you have unlimited Text messaging as part of your plan. Apparently Direct Push works by sending a Text message to your phone to tell it to get the email message as new email arrives.

Verizon had the wrong plan set up for me and I got dinged with a $60 bill just for text messaging! Thankfully they were great about it and credited my account and put me on the right data plan.

Tim Mintner : Exchange

DirectPush with Windows Mobile 5. What to look for to not use Text Messaging

Update: Wrong Setting: Beware of Text Messaging and Direct Push email with Windows Mobile 5