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.

I recently ran into an issue with my ThinkPad while trying to run VMware Workstation 15.0 when I had the Hyper-V role installed on Windows 10 Pro 1809. Having VMware installed at the same time as having the Hyper-V role installed is not an issue, but it is not possible to run both of them at the same time.

I found a really good blog article about the changes that were made to the Windows Subsystem for Linux (WSL) in the Windows 10 1809 update (or whatever it will be called when they eventually release it again) on the Windows Command Line Blog.

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

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.

Not a lot of people realize that Windows can be used on more than just x86 and x64-based hardware. Windows NT was designed from day one to be portable on multiple hardware platforms and was supported at one time on the MIPS, Alpha, PowerPC and Itanium platforms.