Event id: 1010

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Please help,
I just installed Windows 2000 domain last week. I have 4 DCs and 1 of the dc is acting as Terminal Services License Server.
I installed Windows 2000 Server member server as application server and from day 1, i'm getting evernt id: 1010.
I installed licenses and activate the server already. I don't think I have license issue nor License service issue. I already tried Q239107--- hardcoding preferred TS license Server but it didn't not make any difference. It kept saying can't find license server. I do not have networking issues.

Description of the problem
The terminal services could not locate a license server. Confirm that all license servers on the network are registered in WINS\DNS, accepting network requests, and the Terminal Services Licensing Service is running.

Thanks,
 
When you hardcoded the name of the license server into the
registry of the terminal server, did you use the NetBIOS
name, IP address, FQDN, etc?

Some people have reported that even though they use the
DNS name, the terminal server still can't resolve the
license server. They were then forced to use the IP
address.

-M
-----Original Message-----
Please help,
I just installed Windows 2000 domain last week. I have 4
DCs and 1 of the dc is acting as Terminal Services License
Server.
I installed Windows 2000 Server member server as
application server and from day 1, i'm getting evernt id:
1010.
I installed licenses and activate the server already. I
don't think I have license issue nor License service
issue. I already tried Q239107--- hardcoding preferred TS
license Server but it didn't not make any difference. It
kept saying can't find license server. I do not have
networking issues.
Description of the problem
The terminal services could not locate a license server.
Confirm that all license servers on the network are
registered in WINS\DNS, accepting network requests, and
the Terminal Services Licensing Service is running.
 
Thank you so much for your reply.
Right after I posted my question, I found that when I hardcoded ip address
in the DefaultLicenseServer, it seems TS Server found the
License Server. But since both servers are in same subnet and same domain,
aren't they supposed to see each other?
 
Yes, the TS should be able to locate the LS if on the same subnet
and domain and the LS is on a DC.
Note that Event 1010 can persist after you have hardcoded the LS
into the TS, sinve the registry entry overrides the standard
discovery process. As long as EventID 1010 is the only EventID you
get, and you do *not* see EventID 1004 "Cannot issue a client
license", then your clients should receive a TS CAL. You can also
verify this in License Manager.

281258 - Event 1010 Is Reported After Specifying Default License
Server
http://support.microsoft.com/?kbid=281258

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---
 
OK, I'm almost getting it.
I've already got below informations but what i'm trying to do is why
Terminal Server did not automatically discover the License Server?
Is there tool that I can use to troubleshoot this? What I'm suspecting is,
there might be bad installation somewhere.
If this problem is normal than i'm not going to worry about it but if it's
not I would like to know why...

Thank you,
 
Yes, that puzzled me as well. One thing that I can think of is
that something is missing in your WINS/DNS, which prevents the TS
from automatically discovering your LS.

The Terminal Services Licensing Server object is stored in the
Configuration container of the AD. This container is replicated to
every domain controller in the forest.

The distinguished name (DN) for the object is:
LDAP://CN=TS-Enterprise-License-Server,CN=site-
name,CN=sites,configuration-container

Could you have a replication problem between your DCs?
 
I think I fixed the problem, i'm not getting Event id: 1010 in the system
log anymore.
Here's what I did about a week ago. I removed "Authenticated Users" read
permissoin from all the OUs in the AD users and computers MMC.
I was tightening the security of the OUs so Account Operators can only see
what they supposed to see to do their job. After I made the change, I did
not see any problem in the Active Directory nor network operation but I
started seeing Event ID: 1010 in the Terminal Server's system log... I
think. Anyway, after researching and testing, I enabled "Authenticated
Users' read permission in the all the OU security and it's not generating
that event anymore. I don't know why it's acting that way but giving read
permission to authenticated users was fix to my problem.

** If I'm not seeing event id: 1010, my TS is communicating with TS license
server right?

Thank you much for your ideas and help.
 
Aah, that makes sense! I'm not exactly sure under which user
context the TS does a lookup for the LS, but if security on the
Configuration OU is to tight, this process might fail.

And yes, the absense of eventid 1010 should mean that the TS can
locate the LS. I would keep an eye on the TS Licensing Manager,
though, to verify that your clients are really getting their
licenses.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---
 
hmm does win2k and xp clients still need to get a license from TS? I
thought if the clients are win2k and xp, they don't need to get a license
from the license Server. If I only have win2k and xp clients, I only need
to activate the server right!
 
*All* clients need a TS CAL, but W2K Pro and XP Pro clients will
get a free TS CAL from the Licensing server. If you have a look at
the Licensing Manager, you will see an entry called something like
"Existing Window 2000 licenses" Type: Built-in, Available:
Unlimited. Those licenses will be issued to W2K and XP Pro
clients.

And yes, the only thing you have to do is to install and activate
the TS Licensing Service.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---
 
Back
Top