O-Xchange Notes from the Field!

Monday, December 30, 2013

Delivery status notifications in Exchange Server

Non-delivery reports (NDRs) are system messages that report the delivery status of a message to the sender. The messages are a subclass of a general message information structure that is known as delivery status notifications. Delivery status notifications describe three kinds of situations:
  • Success (2.X.X numeric codes)
  • Persistent transient failure (4.X.X numeric codes)
  • Permanent failures (5.X.X numeric codes)
NDRs are generated when a message cannot be delivered. If the computer can detect the reason for the failed delivery, it maps the reason onto a status code, and a corresponding error message is printed. For NDRs, most numeric error codes are reported in the form of "5.X.X" and are described as permanent failures. However, certain transient conditions cause "4.X.X" codes. 

Reference:

Check the Event Viewer from PowerShell

Below are examples of checking the event viewer via PowerShell.
Running local with event id and date range
Get-WinEvent -FilterHashtable @{logname='application';id=4107;StartTime="1/15/11";EndTime="1/17/11"}
 
Running on remote computer with event ID
Get-WinEvent -computername <remote computer> -FilterHashtable @{logname='application';id=15006}

Allow Exchange 2013 to accept remote powershell from Orchestrator

Scenario: Orchestrator was not able to connect and run Exchange powershell commands. The error received is:
Error opening remote PowerShell runspace to endpointhttp://exchangeservername/powershell: Connecting to remote server failed with the following error message : The WinRM client cannot process the request.
 
Resolution:
1. Make sure the Execution Policy on the Exchange Shell is set to RemoteSigned.
a. Use Get-ExecutionPolicy to see what it is.
b. Use Set-ExecutionPolicy RemoteSigned to set it.
2. Enable Basic and Windows Authentication on the Powershell IIS Site.
a. Expand: Default Web siteàPowershell.
b. Click on Authentication
c. Enable Basic and Windows Authentication.
  
The above steps did the trick for me, but the site below offers a few more steps.

Remove stale ActiveSync Devices from Exchange 2010

Scenario: Exchange accounts have a max of 10 ActiveSync devices per account. This script will remove stale devices that are older then 180 days.
The initial report will take hrs to run. the code is listed below. This will run and export the results to a CSV file.
$DevicesToRemove = Get-ActiveSyncDevice -result unlimited | Get-ActiveSyncDeviceStatistics | where {$_.LastSuccessSync -le (Get-Date).AddDays("-180")}| Export-CSV C:\scripts\staleeas.csv

The code below will remove the device by pulling the list from the CSV you created above.
import-staleeas.CSV | foreach-object {Remove-ActiveSyncDevice -Identity $_.guid -confirm:$False}

Issue user getting error “Could not read the Calendar”

Issue: User is getting an error when trying to open shared calendar.
“Could not read the Calendar”
Solution:
run: outlook.exe /cleanviews
url to findings:
Also link to useful outlook cmd line switches.

Thursday, December 12, 2013

Subscribing to folders in Outlook 2011 when using IMAP

Scenario: When you are using Outlook 2011 and your mail profile is setup to connect via IMAP, you may not see all of your folders\subfolders in your mailbox.
Solution: These folders may need to be subscribed to. Follow these steps to import these folders into Outlook 2011.
1. With Outlook 2011 open, select Tools --> IMAP Folders.
2. You will see a list of folders available to import into Outlook. You can click each folder and select Subscribe.
3. The new susbscribed folders will now be located in the folder list on the left hand pane of Outlook.

Troubleshooting EAS that stopped processing on a Exchange 2010 Server

Scenario: We had an Exchange 2010 server that stopped processing requests for Exchange Active Sync. Users were getting the error “Unable to verify the account information” on their mobile devices or other connection related messages. This problem was not enterprise wide and only a problem for whichever mailboxes were hitting this one Exchange 2010 Client Access server.
Solution: We had to find the server that was not processing the Exchange Active Sync requests. Once rebooted, the server started processing the requests again. Below are the key troubleshooting steps we took to validate the problem on the single server.
Troubleshooting Steps:
1. Test the problem user’s account with Microsoft Remote Connection Analyzer – Exchange ActiveSync test (https://testconnectivity.microsoft.com/). Where the test was failing, there was a common X-CalculatedBETarget Exchange 2010 server amongst all of the accounts.
2. In a web browser, going to the website: https://<servername>/Microsoft-Server-ActiveSync and comparing the behavior of the failed server to a good server. On the failed server we were getting the error message: 500 – Internal Server Error. There is a problem with the resource you are looking for, and it cannot be displayed. On the good server we were getting: The page cannot be displayed because the HTTP version is not supported. This let us know that this server was having a problem with the IIS website.
3. Taking it a step further, we browsed to the ActiveSync site from the Servers IIS manager. Here we got a similar, but more detailed error: HTTP Error 500.19 – Internal Server Error. The requested page cannot be accessed because the related configuration data for the page is invalid. Comparing these contents to a working server’s content, this helped support that there was a server problem.
4. Reviewing the IIS logs for this Ex2010 server also revealed that every ActiveSync request had a Http code of 500 (the 4th column from the end of each log entry).
5. Restarted the Server -- ActiveSync worked on that server when it came back up.

Can't load OWA Premium by using Internet Explorer 11 in an Exchange Server environment

When you try to access Outlook Web App (OWA) Premium by using Internet Explorer 11 in a Microsoft Exchange Server 2013, Microsoft Exchange Server 2010, Microsoft Exchange Server 2007, or Microsoft Exchange Server 2003 environment, OWA Light is loaded instead.
To work around this issue in Exchange Server 2013, Exchange Server 2010, Exchange Server 2007, or Exchange Server 2003, use Internet Explorer 11 in compatibility mode to access OWA. To do this, press F10 to display the menu bar, go to the Tools menu in Internet Explorer 11, and then click Compatibility View settings. Then, add the OWA site to the list of sites to be viewed in compatibility view.

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.