Skip to main content

Outlook Anywhere (formerly RPC over HTTP)

 Use Outlook Anywhere to connect to your Exchange server without VPN


Applies to: Microsoft Office Outlook 2007

This feature requires you to use a Microsoft Exchange Server 2003 or Exchange Server 2007 account. Most home and personal accounts do not use Microsoft Exchange. For more information about Microsoft Exchange accounts and how to determine which version of Exchange your account connects to, see the links in the See Also section.
In a local area network (LAN) (LAN: A computer network technology designed to connect computers separated by a short distance. A local area network (LAN) can be connected to the Internet and can also be configured as an intranet.) environment, communicates with Exchange by using remote procedure call (RPC) (remote procedure call (RPC): In programming, a request by one program to a second program on a remote system. The second program generally performs a task and returns the results of that task to the first program.) with Transmission Control Protocol/Internet Protocol (TCP/IP).

This method provides quick and efficient access in a corporate network. However, access to Exchange when you are outside of your organization's firewall, such as when you are at home or traveling, usually requires a virtual private network (VPN) (virtual private network (VPN): Extension of a private network encompassing encapsulated, encrypted, and authenticated links across shared or public networks. VPN connections provide remote access and connections to private networks over the Internet.) connection to the organization's network. A VPN provides you with a connection within an organization's network and within its firewall. A VPN also enables access to more network services than those required for just e-mail access.

For remote connections, Outlook offers Outlook Anywhere, an alternative to VPN connections that allows you to use Outlook just as you normally do at your organization, without the need for any special connections or hardware, such as smart cards and security tokens. Outlook can connect to Exchange through the Internet by using remote procedure call (RPC) over HTTP. The Outlook Anywhere feature allows you to access your Exchange account remotely from the Internet when you are working outside your organization's firewall.
System requirements

There are several minimum requirements for using Outlook Anywhere. If your computer and Exchange do not meet all requirements for this feature, these options will not be available. The requirements include:
  • Your computer must have Microsoft Windows XP Service Pack 2 or a later service pack.
  • Your account be hosted on Microsoft Exchange Server 2003 or Microsoft Exchange Server 2007 running on Microsoft Windows Server 2003.
  • Your Exchange administrator must configure the server to permit connections via HTTP. For more information about configuring this feature, see the Microsoft Office Resource Kit and the Microsoft Exchange documentation.
Enable Outlook Anywhere in Outlook

Your Exchange administrator can automatically configure all copies of Outlook in your organization or provide a special executable script file that enables Outlook Anywhere. You can also manually configure Outlook Anywhere if the system requirements are met and you have the correct URL and security information from your Exchange administrator.
  1. On the Tools menu, click Account Settings, select the Exchange account, and then click Change.
  2. Click More Settings, and then click the Connection tab.
  3. Under Outlook Anywhere, select the Connect to Microsoft Exchange using HTTP check box.
     Note If the Outlook Anywhere section is not available, your computer is probably not running Windows XP Service Pack 2 or a later service pack.
  4. To specify a proxy server, click Exchange Proxy Settings.
      Type the URL provided by your Exchange administrator.
     If your Exchange administrator tells you to use a Secure Sockets Layer (SSL) connection, select the Connect using SSL only check box.
     If your Exchange administrator instructs you to do so, select the Only connect to proxy servers that have this principal name in their certificate check box, and then type msstd: followed by the URL provided by the administrator.
  5. Under Proxy authentication settings, click Basic Authentication or NTLM Authentication as instructed by your Exchange administrator. 
Note If you click Basic Authentication or NTLM Authentication and an LM Compatibility Level of less than 2, you will be prompted for a password each time a connection is made to Exchange. With Basic Authentication, the password is sent in clear text. For increased security, we recommend that you select the NTLM Authentication and Connect using SSL only options.



__________________________________________________ ______________
Second article:
www.EgyEng.com
Outlook Anywhere allows Faculty, Staff, and Students to use Microsoft Outlook 2003 or Outlook 2007 from off-campus without the use of a VPN client. You must be running Windows XP SP2 or Windows Vista.
NOTE: After making this change you will need to authenticate every time you open Outlook, regardless of whether you are on- or off-campus, or if you are logging into the ADMIN or STUDENT domain.
  • How to create an Outlook profile to use Outlook Anywhere
  • How to Modify an Existing Outlook Profile to use Outlook Anywhere
