Author: Steve Man

​Error moving user to Office 365 (onboarding)

​Error moving user to Office 365 (onboarding)
“The user doesn’t have a matching SMTP address with target destination domain”
User has a mailbox on prem and need to be onboarded to Office 365
Resolution: Run dirsync and ensure user is fully synced. The mailbox on prem must have corresponding mail user in Office 365. Move was successful after dirsync

something went wrong UserHasNoMailboxException

Issue: Customer couldn’t access office 365 mailbox using the unified URL and kept getting “something went wrong, user has nomailboxexception” errors.
Notes: Customer was running hybrid configuration with Office 365 and Exchange 2013. Also the mailbox is a remote mailbox
Resolution: TargetOWAURL for the organization relationship at customer site was
outlook.com/owa/servicedomain.edu
Issue was resolved when customer modified remote routing address of the remote mailbox to user@servicedomain.edu
The service domain in the target OWA url needs to match the remote routing address of the remote mailbox

Exporting Mailbox to a PST File

​Exporting mailbox to a PST File
Note: Must have the “Mailbox Import Export” role assigned
 
From powershell, type New-MailboxExportRequest -mailbox testmbox -name -filepathservernamepstfilestestmbox.pst
This will export all folders and data in each and export it into the specified PST file. Also note that the dumpster will also be exported by default.
If you want to get additional details about the mailbox export request, you can use the Get-MailboxExportRequest or Get-MailboxExportRequestStatistics cmdlet.
 
if the export fails to complete, you can add -baditemlimit for eg
 
New-MailboxExportRequest -mailbox testmbox -name -filepathservernamepstfilestestmbox.pst -baditemlimit 50

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:scriptsstaleeas.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.

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 folderssubfolders 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.

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.