System requirements for Forefront UAG servers
Updated: July 31, 2012
Applies To: Unified Access Gateway
The following summarizes the system hardware requirements, and software and deployment requirements for installing Forefront Unified Access Gateway (UAG).
If you are reading this help from the Forefront UAG Management console, the latest version of this topic is available in the Forefront UAG TechNet library.
Processor |
2.66 gigahertz (GHz) or faster processor. Dual core CPU |
Memory |
4 GB |
Hard drive |
2.5 gigabyte (GB) (in addition to Windows requirements) |
Network adapters |
Two network adapters that are compatible with the computer operating system. These network adapters are used for communication with the internal corporate network, and the external network (Internet). Deploying Forefront UAG with a single network adapter is not supported. In addition, Forefront UAG supports configuration of two networks (internal and external). Connecting to different network switches for network redundancy is supported, providing that both are defined as part of the internal or external network. Using Forefront TMG running on the Forefront UAG server to provide multiple network routing is not supported. |
Operating system |
Forefront UAG can be installed on computers running the Windows Server 2008 R2 Standard or Windows Server 2008 R2 Enterprise 64-bit operating systems. |
Windows roles and features |
The following roles and features are installed by Forefront UAG, and are required for Forefront UAG to function properly.
Roles and features installed during Forefront UAG setup are not uninstalled automatically if you uninstall Forefront UAG. They must be removed manually after uninstalling Forefront UAG. |
Other software |
Forefront UAG automatically installs and uses the following applications:
|
Remote installation |
Remote installation of Forefront UAG from a network location is not supported. You can run setup from a local folder accessed over a Remote Desktop Connection using IPv4. An IPv6 connection is not supported. |
Array deployment |
If you want to deploy an array of multiple Forefront UAG servers, each server that will join the array must be installed as a domain member before beginning Forefront UAG installation. For more information about array deployment requirements, see Multiple server infrastructure design. |
Co-located applications |
The computer on which you are installing Forefront UAG should have a clean Windows Server 2008 R2 installation, with no other applications installed on it. For considerations on running antivirus products on Forefront UAG, see Considerations when using antivirus software on Forefront Edge products (https://go.microsoft.com/fwlink/?LinkId=193579). |
Installation permissions |
When installing Forefront UAG, you must have administrator permissions on the local server. You must also be a domain user in the domain to which the Forefront UAG server belongs. |
Domain and workgroup considerations
|
If the Forefront UAG server is a member of a workgroup, ensure that a DNS suffix is defined for the workgroup. |
Some deployment scenarios require Forefront UAG to be installed as a domain member. For more information, see Joining the Forefront UAG server to a domain or a workgroup. |
|
Forefront UAG does not support installation with a read-only domain controller. |
|
Virtual requirements
|
Forefront UAG is supported on Hyper-V running on computers with Windows Server 2008 with SP2, or Windows Server 2008 R2. Both host and guest operating systems must be 64-bit. |
For more information on virtual support, see Security considerations with Forefront Edge virtual deployments (https://go.microsoft.com/fwlink/?LinkId=193580). |