MS Exchange

Exchange Server

Create Certificate Request (CSR) on Exchange 2016

Issue: You need to install a third party ssl certificate on Exchange 2016 Solution: The first step is to create a certificate request that can be submitted to a third party certificate authority. In Exchange Admin Center, click "Servers" on the left side and then click the "Certificates" tab Click the Plus Sign to add a new certificate Click 'Next' On the New Exchange Certificate screen Input a friendly name for your certificate, I generally make this the primary hostname that Read more [...]

Change Internal URL to match External URL

Issue: You need to efficiently change all the internal URL's on an Exchange server to the value of the External URL. Background: This is a common necessity when your internal AD domain name has a .local and/or cannot be included in the SSL certificate on the Exchange server.  This article applies to Exchange 2010, 2013 and 2016.  It may also work on Exchange 2007 but I have not tested it. Solution: Using Exchange Management Shell we can populate all of the internal URL fields using the Read more [...]

Exchange 2016 Windows 2016 prerequisites

Issue: You need to efficiently install the required prerequisites for Exchange 2016 on Windows Server 2016.   Solution: The below commands will prep Windows 2016 for the Exchange 2016 Mailbox Server Role (Note: CAS role is built-in in Exchange 2016). Launch a run-as-administrator Powershell and use the following command to install the Windows 2016 prerequisites: Install-WindowsFeature NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, Read more [...]

Error during Exchange CU update: “System.Management.Automation.RemoteException”

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 [...]

Exchange 2013 CU16

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 [...]