Exchange Active Sync Fails After Transition From 2003 to 2010

The title sums this one up with ease. After transitioning / migrating from Microsoft Exchange 2003 to Exchange 2010 some of the first accounts that we tested with were unable to connect to EAS. Errors on the mobile client ranged from server not found/available, to bad user name and password errors. After much research and troubleshooting I came across a few users that were experiencing the exact same issue. You can read more about the issue and the fix here.


Debian Squeeze & Broadcom b43 etc

So you like Debian, and why wouldn’t you, it is great after all. Unfortunately, many laptops come from the factory sporting Broadcom-based chipsets. So inevitably I complete a Debian install and Broadcom takes the wind out of my sales. I then trudge over to and go through the paces. Why? I do it over and over. Well enough is enough, I mean this isn’t a tricky script to write. So for your enjoyment, I have put it all together into a small bash script to simplify things for future installs. First, be sure to add the non-free repo to your /etc/apt/sources.list file.
Then create and run a .sh file containting:

aptitude update
aptitude install module-assistant wireless-tools
m-a a-i broadcom-sta
echo blacklist brcm80211 >> /etc/modprobe.d/broadcom-sta-common.conf
update-initramfs -u -k $(uname -r)
modprobe -r b44 b43 b43legacy ssb brcm80211
modprobe wl