After installing the DPM server you need to add clients to protect. You will need to install the client on the computer you want to protect. You can do this from the DPM server but it requires that you add the following incoming firewall rules.
| Protocol | Port | Details |
|---|---|---|
| DCOM | 135/TCP Dynamic |
The DPM control protocol uses DCOM. DPM issues commands to the protection agent by invoking DCOM calls on the agent. The protection agent responds by invoking DCOM calls on the DPM server.
TCP port 135 is the DCE endpoint resolution point used by DCOM. By default, DCOM assigns ports dynamically from the TCP port range of 1024 through 65535. However, you can configure this range by using Component Services. For more information, see Using Distributed COM with Firewalls(http://go.microsoft.com/fwlink/?LinkId=46088). |
| TCP | 5718/TCP 5719/TCP |
The DPM data channel is based on TCP. Both DPM and the protected computer initiate connections to enable DPM operations such as synchronization and recovery.
DPM communicates with the agent coordinator on port 5718 and with the protection agent on port 5719. |
| DNS | 53/UDP | Used between DPM and the domain controller, and between the protected computer and the domain controller, for host name resolution. |
| Kerberos | 88/UDP 88/TCP | Used between DPM and the domain controller, and between the protected computer and the domain controller, for authentication of the connection endpoint. |
| LDAP | 389/TCP 389/UDP |
Used between DPM and the domain controller for queries. |
| NetBIOS | 137/UDP 138/UDP 139/TCP 445/TCP |
Used between DPM and the protected computer, between DPM and the domain controller, and between the protected computer and the domain controller, for miscellaneous operations. Used for SMB directly hosted on TCP/IP for DPM functions. |







