Taking the plunge with Office 365
Posted on 27 Mar 2012 at 10:09
Jon Honeyball shares his experience of migrating lock, stock and barrel to Office 365
I've taken the plunge and moved my daily workload into Office 365, Microsoft’s online productivity suite. Having recently moved into a new bricks-and-mortar office, I decided now would be a great time to rationalise my email, domain names and phone numbers to match.
Ditching my old domains jonhoneyball.com and woodleyside.co.uk (my company is called Woodleyside IT Ltd) for a single new work domain of woodleyside.com afforded a rare opportunity to perform a green-field, scorched-earth, mixed-metaphor clean out, and if you ever get the opportunity to do the same, it’s worth planning carefully how best to do it.
Now click hereOffice 365 - the complete guide
I thought long and hard about my mail options. I could have stayed with my ISP’s hosted IMAP/SMTP/web interface, which I adopted prior to my previous office move two years ago (because it let me dump the Exchange server I was hosting at my old office and ensured continuity during the move). Why didn’t I stay with this ISP solution? Because I was unhappy with it: the web interface tended to lose my login information and required me to log in manually time after time.
I could have installed a new local Exchange server, but I prefer to reserve my local server farm for local R&D tasks, to avoid the temptation to run test software on a line-of-business hosting server (thus breaking the separation of church and state that underlies any well-designed IT infrastructure).
the online Outlook web client is superb, a huge improvement over the clunky thing that haunted those of us who grew up on Exchange 2000/2003
Had I plumped for a local Exchange server I probably would have migrated to the shared on-site/off-site model that Office 365 supports. You host your own Exchange server and it communicates with the cloud server in such a way that all internal messages go to the local server, external ones to the external. It’s a great solution if you want to manage your migration to a pure cloud environment, letting you progressively move mailboxes from the internal server to the external one. But remember, I had a green-field site to play with, and assuming my main machines all had copies of the archived emails, I really could start from an empty server – it made more sense to leap straight into a fully cloud-hosted Office 365 environment.
Of course, no-one with any sense would perform such a leap onto an unproven solution (by which I mean “unproven to me”). Having the new domain name helped, since I could point a 30-day trial of Office 365 at that, and then kick its tyres hard for several weeks before deciding whether to go ahead. My first impressions are that it’s a good-quality product: it behaves just like a local Exchange server without the noise, power consumption and rack space, and setting it up is fairly straightforward, with a couple of caveats.
First, you’ll need to decide which version of the product to buy: a P plan or an E plan. P plans are for small businesses, while E plans are for enterprise users. For example, the P plan costs only £4 per user per month, for which you get an Exchange Server account with 25GB of mailbox storage and a 25MB attachment limit. You can work online using the Office Web Apps and keep a SharePoint Online database, plus you get Forefront Server antivirus and spam filtering for the Exchange server, and all the Lync Server telecoms capabilities. It’s aimed at businesses with up to 50 seats, but it has two major limitations: no serious technical support (online community only) and you can’t migrate from plan P to plan E. That’s fine if you’re small and plan to stay small, and four quid per seat per month is cheaper than chips.
Move up to the E plans and you’ll find a range of extra options: E1 starts at £7 per user per month and offers Exchange Server, SharePoint, Lync and Forefront, along with licences to run local on-premises deployments of those servers (CALs in old-speak); E2 at £11 per user per month adds the Office Web Apps; E3 at £16 brings a rolling licence for Office Professional Plus for each desktop, more advanced SharePoint Server capabilities and archiving, unlimited storage and hosted voicemail on Exchange Server; and at £18 E4 tops the bill with enterprise-grade voice PBX abilities via an on-premises Lync Server.
For me, the E3 bundle was the sweet-spot, offering sufficiently rich enterprise services without delving too deep into PBX mysteries (which I’d already decided to provide via the excellent and familiar 3CX).
Buying the service was easy, requiring only the waving of a credit card; buying additional seats is simple, too, as is bolting on extra storage for SharePoint Server. To actually get everything up and running requires some DNS work, however, and changing over your DNS is a process involving several steps.
...one thing worth checking
Good article - as a newbie to 365 but otherwise pretty IT savvy a good thing to check that will bring things to a grinding halt is the level of 'contamination' of your data you are moving to 365.
Contamination?? Yes - make sure your data's filenames are free of illegal characters [read about them here>>] (http://bit.ly/MiYOOO)
IF you try to upload any filename like this to your 365 portal you will get very non-commital errors reported.
Use this (Search Everything Engine)to check your filenames from(http://bit.ly/4cFpTR)and acertain the level of crap characters.
Then use this (Bulk Rename Utility) from [http://bit.ly/15K3ot] to replace/delete dodgy characters.
You day should then run smoothly (unlike mine did today)
By AlienPsyTing on 4 Aug 2012
.......and one other thing worth checking
..ops forgot to mention. Check also for corrupted filenames. I had a bunch of data starting with ~$, these files will also bring your document upload to a screeching halt. Run a good ole' command prompt and then type dir /ah /s > outputfile
Look at the output file to find more garbage filename. If you cant delete them by unhiding their hidden attrib simply make a new directory copy the clean files in it and delete the old one.
By AlienPsyTing on 5 Aug 2012
- 10 ways to make your business more secure
- Top five VoIP mistakes
- How to add in-app purchasing to an iPhone, Android or Windows app
- Remote-control ransomware: TeamViewer and software hardball
- Why laptops with serial ports matter to the Internet of Things
- Make your mobile battery last longer
- Small steps into handling Big Data
- Nexus 5: does it really run stock Android?
- How to get broadband to a garden office
- How to write your company's IT security policy
- How to turn off Google Location Tracking
- 20 years of PC Pro: our greatest review mistakes
- 20 years of PC Pro: our first A-List
- Wikipedia's "right to be forgotten" protest hits the wrong note
- 3D printing hits the high street for plastic selfies
- 20 years of PC Pro: What amazed us in our first issue
- How Google Glass ruined my lunch hour
- Smartphone battery packs: can a USB power pack beat the festival battery blues?
- Windows Easy Transfer – not so "easy" in Windows 8.1
- Formula 1: what a difference virtualisation makes
- Microsoft yanks Windows 8.1 update after crash reports
- Microsoft backtracks on blocking out-of-date Java
- Gartner: time to start planning your Windows 7 upgrade
- Still on IE8? You've got 18 months to upgrade
- Who's buying Chromebooks? American schools
- Microsoft targets Windows in next Patch Tuesday
- Microsoft to block old ActiveX controls in security push
- Samsung and Apple call off all legal disputes, except in the US
- Microsoft ordered to hand over European data
- Will the next Windows 8.1 update arrive next month?