Where’s that Darned Licence Server?
So you added the Role for Licencing Server (on same or preferably another more dedicated server) and even the additional Remote Desktop Session Host role on the one users are accessing. But they still get that pesky “You have 119 days” message. Embarrassing.
Where on earth do you tell this server where to contact the Licencing Server you carefully setup and used the Microsoft Clearing House to activate your User or Device CALs? Trawling through those Technet and MSDN articles just goes around in circles! Googling it comes up with too many different issues, and some “fixes” involve Registry Key updates… surely that can’t be right… Arrgghhh!
The answer, my friend, is… Group Policy. Yep, it’s hidden away in there. You’ll know that because once you get Microsoft support (if you’ve got it), you’ll note on the shared session that the engineer is straight in there like a rat up a drainpipe. Trouble is, next time you have to do it, it’s far from obvious again, including where exactly that GP setting is. We’ll its here:
Computer Configuration/Administrative Templates/Windows Components/Remote Desktop Services/Remote Desktop Session Host/Licencing.
Obvious innit! Set that – best to use direct IP if they’re stable, in case DNS Server not available.
Oh, and if it still doesn’t kick in, try:
Heheh, that made it do some work. Now no awkward messages or lockouts > 2 users, and you can get on with your life again.