I’ve been working on a simple PowerShell command today to import into our endpoint management solution so we can alert on disks with low diskspace. It’s been a while since I’ve dabbled with PowerShell, and it reminded me just how flexible it is and much I love it!
So I thought I would walk you through the evolution of the command I ended up with.
In this blog post we’ll look at how to install the latest version of Exchange 2016 on Windows Server 2016. At the time of writing the current version of Exchange 2016 is CU3.
When Exchange 2016 was first released it wasn’t possible to install it on the Windows Server 2016 Technical Previews due to some missing features in the OS that it relies upon, but now Windows Server 2016 has been released to manufacturing, installation of Exchange 2016 on WIndows Server 2016 is supported.
The demo environment I am using includes a Windows Server 2016 domain controller that is running at the Windows 2016 forest and domain level, and a Windows Server 2016 member server.
In the demo environment no previous versions of Exchange have been installed so as part of the installation the Exchange 2016 we will upgrade the AD Schema.
Finally before we start, always test in a demo environment before deploying in Production!
In this post I’ll look at how to find out the mailbox sizes in Office365 using PowerShell.
I’m working with a few more companies now who use Office365 so I thought I would look at how to perform a few general Exchange administration tasks in Office365 using PowerShell so that I can manage and maintain them more easily.
Note: the steps below also work for Exchange 2016.
So I turned on my test SBS 2011 server today to test out the latest Exchange Update Rollup and was greeted by an VM that was hanging on startup. Looking into the issue more closely the virtual network adapter was disconnected and when I tried to select ‘connect’ I received the following error message:
The network bridge on device ‘VMnet0’ is not running. The virtual machine will not be able to communicate with the host or with other machines on your network. Failed to connect virtual device ‘Ethernet0’.
In part 10 of this mini-series, I’ll look at how to configure the virtual directories used by Exchange 2013. We’ll need to configure these to match the FQDNs we request on our SSL certificate.
It’s assumed that split-brain DNS will be setup for the configuration to work. The essenace of split-brain DNS is that your external domain name is also configured on your internal DNS servers, but the A records on the internal DNS server point to the internal IP address of the server whereas the domain name configured on your external DNS servers point to the external IP address of your server. So whether a client is internal or external the FQDN will always resolve to the correct IP address.
In part 9 of this mini-series, I’ll look at how to configure the Fully Qualified Domain Name (FQDN) of the Default Frontend receive connector in Exchange 2013.
Firstly a warning: Don’t modify the FQDN value on the default Receive connector Default that’s automatically created on Mailbox servers. If you have multiple Mailbox servers in your Exchange organization and you change the FQDN value on the Default Receive connector, internal mail flow between Mailbox servers fails.
In a single Mailbox server environment to change the Default Frontend receive connector FQDN follow the steps below.