How to create an Outlook profile to use Outlook Anywhere

  1. Connect to the WPI VPN client using your UNIX username and password.
  2. Click Start, and then click Control Panel.
  3. In Control Panel, double-click Mail.
  4. In Mail Setup, under Profiles, click Show Profiles.
  5. In Mail, click Add.
  6. In New Profile, in the Profile Name box, type a name for this profile, and then click OK.
  7. In the E-mail Accounts wizard, click Add a new e-mail account, and then click Next.
  8. On the Server Type page, click Microsoft Exchange Server, and then click Next.
  9. On the E-mail Accounts page, do the following:
    1. In the Microsoft Exchange Server box, type: exchangemail.wpi.edu
    2. Select the check box next to Use Cached Exchange Mode (optional, but recommended).
    3. In the User Name box, type your ADMIN or STUDENT domain username.
    4. Click More Settings. (Please note that if you are not connected to the VPN, this will fail.)
  10. In the Microsoft Exchange Server dialog box, do the following:
    1. On the Connection tab, in the Exchange over the Internet pane, select the Connect to my Exchange mailbox using HTTP check box.
    2. Click Exchange Proxy Settings.
  11. In the Exchange Proxy Settings dialog box, in the Connections Settings pane, perform the following steps:
    1. In the Use this URL to connect to my proxy server for Exchange box, enter: exchange.wpi.edu
    2. Select the Connect using SSL only check box.
    3. Enable mutual authentication by selecting the Only connect to proxy servers that have this principle name in their certificate: check box. (Outlook 2003 will have this text be Mutually authenticate the session when connecting with SSL)
    4. In the text box under that option, enter msstd:exchange.wpi.edu
  12. In the Exchange Proxy Settings dialog box, in the Proxy authentication settings pane, in the Use this authentication when connecting to my proxy server for Exchange list, select NTLM Authentication.
  13. Click OK in the Exchange Proxy Settings box, click OK in the Microsoft Exchange Server box, click Next on the E-mail Accounts page, click Finish to close the wizard, and then click OK.
Return to Top
How to Modify an Existing Outlook Profile to use Outlook Anywhere

  1. Connect to the WPI VPN client using your UNIX username and password.
  2. Use either Control Panel or Outlook to open the E-Mail Accounts wizard.
    To open the E-Mail Accounts wizard using Outlook, click E-Mail Accounts on the Tools menu.
  3. In the E-mail Accounts wizard, click View or change existing e-mail accounts, and then click Next.
  4. On the E-mail Accounts page, select the Microsoft Exchange Server account, and then click Change.
  5. On the Exchange Server Settings page, click More Settings.
  6. In the Microsoft Exchange Server dialog box, do the following:
    1. On the Connection tab, in the Exchange over the Internet pane, select the Connect to my Exchange mailbox using HTTP check box.
    2. Click Exchange Proxy Settings.
  7. In the Exchange Proxy Settings dialog box, in the Connections Settings pane, perform the following steps:
    1. In the Use this URL to connect to my proxy server for Exchange box, enter: exchange.wpi.edu
    2. Select the Connect using SSL only check box.
    3. Enable mutual authentication by selecting the Only connect to proxy servers that have this principle name in their certificate: check box. (Outlook 2003 will have this text be Mutually authenticate the session when connecting with SSL)
    4. In the text box under that option, enter msstd:exchange.wpi.edu
  8. In the Exchange Proxy Settings dialog box, in the Proxy authentication settings pane, in the Use this authentication when connecting to my proxy server for Exchange list, select NTLM Authentication.
  9. Click OK in the Exchange Proxy Settings box, click OK in the Microsoft Exchange Server box, click Next on the E-mail Accounts page, click Finish to close the wizard, and then click OK.

Comments

Popular posts from this blog

Integration with vCloud Director failing after NSXT upgrade to 4.1.2.0 certificate expired

  Issue Clarification: after upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Issue Verification: after Upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Root Cause Identification: >>we confirmed the issue to be related to the below KB NSX alarms indicating certificates have expired or are expiring (94898)   Root Cause Justification:   There are two main factors that can contribute to this behaviour: NSX Managers have many certificates for internal services. In version NSX 3.2.1, Cluster Boot Manager (CBM) service certificates were incorrectly given a validity period of 825 days instead of 100 years. This was corrected to 100 years in NSX 3.2.3. However any environment originally installed on NSX 3.2.1 will have the internal CBM Corfu certs expire after 825 regardless of upgrade to the fixed version or not. On NSX-T 3.2.x interna...

Calculate how much data can be transferred in 24 hours based on link speed in data center

  In case you are planning for migration via DIA or IPVPN link and as example you have 200Mb stable speed so you could calculate using the below formula. (( 200Mb /8)x60x60x24) /1024/1024 = 2TB /per day In case you have different speed you could replace the 200Mb by any rate to calculate as example below. (( 5 00Mb /8)x60x60x24) /1024/1024 =  5.15TB  /per day So approximate each 100Mb would allow around 1TB per day.

Device expanded/shrank messages are reported in the VMkernel log for VMFS-5

    Symptoms A VMFS-5 datastore is no longer visible in vSphere 5 datastores view. A VMFS-5 datastore is no longer mounted in the vSphere 5 datastores view. In the  /var/log/vmkernel.log  file, you see an entry similar to: .. cpu1:44722)WARNING: LVM: 2884: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device shrank (actual size 18424453 blocks, stored size 18424507 blocks) A VMFS-5 datastore is mounted in the vSphere 5 datastores view, but in the  /var/log/vmkernel.log  file you see an entry similar to: .. cpu0:44828)LVM: 2891: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device expanded (actual size 18424506 blocks, stored size 18422953 blocks)   Purpose This article provides steps to correct the VMFS-5 partition table entry using  partedUtil . For more information see  Using the partedUtil command line utility on ESX and ESXi (1036609) .   Cause The device size discrepancy is caused by an incorrect ending sector for the VMFS-5 partition on the ...