I'm looking to upgrade my standalone Remote Desktop Services (RDS) server from Windows Server 2016 to Windows Server 2025. We're using it for some remote staff, and I'm curious if there are any specific tips or issues I should be aware of during the in-place upgrade process. Also, do we need to buy new Client Access Licenses (CALs) since our current 2016 ones—will those carry over to the new version? Appreciate any insights!
3 Answers
For a smoother upgrade, I recommend creating a brand-new server from scratch instead of upgrading directly. Configure your services and apps on the new one, test them out, and once you’re confident, switch your DNS or IP over to the new server. This way, you still have your old server as a backup for a while until you’re sure everything is running smoothly.
It might be worth asking why you want to jump to 2025 specifically. Are there features you're absolutely looking for, or are you being pushed to upgrade? If not, maybe consider going to 2022 instead, which could save you some headaches. If you do decide to stick with 2025, I’d suggest cloning your current setup first and testing the upgrade there.
Good point! Honestly, I don’t need 2025 features right now; we’re just updating our old 2016 servers as we go. I might just grab a 2025 license and upgrade to the more established 2022 instead.
You're going to need new CALs to connect to the 2025 server, and the upgrade itself isn't too complicated. But be sure to test everything before diving in—there are often software compatibility issues that can crop up.
Yeah, I've done in-place upgrades plenty of times. I’m more concerned about the RDS specifics and the CALs not carrying over—definitely sucks!
Totally agree! We've stuck with 2022 for now. Plus, I’ve heard enough complaints from others who jumped to 2025—that’s not the nightly surprise I want!