[SOLVED] enterprise IT

Issue: During Exchange 2013 Cumulative Update at step 12 of 13 the following error occurs: error was generated when "$error.Clear(); $dependentAssemblyGeneratorExePath = [System.IO.Path]::Combine($RoleInstallPath, "bin", "DependentAssemblyGenerator.exe");..." was run: "System.Management.Automation.RemoteException". Note: The full error messages is contained below in the resources section. Cause: We believe this issue is caused by the relatively short timeout value of 120 that is specified Read more [...]

CU16 will likely be released sometime in February or March of 2016.   While Exchange CU15 introduced support for .NET framework 4.6.2, CU16 will allegedly require .NET framework 4.6.2.  We will add additional details as we speculate as to what features and notable fixes CU16 will include.  At this time Exchange 2013 CU15 is the current version of Exchange 2013. Read more [...]

Exchange 2013 CU15 was released on 12/12/2016.  Here are some key CU15 tidbits: CU15 fixes the public folder indexing issue that was introduced in CU13 and CU14.  If you were either CU13 or CU14, Microsoft advises you move your Public Folders to a new database to ensure the contents are indexed correctly. CU15 supports .NET framework 4.6.2.  You are note required to upgrade .NET for CU15, however the next CU, CU16 will allegedly require .NET framework 4.6.2. On new installations Read more [...]

Exchange 2016 CU4 should be coming out shortly, and we expect better compatibility with Windows Server 2016.  However at this time the latest release of Exchange 2016 is CU3.

Issue: You need to download the newest version of Exchange 2016

Solution: The newest version of Exchange 2016 is currently CU3.  Click to download Exchange 2016 CU3 direct from Microsoft.