Exchange Server 2007 as the Focal Point for Remote and Mobile Communications

written by: Ruper Meredith; article published: year 2007, month 05;


In: Categories » Computers and technology » Servers » Exchange Server 2007 as the Focal Point for Remote and Mobile Communications

Starting with Exchange Server 2003, Microsoft has added significant focus on support for remote and mobile access to Exchange. Remote and mobile access takes on two forms for Exchange: One is in the support of remote access users to Exchange with the improvement of the OWA client and mobile laptop user, and mobility is enhanced in the areas of access and synchronization with Windows Mobile and Pocket PC devices.

Remote access to Exchange has become extremely important as users want to access Exchange outside of the business office, potentially from a home computer, an Internet café kiosk system, or from a laptop they are carrying with them. OWA 2007 is now nearly feature complete compared to the full 32-bit Outlook 2007 client with full support for filters, spell checking, drag and drop of messages, out of office rules management, calendar and contact access, and the like. Many early adopters to Exchange 2007 have found the new OWA so feature complete that when they are remote, they only use OWA as their method to check and manage their messages.

A new feature of OWA in Exchange 2007 is the remote document access feature. Remote document access is a new function that allows the administrator of a network to share internal network shares through OWA. Normally, for a user to access an internal Universal Naming Convention (UNC) such as \\server\share\, the user needs to be on the local area network (LAN) or they need to have a virtual private network (VPN) connection to securely connect to the network from a remote location. With remote document access, after a user is logged on to OWA, any network shares that the network administrators specifically allow to be accessed using remote document access can be accessed from the remote user, as shown in Figure 1.3. For organizations that have implemented remote document access in Exchange 2007, most have gotten rid of their need for VPNs because between OWA and remote document access, a user can access email, calendar, contacts, and internal file shares. From a security perspective, whatever file-level security has been enabled on the network shares relative to user access are activated as part of the remote access security for the user to the remote document access share privileges.

Additional remote access improvements in Exchange 2007 include just a name change of what used to be called RPC over HTTPS to what is now called Outlook Anywhere. RPC over HTTPS, or Outlook Anywhere, is the ability for a user running Outlook 2003 or Outlook 2007 to connect to an Exchange server using HTTPS and synchronize with the server using 128-bit encryption without using VPN access. The remote connection between the Outlook client and Exchange is encrypted so that the synchronization is protected. Although a VPN connection is no longer needed, Outlook Anywhere also does not require special ports or configurations to be opened up on firewalls or special settings to be configured. Outlook Anywhere uses the same connection address that the organization uses for OWA. So, if users normally type in https://owa.companyabc.com to get access to OWA, the Outlook Anywhere connection point for the Outlook user is also owa.companyabc.com. Between remote document access and Outlook Anywhere, an organization can seriously evaluate whether it needs to continue providing remote VPN access to the network, or possibly provide VPN access to a limited number of users whose remote access needs go beyond the requirements provided by OWA, remote document access, and Outlook Anywhere.

On mobility, Microsoft has greatly enhanced the capabilities of remote access of users who have Windows Mobile and Pocket PC devices. Exchange 2007 had a significant improvement to ActiveSync that extends the direct push function that was included in Exchange 2003 SP2 that has the Exchange server push or send messages to Windows Mobile devices instead of having the Windows Mobile devices constantly poll the Exchange server for new messages. New to Exchange 2007 mobility is the ability for Windows Mobile systems to remotely search for old messages. In the past, a mobile device only had access to the messages that were synchronized by ActiveSync to the device, which usually meant 2-3 days of historical calendar appointments, and only the Inbox for messages. With Exchange 2007, a Windows Mobile device can now query all folders to which the user has access to find messages and download them to the mobile device at any time. In addition, just as OWA has the remote document access feature that brings down files from network shares without setting up a VPN connection, Exchange 2007 provides remote document access to Windows Mobile users.

legal disclaimer

