Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Log & Event Manager (LEM) > LEM - Knowledgebase Articles > Which user to log in for LEM console

Which user to log in for LEM console

Table of contents
Created by Tim Rush, last modified by Abdul.Aziz on May 24, 2018

Views: 1,012 Votes: 0 Revisions: 5

Updated August 30, 2016

Overview

This article provides additional assistance for log in. 

Environment

All LEM versions 

Detail

Before choosing a user to log in, there are several things to take note of:

 

  • When the LEM is first deployed, the first (and only) user to log into the LEM is "admin", and during that first log in, you will be forced to change the password to a secure password of your choice. 
  • The "admin" user is the default user for the 'web-based' GUI-console login to LEM.
  • Like Windows you cannot delete this user, but unlike Windows you cannot rename this user.
  • Also like Windows, you can login using admin whenever you want. We advise logging in with a specific user (local user or AD user) so that activity is tracked to the user.  And if a mistake was made in Monitor (filters) to make your user login unusable, you can always login with "admin" to verify access.
  • Never allow two users to login with the same user at the same time, especially the "admin" account. When using the web-based access to the LEM console, the user profile is kept on the LEM itself. Either user can corrupt the filters, and the nDepth searches created by this user. It may be possible to cause other problems as well.

 

Refer to creating new users in the LEM console:

  • Always log into the LEM with either your created local user account, or the Active Directory (AD) account.
  • The AD account will need to be all lower case characters for the fully-qualified domain and include the user (for example, microsoft.com\bill.gates). The domain name must be lower-case.

 

Always create users with the lowest permissions possible:

  • If the user only needs to receive email notifications, set the user role to 'contact'.
  • If the user only needs to view filters and rules, set the user role to 'monitor'.
  • If the user only needs to create/change filters, and only view rules, set the user role to 'auditor'.
  • If the user only needs to run reports, set the user role to 'reports'.

 

 

 

 

Last modified

Tags

Classifications

Public