A Case for Change Management
What I call my lab is increasingly becoming a production system that services my family of 4. Recently I decided to get Nextcloud deployed as an alternative to OneDrive for the family, and so I spent the weekend prepping my domain for better manageability and redundancy. Since I’m in my “lab,” and I’m the only admin, I got cocky and I made a rookie mistake: I made a bunch of changes at once.
First I changed my domain controller IP addresses to better match the IP plan I’ve had in place for my other application servers. I did this on a whim and didn’t think it through. Peer review and a bit of planning might have reduced some of my problems.
Next I deployed a third domain controller in a virtual machine on a different piece of hardware then just assumed the thing worked without any actual testing. How often does a DC Promo fail anyway? 😁
Third, I performed a series of updates on a member server that then started showing errors in the event log and I dismissed them as a server problem and not a symptom of a larger problem.
When it was all said and done, or more accurately when I realized I had actual problems I had to fix, I had already added each of my kids’ desktops to the domain but the computers were not applying group policy! D’oh!
With that being said: