Problem with T-Server User CAL Win 2003 SP1
in [Terminal Services]
|
Prev: Profile Issues
Next: Pass credentials to Gateway Login
From: Eberhard Wagner on 21 Apr 2008 08:24 Hi All, I don't get the Terminal Server User Cals working. There is still the balloon "Cannot find Windows 2003 Terminal Server License Server". Installing the License was without any error, no error in eventlog, I restartet the Service "Terminal Service License". In the window "Terminal Server Licensing" the Server is activated, in Product: "Windows Server 2003 - Terminal Server Per User CAL Token", Type: "Open", Total and Available: "5", Issued: "Not Applicable", which seems to be ok in Server 2003 SP1. Under Terminal Services Configuration- Server Settings is Licensing "Per User", Server discovery: Automatic and discovered under Domain/Workgroup role. Any suggestions, why still there is the warning ? Thanks in advance, Eberhard
From: Vera Noest [MVP] on 21 Apr 2008 17:33 If the Licensing Services runs on the same server as the TS and it isn't a DC, then you have to point the TS to itself, in tscc-msc - server settings - licensing server discovery. _________________________________________________________ Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server TS troubleshooting: http://ts.veranoest.net ___ please respond in newsgroup, NOT by private email ___ "Eberhard Wagner" <2725-7001(a)centermail.com> wrote on 21 apr 2008 in microsoft.public.windows.terminal_services: > Hi All, > > I don't get the Terminal Server User Cals working. There is > still the balloon "Cannot find Windows 2003 Terminal Server > License Server". Installing the License was without any error, > no error in eventlog, I restartet the Service "Terminal Service > License". In the window "Terminal Server Licensing" the Server > is activated, in Product: "Windows Server 2003 - Terminal Server > Per User CAL Token", Type: "Open", Total and Available: "5", > Issued: "Not Applicable", which seems to be ok in Server 2003 > SP1. > > Under Terminal Services Configuration- Server Settings is > Licensing "Per User", Server discovery: Automatic and discovered > under Domain/Workgroup role. > > Any suggestions, why still there is the warning ? > > Thanks in advance, > > Eberhard
From: Eberhard Wagner on 22 Apr 2008 04:05 "> If the Licensing Services runs on the same server as the TS and it > isn't a DC, then you have to point the TS to itself, in tscc-msc - > server settings - licensing server discovery. Licensing Service runs on the same server as TS and it is configured as DC, but stands allone. in tscc -> licensing server discovery mode -> <check> use these licence servers (Pointing to itself). When I press the button "Check names" it says "The specified License Servers are valid Windows Server 2003 Terminal Server License Servers" So everything seems to be ok. I used als0 the "lsview" from the resource kit, it shows the License server as type domain, everything seems also ok. But still the balloon pops up "Cannot find Windows 2003 license server". I have read, that user CALs are making sometimes problems. Is it a good idea to set the registry entry "LicensingGracePeriodEnded" to 0 , that the popup no longer exist? BR Eberhard
From: Vera Noest [MVP] on 22 Apr 2008 15:06 If the TS cannot locate the LS, then the type of TS CALs don't play a role. What do you mean with "it is configured as DC, but stands allone"? Either it's a DC, and then it is part of a domain, or it is a standalone server in a workgroup. It can't be both. Are you logged on with a Domain Admin account? _________________________________________________________ Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server TS troubleshooting: http://ts.veranoest.net ___ please respond in newsgroup, NOT by private email ___ "Eberhard Wagner" <2725-7001(a)centermail.com> wrote on 22 apr 2008 in microsoft.public.windows.terminal_services: > "> If the Licensing Services runs on the same server as the TS > and it >> isn't a DC, then you have to point the TS to itself, in >> tscc-msc - server settings - licensing server discovery. > > > Licensing Service runs on the same server as TS and it is > configured as DC, but stands allone. > in tscc -> licensing server discovery mode -> <check> use these > licence servers (Pointing to itself). > When I press the button "Check names" it says "The specified > License Servers are valid Windows Server 2003 Terminal Server > License Servers" So everything seems to be ok. > I used als0 the "lsview" from the resource kit, it shows the > License server as type domain, everything seems also ok. > > But still the balloon pops up "Cannot find Windows 2003 license > server". I have read, that user CALs are making sometimes > problems. Is it a good idea to set the registry entry > "LicensingGracePeriodEnded" to 0 , that the popup no longer > exist? > > BR > Eberhard
From: Eberhard Wagner on 23 Apr 2008 05:01
Hello, thanks for the answer. > If the TS cannot locate the LS, then the type of TS CALs don't play > a role. What is the solution? It seams everything right configured with the LS. LS is activated, "Terminal Server Licensing" shows the 5 user CALs, in tscc - Server Settings is the Licensing "Per User" and in License server discovery it recognize the LS if you press the button "Check names". Other programs like "License Server Viewer" recognize it. It's just the warning baloon, which says time ist running. It shouldn't be that difficult to install just a license? > What do you mean with "it is configured as DC, but stands allone"? > Either it's a DC, and then it is part of a domain, or it is a > standalone server in a workgroup. It can't be both. I mean, as I can see, it is created as the first windows server 2003 domain controller in a domain, but it is running in the moment only as a VPN Server for SAP applications and Terminal Server, in the moment just for administration. No other computers in the domain. No dependencies to other computers. Just a simple configuration. In System Properties: <computername>.<domainname>.local. > Are you logged on with a Domain Admin account? I'm logged on with the administrator account, that should fit it. BR Eberhard |