After making configuration changes using Manager, the process of saving the changes performs several actions:
The configurations are validated for consistency.
For those systems for which configuration changes have been made, the new configuration is sent to that system.
Manager defaults to rebooting those systems where a reboot is necessary for the configuration changes to come into effect.
A time stamped copy of the new configuration is also stored on the Primary Server server.
For a new Secondary Server or expansion system added to the network configuration using the create off-line configuration option, the offline file is stored, allowing the new system to be configured even though not yet physically present.
When opening the configuration from a network, if the timestamp of the stored copy differs from that of the actual system configuration, Manager will prompt for which configuration it should load for editing.