Ports Used by Directory Migration Agent (DMA)
The following table lists ports required to be opened between Directory Migration Agent and the other Migration Manager components so that Directory Synchronization Agent is be able to communicate with those components properly:
| Inbound |
User-configured (default port:1001) |
TCP/UPD |
Migration Manager for Active Directory (Microsoft Office 365) console |
| Outbound |
User-configured (default ports:389, 636, if available) |
TCP/UPD |
ADAM/AD LDS instance |
| 389 |
TCP/UDP |
Source domain controllers |
| 3268 |
TCP |
Source global catalogs |
| 1000 |
TCP/UPD |
Migration Manager for Active Directory (Microsoft Office 365) console |
| 80 |
TCP/UPD |
Microsoft Office 365 |
| 443 |
TCP/UPD |
Ports Used by Resource Updating Manager
The following sections provide a comprehensive list of port requirements for Resource Updating Manager (abbreviated to RUM). The list of required ports depends on the way you process resources:
- Processing Resources with Agents
- Processing Resources Remotely (without Agents)
|
|
TIP: For information on Resource Updating Manager, refer to the Resource Update section of the Migrating Manager for Active Directory User Guide document. |
Processing Resources with Agents
RUM Console
The following table lists ports required to be opened between RUM Console and the components specified in the table so that RUM Console may communicate with those components properly:
| Outbound |
User-configured (default ports:389, 636, if available) |
TCP/UDP |
ADAM/AD LDS instance |
| 389 |
Source and target domain controllers |
| 3268 |
Source and target global catalogs |
RUM Controller
The following table lists ports required to be opened between RUM Controller and the other Migration Manager components so that RUM controller is be able to communicate with those components properly:
| Inbound |
445 |
TCP/UDP |
RUM Agent |
| 1024-65535 |
| Outbound |
389 |
TCP/UDP |
Source and target domain controllers |
| 3268 |
Source and target global catalogs |
| User-configured (default ports:389, 636, if available) |
ADAM/AD LDS instance |
| 135-139 |
RUM Agent |
| 1024-65535 |
|
| 53 |
DNS Server |
|
RUM Agent
The following table lists ports required to be opened between RUM agent and the other Migration Manager components so that RUM agent is be able to communicate with those components properly:
| Disabled |
Inbound |
1024-65535 |
TCP/UDP |
RUM Controller |
| Outbound |
389 |
Source and target domain controllers |
| 3268 |
Source and target global catalogs |
| 53 |
DNS Server |
| 135-139 |
RUM Controller |
| 445 |
| 1024-65535 |
| Enabled |
Outbound |
389 |
TCP/UDP |
Source and target domain controllers |
| 3268 |
Source and target global catalogs |
| 53 |
DNS Server |
| 135-139 |
RUM Controller |
| 445 |
| 1024-65535 |
|
Processing Resources Remotely (without Agents)
RUM Console
The following table lists ports required to be opened between RUM console and the other Migration Manager components so that RUM console is be able to communicate with those components properly:
| Outbound |
User-configured (default ports:389, 636, if available) |
TCP/UDP |
ADAM/AD LDS instance |
| 389 |
Source and target domain controllers |
| 3268 |
Source and target global catalogs |
RUM Controller
The following table lists ports required to be opened between RUM Controller and the other Migration Manager components so that RUM controller is be able to communicate with those components properly:
| Outbound |
389 |
TCP/UDP |
Source and target domain controllers |
| 3268 |
Source and target global catalogs |
| User-configured (default ports:389, 636, if available) |
ADAM/AD LDS instance |
| 135-139 |
Workstation processed |
| 1024-65535 |
|
| 53 |
DNS Server |
|
Workstation
The following table lists ports required to be opened between each workstation you plan to process with RUM and RUM Controller so that they may be processed successfully:
| Inbound |
135-139 |
TCP/UDP |
RUM Controller |
| 1024-65535 |
