Event 202 - Server Out of Licences Errors

[John French]

At work, we have a main facility (4 Domain Controllers - Win2000 AD) and 4
remote sites (1 Domain Controller each - Win2000 AD) connected back to the
main site via T1's. All servers were in the DefaultFirstSite in AD Sites
and Services. Last week I created a separate site / IP link / subnet for
each remote site and moved the appropriate DC from the default site into its
appropriate site. I am now getting Event 202 (This server is out of
licenses) errors on all the DC's in the remote sites (They are also the Site
Licensing Servers). The main site has 560 CALS and every server in all
sites is set for Per Seat Licensing. I'm not understanding how the
licensing replication truely works, obviously. Do I need to add per seat
CALs to each site and remove some from the main site... or do the site
licensing servers receive replication from the Licensing server in the main
site? I'd rather not point each site licensing server back to the main site
for bandwith reasons, unless necessary. If someone can explain in detail
how this works, I'd be very greatful.

 

[Lanwench [MVP - Exchange]]

The true answer - license logging just plain don't work right. Stop/disable
the service, and keep track of your licenses manually.

 

[John French]

What will happen if the DC also runs SQL server and/or Exchange server and
you disable License Logging? Would disableing the service ever create a
user lockout situation due to lack of licenses?


"Lanwench [MVP - Exchange]"

 

[Lanwench [MVP - Exchange]]

No - if you disable the service, you're considered to be in "per seat" mode,
and things will still run. Exchange, SQL, whatnot. The license logging
service isn't mandatory.