Freigeben über

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

  • Artikel

Ok.  After the slack I took for my last my post: https://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:

https://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:

https://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:

https://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!

Comments