GPOADmin

Client Install

• 1 GHz processor
• 512 MB RAM or greater
• 100 MB hard disk space
• Windows XP Service Pack 2, Windows Server 2003, Windows Server 2003 R2, Windows Vista, Windows Server 2008, Windows Server 2008 R2 or Windows 7 operating systems
• MMC 3.0
• .NET Framework 3.5 Service Pack 1
• Microsoft Group Policy Management Console with Service Pack 1 or Remote Server Administration Tools

Server Install

• 1 GHz processor
• 1 GB RAM or greater
• 200 MB hard disk space
• Windows XP Service Pack 2, Windows Server 2003, Windows Server 2003 R2, Windows Vista, Windows Server 2008, Windows Server 2008 R2 or Windows 7 operating systems
• MMC 3.0
• .NET Framework 3.5 Service Pack 1
• Microsoft Group Policy Management Console with Service Pack 1 or Remote Server Administration Tools
• Either ADAM/AD LDS or Active Directory must be available on the network to be used for the application's configuration storage.

GPMC Extension

• 1 GHz processor
• 512 MB RAM or greater
• 100 MB hard disk space
• Windows XP Service Pack 2, Windows Server 2003, Windows Server 2003 R2, Windows Vista, Windows Server 2008, Windows Server 2008 R2 or Windows 7 operating systems
• MMC 3.0
• .NET Framework 3.5 Service Pack 1
• Microsoft Group Policy Management Console with Service Pack 1 or Remote Server Administration Tools

Watcher Service

• 1 GHz processor
• 1 GB RAM or greater
• 200 MB hard disk space
• Windows XP Service Pack 2, Windows Server 2003, Windows Server 2003 R2, Windows Vista, Windows Server 2008, Windows Server 2008 R2 or Windows 7 operating systems
• .NET Framework 3.5 Service Pack 1
• Microsoft Group Policy Management Console with Service Pack 1 or Remote Server Administration Tools
• Either ADAM/AD LDS or Active Directory must be available on the network to be used for the application’s configuration storage

Port Requirements

Important! It is recommended that you conduct a thorough threat analysis before opening these services to an untrusted network. 

The following ports must be open for the application to function correctly:
Name resolution can be achieved using DNS on port 53 or WINS (down-level) on port 137.

Between the client and the Quest GPOADmin Server:
      Inbound: Port 40200 (default)
      Outbound: all TCP ports

Note: To run the Version Control server on a custom port, you must set the following registry value:
Key:                HKLM/Software/Quest Software/Quest GPOADmin/RemotingValue 
Name:             Port
Value Type:    DWord
Valid Values:  1-65536
If this value is not set, the default (port 40200) will be used. 

From the Quest GPOADmin Server: 

Configuration Storage

• LDAP Service - TCP/UDP - 389 -or- ADAM port (defaults to 389 or 50000)

GPO Archives

• If you are using a network share for GPO backup storage, you may require open ports on 135, 136, 138, 139, and/or 445.
• If you are using SQL Server for GPO backup storage, the appropriate ports will need to be open. SQL Server’s default port is 1433 or 1533 if the "hide server" option is enabled.
• If you are using Named Pipes with SQL, arbitrary ports may be required. SQL Named Pipes is not a recommended configuration through firewalls.
• If you are using ADAM for GPO backup storage or configuration data, ADAM will default to port 389 if not coexisting with AD. If AD is already installed, ADAM will default to port 50000.