Exchange 2010 sp3 not upgrading.

Recently in support we’ve noticed an abnormal amount of cases come in regarding upgrading Exchange 2010 sp3.  Now normally with upgrade cases they can be traced back to not having the correct permissions, broken permissions, or another sort of restriction.  Lately we’ve had several cases come in where the upgrade will start, then after a…

0

Using Advanced Query Syntax for searching in Exchange 2010.

I’ve noticed for some time now that we don’t have a lot of documentation on searching in Exchange 2010 which I believe has led to our customer having issues when doing searches in their environments.  I’ve noticed that a majority of search cases I’ve handled were related to inconsistent results, which have been resolved by…

2

Having issues moving mailboxes from Exchange 2007 to Exchange 2013

While working a case where an admin was having issues migrating users to the cloud we came across a fairly common error. Cannot open mailbox/o=ORG/ou=Exchange Administrative Group(FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=E2K13/cn=Microsoft System Attendant Now normally we can correct this behavior by modifying the HomeMDB of the system attendant to rehome it to a different database, or by mounting the database…

0

Issues with Database Scopes not applying when using EMCEAC.

So I recently discovered an issue when attempting to apply database scopes within Exchange 2010/2013/2016 when not using the Exchange Management Shell.  It happens every time you attempt to apply a database scope to a Role Assignment in the User interface of Exchange.  We’re currently investigating this behavior in Exchange versions 2013 and 2016, but unfortunately since…

0

Wrong Mailbox Server IP Showing up in Email Message Headers.

So I recently ran into an issue where a customer was seeing emails getting stuck in the spam filter.  When looking in the message header he noticed that the IP address for the mailbox server was incorrect, he thought this was causing emails to be caught in the SPAM filter and wanted to correct this behavior. Message…

0