[There's a reason that Yoda is the unofficial mascot of SBS. Size indeed matters not.] The licensing log can consume a significant amount of hard disk space - THE OFFICIAL BLOG OF THE SBS "DIVA"
Sun, Dec 14 2008 15:11 bradley

The licensing log can consume a significant amount of hard disk space

Just saw someone report that they were getting an alert on their SBS 2008 regarding licensing.

Now you know that there's no console for licesning, right?  You do need to be legal, however but the engine underneath doesn't count.

It can however get large ...therefore keep this "known issue" section bookmarked:

http://technet.microsoft.com/en-us/library/cc546071.aspx

The licensing log can consume a significant amount of hard disk space

If you receive warnings that the system drive is low on hard disk space, you can delete the events in the Windows SBS 2008 licensing log to free up additional space on the hard disk drive.

To delete events in the Windows SBS 2008 licensing log

  1. From the server, open a Command Prompt window as an administrator. To do this, click Start, and then in the Search box, type command prompt.

  2. In the list of results, right-click Command Prompt, and then click Run as administrator.

  3. At the command prompt, type the following command:

    del "%systemroot%\system32\winevt\logs\Microsoft-Windows-Server Infrastructure Licensing*%4Debug.etl.*"

You can also use Registry Editor to disable the licensing log.

CautionCaution
Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.
To disable the Windows SBS 2008 licensing log

  1. Click Start, type regedit, and then press ENTER.

  2. In Registry Editor, locate and then click the following registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ServerInfrastructureLicensing

  3. In the details pane, right-click TraceMask, and then click Modify.

  4. In the Edit DWORD dialog box, change the value for Value data to 0 (zero), and then click OK.

  5. Restart the server.

Filed under: