Microsoft has released Cumulative Update 13 for Exchange Server 2013. This release adds support to .NET Framework 4.6.1.
Exchange has come a long way & is capable of “self healing” to an extend and it does it by runnning tasks like restarting the service, moving the database to a different copy etc. It is a good thing that Exchange fails over a database if it finds an issue with it, say for example
It’s not common that one needs to play with Exchange 2013 daily performance log files on a daily basis, unless you work for Microsoft support. You will be hunting for it, especially if you have raised a ticket with performance issues with the Exchange support team.
Microsoft has released .Net Framework 4.6.1 and this doesn’t go well with any version of Exchange server, including 2016 yet. You need to watch out for this one especially if you use Windows update to patch the servers.
The Azure team has released the much awaited Azure AD Connect binaries for download.
While running Connect-MSolService in Windows Azure Active Directory Module for Windows PowerShell, I was surprised to see the error below. This has worked like a charm in the past!
You can now specify a password for a new Office 365 user, just as you would while creating an account in Active Directory.
Office 365 RoadMap url is one to be added to your browser’s favourites.
Forefront Protection 2010 for Exchange was an antispam/antimalware product that was used heavily with Exchange 2010, especially in greenfield projects.
What is the difference between Office 365 first & standard release and how can I jump between the releases?