Archive

The quick answer to this is, of course, no.  You don’t need a partner to help you migrate to O365, you could do it yourself.  But you might want to have a partner, specially so if you do not  have internal resources that understand all that is involved with a migration. Office365 is built on …

As I mentioned in an earlier post, we have been in the process of migrating a customer to Office365 in preparation for their migration from SBS2003 to SBS2011 Essentials.  We decided to move them to 365 well in advance of the server migration itself in order to lessen the “shock” of the migration to all …

We (itgroove) have held back a bit on implementing SBS 2011 Essentials for any of our customers while we waited on some of the dust to settle around Office 365.  Now that 365 has proven itself to be a worthy offering we have started talking up SBS Essentials to those of our clients that might …

I just finished blowing my brains out for the better part of a week trying to figure out WHY a brand new Exchange 2010 install was blowing up on the Exchange Remote Connectivity Tester (ExRCA) for RPC over HTTP.  As well, Outlook 2007 and 2010 clients were also exhibiting all sorts of errors while using …

We have lots of customers ask us this question and it is a valid one when you are looking at what is required to connect back to your Exchange backend. If you have Exchange 2007 or 2010 (SBS2008 or SBS2011) in-house the super simple answer is any one of the above EXCEPT BlackBerry (more on …

We’ve seen this quite a bit on Exchange 2010 machines where the Exchange 2010 console will just hang when you try to access it.  After a period of time you might get a Kerberos or a WinRM error being displayed.  This seems to be a fairly common problem as there is a great deal of …