Main Area and Open Discussion > General Software Discussion

Wndows Home Server as a SOHO business server. Your thoughts?

(1/2) > >>

40hz:
I'd like to bounce this one off the DoCo community.

Wndows Home Server as a SOHO business server. Your thoughts?

I have a friend who asked whether or not it would a good idea to use Windows Home Server as the general office server for her small (3-person, <$400K annual revenue) company.

My initial reaction was to say "not really," and point her towards one of the regular MS server offerings. But now that I've done some research, I get the impression that all of the earlier reliability and showstopper issues have gotten sorted out and the current release is good to go.

I loaded up a test copy to play with it a bit. From what I can see, WHS appears to be very solid. It's extremely easy to administer. Some of the disk management features are actually quite innovative. (Or at least they are for Microsoft! :P) The account security model is adequate enough for what she needs. And the overall feature set (especially the implementation of remote access) should be able to handle everything she wants to do.

Since money is an issue (when isn't it?) and a NIX/FOSS solution would be well outside of her technial comfort zone, WHS could be a nice simple way for her to go.

So here's my question: does anybody out there either (a) use WHS for their SOHO server; or, (b) have direct experience/involvement with someone who does?

Any feedback or relevant experiences would be greatly appreciated.

Thx! :)

Stoic Joker:
"$400K annual revenue" and they're tight for cash?!?

While 3 people probable could be just fine on a WHS, I'd still go for a low buck SBS server. www.stikc.com is a great source for referb'ed (off lease) Dell servers. I've bought 3 from them so far & they have all been gems.

While I do like WHS, it just doesn't strike me as a good idea in a business environment...too many gotcha type restrictions that won't be readily appearent until it's too late.

cranioscopical:
"$400K annual revenue" and they're tight for cash?!?
--- End quote ---
Alas, annual revenue <> profit.
Even were it profit, when divided by three that doesn't go far these days.  :(

And... thanks to both of you for this topic and the info it's likely to generate.

40hz:
"$400K annual revenue" and they're tight for cash?!?

-Stoic Joker (October 08, 2009, 02:10 PM)
--- End quote ---

Thx for the feedback.

I'm not too inclined to go with SBS because they need to be mostly self supporting. I've done a lot of support for that product, and I'm firmly convinced it's more trouble than it's worth for 90% of the companies that buy into it. I'm much more partial to the doing plain vanilla servers since most small companies are only looking for centralized user account admin & backups, file & print sharing, and remote access. And if you actually do need SQL or Exchange, you're far better off contracting it out if you can't afford a full time IT person who knows what they're doing.

FWIW: add up salaries for 3 people + medical  & liability insurance + legal fees + business taxes + property taxes + vehicle expenses + cost of goods sold + fulfillment services + general business overhead expenses and $400K suddenly isn't that much money any more. Sure, if it were all going straight into their pockets it would be a goldmine. But it ain't. :-\

(Heck, if what I bill hourly was pure gravy and personal income, I could have retired ten years ago. ;D)

Stoic Joker:
Ah! I see where you're going and I also like have your cake & eat it too solutions. When you install SBS stop after disk1 and you have what you're after. Outlook comes with SBS also as I recall.

The key with SBS is to skip the corny wizards & just do everything the normal server way. I manage 3 of them for clients (2 with Exchange and 1 without) & they're completely painless.

You can get a decent generation old server (with a 1 year warranty) from the company I mentioned earlier and most (not all) come with a valid SBS COA (no media, but that's not too hard to find) for $600-$800.

Navigation

[0] Message Index

[#] Next page