Author: Steve Man

Logging into Outlook Web Access (OWA) always defaults to OWA Lite.

issue: Logging into Outlook Web Access (OWA) always defaults to OWA Lite

synopsis: The accessibility option in OWA designed to assist the visually impaired is selected.
Resolution
1.Go to Options.
2.Click Accessibility.
3.Clear the Use the blind and low vision experience check box.
Clearing this check box prevents the mailbox from always defaulting to OWA Lite.

Permission issues Ex2013 shared calendar with Ex2010 mailbox

​​Scenario: A user with a mailbox in Exchange 2010 is getting permission errors in Outlook when trying to access and edit a shared calendar of a mailbox in Exchange 2013 even though the correct permissions are set for that Exchange 2010 mailbox. The error is:
“You do not have permission to veiw this calendar. Do you want to ask user to share his or her Calendar with you?”
Resolution: Enable Outlook to connect to Exchange using HTTP for the Exchange 2010 mailbox in the Outlook Profile
1. Start Outlook if not started already.

2. Navigate to your Outlook Account Settings:

a. Outlook 2013/2010: Click on File –> Account Settings–> Account Settings.
b. Outlook 2007: Click on Tools –> Account Settings.
3. Select your Exchange account, and then click Change.

4. Click More Settings, and then click the Connection tab.

5. Under Outlook Anywhere (Exchange over the Internet for 2007), select the Connect to Microsoft Exchange using HTTP check box.

6. Click Exchange Proxy Settings.

7. Make sure the following settings are set:
a. Enter the URL to connect to  proxy server for Exchange: https://mail.domain.com
b. On fast networks, connect using HTTP first,… is checked.
c. On slow networks, connect using HTTP First,… is checked
d. Proxy Authentication Settings is set to Basic Authentication.

8. Click OK to close each Outlook window.

9. Restart Outlook

10. If your are prompted for authentication, use the following:
a. username: domainusername
b. password: your password.

IMAP4 backend service not authenticating to any mailbox on that server.

Scenario: The IMAP4 Backend Service cannot connect to local mailboxes in Exchange 2013 after confirming there was a certificate on the Exchange 2013 server with the IMAP and POP services assigned. The symptom on the client end is failed authentication prompts when connecting to their mailbox via imap using valid credentials and IMAP being enabled on their mailbox.

The IMAP log displays the following: 
NO AUTHENTICATE failed.””;Msg=””AuthFailed:LogonDenied
 
The application log in the event viewer displays the following:
EventID 1102: The IMAP4 service failed to connect using SSL or TLS encryption. No valid certificate is configured to respond to SSL/TLS connections. Check the configured host name as well as which certificates are installed in the Personal Certificates store of the computer.
Resolution: 
1. Remove the certificate and re-add the certificate again on that Exhange 2013 server.
2. In Exchange Management Shell run the following: Enable-ExchangeCertificate -Thumbprint XXXXXXXXXX -Services POP,IMAP
3. Restart the Imap and Pop frontend and backend services.

Exchange Management Console initialization failed when opening

Scenario: You have installed Exchange 2010 management tools on a computer, but EMC can no longer connect to the server (we knew this server was turned off). You receive this error message:

 
Initialization Failed
The following error occurred while attempting to connect to the specified Exchange server ‘servername’.
The attempt to connect to http://servername/Powershell using “Kerberos” authentication failed: Connecting to remote server failed with the following error message : The WinRM client cannot process the request because the server name cannot be resolved.
 
Resolution:
1. Navigate to C:users(username)AppDataRoamingMicrosoftMMC and deleteExchange Management Console.
2. Navigate to: HKCUSoftwareMicrosoftExchangeserverv14AdminTools and deleteNodeStructureSettings.

EMC was able to connect to a different server and open successfully.

Connecting to Exchange 2013 EWS with Exchange 2010 Folder Permissions

Scenario: When making Exchange 2013 EWS calls that proxies down to a Exchange 2010 mailbox connecting via shared folder permissions of another Exchange 2010 mailbox, the EWS connection may be unstable. Programs such as Starfish, SoapUI, or other programs making EWS calls, may or may not connect consistently and some errors encountered are 400 Bad Request errors.

Resolution: We created a new mailbox in Exchange 2013 and gave this mailbox the folder share permissions to the Exchange 2010 mailboxes. Making EWS calls to Exchange 2013 by using the 2013 mailbox to connect to the mailbox folders of the 2010 mailbox, EWS had become stable and successful.

Exchange 2013 IMAP and POP Backend Services

Microsoft has made changes in Exchange 2013 for how IMAP and POP communicate between the Exchange servers holding the Client Access and Mailbox role. The roles below need the following services started for the Exchange servers to communicate properly with IMAP and POP.
Client Access Role: The following services need to be started for each server holding the CAS role to accept the connection from clients.
  1. MSExchangeIMAP4
  2. MSExchangePOP3
Mailbox Role: The following services need to be started for each server holding the Mailbox role to accept the connection from the CAS.
  1. MSExchangeIMAP4BE
  2. MASExchangePOP3BE
On servers where the Client Access and Mailbox roles are running on the same server, you manage both services on the same computer.

About AutoComplete Address Cache in Outlook

About Frequent contacts in Outlook
Outlook provides a cache of email addresses as you use them in new email messages. This cache, sometimes called a nickname cache, is intended to improve user productivity. As you type an address in an email address field, Outlook lists possible addresses matching the letters you’ve entered. Autocomplete is a productivity enhancement that shows an address as you start to type a common recipient address so you can select the address instead of typing it
 
 
Clearing the Auto-Complete Address Cache
Outlook has an auto-complete cache to help fill in recipient information when adding recipients. If you want to delete this auto-fill cache, you can delete individual items or the entire cache. You remove individual items by typing an address on the To line of an email, and when the auto-fill suggestion is displayed, press the Delete key.

Exchange 2013 Mailbox Creation Hangs

Scenario: Mailbox creation hangs in Exchange 2013 in EAC and EMS, although the mailbox will eventually be created. When creating a mailbox in Exchange Management Shell and enabling verbose logging, the following log is displayed after it hangs:

VERBOSE: [19:50:51.165 GMT] New-Mailbox : Unable to generate the e-mail address. Unable to load address module ‘C:Program FilesMicrosoftExchange ServerV15MailboxaddressGWISEAMD64gwxpxgen.dll’ for address type ‘GWISE’. Additional message: ‘The specified module could not be found’.
Resolution: There is a GWISE value still present in the Default Recipient Policy.
1. Open ADSI Edit.
2. Connect to the Configuration Naming Context of a Domain Controller or your domain.
3. Navigate to: Configuration –> CN=Services –> CN=Microsoft Exchange –> CN=<Exchange Name> –> CN=Recipient Policies
4. Right click on CN=Default Policy and select properties.
5. Locate the gatewayProxy attribute and remove the GWISE value.
Note: Other articles suggested looking at the disabledGatewayProxy as well and removing the GWISE value.