Microsoft
Software
Hardware
Network
Question : Windows licensing logging service
I am having an issue with windows licensing logging service. My boss believes that it is required for terminal service licensing to work properly. I know and my team knows that the two are not connected, however she will not let us continue with are terminal server project until I resolve the issue with LLS. grrrr.
So the issue with LLS is between a few select servers the logging information is not being replicated. Other servers are replicating this information correctly.
Some background:
I think they had LLS running before, my company merged with another, they built a new dc and demoted a few others. The server that was handling the lls was a dc which got demoted and dismantled, the IT manager quit, I got hired and stuck with many issues.
What I have already done:
1) ensured the correct server was listed as the licensing server in AD sites and services.
2) ensured the servers can communicate with each other. (no simply network communication error)
3) restarted the licensing logging service on servers in the enterprise. Microsoft kb article 194065
We have a mixed enviroment. 2000 servers are sp4, 2003 servers are r2, sp1 and sp2. DCs are 2003. No servers are SBS.
So any help with LLS and suggestions on how to get LLS to replicate would be welcomed.
Thanks
~Weasel
Answer : Windows licensing logging service
Both articles clearly state that the LLS is not necessary, disabled by default, and discontinued, and that isn't proof enough?
Oh well; whatever. Make sure that ...
- The license server in AD Sites and Services is the PDC emulator as well; if not, move the licensing to the PDC emulator.
- All servers are configured to use "Per Seat" licensing (not "Per Server", those will not take part in replication anyway; come to think of it: IIRC, back in NT4 days, it were only DCs that actually replicated the LLS information anyway).
- After this is done, eradicate the current license information on all servers as described in the 883399 article; stop the LLS first on all servers, recreate the information on all servers, only then start the LLS on all servers again (or just forget about the restarting ...)
Random Solutions
LDAP Query help
total of user accounts in active directory
Need information on Long Integer, Integer, Byte, Single, Double, Replication ID, etc.
Using Tasks in Outlook as with update list
Email Button In Access
EPSON LQ-300 II
fetchrow_array() no print
DBase IV and Unexpected Error
Unable to uninstall a program
Animated horizontal pop-out menu or Slide-out menu...