Why @Office365 for SMB is broken, but why have they not fixed it? 

The company’s IT infrastructure I manage has been using Office 365 for over a year now, but have we? Office 365 gives access to a great Outlook Exchange hosted email, as well as optional Office subscriptions. The subscription costs a lot, but enables easy use of Office that is common in most companies. The flexibility on install makes it much easier in a company that has more computers than people.

What the package should be is:

  • Email through Exchange
  • Document collaboration through SharePoint
  • Office desktop [Opt]

As you may have noticed there is a SharePoint step that we miss, now I explain why Office 365 is broken. SharePoint I admit I have never fully understood but I know if used properly can have great integration with other Office product. As always there is a but though and this but I feel to be quite a big issue to a small business.

As companies develop from a single person to multiple people they go through one computer, to several computers, to several computers accessing shared storage. So most small companies quickly achieve a shared folder or pooled space style approach, to migrate this to Office 365 requires a learning step that is quite hard. The most logical way is to move your files to SharePoint so this could include Quotes, Accounts etc and here comes the but, most people would want to keep a fairly substantial back history to avoid having some files here and some files there creating a nightmare document version and backup scenario.

In Office 365 SMB you get 10gb of storage + 500mb per user, so 10 users a 15gb. If you are a new company that would be enough for a short time and you would quickly burn through and upgrade(will talk about soon). For an established company 10gb is probably not enough to even move one of there operating folders up so where do you go?

Sadly there is no answer, on SMB plan there is no way to pay for additional storage… I thought this would be fixed in the recent update but they have still left it as is. Oh and it gets better, there is no way to automatically update to an enterprise plan, and that is ignoring the increased cost. To upgrade you have to download your files and re-upload them (don't ask how file version histories work for that).


So what are you really getting? a service you can partially use and late software updates… It doesn’t sound like a way to keep people happy with your ecosystem. In fact it makes you wonder if it is worth moving over to LibreOffice and saving a very large amount of money.


As I am saying far to often Microsoft great promise, yet just failing to get it just right.

Posted by Stuart James Wednesday, May 22, 2013 11:29:00 AM Categories: Microsoft Office365

C++ + Visual Studio 2012 (VS2012) + Win8 , converting projects up some conflicts I found 

Having loved the ability to compile VS2010 projects inside the VS2012 shell as a way of delaying the update, I thought it was time to stop delaying ( 1 Year late ).

std::cout << "Minimum value for int: " << std::numeric_limits<int>::min() << std::endl;
std::cout << "Maximum value for int: " << std::numeric_limits<int>::max() << std::endl;

Generates error:

error C2059: syntax error : '::' [path]\source.cpp

There is a good chance if you have these lines and are including the windows header you will hit an error. The Windows team put in a solution to the #define min conflict in <minwindef.h>.

So instead of

#include <windows.h>

You use a #define to avoid this

#define NOMINMAX
#include <windows.h>

Another issue I found was with an annoying char define, again from the Windows team in <rpcndr.h>.

#define small char

This one doesn’t have the ability to comment out for so if you have a small function with something like:

AnObj small = large.resize(val);

Generates error:

error C2628:'AnObj' followed by 'char' is illegal (did you forget a ';'?) [path]\source.cpp

You will have to suffer and change the name, in some ways it teaches you (me) for not being very specific, still annoying though. Hopefully this is all the conversion errors I’ll hit.

Posted by Stuart James Sunday, May 12, 2013 4:13:00 PM Categories: API C++ Visual Studio Windows8
Stuart James