[SOLVED] enterprise IT

Exchange 2013 CU10 was released September 15th.  Cumulative Update 10 or higher is required to co-exist with Exchange 2016.  CU10 does not require a schema update unless you were running a version of Exchange 2013 older than CU7. Warning: CU10 contains an issue introduced in CU8 where there is an increased IOPS write load that can cause mail delivery delays to the mailbox database.  I'd recommend skipping CU10 and installing CU11, CU12, or newer as this issue was fixed in CU11. For convenience, Read more [...]

Issue: You are having issues with inbound mail or receive the following error in the application event log: "maximum number of connections per source (20) for connector has been reached" Background: Your most likely to see this error on receive connectors that are receiving mail from your spam filtering solution.  This is because your spam filter likely sends large batches of messages in each SMTP conversation.  The receive connector getting mail from your spam filter is in theory receiving Read more [...]

Issue: Content index errors may prevent you from performing DAG Database switchovers:  "Error: An error occured while trying to validate the specified database copy for possible activation. Error: Database copy on server has content index catalog files in the following state: 'Failed'" Resolution: The following Exchange Management Shell commands can be used to troubleshoot failed or corrupt DAG Database Content Index.  These commands will identify and re-build/re-seed any  bad content indexes Read more [...]

Issue: OWA HTTP redirection breaks after upgrading from Exchange 2013 CU7 to Exchange 2013 CU8. Solution: I reviewed all the settings in IIS related to HTTP redirection and several settings reverted to the default Exch/IIS values while many settings remained intact from when I first setup Exchange 2013 OWA HTTP Redirection. Here are the settings that I changed in order to make HTTP redirection work again, hopefully this can save you the work of re-doing all the settings: - default website Read more [...]

Issue: There is a plethora of threads and confusing articles online about the topic of manually removing an Exchange 2003 server from your Exchange Org.  This might be required when a server fails and is not restored from backup or when your graceful uninstall efforts through add/remove programs fail in the middle.  If add/remove is simply giving you errors like mailboxes still exist or public folders still exist then I would take the time to properly decommission the server and continue with the Read more [...]