With the change from a MMC based administration model (Exchange 2010) to a web based administration model in Exchange 2013/2016, Microsoft created an overlap between the options page in OWA (which is the ECP virtual directory in 2010) and the administration page in Exchange 2013 and 2016. The issue becomes the exposure of the Exchange Admin Center to the Internet via this ECP virtual directory. For some companies this is considered a security issue and requires that this virtual directory be blocked. However, in blocking the directory OWA functionality becomes limited due to the inaccessible Options page.
What Can Be Done?
Luckily, Microsoft did write up a blog post to cover this particular need:
Configuring Multiple OWA/ECP Virtual Directories on the Exchange 2013 Client Access Server Role
The problem lies in its execution and the usual case of human error.
The long road is done. The book is done. Now I can relax…. and market it!
After running my updated Exchange 2013 and 2016 scripts I noticed that .NET was tripping on itself during the install of either the prerequisites or post hotfixes. So, I decided to completely re-write those sections for .NET 4.6.1 and 4.6.2. I also cleared out .NET 4.5.2 as this one will be deprecated soon. Windows 2008 R2 support has also been removed from the 1.17 version of the Exchange 2013 script.
A separate script was created for Windows 2008 only (third link below). This will be updated until Windows 2008 R2 leaves extended support.
As you can see from the screenshots, the menu has changes a bit from the last version:
Removing the very first database can be a bit challenging if you don’t know what to expect. This is because Microsoft stores some important system mailboxes on the very first database that was created. I’ve written about this for Exchange 2010 and 2013:
Remove First Database – Exchange 2010
Remove First Database – Exchange 2013
Why Cover Exchange 2016?
A lot of companies are moving to Office 365. The reality is that cloud is hot and a lot of companies see Exchange Online as a way to remove some complexity from the environment. However, there are still quite a few companies that are deploying Exchange 2016, whether this is a Hybrid server or as an upgrade from an existing Exchange 201x environment. Thus, rehashing an old topic with the changes that are specific to Exchange 2016. Read more…
This is the first update since Oct. 2016. New changes:
- Fix .NET 4.6.1 installation process
- Added .NET 4.6.2 installation
Added DWORD for registry items in RC4 disable section
The new menu looks like this:
Please comment if you notice anything.
Download the new script HERE.
** Note **
New Exchange 2013 script will be out over the weekend.
While working on my Prerequisite scripts for Exchange Server 2013 and 2016, I realized that the code section for .NET was no longer working. It turns out that there are quite a few recommended hotfixes that are required for .NET 4.6.1 and .NET 4.6.2 to install properly. In order to facilitate the installation of this for Prerequisite scripts I had to strip out the code for .NET and rebuild it in a separate script. This required a non-Windows 2016 server which has .NET 4.6.2 installed by default as well as a server that did not have .NET 4.6.1. So, using a base loaded Windows 2012 R2 server I was able to work out the script.
You will notice that the .NET 4.6.1 download page (found here) does not list any prerequisites in order to install it. However, when you install it, you will find that you need to install KB2919355. If you review the download page for this patch, there is a list of other patches that must be installed: Read more…
Exchange Online and Exchange Server have a lot of similarities, but with Microsoft improving its cloud services, Exchange Online also has its differences. One of these new features is Office 365 Groups. Office 365 Groups are a useful feature that was added to Exchange Online, but sometimes a simple distribution list is all that is needed. Exchange Online, like Exchange Server, provide two methods for creating groups – EAC or PowerShell.
You would expect that creating a Distribution Group in Exchange Online and Exchange Server would be the same because the code bases are similar. Well, this seems to have changed because creating a simple Distribution Group in Office 365 is not the same in the EAC as it is on an Exchange Server. To create a Distribution in Office 365, you can log into the normal Office 365 Portal, then select the Exchange Admin Center: