This has been a source of irritation for many recently. Simply disabling wake timers and disabling the Windows Update service is no longer enough to keep Microsoft from waking your machine from sleep mode to carry out maintenance and install updates. It looks like this was introduced as an update sometime in 2018 and affects Windows 10 1607, 1703 and 1709. Fortunately there are a number of steps you can take to stop Microsoft meddling with your machine and leaving it running all night costing you larger electrical bills.
This is a quick post to mention a fix for an annoying problem that cropped up today after Sage had been installing their applications on one of our servers. It first appeared that Windows was not activated (even though I knew I had done this) and the Software Protection service was unable to start. It was giving the error Windows could not start the software protection service on Local Computer. You may also notice that Microsoft Office pops up with an error stating Microsoft Office can’t find your licence for this application. A repair attempt was unsuccessful or was cancelled. Microsoft Office will now exit. I experienced the error on Windows 2012 R2 Server but it seems that this is common on all operating systems above Windows 2008 R2.
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.