I'm currently migrating my company's ERP system to a new Windows server, and I've noticed something puzzling regarding Remote Desktop Services (RDS) licensing. Users connect remotely using a .rdp file that opens our ERP application directly on the server, bypassing desktop access altogether. I discovered that while our RD License Manager indicates we have only 125 installed licenses and 120 available for Per User CAL, we actually have over 200 users connecting daily. My question is: since we have more users than licenses according to the RD License Manager, when exactly is a Per User CAL necessary? Do I need to worry about licensing even if I'm not using the typical RDS Server Roles and Features?
4 Answers
Honestly, I'd recommend setting up the full infrastructure for web access, like RD Gateway and Connection Broker. It would streamline everything, especially for RemoteApp. That’s really what it’s meant for.
Exactly! The license isn't about how many are logged in at once; it's about how many users are accessing the server. You'll need one per user that connects, regardless of the server roles in play.
Yeah, anyone remote accessing the server’s resources does need an RD license. The roles don't really change that requirement. You should have the right licenses for the users connecting, regardless of how they connect.
Just a heads up, make sure to check your Microsoft 365 licensing too. If you're on E3 or E5 plans, they might include a Per User CAL, which could save you some headaches even if you're unsure about RDS features.
Got it! By the way, the server you mentioned—it's a 2016 Standard, right? Does that mean it has some built-in licenses? I remember reading about an unlimited TS per Device CAL, but I wasn't sure how it works with the newer RDS licensing.