Today it was a long day as we attended the VMUGCZ meeting in Prague, which include some great presentations.
Here is the full schedule of the event as below I do mention what I found more interesting.
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.
Microsoft came a long way from when i stared working as an administrator back at the 2003 Server edition and I love what they did with the 2016 edition , thought did move some useful features on the enterprise tier.
Azure stack was the next logical step to create a bridge between the on-prem and cloud infrastructure, but when you need the similar abilities for your on-prem but can’t go for an Azure stack… Project Honolulu comes into play.
Form what MS describes to be, is the next step of your native GUI tools in a new sleek web-based package and will be soon in Technical preview and I can’t wait to try it out.
Also I can’t wait for the new announcements on the MS Ignite and getting ready for the MS Tech Summit in Frankfurt.
You can read more on Technet blog
This week there will not be a technical post as I am evaluating DSC (Desired State Configuration) for the production environment and I had my exam for the VCP-DCV.
It was a long goal of mine to become a VMware Certified Professional and i will keep moving forward with that. For this year my goal is to finish with a new Microsoft exam the Implementing a SDDC. But for 2018 I am already looking into the VCP6.5 Delta Exam and afterwards the VCP-NV.
Again thank you for reading and have a great day
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:
Hello, as I disclosed before I’m studying for the VCP6-DCV and wanted to share some parts of the process with you.
So let us start with the LAB ,after spending many hours studying the material there is always a thirst to try them out. The lab setup involves my PC i7-4970k ,32GB of Ram, 1TB HDD and 2x250GB SSDs plus my old trustful Synology DS-211j.
Currently I am running an AD/DNS Windows 2016 Server, a Win2016 File Sever and 2 ESXi 6.5. The next step is to build my vCenter Appliance.
What I forgot to mention is that everything running on my VMware Workstation Tech Preview 2017 Pro. Which also makes redundant the configuration of the VMX file after importing the OVF of the vCenter appliance and before powering it on.
As for networking, I have a Host dedicated management network and there will be also a storage one too.
And with that I leave you as the long wait for my Tiny vCenter Appliance starts.
This is my very first post on my very first blog. The main reason I created this blog is to record my Journey to the Centre of the Software Defined world (and who knows, like Robur will float in the Cloud ). Thank you for being here with me.
I aim for a mix of Microsoft and VMware posts, as currently I am studying for the VCP6-DCV and in the end of this year intend to take the new MS Exam 70-745 Implementing a Software-Defined Datacenter.
Far and away the best prize that life offers is the chance to work hard at work worth doing
Virtually everything is POSHable
Cloud and Virtualization
Scotty, we need more power.