Terminal Server has license logging error after replacement of PDC running license service?

I replaced our PDC which was running Server 2000 with a new machine runnign Server 2003.  All services were installed and configured including the license service.

After the replacement our terminal server which is running Server 2000 ad is a member server started throwing the Event ID 213:  replication of license information failed because license logging service on \\******* could not be contacted in the event logs.

This is the only server throwing this error.

I have veriffied that the new server is listed as the license logging server in Sites and Services in AD.

I have verified that the licensing logging service is running on the PDC.

I have verified that the terminal server can connect to the PDC.

What changes can I make to correct this issue or is it OK to disable the license logging service on the terminal server?

Thanks!
kxcrazyAsked:
Who is Participating?
 
oBdAConnect With a Mentor Commented:
The following link includes a method to reset the license information, but you can do yourself a favor and simply disable the license logging service on all servers (unless this is an SBS domain).
The LLS isn't really doing what it was designed/supposed to do, and Microsoft says that it can be safely disabled in most environments (it is disabled by default in W2k3 and not included anymore in W2k8). Check here for details:
Description of the License Logging Service in Windows Server operating systems
http://support.microsoft.com/kb/824196
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.