Loading the Administrative Template
The Administrative Template consists of the ActiveRoles.admx (ADMX) and ActiveRoles.adml (ADML) files. The ADML file is a language-specific complement to the ADMX file.
To load the Administrative Template to a domain-wide Group Policy object, you need to copy the ADMX and ADML files to the central store in the sysvol folder on a domain controller:
-
Copy the ADMX file to the %systemroot%\sysvol\domain\policies\PolicyDefinitions folder.
-
Copy the ADML file to the %systemroot%\sysvol\domain\policies\PolicyDefinitions\en-US folder.
Create those folders if they do not exist. For more information about ADMX files, see Managing Group Policy ADMX Files Step-by-Step Guide.
Group Policy Object Editor automatically reads all ADMX files found in the central store of the domain in which the Group Policy object is created. You can configure Active Roles policy settings in Group Policy Object Editor by selecting User Configuration > Templates > Active Roles Snap-in Settings or Computer Configuration > Templates > Active Roles > Administration Service Auto-connect Settings, then apply the Group Policy object as appropriate.
Communication ports
This section provides a list of communication ports that need to be open in the firewall for Active Roles to function properly.
Access to the managed environment
If the environment managed by Active Roles is located behind a firewall, then the following ports must be open between the Active Roles Administration Service and managed environment.
For instance, if there is a firewall between Active Roles and DNS, then port 15172 must be open (Inbound/Outbound) on the Active Roles host (or the firewall between Active Roles and Exchange) and port 53 must be open on the DNS server (or the firewall between Active Roles and DNS).
Access to domain controllers
-
Port 88 (Kerberos) TCP/UDP Inbound/Outbound
-
Port 135 (RPC endpoint mapper) TCP Inbound/Outbound
-
Port 139 (SMB/CIFS) TCP Inbound/Outbound
-
Port 445 (SMB/CIFS) TCP Inbound/Outbound
-
Port 389 (LDAP) TCP/UDP Outbound
-
Port 3268 (Global Catalog LDAP) TCP Outbound
-
Port 636 (LDAP SSL) TCP Outbound
This port is required if Active Roles is configured to access the domain by using SSL.
-
Port 3269 (Global Catalog LDAP SSL) TCP Outbound
This port is required if Active Roles is configured to access the domain by using SSL.
-
The TCP port allocated by RPC endpoint mapper for communication with the domain controller.
You can configure Active Directory domain controllers to use specific port numbers for RPC communication. For instructions, see How to restrict Active Directory RPC traffic to a specific port.
-
The following ports must be open for the notifications specific to SaaS-based operations to work. The Web Interface machine should be able to resolve Service machine name for notifications to work.
Access to Exchange servers
You can configure Exchange servers to use specific port numbers for RPC communication. For more information, contact Microsoft Support.
The following ports must be open for operations related to the WinRM service to work:
-
Port 5985 (HTTP) TCP Inbound/Outbound
-
Port 5986 (HTTPS) TCP Inbound/Outbound
-
Port 80 TCP Inbound/Outbound
Computer resource management
Computer restart
-
Port 139 (SMB/CIFS on the managed computers) TCP Inbound/Outbound
-
Port 137 (WINS) UDP Outbound
-
Port 138 (NetBIOS datagrams) UDP Outbound
Home folder provisioning and deprovisioning
Access to SMTP server for email integration
-
Port 25 (Default SMTP port) TCP Outbound
-
Active Roles uses SMTP port 25 by default. The default port number can be changed in the properties of the Mail Configuration object in the Active Roles Console. If Mail Configuration specifies a different port, open that port rather than port 25.
Access to AD LDS instances
Access to Active Roles Administration Service
You can set up a firewall between Active Roles client components, such as the Active Roles Console (also known as the MMC Interface), Web Interface, ADSI Provider or Management Shell, and the Active Roles Administration Service.
To access the Active Roles Administration Service with the Active Roles client components through a firewall, you must open port 15172 and all high ports (1024-65535) on port 15172 in the firewall. The client machines randomly select high ports to use for outgoing traffic on port 15172 to access the Active Roles Administration Service.
To give access to the Active Roles Administration Service through a firewall
-
In the firewall, open port 15172 TCP Inbound/Outbound.
NOTE: For more information about opening ports in your firewall, refer to the operating system's or the network device vendor's documentation.
-
In the firewall, open the high ports (port range 1024-65535) on port 15172.
NOTE: To check the list of high ports being used on port 15172, in the Active Roles Console of a client machine, use the netstat -an command.