1.What is Outlook Anywhere in Exchange Server 2010?
In Microsoft Exchange Server 2010, the Outlook Anywhere feature, formerly known as RPC over HTTP, lets clients that use Microsoft Office Outlook 2010, Outlook 2007, or Outlook 2003 connect to their Exchange servers from outside the corporate network or over the Internet using the RPC over HTTP Windows networking component.
2.What recommendations should be followed to successfully deploy Outlook Anywhere?
- Use at least one Client Access server per site;
- Enable Outlook Anywhere on an Internet-exposed Client Access Server.
3.How to test Outlook Anywhere Connectivity?
- Running the Test-OutlookConnectivity cmdlet;
- Running the Outlook Anywhere connectivity test using the Exchange Remote Connectivity Analyzer (ExRCA).
4.What are the prerequisites for support MAPI over HTTP?
- Upgrade Outlook clients to Outlook 2013 SP1 or Outlook 2010 SP2 and updates KB2956191 and KB2965295 (April 14, 2015);
- Upgrade Client Access and Mailbox servers to the latest Exchange 2013 cumulative update (CU);
- On all Exchange 2013 servers, install the Microsoft .NET Framework version supported by the CU running on our Exchange server.
5.What are the steps for configure MAPI over HTTP for our organization?
Virtual directory configuration;
Update server rules;
Enable MAPI over HTTP in our Exchange Organization using the following command:
Set-OrganizationConfig -MapiHttpEnabled $true
6.Where are the logs for MAPI over HTTP activity located?
%ExchangeInstallPath%Logging\MAPI Address Book Service\
%ExchangeInstallPath%Logging\MAPI Client Access\
7.What are the difference between POP3 and IMAP4?
- By default, when POP3 email applications download email messages to a client computer, the downloaded messages are removed from the server;
- When IMAP4 email applications download email messages to a client computer, a copy of downloaded messages remains on the email server.
8.What are the steps to configure http to https redirection for Outlook on the web in Exchange Server?
- Step 1: Remove the Require SSL setting from the default website;
- Step 2: Restore the Require SSL setting on other virtual directories in the default website;
- Step 3: Configure the default website to redirect to the /owa virtual directory;
- Step 4: Remove http redirection from all virtual directories in the default website;
- Step 5: Restart IIS.
9.How to remove the Require SSL setting from the default website using command line?
%windir%\system32\inetsrv\appcmd.exe set config “Default Web Site” -section:access -sslFlags:None -commit:APPHOST
10.How to restore the Require SSL setting on other virtual directories in the default website using command line?
%windir%\system32\inetsrv\appcmd.exe set config “Default Web Site/<VirtualDirectory>” -section:Access -sslFlags:Ssl,Ssl128 -commit:APPHOST