Error while moving a mailbox to Exchange 2013 Error:Migration Permanent Exception: Active Directory property ’homeMDB’ is not writable on recipient.
The Delegates settings were not saved correctly. Unable to activate send-on-behalf-of list. You do not have sufficient permission to perform this operation on this object
SPAMFighter for Exchange 2013 and Server 2012 review. A bargain alternative Anti Spam product of Exchange 2013.
When launching OWA 2010 in Exchange 2010 you see the error Outlook Web App didn’t initialize. If the problem continues, please contact your helpdesk.
Couldn’t find a base theme (folder name=base) . This can be fixed with a power shell command
When creating a new user in Exchange 2013 you receive the following error – Exception has been thrown by the target of an invocation. This could be a Nested OU issue.
If you have Exchange 2013 installed on Server 2012 then when you manage Exchange 2013 with Internet Explorer 10 then it crashes constantly. A patch is now available to fix.
When migrating mailboxes you may see a Transient error StorageTransientException has occurred, this is because the mailbox is poisoned and quarantined.
With IE10 OWA 2003 does not display correctly, inbox is displayed incorrectly and the screen is garbled. We can resolve this with compatibility mode.
After installing office 2013 you cannot launch Office 2013 as there are no icons to run applications, this can be fixed by removing some reg keys and reinstalling.
When printing from Office 2013 to a HP Laserjet Word,Excel,Powerpoint 2013 will hang with Windows Host Process (Rundll32) Not Responding. We need to scrub the driver
During an Exchange 2010 to Exchange 2013 migration when you try to connect to OWA 2010 you cannot instead you redirect to iis or OWA 2013.
Find out what mobile devices are connecting to Exchange 2013 or Exchange 2016 and gather the activesync information of mobile devices that are connecting.
When connecting to Exchange 2013 you receive the error Exchange 2013 451 4.7.0 Temporary server error. Please try again later. PRX5, this is a known DNS issue.