# Redeploy connectors

Supported in:

> [!NOTE]
> **Note:** This feature is covered by [Pre-GA Offerings Terms](https://chronicle.security/legal/service-terms/) of the Google Security Operations Service Specific Terms. Pre-GA features might have limited support, and changes to pre-GA features might not be compatible with other pre-GA versions. For more information, see the [Google SecOps Technical Support Service guidelines](https://chronicle.security/legal/technical-support-services-guidelines/) and the [Google SecOps Service Specific Terms](https://chronicle.security/legal/service-terms/).  
> If this feature isn't visible in your environment, see [Manage preview features](https://docs.cloud.google.com/chronicle/docs/secops/preview-features-manage) or contact your system administrator.

When you redeploy connectors, the connector's scheduler moves from the Remote Agent
to the Google Security Operations server. You can manually redeploy connectors
for each Remote Agent.

The connector redeployment process is connected to the
[Remote Agent's high availability](https://docs.cloud.google.com/chronicle/docs/soar/working-with-remote-agents/deploy-high-availability-for-remote-agents)
feature. During redeployment, the system validates each connector. If it detects
any issues, it automatically reverts all changes and restores the connector to its
previous working state.

The redeployment process may take some time. You can track its completion on the
**Remote Agent** page. If you get an error message, repeat the redeployment process.
If you continue to get an error, contact [Google Support](https://docs.cloud.google.com/chronicle/docs/getting-support).

**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/)