Exchange 2013 is a whole new beast when it comes to a stand alone Exchange server. A failed Exchange 2013 CU (Cumulative Update) can leave your Exchange server unresponsive to outside requests even though all Services are up and Powershell diagnostics are reporting everything working correctly. It leaves many Exchange Admins new to 2013 scratching their heads and attempting to restore from backup only to learn that a restore from backup does not work! What is this sorcery?! Stay calm. This is an easy fix and a lesson for new 2013/2016 Exchange admins that are used to the previous versions.
This sounds really easy but it can be challenging if you have never done it before. Out of the box Windows does not want to run Powershell scripts in an automated fashion. There are some security hurdles put in place for this reason. This blog post will show you what you need to know to make Powershell task scheduling a breeze.
Over the years I have seen so many approaches to migrating Windows file server shares to new servers. Most methods are valid and some are down right brilliant uses of native tools. I have an affinity for migrating shares in a specific way that does not utilize the native tools. It has worked really well for me over the years and I want to share it with all those out there that might need help with shares that are problematic.