With the end-of-life for Office 2016 and Office 2019 approaching next month, I'm curious about how everyone is managing their migration plans to Office 2024 or Microsoft 365. We've made some progress across our 20,000+ systems, but it feels like we've hit a wall lately. For those who've been through this process, what strategies have worked well for you? We're mostly deploying with PDQ packages. Also, any advice on managing Project version migrations would be greatly appreciated!
5 Answers
Honestly, I'm clinging to Office 2016 like it’s a life raft! Making that switch feels like a huge decision. But I hear you on the reasoning behind needing to migrate; it's just tough to let go.
I'm interested in the challenges you're facing. Is it more about user resistance, technical issues, or something else? All the companies I've worked with over the past few years have already switched to M365, so I’ve only had to deal with updates, not the transitions.
We went with SCCM for our installations, made it a must-have software update. We had a week-long grace period for users to comply, and rolled it out at 20% of the machines each week. It seems to keep people on their toes without overwhelming them.
We wrapped up our migration already! Windows 11 does throw a few curveballs into the process with new controls and features—like the altered print screen function, ugh! But hey, better late than never!.
I totally feel you on this struggle! Transitions can be really tough, especially when people's workflows are deeply ingrained. It's one thing to update Windows, but changing email systems can send a lot of folks into a panic. It could help to communicate with the management team to get executive support. If anyone pushes back, direct them to management for clarity on why the change is necessary.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures