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.
Last week I have blogged about Project “Honolulu” and here is the tech preview I was waiting for. So Microsoft’s project Honolulu is a new local web-based management for your server infrastructure.
I personal belive it was time for Microsoft to provide a more unified GUI management, which is something VMware was doing for a long time now.
So starting with deployment, there are several ways, installing locally in your own windows 10 machine, having a dedicated gateway server and directly in on a server cluster you manage. Also not the gateway service can be installed on 2016 R2 and 2016.