![]() |
||||||||||||||||||||||
Get up to speed faster with on-line Video Tutorials of ELM today! We Offer a Looking for budget numbers to add-on or get started? Contact an Account Manager today We offer live, on-demand product demonstrations for automated log management and server monitoring! Chat live with our Account Managers! Affordable Training and Configuration Assistance for ELM.
Dates to Remember May 8 May 21 May 30
|
With the powerful event filtering capabilities in ELM for collection, Event Views, Notifications and Reporting, our market research indicated that this enormous amount of flexibility sometimes led to a disconnect between seeing an event and configuring ELM to send a Notification on that event occurring. Our product management and development teams were put to the test to come up with a more streamlined way for ELM users to setup Notifications based on what they are seeing in the ELM Console. The previous method for creating a Notification was based on three building blocks.
Working with Event Filters is very straightforward. Setting up different Notification Method types is pretty easy as well; the potential for confusion appeared to come about when trying to establish Notification Rules to tie these two together. If you don't work with them on regular basis, remembering the process was not intuitive enough. In ELM Enterprise Manager 6.5, we've taken a new approach to setting up Notification Methods based on Event Views to streamline and simplify setting up Notifications. The basic premise is "What You See is What You Get" and Notification Rules have gone away.
Stay tuned for future updates on other new features and enhancements coming in ELM Enterprise Manager 6.5 - scheduled for release later this year!
|
|||||||||||||||||||||
Last month we mentioned living in a world of checks and balances. Full of policies, procedures and proof that we're following the rules and maintaining security. With that in mind, we got to wondering... "What compliance mandates are you required to adhere to?" As of the publishing of this newsletter, here's what respondents had to say.
Regardless of your industry or the rules you must follow, this chart shows that compliance requirements are strong across the board.
|
||||||||||||||||||||||
|
If you are wondering about the latest product offerings and where your upgrade path leads, please do not hesitate to contact our Sales or Support departments. (ELM Version 5.5 products will continue to be supported)
|
||||||||||||||||||||||
|
We first asked about this in 2009. Revisited it in 2010. It's back again! Here we are in 2011 and it's time to see what's changed with our reader's use of smart phones for administrative tasks.
Be sure to vote and next month we'll compare results from 2009, 2010, and 2011!
|
||||||||||||||||||||||
Admins everywhere use scripts and batch files to quickly and accurately automate mundane or routine tasks. Under normal circumstances all goes well and these little babies are real time savers. However sometimes "stuff happens" and not all goes as planned. So how do you know or how can you find out when things don't go as planned? Sometimes it will be very obvious that something is broken. Sometimes it isn't. Using ELM together with a batch file you can confidently move forward knowing what worked and what didn't. Here's how... Take the scenario where you have 50 workstations spread across your facility and you need to push out an application install. Using a batch file you can accomplish this fairly easily (for example using Group Policy). But how do you know if all of the installations were successful? By adding a simple script to the end of your batch file, you can have it create a custom event. For example:
In the EventCreate command:
So now once the batch file is executed it will generate a custom event on that workstation with the parameters which you have specified. Within ELM you would create a new Event View with a Filter that includes the parameters to look for this custom event. If the View shows 50 events, then you know the batch install was a success. If you see less than 50 you know there is a problem and can sort by Computer or another field and quickly track down which one is missing.
Okay, but what if we're talking about 500 instead of 50 workstations? In a situation like this you could go more advanced and setup an Event Alarm monitoring item for Event Not Found.
After walking through setup, we assign this monitor item to the Windows--Workstations category and you are ready to go.
If the batch runs successfully it will create the custom event; the Event Alarm will find it and stay quiet. If the batch file is unsuccessful on a particular machine however, the Event Alarm will not find the custom event, and be triggered to perform the Action you assigned. You could then setup a notification from this if you so desire. Creation of custom events within batch files and scripts along with the monitoring of ELM can not only simply those mundane tasks but also confirm that everything worked as planned. For more details on the EventCreate utility, visit http://support.microsoft.com/kb/324145. We hope that you found this article informative and wish you continued success with your ELM deployment! NOTE: All ELM 411 articles are written based on ELM Enterprise Manager Version 6.0 and instructions may not be accurate for previous ELM Versions. If you would like assistance upgrading to ELM 6.0 so you can use these tips - please contact support@tntsoftware.com. Share your own ELM tips!
|
||||||||||||||||||||||
Getting this sent to you by someone else? Sign up to receive our monthly email newsletter here. |
||||||||||||||||||||||