Our network runs Exchange 2003 with SP2, the application-level firewall ISA 2000, and now Windows Mobile 5 devices (which I’m not happy about) trying to connect via the new TCP/IP Activesync 4. The ISA server passes Activesync 4 traffic to those shiny, new Windows Mobile 5 devices (I could see the traffic), but it filters the content and is keeping Exchange SP2 policies from being applied. I understand ISA 2004 doesn’t have this problem, but an upgrade to ISA 2004 isn’t in the budget.

There is a fix in Microsoft’s Knowledge Base, but it references only ISA 2000 and not Exchange SP2, Windows Mobile 5, or Activesync 4. I found it via Neil Chapman’s article Exchange SP2 and feature pack issue with ISA 2000, which says:

If you use ISA 2000 to reverse proxy your Activesync requests, I’ve come across an issue where the Exchange server cannot apply the new policies to a WM5 MSFP device.

Basically, the ISA 2002 firewall server filters the Activesync headers and doesn’t forward all necessary data to the mobile device. The fix for ISA 2000 requires BOTH the latest ISA service pack and a registry change to allow all the communcations options to be passed via Activesync:

Once the ISA 2000 Service Pack is installed, set the registry key DWORD HKLM\System\CurrentControlSet\Services\W3Proxy\Parameters\PassOPTIONSToPublishedServer - Data value to 1, and reboot the ISA server.

Then all those nice Exchange SP2 policies for mobile devices will be applied correctly.

Article tagged: Exchange, server, 2003, SP2, bug, fix, Windows, Mobile, ISA, 2000, activesync, headers, forward, firewall

We’re running Windows Mobile 5.0 Smartphones in my office now and I’m not happy about it. Any other IT managers working at legal or accounting firms can understand the frustration of being unable to stop technophile partners from bringing in new technology. With many partners asserting their “ownership” the firm it’s near-impossible to get a consensus on when to implement “cool” things. …but I can always tolerate that, I’m really unhappy about the Windows Mobile 5.0 OS and its new ActiveSync system.

<Actual Troubleshooting tip here:>
Odds are that you’re using USB to connect to the PC, and that your having problems with it… that’s the same thing we saw with every device our users installed before consulting the manuals/IT-staff. For solutions, first check out the basic Windows Mobile Help site, in case any new patches will eliminate errors. Then, look to the ActiveSync 4.0 USB Guide for pseudo-tips like “it’s not ActiveSync, check your firewall/VPN/USB docking station/parental control tools” - so why is a “USB Guide” if the problems described are all TCP/IP issues?

The number one solution, try to enable the ActiveSync ports and executables (listed on the “USB Guide”) before installing ActiveSync. Once we saw communication errors a reset of the device and a reinstall of ActiveSync was almost always required.
</:End of Actual Troubleshooting tip>

While my users may not like that their shiny, new PDAs don’t work, I’m slightly consoled by the fact that I’ve managed to stem the tide of Windows Mobile 5 for this long. After all, Stephen Manes a writer for Forbes has already seen the issue and gotten the article published: Smart Phone. Stupid Software. (signup required or use BugMeNot.com for login, and article may only be free for a limited time, so check Google’s cache for the full article).

I think anyone’s best bet at supporting Windows Mobile 5.0 is …to prevent those devices from being purchased until they’re running Windows Mobile 5.1-5.9. Just remember to skip 6.0 too…

If you’re an employer, consider my attitude about supporting new products - it’s great to get to learn on the newest toys, but it stinks when I’m surprised by a completely new system. Really, new technology launches are a great chance for employers to provide a low-cost, high-value benefit for IT employees. The problem here is that neither myself nor any of our admins/techs know Windows Mobile 5, but we’re being asked to support it. Instead of learning new things on our own schedule we have to put aside all the network upgrades and development projects to learn how to use, and then how to fix, a few desktop devices. Since most of my staff is in this business because they like technology (it sure isn’t for easy money and short working hours) I could really help with retention and Help Desk attitude if the firm would buy an extra device that I could give out to whomever would be willing to put in the extra time to learn it.

Article tagged: Windows, Mobile, 5.0, ActiveSync, SmartPhone, sync, error, help, TCP/IP

Are emails sent from a Smartphone taking several days to be delivered?

Several settings need to be just right - but it’s an Exchange 2003 error and not a Smartphone problem. An email sent from a Smartphone and addressed to a domain outside the organization via Exchange 2003, with an SMTP connector configured to send SMTP messages to an external domain, will delay a message without Enter pressed at the end.

Microsoft has a patch for Exchange 2003 to correctly recognize the end of these messages and correct the delays.