Always set a Master Password

Always set a preexec and postexec even if they start out blank

Always include a mod even if its the blank, filler, stub, or watcher  mods

Always zip up the map and email it off system

Always create a restart script so you dont have to remember settings and 
port etc etc. It will also make you much more willing to do changes

Its a good idea to turn debug to a log and have the postexec rotate it

Its a good idea to have the pre-exec zip the game and EMAIL IT OFF SYSTEM 
even if its just to a junk free email account in the games name

Almost always turn on quick host

For large games with many players you might want to google for the port 
number you are planning to use. This is to make sure that port is not 
associated with something nasty which might get it blocked by some ISPs. 
This site can help.
http://www.auditmypc.com/freescan/portsearch.asp

Setting hosting to specific days and times is easier on the host when 
players ask for changes (pause, delay, etc) or the game needs patched than 
setting it to something like 24 hours because the players hate having the 
counter start over

You can create a crontab that says "on reboot" so that any system problem 
will automatically restart the game

It can be a good idea to have the postexec copy or move, some or all, of 
the files to a web accessable directory. Such as stats file, scores.html, 
and possibly the players turn files. But only on very special games should 
be log file be included as it can give too much game information.

it is sometimes appreciated to rotate the scores.html for a history

it is sometimes a good idea to rotate the zip name for restore purposes. 
probably at least 2 to be able to restore to the last, or the one before 
that.

People appreciate being offered to include a "turn ready" notice in the 
postexec. Also remember to offer SMS text messaging. You can also offer to 
include the turn file. IM might also be possible.

its a good idea to include something like an "uptime" to a file in the 
preexec and append the same command to the file in the postexec. This will 
give you an idea of load and how long it takes to host. This can be 
important for scheduling around cron jobs or other large games hosting.