OnLAN Messenger Administrator Manual - Modifying the database

OnLAN Messenger Administrator Manual

Introduction Contents and system requirements Terminology Installation and setup
	Loading the server Setting up the OnLAN Monitor module Setting up the OnLAN Server module
		License activation Setting the database file path Saving data to the database Setting up the main parameters
	Loading the client Client setup Advanced setup
		Choosing the network interface Registering debug information
Management tools
	Managing the OnLAN Server Managing the OnLAN Messenger
		Control console
		Testing the server Testing the client Managing online users Modifying the database
			Modifying group policies Modifying standard groups Modifying user registration data Using Microsoft Access to manage the database
		Authorizing new contact creation Managing active http-sessions Audit tools
			Managing logs
				Event log Command history Message history Unsent message log Unsent message status log
	Managing data through the web-interface
Updating and deleting
	Updating OnLAN Messenger
		Refreshing the license Updating the server version Updating the client version
	Deleting OnLAN Messenger
		Deleting the client Deleting client groups Deleting the server
Appendix
	Event log-files Codes in use Ports in use Group policy keys

Modifying the database

This chapter covers two methods of modifying the data contained in the OnLAN Messenger database, one of which is the manual alteration of the data in the tables by means of the OnLAN Messenger, and the other is using MS Access to modify data (not recommended).

Note that the OnLAN Messenger service supports the additional option of importing data from other sources, which makes entering and refreshing the employee data more efficient. This option becomes available through additional OnLAN DBSync software, currently in development by "Corp Soft", which can be downloaded for free from our site (www.corpsoft.org).

Modifying group policies
Modifying standard groups
Modifying user registration data
Using Microsoft Access to manage the database

Back Next