We have talked a few months back about the new management experience Microsoft wants to add in their Server products, Project “Honolulu”.
So a few days back we did get an update that adds some really cool new features.
For you have it already installed then you will see on the top that there is an update available.
This is something that coming back over and over again. For most windows admins is/was an issue till the Windows 2k16. I always preferred to handle split-dns in a linux environment than building a separate server just to provide the external, NAT, Geo-location IPs.
Though as the Active Directory loves DNS, it is hard to separate it. At last we do have a solution with the new policies and split-scope zones. Below I will provide a simple scenario where you are having two networks and the subnets are NATed. In my experience the best way to handle it is by scripting and building the server from the scratch. Outsource you can add the AD integrated zones, but there are things you maybe don’t want to inherit.
So at first is good to create a number of CSV files to hold the SRV, A, CNAME , Zones and the outsource don’t forget to add , where is needed, a column with the NATed IP.
During my short time with O365 and especially the Exchange Hybrid configuration, I did discover the one of the hardest things to do is to decide which is the best course of action for creating new mailboxes. Either create them on-prem first and then do a migration to the cloud or start from the cloud and then configure a remote mailbox at the on-prem?
Personally i do prefer creating the remote mailbox and the O365 user/mailbox at once by using the New-RemoteMailbox command. But there is something missing in the parameters , the Shared Mailbox trigger.
So for creating a mailbox in the a Hybrid environment, and then if it is needed to make a Shared on we would first connect to Exchange management shell, use the get-Credential command to set the username and credentials that you will use for the mailbox.
During the last months I came across an influx of full mailboxes. In most cases were used to relay messages from other platforms. One of those has exceeded our Organization default quota by 102% and of course the rest were at 97% to 99% of the current quota.
My first though was to change the Retention policy down to a month with the users approval and start the Managed Folder Assistant which unfortunately did not solve the issue. You can find more on that on Sam’s IT Blog.
When working with Exchange online Powershell there are several things to keep in mind:
- You can have up to 3 Sessions at the same time
- Exchange Online sessions do have restricted language mode enabled and you can find a way to solve the variable issue on michev.info
- There is a Powershell Throttle , please refer to this post on how to calculate your micro delays .