Microsoft Windows Server 2016: A Frankenstein of Services

Microsoft adopted an “everything but the kitchen sink” strategy with the launch of Server 2016. While it is possible to tell if this was a brilliant move or a well-intentioned disaster, SysAdmins are still struggling to understand a range of server roles and configurations that could make Victor Frankenstein’s head spin.
This new functionality is a direct result of Microsoft’s Azure evolution. Microsoft learned a lot from running their own cloud how to implement virtual machines, containers and networking. Server 2016 would still be diagnosed with schizophrenia in any other environment and taken to the lab to have its bolts checked. Administrators are responsible for navigating the chaos to find the right solution.
You may only be interested in installing a WISA stack that includes Exchange functionality and file storage. You suddenly find yourself faced with seemingly unrelated life choices that even your therapist cannot help you solve.
Are you looking for Standard, Datacenter or Essentials?
Nano, Core, Hyper-V?
Azure or local?
How many virtual machines can you host guard?

Containerize volatile applications? This container is Windows Server.
Hyper-V Isolation?

Although Dr. Frankenstein will eventually hate his invention, how can we avoid the same fate when installing Server 2016? You can avoid this fate by learning Windows Server 2016 training. The most difficult part of planning and configuring Server 2016 will be identifying the dependencies. It is easy to get lost in the maze of possibilities and end up starting over every time we reach a dead end. There are many resources that can help you get past the configuration hurdles with minimum hassle.
Learn how to become a security expert with SPOTO’s Cybersecurity Training
Start trainingIdentity with Windows Server 2016 Exam 70-742)
Networking with Windows Server 2016 Exam 70-741)
Windows Server 2016 Virtual Labs

Start at the end and think about the long-term goals. You will be able to find a configuration that works without breaking the budget by working backwards. If not, you can always try again! The Essentials Edition is the best option for IT departments. Small organizations will find it easy to use and provides a native ability to secure Azure expansion.
The initial decision for most people is between Standard, Datacenter, and cloud hosting in Azure. Datacenter is the only edition with advanced storage capabilities (such as Storage SpacesDirect), shielded virtual machine and software-defined networking. The choice is easy for those who require these additional functions.
Everyone else will have to choose their flavor based on cost versus ease-of-administration. Server 2016 in Azure, for example, can be simplified administration for small IT departments, but it comes with a significant monthly cost. The Datacenter Edition also includes unlimited OSEs, Hyper-V containers, and other benefits that could provide significant savings over the Standard Edition.
You’ll need to use your vacation days if you are able to decide on the right edition for you. Even Victor Frankenstein went to the North Pole.
After your vacation, you will need to decide whether the Core option is more convenient or the Desktop GUI. Core’s stability and decreased attack surface are more important than the Desktop’s convenience. Core also has lower resource utilization.