Posted: 12-26-22 5:40 pm
This was rather coincidental. The current server has been around for something like 7 years now and the only reason it was on my radar for an update was because Microsoft is dropping support for Windows Server 2012 R2 during 2023.
So my very next task after 10.9 went out the door was going to be this totally unnecessary imposition to "fix" something that wasn't broken. But then, the day after Christmas, the old server started misbehaving very strangely (idling at 100% CPU most of the time, despite no out of the ordinary web traffic).
Instead of diagnosing and fixing a problem that was probably failing hardware in the datacenter, I just did the server switchover a week early.
If you're reading this, you're on the new Windows Server 2022 box. Congratulations!
If you find any of the usual hiccups (file attachments won't download, etc.) let me know. Over the years I've made a pretty reliable checklist, but Microsoft is always "helpfully" adding new features to their products. I just did a whirlwind tour of most of the website features (including unlocking from the app) and everything seems to have come back up a little faster and easier than any of the other times I've attempted this.
So my very next task after 10.9 went out the door was going to be this totally unnecessary imposition to "fix" something that wasn't broken. But then, the day after Christmas, the old server started misbehaving very strangely (idling at 100% CPU most of the time, despite no out of the ordinary web traffic).
Instead of diagnosing and fixing a problem that was probably failing hardware in the datacenter, I just did the server switchover a week early.
If you're reading this, you're on the new Windows Server 2022 box. Congratulations!
If you find any of the usual hiccups (file attachments won't download, etc.) let me know. Over the years I've made a pretty reliable checklist, but Microsoft is always "helpfully" adding new features to their products. I just did a whirlwind tour of most of the website features (including unlocking from the app) and everything seems to have come back up a little faster and easier than any of the other times I've attempted this.