Remote Office Mail

For large organizations, remote office mail can pose a challenging problem. Mail for an organization with remote offices poses increased complexity and costs in terms of WAN maintenance and bandwidth costs. Either an organization uses a main server system for all their mail, covering all their offices; or they must implement an Exchange server at the remote office to handle mail, requiring dedicated IT staff for that location.

In the case of one server for handling remote office mail for multiple locations, bandwidth use is higher, using unnecessary WAN resources. Local mail between users at the same remote office must be sent through the main server; the message is sent out over the WAN only to be sent right back to the originating location. Not only is mail between users in the same remote office problematic, but one message sent to multiple recipients at the remote office will be sent over the WAN as multiple messages. Outlook operations often run slower as well, since Outlook communicates with the server (in this case over the WAN) for many operations.

If a separate Exchange server is used at the remote office, these problems can be alleviated, but then you are forced to install an expensive server setup which requires dedicated staff.

PostPath's Remote Office Server Edition can help.

PostPath Remote Office Server Edition allows for both backup and administration to be handled from the NOC. The server can be shipped pre-configured on standardized hardware, or even as a virtual machine. It even allows for hot-failover to the NOC in the event of a server failure. All while supporting all of Microsoft Exchange's features.

The PostPath Remote Office Server Edition, overcoming your remote office mail challenges.