The scripts we have looked at in this series of articles provided you with an installation of SQL Server and SP2. These scripts should give you the foundation for taking the scripted deployment process forward and completely developing a solution to fit your needs. Some of the ways that you may want to extend the scripts are the following:
Allowing the script to survive a reboot; that is, the script knows where it left off after a reboot. A little hint: the registry is a great place for kicking off jobs when a machine logs on (HKLM\Software\Microsoft\Windows\CurrentVersion\Run).
Writing a script to install hot fixes as needed for SQL Server. This is usually a case of reading the readme.txt and breaking it down to a simple install procedure.
Configuring SQL Server for your company's specific needs, such as dropping sample databases, separating transaction logs onto a separate partition etc. etc. Just a hint, this can all be done through a command-line utility for SQL Server 2000 known as OSQL.
These are just some of the ideas you might want to put into action. Whatever you decide to do, have fun! Scripting is a great way of reducing the mundane tasks that system admins have to do. Best of all, scripting is simple and relatively easy to write.