Codemeter Enable Logging - Revision history

Chris Huxley: /* Turn On Logging */

2024-03-17T23:18:27Z

Turn On Logging

← Older revision		Revision as of 09:18, 18 March 2024
Line 25:		Line 25:

	If you have any further questions please get in contact with us at [mailto:support@tuflow.com support@tuflow.com].		If you have any further questions please get in contact with us at [mailto:support@tuflow.com support@tuflow.com].

	Click the following link to head back to the [[Main_Page \| Wiki Home Page]].
			<br>
			{{Tips Navigation
			\|uplink=[[Wibu_Dongles\| Return to WIBU Licensing Main Page]]
			}}

Pavlina Monhartova: /* Turn On Logging */

2019-01-14T23:44:03Z

Turn On Logging

← Older revision		Revision as of 09:44, 15 January 2019
Line 24:		Line 24:
	</ol>		</ol>

	If you have any further questions please get in contact with us at [mailto:support@tuflow.com support@tuflow.com]		If you have any further questions please get in contact with us at [mailto:support@tuflow.com support@tuflow.com].
	Click the following link to head back to the [[Main_Page \| Wiki Home Page]]		Click the following link to head back to the [[Main_Page \| Wiki Home Page]].

Mitch3007: /* Introduction */

2018-04-10T00:29:14Z

Introduction

← Older revision		Revision as of 10:29, 10 April 2018
Line 3:		Line 3:
	By default Codemeter will log events, such as when TUFLOW licenses are being used and when they are returned to the dongle. This information can be viewed both via the Codemeter events tab and within the output produced by the [[WIBU_create_cmDust \| cmDust utility]]. Both of these logs however are limited in the history of information they can provide.<br>		By default Codemeter will log events, such as when TUFLOW licenses are being used and when they are returned to the dongle. This information can be viewed both via the Codemeter events tab and within the output produced by the [[WIBU_create_cmDust \| cmDust utility]]. Both of these logs however are limited in the history of information they can provide.<br>
	This page contains instructions for enabling "Logging" in CodeMeter Control Centre. This is a useful feature that can be used to check and monitor licence allocation by CodeMeter over an extended period of time.<br>		This page contains instructions for enabling "Logging" in CodeMeter Control Centre. This is a useful feature that can be used to check and monitor licence allocation by CodeMeter over an extended period of time.<br>
	Please note that logging is compatible ~~for~~ computers with all forms of licensing.		Please note that logging is compatible on computers with all forms of licensing.

	=Turn On Logging=		=Turn On Logging=

Mitch3007: /* Introduction */

2018-04-10T00:29:00Z

Introduction

← Older revision		Revision as of 10:29, 10 April 2018
Line 3:		Line 3:
	By default Codemeter will log events, such as when TUFLOW licenses are being used and when they are returned to the dongle. This information can be viewed both via the Codemeter events tab and within the output produced by the [[WIBU_create_cmDust \| cmDust utility]]. Both of these logs however are limited in the history of information they can provide.<br>		By default Codemeter will log events, such as when TUFLOW licenses are being used and when they are returned to the dongle. This information can be viewed both via the Codemeter events tab and within the output produced by the [[WIBU_create_cmDust \| cmDust utility]]. Both of these logs however are limited in the history of information they can provide.<br>
	This page contains instructions for enabling "Logging" in CodeMeter Control Centre. This is a useful feature that can be used to check and monitor licence allocation by CodeMeter over an extended period of time.<br>		This page contains instructions for enabling "Logging" in CodeMeter Control Centre. This is a useful feature that can be used to check and monitor licence allocation by CodeMeter over an extended period of time.<br>
	Please note that logging is compatible for computers with ~~Local~~ ~~Only, Network Only and a combination~~ of ~~Local and Network Licensing enabled~~.		Please note that logging is compatible for computers with all forms of licensing.


	=Turn On Logging=		=Turn On Logging=

Mitch3007 at 00:28, 10 April 2018

2018-04-10T00:28:26Z

← Older revision		Revision as of 10:28, 10 April 2018
Line 3:		Line 3:
	By default Codemeter will log events, such as when TUFLOW licenses are being used and when they are returned to the dongle. This information can be viewed both via the Codemeter events tab and within the output produced by the [[WIBU_create_cmDust \| cmDust utility]]. Both of these logs however are limited in the history of information they can provide.<br>		By default Codemeter will log events, such as when TUFLOW licenses are being used and when they are returned to the dongle. This information can be viewed both via the Codemeter events tab and within the output produced by the [[WIBU_create_cmDust \| cmDust utility]]. Both of these logs however are limited in the history of information they can provide.<br>
	This page contains instructions for enabling "Logging" in CodeMeter Control Centre. This is a useful feature that can be used to check and monitor licence allocation by CodeMeter over an extended period of time.<br>		This page contains instructions for enabling "Logging" in CodeMeter Control Centre. This is a useful feature that can be used to check and monitor licence allocation by CodeMeter over an extended period of time.<br>
		⚫	Please note that logging is compatible for computers with Local Only, Network Only and a combination of Local and Network Licensing enabled.


	=Turn On Logging=		=Turn On Logging=
Line 21:		Line 23:
	[[File:Codemeter_Enable_Logging_02.png\|800px]]		[[File:Codemeter_Enable_Logging_02.png\|800px]]
	<br><br>		<br><br>
