# Redeploying a Previous Configuration

If a deployment fails, you can easily roll back to a successful earlier deployment.

Note: Only successful deployments can be redeployed. Any EMS servers that failed in the initial deployment are excluded from a redeployment. If only some of the EMS servers included in a deployment were successfully deployed, only those EMS servers are redeployed. If the initial deployment was wholly unsuccessful—none of the EMS servers deployed—the deployment in unavailable for redeployment.

## Procedure

1. Navigate to the Deployments page.
2. Locate the deployment that you wish to redeploy in the Recent Deployments list.
3. Click Redeploy .
4. Click Yes to redeploy this version of the configuration, or No to retain the current configuration.
5. To view details about the deployment, including any errors, click View next to the deployment name.

   If some cases, an EMS server requires a restart before the configuration changes take effect. If such cases, the server deployment log notes this requirement.

6. If required, restart the EMS servers. This task cannot be completed using the Central Administration web interface.

## Result

The Central Administration server reverts all EMS servers deployed in the selected previous deployment.

Warning: Redeploying updates the EMS server but does not affect the working directory or lock file. As a result, the working copy and lock files in Central Administration are out of sync with the running EMS server.

This allows you to retain the configuration changes made prior to the redeploy. To obtain the current configuration, refresh the EMS server configuration. See Refreshing the Server Configuration for details.

Copyright © Cloud Software Group, Inc. All rights reserved.