---
title: Expanding the deployment
description: In the following example deployment, the PingDirectory server is deployed in a third, centrally-located data center.
component: pingdirectory
version: 11.0
page_id: pingdirectory:pingdirectoryproxy_server_administration_guide:pd_proxy_expand_deployment
canonical_url: https://docs.pingidentity.com/pingdirectory/11.0/pingdirectoryproxy_server_administration_guide/pd_proxy_expand_deployment.html
revdate: September 13, 2023
---

# Expanding the deployment

In the following example deployment, the PingDirectory server is deployed in a third, centrally-located data center.

The directory servers in the central city is assigned to a new location named central. The proxies use StartTLS to communicate with the directory servers in the central region.

|   |                                                                                                                                                                                         |
| - | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | Other than the ability to add to the PingDirectoryProxy server's trust store, the `prepare-external-server` tool does not alter the PingDirectoryProxy server configuration in any way. |

The PingDirectoryProxy server itself, installed on `proxy-east-01.example.com`, remains in the east location. This example reconfigures load balancing between the six directory servers in these locations:

* `ds-east-01.example.com`

* `ds-east-02.example.com`

* `ds-west-01.example.com`

* `ds-west-02.example.com`

* `ds-central-01.example.com`

* `ds-central-02.example.com`