⚫	Please note that logging is compatible for computers with Local Only, Network Only and a combination of Local and Network Licensing enabled.
	<br>
	</ol>		</ol>

Mitch3007: /* Introduction */

2018-04-10T00:27:49Z

Introduction

← Older revision		Revision as of 10:27, 10 April 2018
Line 2:		Line 2:

	By default Codemeter will log events, such as when TUFLOW licenses are being used and when they are returned to the dongle. This information can be viewed both via the Codemeter events tab and within the output produced by the [[WIBU_create_cmDust \| cmDust utility]]. Both of these logs however are limited in the history of information they can provide.<br>		By default Codemeter will log events, such as when TUFLOW licenses are being used and when they are returned to the dongle. This information can be viewed both via the Codemeter events tab and within the output produced by the [[WIBU_create_cmDust \| cmDust utility]]. Both of these logs however are limited in the history of information they can provide.<br>
	This page contains instructions for enabling "Logging" in CodeMeter Control Centre. ~~These~~ ~~are~~ useful ~~functionalities~~ that can be used to check and monitor ~~the~~ licence allocation by CodeMeter over an extended period of time.<br>		This page contains instructions for enabling "Logging" in CodeMeter Control Centre. This is a useful feature that can be used to check and monitor licence allocation by CodeMeter over an extended period of time.<br>

	=Turn On Logging=		=Turn On Logging=

Mitch3007: /* Introduction */

2018-04-10T00:24:50Z

Introduction

← Older revision		Revision as of 10:24, 10 April 2018
Line 2:		Line 2:

	By default Codemeter will log events, such as when TUFLOW licenses are being used and when they are returned to the dongle. This information can be viewed both via the Codemeter events tab and within the output produced by the [[WIBU_create_cmDust \| cmDust utility]]. Both of these logs however are limited in the history of information they can provide.<br>		By default Codemeter will log events, such as when TUFLOW licenses are being used and when they are returned to the dongle. This information can be viewed both via the Codemeter events tab and within the output produced by the [[WIBU_create_cmDust \| cmDust utility]]. Both of these logs however are limited in the history of information they can provide.<br>
	This page contains instructions for enabling "Logging~~" and "License Tracking~~" in CodeMeter Control Centre. These are useful functionalities that can be used to check and monitor the licence allocation by CodeMeter over an extended period of time.<br>		This page contains instructions for enabling "Logging" in CodeMeter Control Centre. These are useful functionalities that can be used to check and monitor the licence allocation by CodeMeter over an extended period of time.<br>

	=Turn On Logging=		=Turn On Logging=

Mitch3007 at 00:17, 10 April 2018

2018-04-10T00:17:10Z

← Older revision		Revision as of 10:17, 10 April 2018
Line 25:		Line 25:
	</ol>		</ol>

	~~By using these handy tools we hope it helps you to better understand your network license usage and assists license usage debugging.~~ If you have any further questions please get in contact with us at [mailto:support@tuflow.com support@tuflow.com]		If you have any further questions please get in contact with us at [mailto:support@tuflow.com support@tuflow.com]
	Click the following link to head back to the [[Main_Page \| Wiki Home Page]]		Click the following link to head back to the [[Main_Page \| Wiki Home Page]]
	</ol>

Mitch3007: /* Turn On Licence Tracking for a Network Server */

2018-04-10T00:10:54Z

Turn On Licence Tracking for a Network Server

@@ Line 25: / Line 25: @@
 </ol>
 By using these handy tools we hope it helps you to better understand your network license usage and assists license usage debugging. If you have any further questions please get in contact with us at [mailto:support@tuflow.com support@tuflow.com]
 Click the following link to head back to the [[Main_Page | Wiki Home Page]]

Mitch3007: /* Turn On Licence Tracking for a Network Server */

2018-04-10T00:10:06Z

Turn On Licence Tracking for a Network Server

← Older revision		Revision as of 10:10, 10 April 2018
Line 26:		Line 26:

	=Turn On Licence Tracking for a Network Server=		=Turn On Licence Tracking for a Network Server=
			<ol>
	Please note that License Tracking is only compatible with Network Licensing. i.e. for License Tracking to work you will need to have a valid TUFLOW Network License and Codemeter also needs to be [[WIBU_Configure_Network_Server_2016\| Server configured]].<br>		Please note that License Tracking is only compatible with Network Licensing. i.e. for License Tracking to work you will need to have a valid TUFLOW Network License and Codemeter also needs to be [[WIBU_Configure_Network_Server_2016\| Server configured]].<br>
	To turn on license tracking you need to update a variable within the Windows Registry. <br>		To turn on license tracking you need to update a variable within the Windows Registry. <br>
Line 53:		Line 54:
	By using these handy tools we hope it helps you to better understand your network license usage and assists license usage debugging. If you have any further questions please get in contact with us at [mailto:support@tuflow.com support@tuflow.com]		By using these handy tools we hope it helps you to better understand your network license usage and assists license usage debugging. If you have any further questions please get in contact with us at [mailto:support@tuflow.com support@tuflow.com]
	Click the following link to head back to the [[Main_Page \| Wiki Home Page]]		Click the following link to head back to the [[Main_Page \| Wiki Home Page]]
			</ol>