Saving Configuration SettingsThe Server Assistant's Confirm Settings window gives you the option of saving your configuration settings (Figure 2.40). Doing so has several benefits. You can save a small test file to a local USB storage device or iPod and transfer these settings to a clean installation of Server, thus saving you from typing in the information again. You may also wish to create a clone of your server or quickly reformat and reinstall your server software after a severe disk failure. In addition, you can save the file to a directory record; doing so lets you save the configuration to another directory server on your network, in case a server needs reformatting. You can reformat the server and pull down the initial settings again, saving you from running through the Server Assistant repeatedly. Table 2.1 lists the possible ways to save your configuration settings. Figure 2.40. You can save your configuration settings as a text file for possible printing and saving.
When you're saving configuration settings, choose the method that best fits your infrastructure. Saving to a text file doesn't allow encryption, so anyone can open the file and see your configuration settings. You can save the file anywhere, but the best idea is to save it on a USB, an iPod, or another storage device. Another method is to save the configuration settings as a configuration property list file. Doing so allows for encryption of the file, and the Ethernet address is automatically used as the name of the file (Figures 2.41 and 2.42). To allow for automatic setup, place the file inside a folder called Auto Server Setup on a removable storage device. Figure 2.41. Saving the configuration settings as a property list file offers a Passphrase option.Figure 2.42. If you save the configuration settings as a configuration property list file, the Ethernet address is used as the filename.You can change the name of the configuration property list file to generic.plist. When you do this, any server can use the file to configure itself with the parameters contained in that particular property list file (Figure 2.43). Figure 2.43. Changing the name of the configuration property list file to generic.plist lets any server use the file to configure itself.
The third option is to save the file in a directory record. Doing so creates the file inside another Mac OS X Client or Mac OS X Server. When a freshly installed (and not configured) copy of Mac OS X Server reboots, depending on how the other Mac OS X Server on the network is configured, it will discover the plist directory record on the local network and automatically configure itself (Figure 2.44). Figure 2.44. You can save the file as a directory record in another directory server.To save initial server settings:
To reapply saved server settings:
|