Installing EventMaster Server
Click [Next] when done with this page to move to the next step
Important Note: You must install/upgrade MessageMaster Server before EventMaster Server. You need to do that first if you haven't done so already.
If you are using the EventMaster product, you will need to follow the instructions on this page to install the EventMaster server. It must be installed on the same machine as the MessageMaster server, and MessageMaster server must already be installed.
The following images and descriptions provide an explanation of each step of the EventMaster server installation process:
The Welcome dialog is presented when the installation starts. Press the Next button to continue.
Provide database administrator information. The EventMaster server installation process connects to the SQL Server database on the local machine as the SQL administrator in order to create the required tables, indexes and views in the ObjSoft database.
This dialog collects the SQL Server administrator information required to complete these tasks. This information will not be stored, or used again during the normal operation of the EventMaster server.
If you are using a named instance of SQL Server, you must specify the server name as ServerName\InstanceName.
You must specify a SQL login name that uses SQL authentication, and not a Windows username. Usually 'sa' is the one to use, unless you've set up a different SQL Administrator login.
The EventMaster server software connects to the SQL Server database during its operation. It will require a SQL Server login and password in order to do this.
Note: this user must be the same user entered when installing the MessageMaster server product.
For domain, please enter the DOWNLEVEL domain name of your domain. This is required by Microsoft COM+ technology.
Provide an Active Directory domain user identity for the EventMaster server. The EventMaster server's COM+ components run as this Active Directory user.
Note: the user provided must be the same user entered when installing the MessageMaster server product. The user does not require special privileges or group memberships.
Select the folder under which to install the EventMaster server. All Objective Software, Inc. products should be installed to the same location on any given computer. An EventMaster subdirectory will be created under the directory that you specify.
Confirm the installation in order to start copying files and complete the installation of the EventMaster server.
The progress dialog will be displayed while the installation process is proceeding. This will take a number of minutes.
At the end of the installation, the EventMaster Configuration page will open in Internet Explorer. This will allow you to configure EventMaster settings. You can return to this page from the MessageMaster Management menu at a later time.
None of these settings need to be configured at this time for the system to function.
Unless you have been analyzing event logs in your environment already, you may not have any information to input on this web page. Don't worry. As you use the system, you will no doubt identify events that are critical for your environment, or events that you wish to exclude entirely. You can return to this page at that time. For now, here is a quick overview.
Critical events. Critical events are picked up immediately by EventMaster, and sent to MessageMaster right away. If you subscribe to that event via MessageMaster (e.g. using the e-mail or MyMessages carrier), the event log message will be available to you almost immediately. Compare this with non-critical events, which are collected by EventMaster only once every interval (default is 30 minutes), and only then sent to MessageMaster.
Excluded events. The EventMaster clients running on your machines ignore excluded events. They will never be picked up, and never be sent to MessageMaster.
Unconsolidated events. When EventMaster finds that the same Event ID from the same Source occurs multiple times during one interval, it automatically consolidates them into one MessageMaster message. This one message indicates that the event was repeated n times. However, there are some events that have the same Event ID and Source, but different details in the message body. If these details are important to you, as in the case of Security events, you will want to have EventMaster unconsolidate them, and send each individual occurrence to MessageMaster as a separate message.
