If you look in the AD Delegation document http://www.microsoft.com/downloads/details.aspx?FamilyID=631747a3-79e1-48fa-9730-dae7c0a1d6d3&DisplayLang=en it shows the adminsdholder has permissions defined for the terminal server license servers group. Its allowed to view a terminalserver attribute that is defined on the user object and hence inherited by other classes based on it such as computer. I am not aware of the importance of the terminalserver attribute. But judging by the msdn explanation it looks like something maintained for backwards compatibility.
I cant view the site right now as Its blocked by my corp's net nanny software as an adults only site. Go figure! But I remember it said something about "opaqe data" and Windows NT.
I cannot see any harm with adding your license servers to the group. But then check with others before doing and test in a lab to see if there are any known issues.
Might want to read http://support.microsoft.com/kb/895151/en-us as well.
If you want some good details on terminal server licensing please refer to this doc http://www.microsoft.com/windowsserver2003/techinfo/overview/termservlic.mspx here.
I have a domain based TS License server and it shows up just fine in lsview if launched from a machine in the same site as the license server. If launched from a different site I get the same results as yours. Green with no server names. I enabled the log file and configured lsview to check for a license server every 1 minute and all its logged is checking the local machine to see if its a domain license server. Its not so it failed. No messages about been able to find the correct domain license server.
If I do this on a machine in the same site as my domain license server, it immediately logs the fact that it found it.
I dont have any enterprise license servers to test with so can't comment. I also havent done any network traces either so I am not sure if it is indeed doing the license server discovery as a normal TS Client would at logon time. Might do later if I get the time.
Regards
M@
Hi Freddy,
Thanks for the feedback. But I get the same result from the W2K lsview.exe . And this is running these tools right on the license server/domain controller! I am thinking that I need to manually populate the AD group "Terminal Server Licensing Servers". Conversely, I hate making changes when there are no known problems.
Mike Thommes
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Freddy HARTONO
Sent: Sunday, August 06, 2006 11:34 AMSubject: RE: [ActiveDir] OT: Enterprise Terminal Server Licensing Server question
Hi Mike
I had the same problems in which I actually logged a pss call on, try using the windows 2000 resource kit version of lsview.exe and it works fine.
Basically if i remember this correctly using the win2003 lsview.exe it will only detect it if your machine is in the same site as the tsls server, if you are running the lsview on a machine that is outside the site, it wouldnt detect it.
No solution, fedup with the answers I was getting - closed the ticket (as I thought this only occurs in my ex company, apparently now im getting the same result as well)
Thank you and have a splendid day!
Kind Regards,
Freddy Hartono
Group Support Engineer
InternationalSOS Pte Ltd
mail: [EMAIL PROTECTED]
phone: (+65) 6330-9785
From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED]] On Behalf Of Thommes, Michael M.
Sent: Saturday, August 05, 2006 5:04 AM
To: [email protected]
Subject: [ActiveDir] OT: Enterprise Terminal Server Licensing Server questionHi,
This is not causing any issues that I am aware of, but something does not seem right. We set up two Enterprise Terminal Server Licensing Servers, both DCs. They are both identified in CN=TS-Enterprise-License-Server,CN=site-name,CN=Sites,CN=Configuration,DC=something,DC=com under the attribute "siteServer". When I run the GUI "LSVIEW.EXE" from the W2K3 ResKit, nothing populates but the spotlight icon shows "green" (ie, everything is hunky-dory). Some more research shows that the AD group "Terminal Server License Servers" has *no* members! Would it make sense to populate this group with the appropriate servers? Any idea why it wouldn't have been populated in the first place?
TIA,
Mike Thommes
