For this post I just wanted to note down my thoughts and plan that I recently used to migrate a client from Active Directory 2008 R2 to Active Directory 2016. For this work the servers involved were four Windows 2008 R2 servers which all ran AD, DNS, DHCP and NPS. These roles were being migrated to four Windows 2016 servers. The servers are spread out geographically and are on different networks but are all part of a single AD domain. All of the servers are Global Catalog servers. This is not designed to be low-level guide with all the intricate details but more of an overview (with some useful commands thrown in).
Just recently I was asked by a client to migrate their Active Directory 2008 R2 servers to Windows Server 2016. All was going well until I needed to demote the old domain controllers and ran DCPROMO. I was presented with the error Active Directory could not transfer the remaining data in directory partition. Then below it stated The directory service is missing mandatory configuration information, and is unable to determine the ownership of floating single-master operation roles. Before starting with the fix I would just note that every step here is important. Missing some of the details and skipping over things (you may think you know) will slow you down in the long run.
Recently I wanted to test something with the latest version of VMware Workstation on my test machine that also had Microsoft Hyper-V installed. When trying to start a VM in VMware workstation I received the error ‘VMware Workstation and Hyper-V are not compatible. Remove the Hyper-V role from the system before running VMware Workstation.’
After migrating a client to Office 365 I needed a way of sending email from various applications and devices. I wanted an open relay for email though an onsite Windows Server to Office 365.
I needed to capture all traffic from a particular network port (an IP phone system connected to a Cisco SG300 switch) and mirror this data to a virtual machine in our virtual infrastructure. So effectively I needed to setup port mirroring from a physical network port to a VMWare ESXi virtual machine.
A client recently asked me to setup several VMs using the evaluation copy of Windows Server 2016. After they had put lots of data on the servers and decided to use them for production purposes they decided they wanted to keep the existing server setup. When inputting a purchased Volume Licence Key they were presented with the error ‘That key can’t be used to activate this edition of Windows. Please try a different key’.