Outlook: There is a problem with the proxy server’s security certificate. The name on the security certificate is invalid or does not match the name of the site. Outlook is unable to connect to this server.

Issue: Error message from Outlook: There is a problem with the proxy server’s security certificate, %s. The name on the security certificate is invalid or does not match the name of the site. Outlook is unable to connect to this server. (%s)
  
Finding/Resolution: Checked Outlook provider settings and saw that server and certificate was set to 2 dashes(–)
used this command to fix: set-outlookprovider EXPR -Server $Null and Set-Outlookprovider EXPR -CertPrincipalName $Null
The command will set outlook provider EXPR to Null(Blank). By doing so Outlook will rely on autodiscover to get the correct outlook anywhere settings

Get all messages from all transport servers by a specific sender starting on a specific day and export to CSV

Issue/Task: Get all messages from all transport servers by a specific sender starting on a specific day and export to CSV
Get-TransportServer | Get-MessageTrackingLog -sender:test@test.com -start 7/15/2014 -resultsize unlimited | export-csv c:export.csv

After cancelling the install for Exchange 2013 CU5, users can no longer connect to IMAP.

Issue: The attempted install of Exchange 2013 CU5 was cancelled during the install process.  Afterwards users could not connect to the secure imap service.
Cause: CU5 for exchange 2013 install was attempted on these servers, hence they were put in maintenance state by CU5. Also found out that only the person/software that put the server in maintenance mode can take it off maintenance.
Troubleshooting/Resolution: From powershell type, Get-servercomponentstate servername. Found out Imap proxy was in an inactive state.
Resolution: This registry fix(though not recommended by microsoft) resolved the issue. go to
 HKEY_LOCAL_MACHINESOFTWAREMicrosoftExchangeServerv15ServerComponentStatesserverwideoffline
backup the servercomponentstates key
remove maintenance key
change functional key from 1:0:635407213073684026 to 1:1:635407212984929845 (Note that guid value is unique per server).

You are basically changing from 0 to 1 to make the server active. This activates all the inactive components

Message throttling policy created in Exchange 2013 not applying to Exchange 2010 mailboxes

Issue: In a coexistence environment, message throttling policy created in exchange 2013 not applying to exchange 2010 mailboxes

Resolution: Create message throttling policy in Exchange 2010 powershell. Apply separate throttling policy to Exchange 2010 mailboxes

Clients connecting to recently installed servers, but the clients have delayed/no connection

Issue
**************
Clients were trying to connect to servers that were recently installed, but currently offline for the process of completing setup, causing the clients to have delayed, or no connection at all.
Cause
*************
The servers were not set with the right URL, and once the servers are installed into a site, autodiscover will query AD to get the URL and other information, even if the servers are offline, the information is in AD and can be returned to users.
Once the users received the Internal URL for the offline servers, they would try to connect to that internal URL, and eventually timeout, then they would connect to the externally listed url, https://mail.test.com
Resolution
**************
We did a couple of things to try and prevent users from getting to the down servers
1.       We set the SCP autodiscover record to be mail.test.com on the 4 new servers
a.       Set-clientaccessserver –AutoDiscoverServiceInternalUri https://mail.test.com/autodiscover/autodiscover.xml
2.       We then went into ADSI edit and modified the internal URL for outlook anywhere on the 4 new servers as well
3.       We then restarted the app pool for autodiscover to clear the autodiscover cache
a.       This then allowed users to set the connection point to mail.test.com
4.       For clients, they may need to do a repair profile to remove the server FQDN from the outlook profile and restart outlook
Next Steps
************
When the 4 new servers are brought back up verify that the outlook anywhere settings are correct from powershell.
Get-outlookanywhere <NEW SERVER NAMES> | fl
Check internal URL and make sure it is mail.test.com
May want to change the Internal URL to the mobile. For all the servers, removing the internal FQDN

Also change the AutoDiscoverServiceInternalUri for the client access servers to mail.test.com, so users do not try to use an individual server name when they discover an SCP record.

X-OWA-Error: Microsoft.Exchange.Security.Authentication.TokenMungingException

Scenario:  When a user tries to access OWA, the receive the following error:


something went wrong
Sorry, we can’t get that information right now. Please try again later. If the problem continues, contact your helpdesk.

X-OWA-Error: Microsoft.Exchange.Security.Authentication.TokenMungingException

Resolution: This is the result of the mailbox being a ‘linked mailbox’ and having a value in the ‘linked master account’.

Run the following to view the value:
get-user batman15 | select linkedmasteraccount

Run the following to remove the value:
set-user batman15 -linkedmasteraccount $null

Set up an Exchange connection to your email in Outlook 2010 or Outlook 2013

Follow these steps.

1. Open Outlook 2010 or Outlook 2013. If the Microsoft Outlook Startup wizard appears, on the first page of the wizard, click Next. Then, on the E-mail Accounts page, click Next to set up an email account.
If the Microsoft Outlook Startup wizard doesn’t appear, on the Outlook toolbar, click the File tab. Then, just above the Account Settings button, click Add Account.

2. On the Auto Account Setup page, Outlook may automatically fill in the Your Name and E-mail Address settings based on how you’re logged on to your computer. If the settings are filled in and they’re correct, click Next to have Outlook finish setting up your account. If the settings on the Auto Account Setup page aren’t filled in or aren’t correct, do the following:

      If the settings on the Auto Account Setup page aren’t filled in, type the correct settings based on the information that was provided to you by the person who manages your email account.
      If the name in the Your Name box isn’t correct, you may need to reset the options on the Auto Account Setup page before you can edit your name. To reset the options, click the option button next to Manually configure server settings or additional server types, and then click the option button next to E-Mail Account.

3. After you click Next on the Auto Account Setup page, Outlook will search online to find your email server settings. You’ll be prompted to enter your user name and password during this search. Make sure that you enter your full email address (for example, tony@contoso.com) as your user name.

If Outlook is able to set up your account, you’ll see the following text: “Congratulations! Your email account is successfully configured and ready to use.” Click Finish.

Reference

Configuring a new identity for Outlook 2011

Scenario:  You wish to create a new identity for Outlook 2011 and re-configure Outlook 2011 with your exchange mailbox.

Instructions:
1. Open the Microsoft Database Utility. The default location is in /Applications/Microsoft Office 2011/Office/.  Tip: You can also open the Database Utility if you close Outlook, hold down the OPTION key, and then click the Outlook icon in the Dock.

2. Do one of the following:
   1. Create a new identity:  Click Add via the + button and type a name for the new identity.
   2. Rename an identity: Double-click the identity, and then type a new name for the identity.
   3. Delete an identity: Click the identity you wish to remove and click delete via the – button.

3. Switch the identity:
   1. Click on the identity you wish to become active.
   2. Click the gear button and choose ‘Set as Default‘.

4. Open Outlook:
   1. If this is the first time you’ve opened Outlook 2011, you will be automatically prompted to add an account. If you have an account configured already, click on Tools –> Accounts from the menu bar. Click the + and add an Exchange… account.
   2. In the Welcome to Outlook for Mac window, check Make Outlook the default application for e-mail, calendar, and contacts.  Click on Add Account.
   3. In the Add an Account window, click on Exchange Account.
   4. In the Enter your Exchange account information, enter the following and click Add Account.
        a. E-Mail Address
        b. Select User Name and Password for the Method.
        c. User name *include Domain in front of the user name.
        d. Password
        e. Check configure automatically.

5. Exit out of the Accounts window.

Outlook 2011 is now configured and your email will start downloading momentarily.

Exchange Health Manager has restarted a server even though a Global Monitor Override was in place.

Scenario:  You have a GlobalMonitoringOverride configured to prevent the reboot of an Exchange Server for a specific Exchange Health Monitor responder, but MSExchangeHMWo still rebooted the server anyways.   In our example below, we have an existing global monitor override that should prevent reboots for the responder “ActiveDirectoryConnectivityConfigDCServerReboot”. 
Cause:   The globalmonitoringoverride had an expiration date for 60 days after it was set.
Resolution: Remove the existing GlobalMonitoringOverride and replace it.
step 1 – View the current globalmonitoringoverride

get-globalmonitoringoverride
  
step 2 – View the log file associated with the reboot for the Repsonder

(Get-WinEvent -LogName Microsoft-Exchange-ActiveMonitoring/responderdefinition | % {[XML]$_.toXml()}).event.userData.eventXml | ?{$_.Name -like “ActiveDirectoryConnectivityConfigDCServerReboot”} | ft name,enabled
 step 3 (only if you have override setup already)

remove-GlobalMonitoringOverride -Identity ExchangeActiveDirectoryConnectivityConfigDCServerReboot -ItemType Responder -PropertyName Enabled  
   
Step 4  – Apply Either of the options below.
Apply based on duration of 60 days
Add-GlobalMonitoringOverride -Identity ExchangeActiveDirectoryConnectivityConfigDCServerReboot  -ItemType Responder -PropertyName Enabled -PropertyValue 0 -Duration 60.00:00:00
Apply based on Exchange version

Add-GlobalMonitoringOverride -Identity ADActiveDirectoryConnectivityConfigDCServerReboot -ItemType Responder -PropertyName Enabled -PropertyValue 0 –ApplyVersion “15.00.0847.32”
  
Step 5 – Restart the “Microsoft Exchange Health Manager” service