It means that the administrator did not specify the RDS Licensing Server and/or the licensing mode. The Remote Desktop Session Host server is within its grace period, but the Session Host server has not been configured with any license server.Īs you can see, there are no licenses available to clients, since the licensing mode is not set. Licensing mode for the Remote Desktop Session Host is not configured. Its window shows the following error: Licenses are not available for the Remote Desktop Session Host server, and RD Licensing Diagnoser has identified licensing problem for the RD Session Host server. Maybe I'm wrong but if you're licensing server is trying to hand out per-user CALs (because it detects that's what you need based on the type of login) then you need per-user CALs installed.I have already described a similar problem in the article about the RDS error “ The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license”, but the situation is a bit different here.įor more accurate diagnostic of the problem, you need to run the RD Licensing Diagnoser tool- lsdiag.msc (Administrative Tools -> Remote Desktop Services -> RD Licensing Diagnoser). After all this.does it matter? To me, I think it does. This makes sense to me based on the logic provided in the article I mentioned above, further bolstering the fact that they need per-user and not per-device CALs. It never touches the per-device CALs that are installed. When the new environment is tested, the licensing server creates this alternate per-user (what I would call "temporary") license to provide the user. They have their Citrix licensing but now they have per-device RDS CALs. Maybe a user here and there will go login from a different device but they overwhelmingly all use the same device on a daily basis.Ī new environment is being stood up which is based on XenApp with Server 2016. A typical day for a user is that they walk up to their thin client or workstation, login, do their work, log off. They don't have multiple users sharing devices. By definition, they don't meet the "per-device" scenario. Somewhere along the way their licensing renewal switched to per-device. They have per user installed in their current 2012 environment. Anyway, per-device CALs were purchased and installed and I think they need per-user. It walks you through the different license types and how licenses get checked out etc. I've researched around and the most logical and well written article I could find about licensing is here. Here's the situation.I'm pretty sure the wrong type of RDS CALs were purchased for a client of ours.
0 kommentar(er)
