---
title: Preparing external servers
description: Prepare each external server for synchronization by trusting its certificate, entering manager credentials, and setting the maximum change log entry age.
component: pingdirectory
version: 10.2
page_id: pingdirectory:pingdatasync_server_administration_guide:pd_sync_prepare_external_servers
canonical_url: https://docs.pingidentity.com/pingdirectory/11.1/pingdatasync_server_administration_guide/pd_sync_prepare_external_servers.html
llms_txt: https://docs.pingidentity.com/pingdirectory/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: 2023-09-13T00:00:00Z
superseded_by: https://docs.pingidentity.com/pingdirectory/11.1/pingdatasync_server_administration_guide/pd_sync_prepare_external_servers.html
section_ids:
  about-this-task: About this task
  steps: Steps
---

# Preparing external servers

## About this task

Perform the following steps to prepare external servers: NOTE: The Password Sync Agent cannot be pointed at multiple domain clusters.

## Steps

1. After configuring the source and destination endpoints, PingDataSync prompts to "prepare" each external server. The process requires trusting the certificate presented to the server, and then testing the connection. If this step is not performed, the process can be completed after configuring the Sync Pipes using the `prepare-endpoint-server` command.

2. Configuring this server for synchronization requires manager access. Enter the distinguished name (DN) *(tooltip: \<div class="paragraph">
   \<p>A name uniquely identifying an object within the hierarchy of a directory tree.\</p>
   \</div>)* and password of an account capable of managing the external directory server.

3. Enter the maximum age of change log entries. The value is formatted as `[number][time-unit]`, where the time unit format resembles ("8h" for eight hours, "3d" for three days, "1w" for one week). Setting this value caps how long the PingDataSync server can be offline. A smaller value limits how many changes are stored and is necessary to limit excessive changelog growth in high-modification environments.

4. To prepare another server in the topology, follow the prompts. The previously entered manager credentials can be reused to access additional servers. Repeat the process for each server configured in the system.