Windows Server 2016 Nano Server – Installation and Management
Posted by Mikhail Rodionov on
February 7, 2017
Time to continue our conversation about that “scaled down even further” Server 2016 installation option. In my previous article, I covered general concepts around Nano Server, now I want to switch gears and talk about more practical aspects: installation and management. At the end of the day, you would agree that the best way to learn new technology it is trying to use it – this way you will be exposed to its strengths and weaknesses directly, and can get the real understanding of whether it works for you or not. Though at this point even Microsoft admits that despite all its greatness, at the moment, Nano Server has quite limited utility as it supports only a small subset of roles and features out of those which you can find in full GUI version of Windows Server.
Upgrade your CA to SKP & SHA256. Part I: Setting the Stage
Posted by Didier Van Hoye on
January 31, 2017
Many Certificate Authority servers that were installed on Windows Server 2003 never got upgraded until Microsoft ceased the support of Windows 2003. Some of those are still out there running today. A massive amount of them got set up in an era when Wi-Fi in the SME market became very popular and CA servers were deployed to easily secure access to it. To be fair, a lot of administrators didn’t wait for Windows Server 2003 support to expire and made sure their CA was more or less up to date by upgrading them in place. That alone is something to commend. However, the operating system version only introduces the capability of using modern more secure providers and algorithms. It doesn’t upgrade the ones used by the PKI automatically for you. So many of these upgrade PKI servers are still using an old cryptographic provider, the “Microsoft Strong Cryptographic Provider” (SCP) and an old hash algorithm (SHA1) that’s been deprecated (see SHA1 Deprecation: What You Need to Know) or even banned.
Installing Exchange Server 2016 on Windows Server 2016
Posted by Nicolas Prigent on
January 30, 2017
On October 1st, Microsoft Exchange Team released the new Exchange Server 2016. Microsoft has been testing and improving on millions of mailboxes in their Office365 environment before releasing the product on-premises. I will describe in this article a step-by-step guide for the installation of Microsoft Exchange Server 2016. The installation considers:
- a single server deployment of Exchange Server 2016 with the Mailbox role on a new Windows Server 2016
- Windows Server 2016 forest functional level
- Exchange Server 2016 with the latest Cumulative Update 4
Because Windows PowerShell is a powerful tool that every sysadmin would know, I will use PowerShell to perform the installation. But If you prefer the graphical interface, you can use it!
Windows Server 2016 Nano Server – Just enough OS model
Posted by Mikhail Rodionov on
January 13, 2017
We are in 2017 now, and it’s about fourth month since Windows Server 2016 has been RTMed in September 2016. By now, everyone probably heard about one of the big new features of Windows Server 2016 – Nano Server, new installation option which you can’t select during setup 🙂 . But I think there is still a lot of “why” and “how” questions around Nano Server. In this blog post, I will try to provide a bit of a history and compare Nano Server with other installation types.
Software Defined Networking (SDN) Stack in the Windows Server 2016
Posted by Oksana Zybinskaya on
November 3, 2016
Windows Server 2016 enables building a Software-Defined Data Center (SDDC) with new layers of security and Azure-related approach for hosting business applications and infrastructure. The new Software Defined Network (SDN) Stack provides dynamic security and hybrid flexibility by enforcing network policy in the Hyper-V Virtual Switch using the Azure Virtual Filtering Platform (VFP) Switch Extension. Instead of programming network configurations into a physical switch, the new Microsoft Network Controller delivers the network policy to the Hyper-V Hosts using the OVSDB protocol and is programmed into the VFP extension of the vSwitch by a Host Agent which enforces the policy.