Archive for August 3rd, 2013


So, I recently decided to retire my Exchange 2003 server, in favour of Exchange 2007.

There were a lot of reasons for this.

Firstly, my Windows 2003/Exchange 2003 server was an old HP DL380 G3. In itself, a great, reliable server, which cost me only £20 off Ebay, but getting on a bit, and very noisy in my home office, especially combined with the HP DL 360 G2 I was using for an Untangle server, and the newer Dell T105 which was already running Windows 2008 and Exchange 2007.

Secondly, at work we have Exchange 2007/2010, so I had a desire to expand my skills to better enable me to understand the environments I need to support.

Thirdly, I wanted to also migrate a number of sites I ran (OWA, WordPress) over to IIS 7 due to the improved security features, and ease of management.

And last, but by no means least, the two HP servers are making my electricity bill look like that of an actual data centre, so I wanted to retire them both, enjoy the quieter office, and save some pennies.

The migration from Exchange 2003 -> 2007 was really not so difficult, with the only issue being the move of my wife’s mailbox, which reported there may be activesync issues. It would be her account! She did have issues, so I had to re-do the account on both her iPhone and Galaxy Tab, but all was fine after that.

So why, I hear you asking, is it more secure, but more annoying?

Well, certain feature like tarpit are enabled by default, and also it’s more secure when trying to connect over telnet, and it has some excellent anti spam features built in.

Now comes the annoying bit. Many things can be done via the GUI, but if you want to get at all the really neat stuff, you have to visit the Exchange Powershell CLI. Yes, I said CLI.

For example, enabling the anti spam features requires running some scripts from the CLI, as does adding a list of custom blockwords to the anti spam component.

You can add blockwords via the GUI, but it takes FOREVER!!!!

Same goes for blocked email domains and senders.

CLI = power in the case of Exchange 2007 and beyond. I guess I’d better get used to it!!

So, it’s been a while now since I updated to Jelly Bean, and also since the enforced factory reset due to the fact that things just weren’t quite right after the update.

The factory reset really was the charm though, as everything is running beatifully now, and the battery life is nothing short of amazing compared to before.

What I have noticed though, is that my Nexus 7 doesn’t seem to suffer in the same manner as my One X or Galaxy S2 (Work phone).

It has now had 2 or 3 updates with no factory reset rquired, so that does beg the question ‘Do skinned versions of Android have an update issue?’.

I’d certainly like to know, so if there is anybody out there who has a vanilla Android device, has found a factory reset is needed for updates, please comment!

Otherwise it has got me wondering if my next phone will be an unadulterated Google device. Don’t get me wrong, I love HTC Sense to bits (Touchwiz, not so much), but if it means I have to do a factory reset for each an every update that comes through, I won’t be too happy.

My S2 did just get an update to Jelly Bean, and so far seems fine without a reset, but I’m keeping an eye on it. Maybe It’s just the main version updates that need it, who knows.

For now though, happy bunny, lets just wait to see what the next update brings.

Join the Forum discussion on this post