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

Recreating a missing VMFS datastore partition in VMware vSphere 5.x and 6.x

    Symptoms A datastore has become inaccessible. A VMFS partition table is missing.   Purpose The partition table is required only during a rescan. This means that the datastore may become inaccessible on a host during a rescan if the VMFS partition was deleted after the last rescan. The partition table is physically located on the LUN, so all vSphere hosts that have access to this LUN can see the change has taken place. However, only the hosts that do a rescan will be affected.   This article provides information on: Determining whether this is the same problem Resolving the problem   Cause This issue occurs because the VMFS partition can be deleted by deleting the datastore from the vSphere Client. This is prevented by the software, if the datastore is in use. It can also happen if a physical server has access to the LUN on the SAN and does an install, for example.   Resolution To resolve this issue: Run the  partedUtil  command on the host with the issues and verify if your output

ما هى ال FSMO Roles

  بأختصار ال FSMO Roles هى اختصار ل Flexible Single Operation Master و هى عباره عن 5 Roles فى ال Active Directory و هما بينقسموا لقسمين A - Forest Roles 1- Schema Master Role و هى ال Role اللى بتتحكم فى ال schema و بيكون فى Schema Master Role واحد فى ال Forest بيكون موجود على Domain Controller و بيتم التحكم فيها من خلال ال Active Directory Schema Snap in in MMC بس بعد ما يتعمل Schema Register بواسطه الامر التالى من ال Cmd regsvr32 schmmgmt.dll 2-Domin Naming Master و هى ال Role المسئوله عن تسميه ال Domains و بتتأكد ان مفيش 2 Domain ليهم نفس الاسم فى ال Forest و بيتم التحكم فيها من خلال ال Active Directory Domains & Trusts B- Domain Roles 1-PDC Emulator و هى ال Role اللى بتتحكم فى ال Password change فى ال domain و بتتحكم فى ال time synchronization و هى تعتبر المكان الافتراضى لل GPO's و هى تعتبر Domain Role مش زى الاتنين الاولانيين و بيتم التحكم فيها من خلال ال Active directory Users & Computers عن طريق عمل كليك يمين على اسم الدومين و نختار operations master فى تاب ال PDC Emu

Unlock the VMware VM vmdk file

  Unlock the VMware VM vmdk file Kill -9 PID Sometimes a file or set of files in a VMFS become locked and any attempts to edit them or delete will give a device or resource busy error, even though the vm associated with the files is not running. If the vm is running then you would need to stop the vm to manipulate the files. If you know that the vm is stopped then you need to find the ESX server that has the files locked and then stop the process that is locking the file(s). 1. Logon to the ESX host where the VM was last known to be running. 2.  vmkfstools -D /vmfs/volumes/path/to/file  to dump information on the file into /var/log/vmkernel 3.  less /var/log/vmkernel  and scroll to the bottom, you will see output like below: a. Nov 29 15:49:17 vm22 vmkernel: 2:00:15:18.435 cpu6:1038)FS3: 130: <START vmware-16.log> b. Nov 29 15:49:17 vm22 vmkernel: 2:00:15:18.435 cpu6:1038)Lock [type 10c00001 offset 30439424 v 21, hb offset 4154368 c. Nov 29 15:49:17 vm22 vmkernel: gen 664