1) Our website is not responsible for the information contained by this article as well for any and all copyright infringements by authors and writers. E-articles is a free information resource. If you suspect this article for any copyright infringements, please read the Terms of service and contact us to investigate the problem.
2) The E-articles directory team is not responsible for inaccuracies, falsehoods, or any other types of misinformation this tutorial may contain and will not be liable for any loss or damage suffered by a user through the user's reliance on the information gained here. Please read the Terms of service

Useful tools and features

Translate this article to...    Send this article to you or to a friend

Link to this article from your page   
If you like this article (tutorial), please link to it from your web page using the information above. Linking to this page, this is the only way to help us improve our service, the same time providing your visitors with a way to improve their online experience.

related articles

1. Improvements in Exchange Server 2007 Relative to Security and Compliance
One of the improvement goals Microsoft has had with all of their products over the past few years has been to constantly improve the security in the products. More recently with all of the regulatory compliance laws and policies being implemented, Microsoft has focused a lot of security enhancements to address privacy, information archiving, and compliance support. The release of Exchange 2007 was no different—Microsoft added in several new enhancements in the areas of security and compliance support. One of the addition...

2. Designing Exchange Infrastructure
After Active Directory and the physical OS has been chosen and deployed, the Exchange infrastructure can be set up and optimized for the specific needs of the organization. With these needs in mind, you can do several things to optimize an Exchange 2007 setup, as detailed in the following sections. Determining the Exchange Version When installing Exchange, the choice of Exchange version needs to be made. As with Windows Server 2003, there are two versions of Exchange, Standard and Enterprise. The Standard Edit...

3. Synchronizing Exchange Server 2007 with Novell eDirectory
Novell eDirectory and Novell Directory Service (NDS) environments are relatively commonplace in business environments, and there is often a need to integrate them into deployed Exchange infrastructures. Several tools exist that can make this a reality, including the MIIS 2003 tools discussed. In addition, tools in the Microsoft-supplied Services for NetWare can be used to synchronize directory information between the two directory systems. NOTE Exchange 2000 Server and Exchange Server 2003 included a GroupWise ...

4. Integrating Client Access into Exchange Server 2007 Design
Although the Exchange server is a powerful systems component, it is only half the equation for an email platform. The client systems comprise the other half, and are a necessary ingredient that should be carefully determined in advance. Outlining Client Access Methods Great effort has been put into optimizing and streamlining the client access approaches available in Exchange 2007. Not only have traditional approaches such as the Outlook client been enhanced, but support for nontraditional access with POP3 and...

5. Domain Name System and Its Role in Exchange Server 2007
For computer systems to communicate with each other, whether you are talking about a local area network (LAN), a wide area network (WAN), or the Internet, they must have the ability to identify one another using some type of name resolution. Several strategies have been developed over the years, but the most reliable one to date (and the current industry standard) is the use of a DNS. Accurate name resolution is critical in a mail environment as well. For a message to reach its destination, it might pass through several syste...

6. Synchronizing Directory Information with Microsoft Identity Integration Server (MIIS) 2003
In most enterprises today, each individual application or system has its own user database or directory to track who is permitted to use that resource. Identity and access control data reside in different directories as well as applications such as specialized network resource directories, mail servers, human resource, voice mail, payroll, and many other applications. Each has its own definition of the user’s “identity” (for example, name, title, ID numbers, roles, membership in groups). Many have their own ...

7. Using DNS to Route SMTP Mail in Exchange Server 2007
The primary protocol for sending email on the Internet today is known as Simple Mail Transfer Protocol, or SMTP. SMTP has been used for quite some time in UNIX and Linux environments, and has been incorporated into Active Directory as an alternative transport mechanism for site traffic. Domains that want to participate in electronic mail exchange need to set up MX record(s) for their published zone. This advertises the system that will handle mail for the particular domain, so that SMTP mail will find the way to its destinati...