The Electric Wand : Exchange, Office

Exchange in the cloud or on the ground?

Ewan — Wed, 18 Nov 2009 10:02:42 GMT

Following the price cut on the desperately-in-need-of-renaming BPOS services recently, I’ve been talking with a few people about the where the tipping point might be for running Exchange in house vs using some form of hosted provision.

There are plenty of reasons why a hosted offering makes sense. More and more end-users are away from the office (using web access, mobile devices or VPN-less connectivity such as “Outlook Anywhere” that’s been part of Outlook for the last 6 years), and as the user end-point is increasingly mobile, it starts to matter a lot less where the server end is.

In the first 3 versions of Exchange (4.0, 5.0 and 5.5, released in 1997 and 1998), the accepted rule was that servers would be placed in the same location as clumps of users (say, if you have more than 30 users in a remote office and anything other than a great WAN connection, you’d drop an Exchange server on-site.

Since the client and server maintained a constant connection with each other (using MAPI over RPC, if you’re interested), and since wide area networks for most companies were in the few hundred kilobits between sites, the default was pretty much that servers tended to be in the same physical location as the users.

As network capacity improved (and costs fell), combined with server capability improvements (and price reductions, and technology like Outlook cached mode and the shift to using web access as an alternative, it became more feasible for organisations to centralise and consolidate Exchange into one or a few physical locations – such as Microsoft famously did, by moving from many locations in Exchange 2000 to just 3 in Exchange 2003.

So the position we’re now at is, it pretty much doesn’t matter to an end user whether they’re connecting over a company wide-area network to a remote Exchange server, or if they’re connecting over the internet to one that sits in someone else’s datacenter.

If you’re an organisation with few hundred users, then you probably don’t have a dedicated Exchange administrator who does nothing but feed and water the email system. Moving to an online hosted model such as Microsoft Online or one of the many “Hosted Exchange” partners who offer a more tailored service, could mean a significantly lower cost of operations when measured over the next few years.

Since Hosted Exchange providers and Microsoft Online will both move towards Exchange 2010 in the near future, it’s something that every current Exchange users should consider – is it time to consider moving some or all of your estate to a hosted environment, or you do have specific requirements around backup retention or data control, that you absolutely need to have your own servers on your own soil? If the latter, then maybe “cloud” based email isn’t for you, but Exchange 2010 “on-premise” would be the right choice.

Outlook 2010 beta and E.164 number format updater

Ewan — Tue, 06 Oct 2009 23:26:14 GMT

Well hello again; it’s been a while.
Normal service should now infrequently resume.

I thought I’d update the instructions of a previous post, after I was showing someone how to use my old “Contacts updater” application to make all their Outlook contact phone numbers be E.164 compliant.

(see blogs passim. eg here, here, or here.)

Now the little app I reference is an Outlook custom form, meaning it gets installed into the Exchange mailbox folder, rather than some client-side Add-in to Outlook. Custom Forms have been available since the days of the Exchange 4.0 client and later Outlook, as the installed forms show up an item on the “Action” menu within the view of the folder.

Now that Outlook 2010 has adopted the Fluent UI (aka the “Ribbon”), things have moved somewhat…

Just like the early days of Office 2007, the initial response from some users might be to get annoyed that things are in a different place, but in most cases, it’s a great improvement.

Since custom forms in Outlook have largely faded into the sunset, this particular one gets a bit more obscure… it’s a question of going to “New Items” within the folder, then selecting the “Custom Forms” pop-out (only available when you actually have some custom forms installed in that folder), and any forms installed will be presented there.

Office 2007 SP2 now available

Ewan — Tue, 28 Apr 2009 21:47:45 GMT

I’ve been beta testing Office 2007 SP2 since the beginning of the year, and it’s been great – the single biggest reason to use it is the myriad improvements made to Outlook, in terms of stability & performance (particularly relating to search and to startup & closedown).

Download Office 2007 SP2 here

From the summary of what’s new, check out:

Microsoft Office Outlook

Performance improvements that apply to the following general responsiveness areas:
- Startup
  Removes lengthy operations from initial startup.
- Shutdown
  Makes Outlook exit predictably despite pending activities.
- Folder View and Switch
  Improves view rendering and folder switching.
Calendar improvements
Improves underlying data structures and the general reliability of calendar updates.
Data file checks
Greatly reduces the number of scenarios in which you receive the following error message when you start Outlook:

The data file 'file name' was not closed properly. This file is being checked for problems.
Search reliability
Improves search reliability when you use SP2 with Windows Desktop Search 4
Improvements to Really Simple Syndication (RSS)
There are now fewer duplicated items.
Object Model improvements
Now contains many customer-driven fixes.

For more information about these improvements and details about other Outlook fixes, click the following article number to view the article in the Microsoft Knowledge Base:

968774 Outlook 2007 improvements in the 2007 Microsoft Office suite Service Pack 2

Outlook Thread Compressor download now available

Ewan — Sat, 11 Apr 2009 16:34:00 GMT

Nearly a year ago, I wrote about Thread Compressor on here – it’s an add-in to Outlook which removes unnecessary emails, on the assumption that most people reply to mail and leave the original intact, so you could keep the last mail in each branch of a thread, and remove all the others.

Way back when I was still developing TC, I tried to get it included on the Office Downloads section of Microsoft.com, but our legal department was (with some justification) very nervous about us offering a download which would go through the end user’s mailbox like a dose of salts, deleting stuff. So it stayed (more or less) an internal tool: I even started developing a “version 5” with a much groovier UI and some extra features.

Included in the v5 beta (which is a real pain to install nowadays – the previous v4.2.030 version has nearly the same feature set and is a lot more self contained), was a piece of logic which captured stats on TC usage and emailed them back to me.

Since many people at MS are still running that beta (it’s a long story, but the source code went south so it’ll never get out of “beta” state), I still get maybe 20-30 statistics mails a day…

Since August 2003 when the first statistics email arrived – from me, kind-of naturally – until 24th April 2007 (when I last did an analysis of the stats), TC v5 beta had scanned over 400m email messsages and had compressed over 30m, worth nearly half a terabyte of email data.

To the reader, the spoils

Well, I finally decided – in an “ask forgiveness rather than permission” move – to make the last complete and stable version available for download.

It’s not particularly elegant looking by modern standards (given that most of it was written 7 years ago in VB6) but it does work, even on Windows 7 (x86 and x64) and Office 2007. Basically, anything post-Office 2000/Windows 2000 should be OK.

A reader called Mark Ruggles emailed me the other day and said:

“It is fantastic and it works like a champ in Outlook 2007. I turned it loose on my Inbox and my archive and I deleted 103Mb of redundant data. I sent it out to some of my colleagues and my manager used it cutting his archives down by 2Gb.
…
This is the coolest utility I’ve found in a long time.”

So, thanks to Mark's comment, I’ve now registered www.threadcompressor.co.uk and posted install instructions and a download file up there.

Tip for finding when an appointment was created

Ewan — Mon, 21 Apr 2008 15:52:35 GMT

Here's a tip for when you suspect someone has magicked up an appointment to coincidentally collide with an Outlook meeting request you sent them...

In your own calendar (and other people's), you can see when a meeting was scheduled (ie request was sent or created), as well as other facts (like when you accepted it) - eg:

If a blocked out time in the calendar is just an appointment (ie something that was just put there by the owner of the calendar), you don't see the date it was added...

Remember, they're all just forms in the end

Way back when Exchange was young (it started at 4.0), the design was that emails/meeting requests etc, were just an "item" (which is a collection of fields, different depending on the type of item it is), and a "form" which was associated with a particular kind of item using the Message Class to denote it.

In other words, an email message would have fields like Sender, date, recipients, subject, etc. And when you went to open a message, the Exchange client (later, Outlook) would look at the class on the item (IPM.Note, for a message) and would find the appropriate form to open that item. Clear? If you really want examples of lots of different Outlook items, see MSDN.

Anyway. If I'm looking at an appointment which wasn't a "meeting" (ie it was just put into my or someone else's calendar, not via a meeting request/acceptance), I might not be able to see the date it was created, but the underlying item definitely does have that property. Displaying it in Outlook is pretty straightforward, if a little contrived. Here's one quick & dirty method of doing so (I may post a more elegant solution if there's interest)...

1. Get to "Design this form"

Older versions of Outlook had a Developer item on the menu structure which allowed you to select (via several pop-outs if I recall) to design the current form. Outlook 2007 simplified the menus (now using the Ribbon) and no longer shows that Developer menu. One quick way of putting it back is to add that specific command to the "Quick Access Toolbar"...

Click on little down-arrow just to the right of the Quick Access Toolbar on the top left of a form (eg the form of the appointment you're looking at), then choose "More Commands"...

On the resulting dialogue, select Developer tab in the "Choose commands from:" drop-down list box, then scroll down to find "Design This Form" (note "This Form", not "a Form...". Select that command, click on Add, then OK out of the customize dialogue.

Now you have a little icon supposed to represent designing actions (pencil, ruler, set square) in your toolbar:

Click on the icon and you get into the form designer, with the current item being loaded. You'll see a bunch of tabs - these correspond to "pages" within the form, and any in brackets are hidden. Select the "All fields" tab, choose Date/Time fields from the drop-down (or try "All Appointment fields").

You should now see just the date fields, including the original creation date...

This might seem a real palaver, but once you have the icon on the QAT, it's a 5 second action to show the dates... and can be very handy :)

The lost art of the OOF

Ewan — Sun, 30 Dec 2007 01:10:02 GMT

Some time ago, I posted about how the ".sig" has faded from grandeur. I'd like to add the somewhat terminal dryness of the OOF message to that list, and propose a solution.

OOF is a Microsoft term for Out of Office. It should really be OOO, but is stuck in the days of the predecessor to MS Mail and Exchange. See http://msexchangeteam.com/search/SearchResults.aspx?q=oof for myriad stuff on OOFs, and here (on why it's OOF and not OOO) for one of the first - and for a while, most-read - blog posts on the Exchange team blog.

I've seen a lot of OOFs in my time, and many are of a hugely unimaginative nature. Some are kind-of smart in that they convey the most information in the shortest amount of characters (eg "oof til 7/1 - mail jbloggs if urgent") whereas some have clearly been lovingly hand crafted.

When I worked in the Exchange product group, I sent a mail to one particular guy (who is ex-pat Brit but had been over in Redmond for some time) on the 16th December. Turns out, he'd gone "home" for "the holidays" and I got:

I am so on vacation. By the time I get back, I expect things will look different. See you on 1/17/05. I probably won't ever read your email. Sorry.

There's something refreshingly honest about that - it's admitting that he's not going to be on email for at least a month, by which time, anything he got sent in email will be out of date. Brilliant. Helps build a case for Instant Messaging if you ask me.

Probably the best OOF I've seen came from a somewhat eccentric Canadian (who once replied when I mentioned I'd seen him the previous evening in New Orleans, clearly having a Nice Time), "oh yeah... any night when I don't end up in jail has to be a good night"). Enjoy...

It happened. I knew it would happen some day, but never dreamed it would happen so soon. I tried to hide it from everyone, but word got out and boy did I catch hell for it. Yes, as embarrassing as it is, I must confess before God and country that I was caught, red-handed, Getting Productive Work Done In The Office!

People, please: do try to control your Shock and Horror. I know we used to do real work Long Ago, but we've moved past that, haven't we? It was an honest mistake; an accident in the truest sense of the word. I did my best to hide it from everyone and thought I was successful around the children and my more-dense co-workers. But there is only so long one can live a charade, and in the end, like a house of cards in a hurricane it came down, down, down...

To pay for my egregious act of productivity and practical effort, I've been sentenced to two days of offsite meetings by a jury of my direct management.

Yes, kiddies, that is Two Whole Days of unbridled Tag-Teaming, Outlining, Problem-Solving, Situation-Analysing, Team-Building, Proactively-Leveraging, Federating, Brainstorming Facilitation and Group Contemplation. Unpack the markers and the big pads of paper, Martha: we is gonna have an offsite!!

Can you already feel the sweat drip slowly down ewers of water; the ice cubes grumbling with frustration at their inevitable doom in a pastel room filled with inoffensive Corporate Art? Can you see the elegant buffet of Northwest Grilled Salmon Medallions lounging in a Light Cream Sauce over chirping steam trays, accented by a tossed salad of Garden Fresh Greens? Can you hear that first person raise their hand to state, two hours into to the discussion, that "Before we go any further, we need to define the problem" only to be followed seconds later by another person wondering "what are the criteria for success?"

Do you get the idea that at some point on the first day, I'll be screaming out "BINGO!" to a very confused audience?

Ah; they're used to it...

A co-worker once told me you could solve any team problem with a case of malt liquor, an afternoon of skeet shooting and a strip club. He's no longer employed at the company (something to do with an offsite of his own gone terribly awry near the Montana state border) but I think he was on the right track.

Where I am going, there are no visiting hours, and even worse: no conjugal visits. I might be reachable at <number>. Heck, if it's really important, email or text me. Rumour has it the gardener can smuggle those in hidden in his watering can...

See you on The Other Side,

ian

Now I ask only one thing. We must all put some degree of (professionally relevant) imagination into our OOFs. It's only respectful to the poor sods still at work who're sending us email whilst we enjoy a few days out, isn't it?

Have a Happy New Year, everyone. And please, for the sake of the rest of us, make your OOFs mean something special. Or funny. Or whatever.

Bulk update Outlook Contacts' phone numbers to be E.164 compliant

Ewan — Fri, 30 Nov 2007 12:10:29 GMT

Here's a quick & dirty tool I put together for Outlook to be able to update all the phone numbers of contacts to make them E.164 compliant. It relates back to a post a while back around the challenges of formatting numbers 'correctly', particularly important once you get into using click-to-dial technologies such as Office Communication Server.

The tool itself is basic since it's only really expected that people will run it once, to sort out the numbers of old contacts you might have. It will check all the contacts in a given folder and automatically fix the numbers up, but there are a few caveats...

It's hard coded for UK numbers beginning +44 ... though the code is pretty easy to get to if you know anything about Outlook forms, and you can modify it at will.
It doesn't back up the contacts before modifying, so you might just want to copy your Contacts folder somewhere else before running, if you're of a nervous disposition. I can verify that it hasn't mangled any of my contacts and nobody in Microsoft who's tried it has reported a problem.
It's not exactly straightforward to install - but if you follow the instructions carefully, you'll be OK.
The document in the ZIP file explaining how to install & run it, is in Word 2007 format (docx). If you still haven't either upgraded or installed the compatibility pack to add OpenXML support to your older version of Office, there's a link in the ZIP file to go straight to the download page.

A final word: this is completely unsupported, supplied "as is" etc. If it does mangle all your contacts up, just revert to your backup copy - and if you didn't take a backup then you've only got yourself to blame.

Harsh but fair I think :)

Enjoy.

The logic converts "from" the format on the left to the format on the right... (_ denotes a space)

Old format number begins	New format number begins
0	+44
(0	+44 (
+44_0	+44_
+44(0	+44(
+44 (0)	+44
+440	+44
(0)	+44_

Examples

old number	New number
0118 909 1234	+44118 909 1234
(0118) 909 1234	+44 (118) 909 1234
+44 0118 909 1234	+44 118 909 1234
+44(0118) 909 1234	+44(118) 909 1234
+44 (0)118 909 1234	+44 118 909 1234
+440118 909 1234	+44118 909 1234
(0)118 909 1234	+44 118 909 1234

Outlook 2007 signatures location

Ewan — Mon, 25 Jun 2007 17:51:31 GMT

Following my post about .sig files, I had cause to dig around looking for where Outlook actually puts the Signature files. I came across a post which Allister wrote a little while ago, but it's such a useful little tip that it's worth repeating...

Basically, Outlook 2007 offers a nice simple editor UI for building your own signatures, however it's complicated by the need to present the signature in HTML (the default format for mail now), Rich Text Format (aka RTF, the original Exchange/Outlook format dating back to the mid 90s) and plain old Text (with total loss of colour, formatting etc).

Outlook actually generates 3 versions of the sig, to be used for the different formats. In some cases - notably with plain text - the end result following the conversion isn't quite what you'd want... my nicely formatted .sig about comes out a bit mangled, as

Ewan Dalton | | Microsoft UK | ewand@microsoft.com |+44 118 909 3318 Microsoft Limited | Registered in England | No 1624297 | Thames Valley Park, Reading RG6 1WG

so it may be necessary to do a bit of tweaking to the formats. Do bear in mind, that if you do edit the sig files directly, then go back into the menu in Outlook and make some other change, your original tweaks will be over-written.

Anyway, you could find the signature files in something akin to:

[root]\Users\[username]\AppData\Roaming\Microsoft\Signatures

(there may not be a \Roaming folder, depending on how your environment is set up, or it may be in \Documents and Settings\ and under an Application Data folder depending on your version of Windows).

Thread Compressor for Outlook - do you want it?

Ewan — Tue, 24 Apr 2007 01:35:22 GMT

Here's an appeal - nearly 8 years ago, I wrote* a little COM addin for the-then new Outlook 2000, which "compressed threads". The idea was that it could take an email thread (eg a discussion over a period of time and a number of responses, from any number of people, and typically sent to a distribution list for the purposes of discussion), and compress that thread down to the salient points. It has evolved over a few iterations since but has been largely dormant for the best part of 5 years - it does everything I need it to do, so I've never developed it any further (and if truth be told, a hard disk crash blew away the source for the last version and I could never face going back to a previous beta and re-developing the changes I'd made).

I'd like to understand if anyone else would like it.

The basic assumption with Thread Compressor is that when people reply using Outlook, they tend to add all their comments at the top - some do inline replies, but most eschew that - and don't edit the original contents. If this assumption holds true, then it would be possible to compress all discussion threads down to only holding onto the final email or the final post (to a public folder) since it will contain the entire history of that branch of the thread. Of course, there may be multiple branches of the thread, and Thread Compressor handles that.

The first time many people run TC on a large folder, it will routinely get rid of 50% or more of the content, so proves useful in slimming down folders where you archive stuff, or folders where distribution list contents are sent by Outlook rules, never to be read but to be indexed by Windows Desktop Search or similar.

In my last run, I scanned almost 1Gb of email and the Thread Compressor discovered about 21Mb of mail which could be removed... not quite as dramatic as 50%, but it saved me reading over 1,000 emails and it reduced my mailbox size a little...

There are a few obvious benefits to thread compression...

It reduces the size of your mailbox, so keeps you under-quota
It removes spurious email so you have less stuff to plough through
When searching, it reduces the number of hits since it won't return every mail in a thread which contains the same word(s)

... but some obvious potential downsides...

The assumption at the top of this post. If I reply to someone's email, but change the contents of their original message in the reply, then TC will retain the modified version and it will look like the originator really said that. There may be ways to work around this limitation now, but I never bothered to figure them out.
Legal compliance - maybe you need to keep a copy of every mail for compliance purposes: if so, users programmatically deleting messages could be a *bad thing*.
erm, can't think of any/many more...

If you think this kind of functionality should be either built into Outlook or available as an opt-in addon, then please let me know. We have many thousands of regular users of Thread Compressor inside Microsoft. It would be cool to think of millions more outside as well...

//Ewan

* The really smart bit of TC was actually put together by a guy called Peter Lamsdale. All I did was take his algorithm - which I still have difficulty understanding much less explaining - and strap a UI around it. An earlier version of TC was published (unofficially) on a website and an article was written about it by Evan Morris. There is even an unconnected MSDN bit of sample code which is nowhere near as effective (IMHO)