Microsoft has acknowledged a known issue with Windows Server 2016 and Exchange Server 2016, and has advised not to deploy this configuration for now.
In Exchange Server the Get-MailboxDatabaseCopyStatus cmdlet may return the wrong activation preference value for a database copy.
When moving an Exchange 2013 mailbox to a database that is excluded from provisioning you receive an error.
A critical issue has been reported with the behavior of litigation hold in Exchange Server 2013 and Office 365.
New bugs have appeared in Exchange Server 2013 Cumulative Update 6 impacting Hybrid customers.
A hotfix is available for Exchange 2013 CU6 database crashes/failovers in Exchange 2007 co-existence environments.
Whinging about UAC is for wimps, this is a real Windows Vista annoyance. 1. Open Windows Explorer and navigate through…
