Office 365: A conversion in more ways than one
Our implementation of Office 365 also marks my conversion from cloud computing sceptic to evangelist. Ironically it was the day after my Xero one year anniversary that we moved to Office 365.
I came from a traditional server and infrastructure background and didn’t know much about cloud computing when I started at Xero (other than that syncing your photos via Picasa was really handy). I distinctly remember looking at our outsourced 3rd party mail system and thinking “we need to bring that in-house and manage the servers ourselves like you are supposed to.”
But as my first few weeks of Xero life rolled by I started to realise how cool and powerful cloud computing is and how well it fits Xero’s own use. I couldn’t believe it, but in a few short months I found myself fully endorsing a move to a cloud based email system and I couldn’t wait!
After the decision was made, Office 365 soon became the logical conclusion for us. It’s one of Microsoft’s more exciting products and it’s still running that familiar exchange platform that many of us know and love. It solves a lot of problems, especially in terms of infrastructure.
We have a global presence with several offices around the world. To replicate what we get with Office 365 globally, utilizing a traditional in-house server model, would mean standing up quite a bit of infrastructure, adding a lot of complexity to our environment, and requiring much more support staff. Office 365 didn’t just give us email too; we get Lync which is a great tool and a pretty decent upgrade to the currently used Skype, and of course SharePoint online. Microsoft seems committed to the platform, introducing all sorts of cool features next year. And all this comes with a 99.9% uptime. A lot of our core applications are also Microsoft based (Office, Yammer etc), so choosing a product that integrates with these was extremely important.
Unfortunately my enthusiasm dampened when I looked at the task at hand. Most existing mail servers are either connected to a company’s Active Directory (a centralised source of usernames, passwords and company data that is used when you “log in” to a computer) or not connected to Active Directory (products like gmail etc). We had a system that was connected to the ugly stepsister of Xero’s own Active Directory. It was hosted in a fake Active Directory “bubble”, where all user names and data closely matched our own Active Directory. Although that might sound like it would make things easier, it actually made things a lot more difficult. Conversely our Active Directory was an empty shell. Usernames were in there, but that’s about it. The introduction of Office 365 would also introduce Active Directory as the single source of truth for all our applications – this meant we had to collate and import a lot of data. For the first time (from a Xero point of view) all this information was in one place.
The first step was to get an export of data from our current solution. This included user information, distribution groups, mailbox rights etc. This data then needed to be “massaged” so that it could be imported into our own Active Directory – a tough and laborious task which involved other internal groups such as HR to ensure the data was correct. We also had to factor in the addition of extra information from other sources (mainly other contact details such as cell phone number, office address etc), which were included on our intranet but not in the “other” version of our Active Directory. After much pain and suffering the data was eventually imported into our Active Directory. But we were still several months away from actual cutover – this initiated a period of keeping both our Active Directory and hosted email system up to date. Each change in one system had to be replicated in the other, a tricky task given the rate of change at a company like Xero.
It sounds crazy now but we then had to solve one of the biggest technical challenges of the transition – email signatures. Yes email signatures. With the old email system a product called exclaimer was used to stamp a person’s email signature to outgoing messages. The signature was constructed as it left our system based on their details contained in the “fake” version of Active Directory our hosted email platform utilised. This solution caused us many issues and a lot of support time spent correcting them, especially around the look and feel (any design change precipitated many weeks of difficulty trying to get the format correct).
A centralised client based solution would be ideal. However, with our mixed OSX and Windows environment this proved very difficult. We researched many products but none were suitable, as the OSX platform did not support any of them. In the end we decided a web based solution would be the way forward (cloud based systems to the rescue!) – this would also need to be tied to our Active Directory to keep that single source of truth permeating through. Disappointingly we couldn’t find anything off the shelf that could do this, so we ended up having to employ a 3rd party to develop our own bespoke web application. It seemed a lot of effort just to get a person’s email signature in place! But we achieved we set out to do, a consistently branded email signature that we could easily update and change in the future.
Once done it was then onto the migration itself. Thankfully we never got into the habit of using .pst files at Xero so all mail data was stored in a particular person’s mailbox. This meant for some hefty mailbox sizes (a select few pushing over the 10GB mark – large by corporate standards). We also faced the same issue whereby we could not migrate from an existing exchange implementation, so the transfer of data was problematic. Luckily for us a product called migrationwiz came to our rescue and we set down the long road of our initial migration of data.
Before we knew it we were only a week away from cutover and still had not obtained our licences from Microsoft. The whole system was still running on trial licences. We also discovered that the approach to the migration was potentially wrong and that we would need to actually migrate our data after we had cut across, not before as we had planned. This was due to the fact we would likely cause several double-ups of email messages when we attempted to do the final sync of email. It was also about this time I started to panic a little.
However we pulled ourselves together and focused on the task at hand. The data migration approach was adjusted and the licensing (after several “high level” discussions with Microsoft) arrived a day before the cutover. We were go for launch!
The weekend of the cutover itself was in some ways a straightforward affair. However, the team pulled some long hours both days to make sure we were ready. Because our iPhone users have their contacts in Exchange we then turned to another cloud based product, Airwatch, to centrally reset everyone’s email profiles. On the iPhone suddenly SMS messages weren’t showing who they were from, just numbers, which would have freaked a few users out. We fired off a parallel contact sync and contacts were all quickly restored across the company in minutes. Another massive benefit of having things in cloud and cloud enabled devices.
Monday hit and the preparation we had done served us well. Personally I felt that the power of Yammer as a communication medium really shined through as we were able to help people in real time in multiple locations. As our other offices came online, the team worked through the night ensuring everyone was able to get their email.
And here we are, enjoying the fruits of our labours and utilizing the Office 365 platform. It went well and although there were a few bumps along the way there was minimal disruption to the general Xero workforce. For me it was a bit of an early Christmas present to get the company onto such a cool and exciting platform, as well as to finally see the realization of so much hard work come to fruition. It’s also a good feeling knowing that Office 365 is really just a first step in many improvements to our internal infrastructure – bring on 2013!
7 January 2013 #
8 January 2013 #
8 January 2013 #
14 January 2013 #