We never use it, and probably never will. Google tells me that uninstalling it is pretty straightforward, but several MS technicians also say that it's "not recommended" to permanently uninstall.

Is this kind of like Microsoft not recommending OpenOffice or is there really a downside/drawback in stability/health of the system if it's removed permanently?

EDIT: if a canonical answer cannot be provided, I'm totally ok with anecdotal responses, like "we removed it a couple of years ago, no problems".

1 Answer 1


I wouldn't remove it, personally. I never have, simply from a philosophical perspective.

I'm fine disabling things but I don't hasten to remove them. In the same way that I never make changes to the "Default Domain Policy" and "Default Domain Controllers" policy I try to avoid making changes that are difficult to reverse and that would make a machine drastically "non-stock". I want to be able to return a machine to as much of a stock configuration as possible should I have a tech-support incident.

I rarely engage with "manufacturer" technical support but if I'm getting to the point that I might I start backing-off customizations. There have been times when, in backing off customizations, I've found the root cause to an issue. I like having that ability to back-off my changes.

I work as a contractor, and I also like to keep my Customers' configurations as close to "industry standard" as possible such that they can go to another provider, if they so choose, and get good support. I've followed-up third-party support companies who have made big messes by "customizing" and otherwise "tweaking" off-the-shelf software and I don't think it made them look professional or reputable. I use it as a selling point to my Customers that I am a replaceable part and that, as much as it is feasible, everything I do for them will be recognizable and able to be administered by any other sysadmin who is "skilled in the art".


I have disabled the "Windows SBS Manager" service on multiple Windows Small Business Server 2008 instances, along with disabling the SQL Server instance "SBSMONITORING" with no ill effects.

  • This was an interesting read, but not really what I was looking for.
    – gravyface
    Jul 11, 2013 at 23:26
  • It's an anecdotal response. My anecdote is "It's a bad idea". Disabling it has caused me no problems. I dropped on an edit with a specific statement about the "Windows SBS Manager" service. re: everything else - I can't stop myself from bloviating about philosophy-- that just comes free w/ my answers whether you like it or not. Jul 11, 2013 at 23:35
  • Great, thanks for the edit. If you're interested in what I'm trying to accomplish, I'm trying to identify the source of abnormally large hourly AppAssure snapshots; first culprit I suspected was SBS Monitoring, but I don't believe that's it.
    – gravyface
    Jul 11, 2013 at 23:35
  • I've never used AppAssure so I won't even begin to speculate there (although it does seem a bit annoying that the tool itself can't just tell you what's so big). In my experience the SBS Monitoring functionality has been useless and a waste of server resources. Jul 11, 2013 at 23:37

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .