Insert the Snow Leopard Server DVD and install Server Admin tools on a client machine.

Next, connect client machine to ethernet, not a wireless connection.

Fire up the Server Admin app on this client, Applications->Server->Server Admin and follow along.

Opening screen..

Also noticed a new mac had appeared on the network..

Clicked the Share Screen… button for grins. Used "root" and the first 8 characters of the serial number to initiate a VNC screen sharing session. Not sure whether could finish installation and configuration from the screen sharing window that appeared.

Best just to use Server Admin for the headless install, since that is the Apple tool for the job.

Shut down the screen sharing. Begin server admin setup..

Server Assistant automatically launches and prompts for a password, which is the first 8 characters of the machine serial number.

Enter the serial number when prompted.

Create an admin user.

Clicking continue loads the Network dialog box. Note the change in IP address from .109 that was DCHP assigned by the router -- to .5.

This is purely to accommodate a local network convention of placing servers below .10 to stay out of the way of DHCP addresses that start at .100

Enter a FQDN (Fully Qualified Domain Name). Just plain old mini2 does not work for DNS. This particular server is a home intranet server. A firewalled router sits between it and the internet. The router historically provided DNS and DHCP service to machines on the local network (LAN). This server will work best if it can assume the DNS duties.

Many reports suggest easier setup and configuration further down the line when using a completely mythical top level domain (TLD) for DNS. No .com, .net, .org in other words.

Setting primary DNS Name: mini2.house or .office may be much simpler down the road if not connecting to any other networks.

In my limited experience, using .net as TLD will require manual re-configuration. The change of ip address may be to blame. But If I had it to do over, I would try mini2.house instead of mini2.brethower.net.

Users and Groups is next setup screen. I kept it dead simple here by clicking "Continue"..

Then Services.

I arbitrarily switched service data storage from system drive to the second drive, to reduce load on system disk read-write.

Then Time Machine backups.

***Important to note this is not the Time Machine backup for the server.

This is only for clients that will use this server to store time machine backups.

Mail Options, external smtp in particular for outbound relay since behind a firewall.

Basic configuration finished, summary displayed, may be saved as text.

----------------------------------------------------------------------------

-- Admin Account --

Name Doug Brethower

Short Name dougbrethower

-- License --

Serial Number XSVR-106-...

Registered To Doug Brethower

Organization lakedata.net

-- Names --

Host Name mini2.brethower.net

Computer Name mini2

Bonjour Name mini2.local.

....................lots more info

Basic configuration is complete. The server is ready to use or further configure.

A screen sharing session and time machine backup of the server itself to external drive is highly recommended next step. The Time Machine set up earlier is only for client machines on the network.

If no particular problems, that is it. Next Steps pdf doc on the server desktop is a good place to continue.

More info, or want expert heavy lifting? In Southwest, MO, doug.brethower@lakedata.net

Elsewhere, look for a member of the Apple Consultants Network. ACTC - Apple Certified Technical Coordinators. Experts who are educated and trained, who care about giving clients the personalized service and attention to detail that maximizes the value of Apple Server Systems.