Jason Langridge has an excellent writeup on the availability of WM5. As you can tell by the summary this all but confirms that we in USA live in the third world of mobility - only one of those devices (Sprint 6700) is on sale in retail US; Other WM5 devices available in the retail channels are just rebranded HTC devices so you could pirate and apply one of the iMate roms but legally... its looking very sad to be on Windows Mobility in USA. In a related story, Palm 700w which is by popular aclaim the worst WM5 phone on the market, has promised MSFP release later this month (April).
Orange
SPV M5000
SPV C600
SPV M600 – in ROM by default!
O2
O2 XDA Mini S
Sprint PPC 6700
i-mate all updates via www.clubimate.com
SP5 and SP5m
K-Jam
JasJar
QTEK all updates via www.myqtek.com
9000
9100
Symbol MC70 – in ROM
Gigabye – G-Smart – in ROM
In related news, Mike Calligaro of the Windows Mobile Blog explains why WM5 is slower than previous PocketPC systems. This is something that many have experienced since upgrading WM5. For those of you that have not met me in person but still struggle with a slow WM5 I only have one word for you. XCPUScalar (remember to kiss your warranty goodbye).
Skip a webcast this week, get a to-go sandwich and read this article by Vanitha Prabhakaran. It explains the Direct Push technology, how it works and how its troubleshooted. This should be required reading by anybody involved in Exchange/Mobility. Read it here.
So in an attempt on shaking the stupid off I figured I should post a few resources on mobility that I use as a resource every day. For example, if you're creating a reliable and redundant messaging platform with Exchange 2003 for a larger organization there are good odds you will not find a wizard. The SBS Mobility will not help there. First, there is an awesome document on deploying mobile messaging over at Jason Langridge's blog. Start there. It is the only document out there that goes in great detail on MSFP. That will get your Exchange talking to your phone in more ways than one. Second, this mobility stuff is new (to Microsoft at least) so there is a lot of undocumented behavior in devices and ActiveSync that only developers can see. Microsoft is trying. In addition to the central mobility blog from the Windows Mobile Team, there is also a documentation leaf blog. When you are ready to really dig into Windows Mobile and all it involves you pretty much have to deal with developers. Start with Marcus Perryman, bookmark the MSDN Mobility Library, sign up and live on xda-developers forums and do the improbable task of not crippling your system with the WM5 emulator and dev kit. If there is one thing, one thing, you should del.icio.us out of this whole post its the Channel9 Mobility Wiki. But I don't like to read... Now I know there are a lot of you out there that just cannot read a whitepaper. Something about lots of words and scribbles on white paper without pictures is just not appealing. No need to despair, you can always resort to stalking. You sort of have two options here. You can stalk Peter Galagher who is the mobility expert on the SBS PSS team but he is a pretty tall guy and might kick your ass. The more attractive (sorry Peter) alternative is in Vanitha Prabhakaran who is on the Exchange PSS team. If you're in Europe there are always mamaich and Tuatra from xda-developers.com. So there you go, for developers and stalkers, those are some resources to mobility. Hope it helps.
The SBS & WM5 whitepaper has been released earlier this week. Download it here. I was on the edit team and was not paid so if you don't like it.... $245 to answer questions. Really its quite good, the only missing thing is the part about the ISA 2000 paper. I guess they were really aiming for the sales-side and ground-level technicians and assumed people didn't use ISA 2000 in SBS which is why you won't be able to use this document to get push mail to work. As a slightly higher end resource, check out the Inside SBS podcast on mobility which aired recently. Peter was also on the edit team and was the first one of us to get MSFP so if you've got $245 he is the man to call. I'm installing the new PBX so I probably won't pick up the phone :) Update: Apparently I did not get the final published doc, in which the stuff bounced between me, Mike, Vanitha and Lawrence ended up in the doc. Thanks to Michael Cocanower for bringing this up to my attention.
The subject line says it all: Microsoft (well, iMate) finally delivers on the promise of push mail. Blackberry, R.I.P. http://msmobiles.com/news.php/4983.html
Ok, you need this. Thats all I can say. The new PocketPC web browser based on Mozilla/Firefox code has just been updated to 0.13 and it has some huge improvements. First of all, tabbed browsing. Yes, tabbed browsing on your phone. No more navigating back and forth, open as many maps, pages and directions as you need. Second, and finally, a decent RSS aggregator for your Pocket PC. Need I say more? Go download it! Ok, now the eyecandy:

According to this post by Daniel Melanchthon Mobile Push mail that is coming with Windows Mobile 5 may not work out of the box on Microsoft Exchange 2003 SP2 if ISA 2000 is installed (which particularly also affects SBS 2003). Here is the thing, ActiveSync negotiates Push with the server by checking if its even available. According to Amy Babinchak, if ISA 2000 is installed by default it does not pass OPTIONS it does not know to the published server. Since Outlook Mobile Admin resides on the Front End server of Exchange 2003 SP2 deployment (or just the SBS server) request for options would pass this back: =-=-=-= Server Response =-=-=- HTTP/1.1 200 OK Content-Length: 136 Date: Mon, 30 Jan 2006 19:30:13 GMT Content-Type: application/vnd.ms-sync.wbxml Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Pragma: no-cache MS-Server-ActiveSync: 6.5.7638.1 Effectively, push mail will not work with Exchange 2003 SP2/SBS & ISA 2000 installed without adding the following registry key: HKLM\System\CurrentControlSet\Services\W3Proxy\Parameters Value Name: PassOPTIONSToPublishedServer After it is added the OPTIONS keyword goes to the Exchange server which hopefully produces the following response: =-=-=-= Server Response =-=-=- HTTP/1.1 200 OK Date: Fri, 13 Jan 2006 14:13:41 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Pragma: no-cache Content-Length: 0 Public: OPTIONS, POST Allow: OPTIONS, POST MS-Server-ActiveSync: 6.5.7638.1 MS-ASProtocolVersions: 1.0,2.0,2.1,2.5 MS-ASProtocolCommands: Sync, SendMail, SmartForward, SmartReply, GetAttachment, GetHierarchy, CreateCollection, DeleteCollection, MoveCollection, FolderSync, FolderCreate, FolderDelete, FolderUpdate, MoveItems, GetItemEstimate, MeetingResponse, ResolveRecipients, ValidateCert, Provision, Search, Notify, Ping Now please remember that this applies to ISA 2000, not 2004. I am obligated to say this again to limit the comment outrage: There is still NO device on the US market that has Microsoft Mobility & Security Feature Pack (Push Mail) available.
Las Colinas PSS guys are back. Last week when you were spending an extra hour with your favorite Indian they got a chance to record an awesome podcast on mobility with WM5, SBS, IIS, ActiveSync and everything involved. The sound quality is superb, it is beyond compare to the previous shows so go and give it a listen. MP3: Download the podcast RSS: Subscribe to the feed
Microsoft Mobility & Security Feature Pack (MSFP) beta has been leaked. Check it out, it seems to be an older beta of MSFP, try at your own risk. This one requires a flash so please think twice. Download it here.