Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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

I am looking for a check list of things that every person who is setting up a new server should be looking at. I am trying to create an internal process for our IT team and am looking for the basic main list of configuration when rolling out a new server. Anyone know of anything? (I am not looking for a 400 page microsoft document, just a simple complete checklist.)


locked by HopelessN00b Mar 13 '15 at 13:27

This question exists because it has historical significance, but it is not considered a good, on-topic question for this site, so please do not use it as evidence that you can ask similar questions here. This question and its answers are frozen and cannot be changed. More info: help center.

closed as not constructive by Iain, mfinni, Shane Madden, womble, Chris S Aug 17 '11 at 16:39

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

Which do you want. Simple or complete? Seems to me that the two are mutually exclusive. – Zoredache Aug 16 '11 at 19:58
This is hugely environment-dependent - I'm afraid it's really something you need to develop on your own. My checklist includes 5 items: Install FreeBSD. Enable SSH. Install radmind. Rack & stack box. Run deployment. – voretaq7 Aug 16 '11 at 20:04
up vote 3 down vote accepted

Nobody can give you a checklist for your environment, but here are some basic items you need to make sure you take care of:

  1. Hardware Test (if applicable, but at least make sure it matches what you bought)
  2. Install the OS
  3. Configure the OS. Pay special attention to:
    • Network configuration
    • Domain or other remote login service
    • Local user accounts
    • Necessary software for the server's role
    • OS Patches
  4. Rack & Stack. Make sure to verify:
    • Adequate power/cooling
    • Network connectivity
    • Adding the machine to any asset management system(s)
    • Adding the machine to any patch deployment system(s)
    • Adding the machine to any monitoring system(s)

A simple checklist:

  • "What does it have to do, and does it do it?"
  • "If it goes wrong, do we have enough documented and backed up so we can fix it?"
  • "Does everyone who needs to know about it, know about it?"

More detailed:

  • Documentation of the setup and passwords
  • Installed properly (i.e. all redundant cablework done, no bodges, etc.)
  • Backed up
  • Restores possible
  • Added to your internal procedures for, e.g. warranty updates, OS updates, scheduled maintenance alerts
  • Added to your monitoring platform
  • Added to your hardware inventory system

"A server" is a bit too vague. What kind of server? What OS? What environment? For what purpose?

Keep a printed copy of all documentation. It will come in handy when servers are down or if its just a stressfull situation. – artifex Aug 16 '11 at 21:41
@artifex At least print enough documentation to recover your documentation system. Printing everything could get a bit out of hand. – TessellatingHeckler Aug 16 '11 at 21:49

Although you don't want a 400 page Microsoft document, what you need is a copy of "The Bible" -- The Practice of System and Network Administration, by Limoncelli et al. It has whole chapters that help you identify what you need on your checklists.

This is the book i keep closest to my desk at all times. – artifex Aug 16 '11 at 21:40
Hell, I'm sitting on the couch at the moment and it's still within arm's reach. – womble Aug 16 '11 at 23:38

I would encourage you to research puppet/chef recipes. The only real way to get servers built correctly is to either automate the build or automate the policy enforcement. A well documented puppet recipe will be both a good aid to someone in telling them how things are configured and provide a way to ensure that configuration is the way all servers are built.

More info on Chef:



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