Filter
Top Products
Chapter 3 Installing Server Software and Finishing Basic Setup 51
This creates an environment variable named command_line_install that automates
the update responses. See the softwareupdate man page for more information about
the command.
Moving a Server
Try to place a server in its final network location (subnet) before setting it up for the
first time. If you’re concerned about unauthorized or premature access, you can set up
a firewall to protect the server while you’re finishing its configuration.
If you must move a server after initial setup, you need to change settings that are
sensitive to network location before the server can be used. For example, the server’s IP
address and host name—stored in both folders and configuration files that reside on
the server—must be updated.
When you move a server, consider these guidelines:
 Minimize the time the server is in its temporary location so the information you need
to change is limited.
 Don’t configure services that depend on network settings until the server is in its
final location. Such services include Open Directory replication, Apache settings
(such as virtual hosts), DHCP, and other network infrastructure settings on which
other computers depend.
 Wait to import final user accounts. Limit accounts to test accounts so you minimize
the user-specific network information (such as home folder location) that will need to
change after the move.
 After you move the server, use the
changeip tool to change IP addresses, host names,
and other data stored in Open Directory, NetInfo, and LDAP folders on the server.
See “Changing a Server’s IP Address” on page 66. You may need to manually adjust
some network configurations, such as the local DNS database, after using the tool.
 Reconfigure the search policy of computers (such as user computers and DHCP
servers) that have been configured to use the server in its original location.
For information about configuring a computer’s search policy, see the Open
Directory administration guide.