Planning for file access

Published: January 11, 2010

Updated: February 15, 2013

Applies To: Unified Access Gateway

Some of the Forefront Unified Access Gateway 2010 SP3 features discussed in this article may be deprecated and may be removed in subsequent releases. For a complete list of deprecated features, see Features Deprecated in Forefront UAG SP3.

This topic is designed to help you understand the planning requirements for a Forefront Unified Access Gateway (UAG) file design, as follows:

Planning domain requirements

Planning for file access includes the following domain requirements:

  1. To provide remote access to file structures and shares, both Forefront UAG and File Access servers must be members of the same domain in which users are located, or in a trusted domain.

  2. To allow remote access to Windows file servers, Forefront UAG must be either a member of the domain to which the file servers belong, or a member of a domain which has a trust relationship with the file server domain.

  3. You can create a new domain with the Forefront UAG server as the domain controller, or join an existing domain.

Planning Novell NetWare server access

To allow access to Novell NetWare servers, the following is required:

  • To share Novell NetWare Server resources through the File Access application, you must install a Novell client on the Forefront UAG server.

Next steps

For information on deploying file access, see Setting up the File Access application.