8. Understanding and Configuring Remote File Access
By default, Exchange Server 2010 allows users to access files
remotely through Outlook Web App as long as they have a Premium Client
Access License. This means users will be able to access Windows
SharePoint Services and Universal Naming Convention (UNC) file shares on
SharePoint sites. SharePoint sites consist of Web Parts and Windows
ASP.NET–based components that allow users to share documents, tasks,
contacts, events, and other information. When you configure UNC file
shares on SharePoint sites, you enable users to share folders and files.
To configure remote file access, complete the following steps:
-
In the Exchange Management Console, expand the Server Configuration node, and then select the Client Access node.
-
In the upper portion of the details pane, you'll see a list of your
organization's Client Access servers. Select the server you want to
configure.
-
In the lower portion of the details pane, you'll see a list of option
tabs for the selected server. On the Outlook Web App tab, right-click
the virtual directory for which you are configuring remote file access,
and then select Properties. Typically, you'll want to configure the OWA
virtual directory on the Default Web Site because this directory is used
by default for Outlook Web App.
-
To configure remote file access for private computers, on the Private
Computer File Access tab, select or clear the Windows File Shares and
Windows SharePoint Services check boxes, as appropriate.
-
On the Remote File Servers tab (shown in Figure 8),
you can specify the host names of servers from which clients are denied
or allowed access using block and allow lists, respectively. If there
is a conflict between the block list and the allow list, the block list
takes precedence.
-
To configure the block list, click Block. Use the following techniques to configure the block list, and then click OK:
-
To add a server to the block list, type the fully qualified domain name of the server, such as mailsvr83.cpandl.com, and then press Enter or click Add.
-
To remove a server from the block list, select the host entry, and then click the Remove button.
-
To configure the allow list, click Allow. Use the following techniques to configure the allow list, and then click OK:
-
To add a server to the allow list, type the fully qualified domain name of the server, such as mailsvr83.cpandl.com, and then press Enter or click Add.
-
To remove a server from the allow list, select the host entry and then click the Remove button.
-
Servers that are not listed on either the allow list or the block
list are considered to be unknown servers. By default, access to unknown
servers is allowed. On the Remote File Servers tab, use the Unknown
Servers selection list to allow or block unknown servers.
-
Users have access only to shares hosted on internal servers. For a
server to be considered an internal server, you must tell Exchange about
the domain suffixes that should be handled as internal. On the Remote
File Servers tab, click the Configure button. Use the following
techniques to configure your internal domain suffixes, and then click
OK:
-
To add a domain suffix, type the fully qualified domain name of the suffix, such as cpandl.com, and then press Enter or click Add.
-
To remove a domain suffix, select the suffix entry and then click the Remove button.
In the Exchange Management Shell, you can use the Set-OWAVirtualDirectory cmdlet to manage the direct file
access configuration. Set the –Identity parameter to the identity of
the virtual directory on the server you want to work with, such as:
Set-OWAVirtualDirectory -Identity "Corpsvr127\owa (Default Web Site)"
-UNCAccessOnPublicComputersEnabled $false
-UNCAccessOnPrivateComputersEnabled $true
-WSSAccessOnPublicComputersEnabled $false
-WSSAccessOnPrivateComputersEnabled $true
If you are unsure of the virtual directory identity value, use the Get-OWAVirtualDirectory
cmdlet to retrieve a list of available virtual directories on a named
server, as shown in the following example:
Get-OWAVirtualDirectory -Server "Corpsvr127"
