Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

So, here is the question: I started to work for a small company, where the system is a bit weird... 13 workers, developers mostly, two servers and a lot of cables. I would like to know what would be, in you opinion, the best installation for my server room.

Here is what we already have:

  • 2 servers running Windows Server 2003 (1 for communications, 1 for the developers work) --Software-- *ESTOS ProCall for telephone *Tobit David for Email *A few internal programs and a lot of files that need to be accessed
  • 1 double-wan router
  • 2 switches
  • 10 telephones
  • 12 workstations (all Windows XP or Vista)
  • 4 printers (for different applications)
  • 2 Notebooks for external work

The most important for us is to have a good telephone ans email system, what is not really the case at the time. We use ISDN because of a better quality, but the whole software compatibility between David and ProCall is bringing on some errors, and I think it's not normal to have to reboot a server every 2 days... I would like to have suggestion for a "perfect" server room for us. I was thinking of making the communication server work on Linux or MAC OSX Server? For geographical information, the company is in Germany. Low costs would be good.

share|improve this question
-1, as I think this question is way too open-ended, it is impossible to give a meaningful answer to it. – Jesper Mortensen Sep 9 '09 at 9:24
So for this reason you give a minus??????? Write your idea, if you have so many! That's what I want, get impressions from people with other experiences. My question is just right, and if it seems too "open-ended" for you, just pass by and don't waste your time please! – waszkiewicz Sep 9 '09 at 9:34
By the way, I think any answer could be meaningful, just let me judge about it! – waszkiewicz Sep 9 '09 at 9:35
@waszkiewicz: I wish you the best with your question and your work. Regarding my down vote, I think it is fair. See the words about "require extended discussion" in the site FAQ at . – Jesper Mortensen Sep 9 '09 at 9:57
@jesper.mortensen: thank you. – waszkiewicz Sep 9 '09 at 9:59
up vote 1 down vote accepted

We are missing a lot of info, but I'll add my first thoughts: You don't talk about other services such as Active Directory, SQL, backups, etc. Assuming you need AD, I'd keep a physical domain controller. Like Sybreon, I'd say look at virtualization, Separate the different applications onto dedicated VM's that way if you have to reboot one, you don't bring down everything. Spin up a Virtual Domain controller as well so you have a live backup of your AD. Definitely the Development server and Test/QA server should be separate virtual servers.

share|improve this answer
You're right I forgot to precise the backup system. We don't use AD nor a Domain, an evolution we need to get into! There is only a system that copies every important file from Server1 to Server2, and vice-versa. Then I burn DVDs every week containing the important stuff... A bit Archaic, isn't it? Thanks for your tips. – waszkiewicz Sep 10 '09 at 6:58

My 2 sen.

  1. Virtualisation - there are tonnes of benefit from this. You could try to setup your physical servers to host a number of virtual machines that can be configured for various tasks and applications.
  2. VoIP - you may want to consider using some software phone solutions so that you can dump the physical phones. It is possible to run Asterisk inside a VM.
  3. WiFi - you did not mention wireless. Wifi would be fairly useful for laptop users particularly. It helps reduce cabling (especially in the meeting/training room).
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.