> [!CAUTION]
> **Caution:** This documentation covers Edge for Private Cloud 4.52.00, which is no longer supported. Google does not provide security patches, bug fixes, or technical support for this version. The current supported version is 4.54.00. See the [Edge for Private Cloud documentation](https://docs.apigee.com/private-cloud/latest/overview) for the current version, or [All versions](https://docs.apigee.com/private-cloud/versions) to compare releases.

This section describes how to remove the following components from a Private Cloud
installation:

- Management Server
- Message Processor
- Router

For information on how to remove a Qpid server, see
[Remove a Qpid server](https://docs.apigee.com/private-cloud/v4.52.00/add-or-remove-qpid-nodes).

**To remove a Message Processor, Management Server, or Router:**

1. (Message Processor and Router only) Stop the Message Processor or Router that needs to be deregistered:

   ```
   /opt/apigee/apigee-service/bin/apigee-service edge-message-processor stop
   /opt/apigee/apigee-service/bin/apigee-service edge-router stop
   ```
2. (Message Processor only) Deregister the Message Processor from the organization's environments:

   ```
   curl -u adminEmail:pWord
     -X POST http://management_IP:8080/v1/o/orgName/e/envName/servers
     -d "uuid=uuid&region=regionName&pod=podName&action=remove"
   ```
3. Deregister the server's type:

   ```
   curl -u adminEmail:pWord
     -X POST http://management_IP:8080/v1/servers
     -d "type=[message-processor|router|management-server]&region=regionName&pod=podName&uuid=uuid&action=remove"
   ```
4. Delete the server:

   ```
   curl -u adminEmail:pWord -X DELETE http://management_IP:8080/v1/servers/uuid
   ```
5. (Message Processor only) After deregistering a Message Processor, restart the routers:

   ```
   /opt/apigee/apigee-service/bin/apigee-service edge-router restart
   ```