A full deployment will force Address Manager to deploy all data. You can choose to deploy DNS, DHCP, DHCPv6 or TFTP data.
If the validation options are set, pre-deployment validation will be performed as part of the normal deployment process. For more information about setting validation options, refer to Validating deployment.
Note: Pre-deployment validation doesn't check all combinations of deployment data. The deployment might still fail even after pre-deployment validation is successful. In the event of issues after successful pre-deployment validation, the Deployment Status page will display the results. You can also navigate to the Event List page to check the logs.
To perform a full deployment:
- Select the Servers tab. Tabs remember the page you last worked on, so select the tab again to ensure you're on the Configuration information page.
- Under Servers, select the check box for one or more servers.
- Click Action and select Deploy.
- Under Confirm Server Deploy, review the list of servers to be updated.
- Under Services, select the services to be deployed to the server: DNS, DHCP, DHCPv6, or TFTP.
- In the Deployment Preference section, select Force Full DNS Deployment to force Address Manager to perform a full deployment of all DNS configuration data. By default, Address Manager attempts to perform a differential deployment when possible (deployment of only DNS resource record changes, if these are the only changes made since last deployment). First deployments and changes to DNS zones, DNS deployment options or roles, DNSSEC keys, TSIG keys, Kerberos principals, server groups, or other objects outside of DNS resource records will still result in a full deployment if this box is left unchecked.
- In the Change Control section, add comments to describe your changes.
- Click Yes to deploy data to the listed servers. Click No to cancel the process without deploying data to the servers.