GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I think you'll find if you come from a windows background that a windows server will be substantially easier to manage. As opposed to teaching yourself linux, in a production environment.
If you want to AUTOMATE scheduled maintenance and achieve ZERO downtime (don't fall for Microsoft's "Scheduled maintenance windows are not downtime" bull$#*^) then go with a *nix-based solution. If you like having to be encumbered by a GUI, scheduled downtime for maintenance, pay for per-user licensing IN ADDITION TO software licensing, etc. then by all means choose Windows.
Really, with a server, you have to focus on what you intend for the server to do. What application(s) it needs to run; what services it provides; what other systems it will need to interact with. From that, you determine which type of server fills those business requirements best.
I think that "license costs" should not be a major issue in the decision. And "support costs," whether they're your own employees, yourself, outside contractors or some combination of all three, are going to be fairly high anyway. What you need to do, on that score, is to carefully enumerate them.
Distribution: Microsoft Windows XP Professional SP2; Slackware Linux 10.2
Posts: 215
Rep:
It all depends on your level of experience. Windows is MUCH more expensive in the first place, but is very easy to maintain and set up. However, if you enjoy full-blown configuration and customization, then Linux would be a much better choice.
It all depends on your level of experience. Windows is MUCH more expensive in the first place, but is very easy to maintain and set up.
As sundialcvs pointed out, it depends on business requirements. If, for example, they intent is to run a legacy app built on asp.net and coded in VB (ugh!) then the correct solution would be Windows, because mono support for vb lies somewhere between immature and nonexistent.
Likewise, if they have chosen Microsoft CRM for their custom relationship management needs, then they will be definitely needing Exchange and SQL Server - or at minimum SBS and MSDE (don't try to run Exchange and SQL Server on the same box, even though SBS installs both. You WILL be in for a painfully slow experience).
TCO is generally lower with Linux than with Windows, when you actually take the full TCO into account, and don't selectively analyze it like Microsoft does, and shift numbers by redefining "downtime" to something different than the rest of the industry's definition.
Back when I was a little helpdesk minion the answer presented itself in the middle of the night. (Windows servers paged out problems 10x more than the unix servers).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.