In your Exchange 2016 environment you might come across the following event ID constantly logged in the application log, EventID 1023,Perflib: “Windows cannot load the extensible counter DLL MSExchangeIS. The first four bytes (DWORD) of the Data section contains the Windows error code.” Solution: As we are running in Coexistence Read more…
In this tutorial we will look at an error logged on 1 of our Test Lab Exchange 2016 Servers. We are currently running coexistence with Exchange 2010 and Exchange 2013. In the application log in Event Viewer the following Event ID was logged: The IP address listed is for our Read more…
In Exchange 2016 (and 2013) you can check the health of your server. If you run the following command: Get-Serverhealth -Identity <ServerName> You will get a long list of information. To narrow this down to UnHealthy Alerts, you can run the following command: Get-ServerHealth -Identity <ServerName> | Where {$_.AlertValue -eq Read more…
While Exchange 2016 is still “New”, there are some warnings or errors you may encounter but they are not actually a problem on the server. Let’s look at the example below: You might think the above warning is telling you something is wrong with the database, actually it’s more informational. Read more…
Microsoft released this new “Feature” called “PreferenceMoveFrequency” in Exchange 2016 CU2 – What does this mean for you as an Admin? Previously once you did maintenance on your Mailbox Server you would need to run “RedistributeActiveDatabases.ps1” script to balance the databases again. In CU2 the above option is set by Read more…
For those who have installed Exchange 2016, you might come across some errors or warnings not seen in previous versions of Exchange. To give you an example, MSExchange UnifiedPolicyFileSync warning that keeps getting logged in the application log: Is there a solution? No, not at this point, this is apparently Read more…
If you are running Exchange 2016 coexisting with legacy versions like Exchange 2010 or 2013, you might come across errors logged with regards to MsExchDiscovery. Here is a snippet of the error: The solution? Move the mailbox to the Exchange 2016 database. To do that open up the Exchange Management Read more…
When you introduce a new version of an Exchange Server into your environment, you want your users to be able to take full action of the new features and of course be on the new version of Exchange. In this tutorial we will look at the following: Move a user Read more…
In Exchange 2016 and 2013 Exchange Admin Center (EAC), you will notice that you can only assign services to an individual server whereas in the legacy Exchange, Exchange 2010 you can select multiple servers. In this tutorial we will go through importing an SSL certificate to multiple Exchange 2016 servers Read more…
Microsoft released DOTNET 4.7 on Server 2012 and R2, however it’s not supported yet on Exchange 2013 and 2016. You can read about the new version here: https://blogs.technet.microsoft.com/exchange/2017/06/13/net-framework-4-7-and-exchange-server/ Please take note, DO NOT Install this in a Production Environment. If you did install this through windows update by accident, please Read more…