My experience with BPOS

It’s been about 6 weeks since we have started using Microsoft’s Business Productivity Online Suite (BPOS), and I think it’s a good time to write down a few thoughts about our experience with the service. I’ve scoured the web for reviews when we were in our planning phase, and it was very difficult to find any real world reviews. I have had a couple of requests to describe our experience with BPOS, but I just haven’t had enough time to put down all my thoughts on paper. I hope to write more about our problems and solutions hopefully soon as well.

Let’s start with the good.

Support

I can’t praise the support reps enough that I have spoken to over the past few weeks. I haven’t had this great level of service from any other company before. The reps really went out of their way to help us as much as they could. Again, I can’t thank these guys enough for all their help. There is one caveat. Since this is still relatively a new service, they don’t have all the answers. That’s not their fault by any means, and I only expect it to get better as the service matures. Even when they didn’t have the answers, they went out of their way to help us during our migration and the issues we had afterwards.

Setup

Overall, the setup to get the migration and directory sync was relatively simple. First you have to decide whether you want to live in a coexistance mode vs. strictly using BPOS. Chances are that if you have Exchange on premise, you’ll spend some time living in co-existance mode before fully switching to BPOS. I’ll write about this in a separate entry.

Mailbox Sizes

Recently, Microsoft made a decision to increase everyone’s mailbox limit to 25GB. That doesn’t mean you have to give it all to your users, but it’s nice to know that we have space available if we need it. We don’t give our users the max size because that would mean more forwards and chain-letters stored in their inbox.

Now on to the not-so-good.

Service Uptime

Microsoft has published a RSS feed with notifications about the online services. When I first started going through the feed, I was worried. It seemed that every few days they had some issue affecting the mail servers. In fact, 3 weeks into our service, we had a downtime of almost 2 hours. The good news is that it didn’t affect all of our users. This can be both a good and bad thing depending on who you’re asking. Since I was on the server that went down, I wasn’t thrilled. We haven’t had any major issues since that event, and I expect the uptime to get better as they work out the kinks.

Ancillary Services

One thing we quickly learned after signing up with BPOS is that each piece of the puzzle is handled by multiple departments – 13 total from what I was told. For example, we have signed up to use the Exchange Hosted Archiving solution for our company. The service setup took much longer than expected. Once the order was put in, it took a few business days for the service to be activated. In fact, it’s been over 5 business days since we put in our request for email encryption and we still don’t have the service activated. One thing I want to point out is that this was made known to us from the very beginning. We knew going into this that the setup would not be quick. Once again, as the service matures, I expect this setup process to drastically reduce in time.

Final Thoughts

I am in no way regretting our decision to move to BPOS. If anything, I will miss having a local Exchange server to administer, but this does leave me some room to move on to other projects.

I cannot stress enough about the great support we have received from the reps. Even our rep for our Hosted Archiving has been nothing but helpful. They really have made the service a great experience. I hope that Microsoft commends them for their work.

Even though I have listed a couple of negative points here, I really don’t consider them that bad. I knew that this was a relatively new service and that we would experience a few bumps along the way. If you don’t have the patience to deal with minor bumps, then BPOS is not the service for you – at least not at this point in time.  This service will get better over time, but for now expect some bumps along the way.

If there is something specific you would like to know, please leave a comment. If I have any experience with it, I will be more than glad to let you know how it went.  I still have more to write about how we dealt with BPOS internally, but I’ll have to save that for another entry.

Taz is slowly waking up. Father mode ON.

Configuring a web filter for Microsoft BPOS

I’ve recently started migrating our users over to Microsoft’s BPOS offering. After moving our initial set of users over, we noticed that Outlook was moving at a snails pace when reading emails. It was to a point that Outlook would just lock up and become non-responsive.

We tested a user that was on a different gateway, and we noticed that the speeds were noticeably faster. The only difference between the two gateways is that one had a Barracuda Networks web filter appliance.

After speaking to a Barracuda support rep, we came to the conclusion that we needed to add exemptions for the IPs used by Microsoft. I called Microsoft Online Services support, and got the IPs used for BPOS.

However, after adding these exemptions in, we still noticed that the speeds were unbearable. There were moments that it seemed to work quick but it was short-lived. After searching the firewalls logs to see what exactly was being accessed, I found 3 more subnets that Outlook was connecting too. Once I added those subnets into the exemption list, everything started to run much quicker.

Here are the subnets that are supplied by Microsoft Online Services support for North America:

Primary: 65.55.171.0/24
Secondary: 65.55.63.0/24

These are the additional subnets that I added in:

65.55.236.0/24
65.55.97.0/24
65.55.50.0/24

I’m planning on writing about my experience with Microsoft BPOS once I complete the migration. I’m hoping to be able to complete it within the next two weeks.

Have any of you completed a migration to BPOS? How was your experience?

I’ve actually sat on these for over a month, but I wanted to post them anyways.

Local host file not resolving correctly

We recently re-built a machine with a fresh copy of Windows that had issues resolving names listed in the local host file. All of the entries matched the ones that were on PCs that were able to resolve them. We made sure that the file had no extension listed, and it didn’t. We even copied over a file from a machine that worked thinking something may have happened to the file itself. However, nothing we did worked.

After some searching around, I came across an entry that stated that the Network Service account needs rights to the host file. I verified that the DNS service running on the machine was indeed the Network Service account (which it was), and gave the account rights to the file.

image

Once I made the change, the entries inside the host file started resolving properly.

Cannot start Microsoft Office Outlook

A great way to start a Monday morning after a break is to not be able to check your email. I fired up Outlook, and got the error “Cannot start Microsoft Outlook. Cannot open the Outlook window.” (see below)

11-30-2009 8-49-58 AM

After some searching around, I came across a solution that fixed the problem.

I ran the following command in a Run box:

Outlook.exe /resetnavpane

Once I ran that command, Outlook opened with an error informing me that the data file for my mailbox wasn’t closed properly (see below). After it ran its check, Outlook opened fine.

11-30-2009 8-50-41 AM

Exchange 2007 support on Server 2008 R2

Microsoft has decided to offer support for Exchange 2007 running on Server 2008 R2 after customers gave some feedback. They are going to release an update early next year.

Distribution Group Management in Exchange 2007

Managing a distribution group in Exchange 2007 works little differently than it did in Exchange 2003. In Exchange 2003, you could select a user to manage a distribution group, and select the option so that they could update the members in the list. (see image below)

DGManagement_Ex2003

In Exchange 2007, you have the ability to select a manager to manage the members of the list as well. However, the manager has no rights to add/remove members from the list. (see image below)

DGManagement_Ex2007

In order to grant this permission to the user, you have to run the following command from the Exchange Management Shell:

Add-ADPermission -Identity:'Group Display Name’ -User:domain\username -AccessRights ReadProperty, WriteProperty -Properties 'Member'

Make sure you have the appropriate permissions before you run that command, or it will error out. According to the Technet article, you will need the following permissions to run the command successfully:

1) Exchange Recipient Administrator role.
2) Account Operator role for the applicable Active Directory containers.

Microsoft cuts BPOS pricing.

Microsoft Cuts E-Mail Price, a Bid to Ward Off Google. It seems that Microsoft it getting aggressive with their pricing to compete with Google. Of course, they say it has nothing to do with Google.

Free Exchange 2010 e-book

Red Gate Software is offering a free e-book on Exchange 2010. (via SysAdmin Network)