In order for your logging module to be available through the IIS administrative user interface, you should add it to the /LM/LOGGING path of the metabase. You should give the key the same name as the custom logging module, and it should contain two values: MD_LOG_PLUGIN_MOD_ID and MD_LOG_PLUGIN_UI_ID. MD_LOG_PLUGIN_MOD_ID should contain a string that represents the custom module's GUID, and MD_LOG_PLUGIN_UI_ID should contain a string that represents the GUID of the custom module's user interface.
If you use a script to add a logging module to the /LM/LOGGING path, you should add the GUID for the log module to the LogModuleList automation property.
For more information on using scripts to administer IIS, see Using the IIS Admin Objects.
Note The logging module must be resident on the server machine; it does not need to be resident on the administrator machine. The custom user interface module, on the other hand, must be on the administrator machine, but does not need to be on the server machine (although its GUID does need to be in the metabase as described above).