You never know what your going to get when working with an existing on premise Exchange environment. That’s one of the reasons I love my job as much as I do; every organization is different. While recently preparing to migrate a client from Exchange 2010 to Office 365 via hybrid, I found they had a previous…
After clearing hundreds of move requests in Office 365 via PowerShell, I had to clear all of the disconnected mailboxes in Exchange 2010 those moves created. However, when I ran this command… Get-MailboxStatistics -Database “Mailbox Database” | where {$_.DisconnectReason -eq “SoftDeleted”} | ForEach-Object {Remove-StoreMailbox -Database $_.database -Identity $_.mailboxguid -MailboxState SoftDeleted} …this error came up… Pipeline not…
Updated on 25 June 2015 In my opinion, moving mailboxes in bulk (in a hybrid deployment) is easiest when using the Exchange 2010 Management Console (EMC) or the Exchange 2013 Admin Center (EAC). However, with some additional preparation, we can use a list of commands to perform the same task. On the hybrid server, install…
There are a few consistent issues that I see commonly occur when implementing an Exchange hybrid with Office 365. All affect mail flow to, from, or both to and from an on premise Exchange 2010 or 2013 environment and Office 365 Exchange Online. Below are the most common issues that I would like to describe…
This week, I experienced an issue in which the mailbox for the administrator account could not be accessed via Exchange 2010 Outlook Web App (OWA), Outlook client or mobile device using Exchange ActiveSync (EAS). No other mailboxes were affected. This is the error received when accessing OWA… You don’t have permission to open this mailbox. To give…
