Had to Rebuild TS Server - Now Can't Log On
in [Terminal Services]
|
Prev: Terminal Servers in Cluster - Login/Profile Issues - Please Help!
Next: TS 2003 - Publish Application Options
From: SCAdmin on 7 Apr 2010 10:59 Our terminal services licensing server crashed. I activated TS licensing on a new server, and called Microsoft clearinghouse to complete the activation. The new TS License server is called: TSL-Server. When I log into the TSL snap-in, TSL-Server is listed beneath "All Servers." In the right window pane, this is what I see: Existing Windows 2000 Server - Terminal .....Total = Unlimited. Available = Unlimited. Issued = 2 Temporary Licenses for Windows 2000 Server .... Total = -. Available = -. Issued = 1 Temporary Licenses for Windows Server 2003 Terminal Server Per Device CAL Token. Total = -. Available = -. Issued = 9. Windows Server 2003 - TS Per User CAL Type = Volume License. Total = 65. Available = 65. Issued = 0. Today, when I tried to log into another machine using RDP, I got an error that "the remote session was disconnected because there are no remote desktop client access licenses ...." Looking at the above info, I'm guessing that somewhere I went wrong and selected Per Device instead of Per User. If so, is there any way to fix that? If that is not the problem, can anyone help me figure out what's going on? Thanks
From: Vera Noest on 11 Apr 2010 14:33
"SCAdmin" <scadmin(a)SysCorpDotNet.net> wrote on 07 apr 2010 in microsoft.public.windows.terminal_services: > Our terminal services licensing server crashed. I activated TS > licensing on a new server, and called Microsoft clearinghouse to > complete the activation. > > The new TS License server is called: TSL-Server. When I log > into the TSL snap-in, TSL-Server is listed beneath "All > Servers." > > In the right window pane, this is what I see: > > Existing Windows 2000 Server - Terminal .....Total = Unlimited. > Available = Unlimited. Issued = 2 > Temporary Licenses for Windows 2000 Server .... Total = -. > Available = -. Issued = 1 > Temporary Licenses for Windows Server 2003 Terminal Server Per > Device CAL Token. Total = -. Available = -. Issued = 9. > Windows Server 2003 - TS Per User CAL Type = Volume License. > Total = 65. Available = 65. Issued = 0. > > > Today, when I tried to log into another machine using RDP, I got > an error that "the remote session was disconnected because there > are no remote desktop client access licenses ...." > > Looking at the above info, I'm guessing that somewhere I went > wrong and selected Per Device instead of Per User. If so, is > there any way to fix that? > > If that is not the problem, can anyone help me figure out what's > going on? > > Thanks You seem to have installed 65 Per User licenses, so you have to make sure that the Terminal Server is also using the Per User licensing mode. This is done in tscc.msc. Note that W2K Terminal Servers cannot use Per User licenses, they can only use Per Device licenses. So if you really ment to install the licenses as Per Device, rather than Per user, you will have to call the Clearinghouse and ask them to reissue your licenses and then install them as Per device licenses. _______________________ Vera Noest Remote Desktop Services troubleshooting http://ts.veranoest.net |