Skip to main content

Posts

Showing posts from November, 2014

Exchange 2013 CU6, flawed update

The following are some links referencing the issue and some fixes for the flawed CU6 update for Exchange 2013. Released: Cumulative Update 6 for Exchange Server 2013 The Exchange Team, 26 Aug, 2014 http://blogs.technet.com/b/exchange/archive/2014/08/26/released-cumulative-update-6-for-exchange-server-2013.aspx Microsoft Releases Flawed Cumulative Update 6 for Exchange 2013 Redmond Magazine, by Kurt Mackie 09/02/2014 http://redmondmag.com/articles/2014/09/02/cu-6-for-exchange-2013.aspx Exchange 2013 CU6 hybrid and co-existence bugs cause administrators to despair WindowsITPro, Aug 30, 2014 by Tony Redmond http://windowsitpro.com/blog/exchange-2013-cu6-hybrid-and-co-existence-bugs Don't Deploy Exchange 2013 CU6 If You're a Hybrid Customer Friday, August 29, 2014 by Jeff Guillet  http://www.expta.com/2014/08/dont-deploy-exchange-2013-cu6-if-youre.html I ssues with Exchange 2013 Cumulative Update 6 (CU6) Exchange World, 10 Sep 2014 by nawaral http://blogs.technet.com/b/nawar...

Exchange: Beware of Disk with 4-kilobyte Sector Size

Beware of Disk with 4-Kilobyte Sector Size! Microsoft reference: http://technet.microsoft.com/en-us/library/ee832792(v=exchg.141).aspx Support requires that all copies of a database reside on the same physical disk type. For example, it is not a supported configuration to host one copy of a given database on a 512-byte sector disk and another copy of that same database on a 512e disk. Also be aware that 4-kilobyte (KB) sector disks are not supported for any version of Microsoft Exchange and 512e disks are not supported for any version of Exchange prior to Exchange Server 2010 SP1. Hyper-V gothcha: http://jeffreypersson.wordpress.com/2014/04/17/microsoft-exchange-server-2010-dag-on-vhdx/ "Continuous replication - block mode has been terminated. Error: the log file sector size does not match the current volume's sector size (-546)" Turns out that the issue is that the VHDX files are the default settings of 4096 PhysicalSectorSize. But it is not sup...