This is the start of an 8-part series on building a Certificate Authority using Active Directory Certificate Services in Windows Server 2019. The process is quite involved, but with this guide and planning on your part, you should be able to build this important infrastructure component with ease.

I liked Windows 7 a lot, it was a great operating system that I deployed and supported very early in my IT career. An end of an era, but it had to happen.

It had a good run, but the time has finally run out on Windows XP and all its variants. It was a great OS (eventually), but ultimately it has been succeeded by more modern operating systems and better practices.

Active Directory is an incredibly powerful tool that pretty much every business relies on for user authentication and management. That doesn’t mean that people set it up properly though, and Microsoft has provided a very good guide on how to avoid those mistakes.

One of the biggest and most welcome changes to the Windows 10 1809 update and in Windows Server 2019 was the addition of the OpenSSH Client and OpenSSH Server features. Certainly, this was something that I never expected to happen, but it is a welcome change.

The Windows Kernel Internals team posted a very interesting article about the architecture of the Windows Kernel and on its ability to scale up from embedded IoT devices to servers running the Azure datacentres.

I wanted to do a follow up my previous post about Windows on ARM since I have had some recent hands-on experience with this platform. I was able to obtain a Lenovo Miix 630 through a contract that I am working on, and I have been using it in a daily basis for the last 2 months. I had wanted to give this platform a fair chance, and here is what I found out.

I ran into a few issues with running this very old operating system as a virtual machine on Hyper-V a few days ago. I needed to do this for a personal project that I am working on, one that I have been thinking about doing for a while now. Since I ran into a few issues with getting this to work correctly, I thought I should share my findings and write a quick guide on how to get Windows NT 3.51 Server and Windows NT 3.51 Workstation running on Hyper-V.