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

What things can be done around the network in the unusual time when a sysadmin is not busy.

share|improve this question

closed as not constructive by Michael Hampton, Chris S Oct 11 '12 at 0:42

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.

You might want to wiki this question. – GregD Jul 8 '09 at 4:08
"... when a sysadmin is not busy." so this is a hypothetical question. ;-) – splattne Jul 8 '09 at 19:55
@splattne of course ;) – Shard Jul 9 '09 at 4:11

11 Answers 11

up vote 19 down vote accepted

In no particular order:

  • Freak out because you have spare time
  • Test your backups
  • Check your Anti-Virus
  • Check your updates (WSUS)
  • Update network documentation (eg: Touch up your SysAdmin Wiki)

and possibly the most important...

share|improve this answer
+1 for the link. Looks interesting. :-) – splattne Jul 8 '09 at 19:57
+1 for 'Touch up your Sysadmin Wiki'. – faultyserver Jul 26 '09 at 23:48

Do you have centralized logging yet?

Get to it! Set this up ASAP.

I had all my windows and UNIX machines sending event log / syslog entries to a central syslog server, and a perl script in cgi-bin parsing this, highlighting scary things, filtering out the mundane, and displaying other things for categorization.

The ability to read through the logs of ~100 machines (or more, once your filters and categorization get better) in a minute or so is huge for staying in touch with what's going on in your LAN.

share|improve this answer
FTP your configs from all your switches and routers into this centralized logging system daily as well. Write scripts to compress archive and delete it after a few weeks. Do the same with performance statistics if you so desire, centralized monitoring with nagios or cacti. All those are (borderline) optional, but logging is essential. – matt Jul 8 '09 at 9:53
Agreed. You may want to look into Splunk ( as well. The idea is simple but it works very well. The search functions give great insight into your logs, even if there are many. You can easily create graphs, reports, alerts, etc. Some of the advanced stuff requires a license, but I've found the free version a great tool as well. – Martijn Heemels Jul 26 '09 at 22:16

work on automation solutions to improve reporting of network/ad/etc to sysadmin. (eg report dcdiag status from all dcs to you every morning). warning : results might make you have even more "free" time

share|improve this answer

Documentation, documentation, documentation. It's not fun but its a necessary evil that often goes overlooked. Good documentation is worth its weight in gold especially when you're out of the office on the beach with your family and someone tries to call you to do a relatively simple task. With proper documentation you can have a jr. level employee or operations personnel tackle those tasks using that documentation. Plus it gives management the warm and fuzzies that if something were to happen to you (or whomever is responsible for that system) that support can be transferred with relative ease.

share|improve this answer

I like to interact with the end user during slow periods. Often this will reveal an issue you were not aware of. Then they are happier because they are getting something that bothers them fixed. Most importantly you are creating a good relationship. You are also letting them know you are a real human and not some kind of troll living under the server room floor.

share|improve this answer
I really respect this idea! Getting to know your end-users can be so helpful in the long run. – JJ01 Jul 27 '09 at 1:02
  • Clean up Active Directory. Invariably, you wind up with empty Groups, empty OUs, and test AD accounts.

  • Backup your GPOs

  • Print out your GPOs

  • Start/Finish that desk manual.

share|improve this answer
  • Be up to date with the latest news/blogs
  • Check if your backups work
  • Check if any machines are lying idle and get them back to good use
  • Take inventory of all software's and hardware's this will give a good base for upgrade plans
  • Check if your software's have critical patches
  • Learn a good scripting language : My Choice shell or Perl or python or Ruby and on windows PowerShell
share|improve this answer
If you have idle time and don't already know if your backups work you probably need to rethink how you do things. – John Gardeniers Jul 8 '09 at 4:59

Do some security checking and hardening of your infrastructure

  • Open ports discovery (using nmap)
  • Simple (or not) vulnerability analysis (using nessus)
  • Checking server configurations from a security point of view
  • Firewall rules rewview
  • etc.

After knowing the security state of your infrastructure you can start making changes to improve it in two ways:

  1. Removing the vulnerabilities (the so-called hamster wheel of pain if you don't do number 2.)
  2. Identifying the root causes and implement measures to avoid them in the future
share|improve this answer

There's no such thing as "Free time", there's just time to do all of those things that dropped to the bottom of the todo list. I think if I had free time, I would wonder where all the users went and why I didn't get the memo about the site closing for good.

share|improve this answer
Really? Every sysadmin job I've had has had some noticeable level of "free time" - wherein tasks could be found that hadn't been on the list in the first place :) – warren Sep 28 '09 at 6:21

If I had spare time, I'd probably try to work out what my cause of death was.

share|improve this answer

Identify servers that are candidates for decommissioning. Begin investigative work necessary to prove or disprove that the server should be decomissioned.

In a similar vein, identify systems that are in need of upgrade, and start making the case for that.

share|improve this answer

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