|
BPOS is a story of inflexibility. In three parts. Multizone as a Microsoft Business Partner, Trialists as potential customers for Microsoft and Multizone, and Microsoft Online, for the settings in place in BPOS. My Inflexibility as a business partner Like it or not my business has more than one client. This means that I have to be able to satisfy their request that I help them administer their BPOS. Its almost impossible. I have a live email system, and a demo BPOS system that is part of the business partner program that Im specifically not allowed to use for real world email. Its not possible to have this configuration work on one windows login. Consequently it wont get used because its just too much pain to have multiple images of Windows and multiple logins with multiple MAPI profiles. Of course this same problem means that I cant have multiple client BPOS systems set up on my PC at the same time. And it means that my clients who are also in fact BPOS customers cant give me effective access to their email. There can be only one BPOS/Exchange account in your Outlook. Its 2009. Thats ridiculous. Its a non comprehension of how companies interact. Its:- 'We, the wise people of Microsoft use Exchange like this so its how you must use it too... All companies are structured like Microsoft and have the same poilicies arent they' behaviour at best, or 'We cant make it work better for BPOS in a supportable way so it has to have reduced capabilities' at worst. The Inflexibility of trialists My trialists arent green field sites. They dont like email downtime. They avoid it like the plague. Migrating domains should be easy but it isnt. Exiting DNS hosters dont like people leaving and make it difficult. Trialists dont want to hear about these kinds of issues. Trialists want to put a few people onto the system at a time, and others, well they want them to get their email but not be on the system until its proven. With BPOS thats not possible. Trialists dont want to hear that. They also dont want to hear how its only fixable with a domain forwarding hosting account dealing with all email before forwarding it to BPOS. 'Why, is my enterprise email behind a hundred bucks a year domain forwarding service?' they would ask if you even get to the point of having the conversation.Trialists like things to be 'just so' Consider this request I had from a potential client:- 'Why cant I have my header and footer auto generated just the way it is now by my Exchange Server, because our emails look the same as our headed paper with our logo on the top and standard text including name and job title at the bottom. I dont want this in Outlook, I want it like it is - done by the server because then it cant be broken' My answer after conferng with support and the forums "BPOS are providing company disclaimer texts as a support issue' Trialist responded 'yeah but we have to have our logo at the top - so it looks like our headed paper, just like it does now and so it cant be deleted by our people - If youre saying you cant do that I dont want it.' (Pick your own trialist inflexibility here and replace - the argument is the same).BPOS inflexibility - Client side single sign on application, not customisable, impossible to add other programs like say CRM or internal tools that could benefit from this new model of authentication/authorisation sync between apps. Lack of colour about how open and supported this tool is.
- Only one BPOS/exchange account at a time. Period. (well unless you use Entourage for Mac which supports many, but the incredulous look from the client when you explain that is no longer funny)
- No server side rules
- No company imposed letterhead / signature variables / disclaimer
- No forwarding
- No POP
- No IMAP (if I had those I could have a client email address, like most of my clients want me to - currently the only way to do this is to use a Mac)
- No turning off the original domain name (careful then what you choose on the first screen of installig BPOS - a decision here must be right and youre frankly not equipped to make it when you're asked).
- General hotch potch look and feel of the BPOS apps. Hardly a suite of like designed programs
Conclusions? So there you have it. Three inflexibilities. But they are important ones to navigate round to get a successful implementation. Ive only had a 20% hit rate of success so far. If you cant avoid these inflexibilities, and if they dont get addressed where possible, soon, in new releases of BPOS, then its going to be very difficult to see the value. Ive spent a day training, taken an online assessment, signed the legalese, and invested a lot of time in pre-sales activity. The BPOS effort has a long way to go before I see any meaningful payback. That said if you are a green field who wants pin sharp Microsoft based infrastructure and will bend towards what it can do in exchange for peace of mind then BPOS is perfect.
Disclosure: For several years I was a senior architectural engineer for Microsoft Exchange at Microsoft, leading pre sales technical engagements it in its original incarnation to BT, Glaxo, British Gas, Rolls Royce, and other leading enterprise customers. Now Im a Microsoft Online business partner and qualified Small Business Partner.
|