Cool Solutions

Configuring a SMTP Server for Email Notifications in ZENworks



By:

July 1, 2013 4:50 pm

Reads: 1061

Comments:0

Score:0

Problem:

Configuring a SMTP Server for email notifications in ZENworks.

Overview:

You can configure a SMTP Server in ZENworks to get the email notifications.

  • Email notification when a Patch Management Server detects a new patch.
  • Scheduled (available/customized) reports to run automatically and send out email notifications to specified people.

The following sections will guide you through the detailed steps:

  • Configure the notification server
  • Import email addresses
  • email notification settings
    • Centralized Message Logging
    • Patch Management
    • Reports

Pre-requisites:

  1. SMTP Server setup is up and running. (Ex: Novell GroupWise 2012 SP1)
  2. ZENworks server is up and running.
  3. Configure the LDAP (Ex: eDir 8.8.7) in both SMTP and ZENworks servers.
  4. Both the servers are pointing to same DNS and NTP servers to resolve the host name and time synchronization.

Configure the notification server:

  • Login to ZCC as an administrator.
  • Browse through the notification servers page i.e. Configuration -> Event and Messaging -> notification servers.
  • Provide the SMTP server details (server name/address, SMTP port and authentication details if required) on the email notification section.

Import email addresses:

  1. In ZENworks Control Center, click Configuration.
  2. Click the Asset Inventory tab.

    You can configure the email addresses to send the notifications through Asset Inventory page (Configuration -> Asset Inventory -> email Addresses).

  3. In the Email Addresses Panel, click Action > Manage Email Addresses.
  4. In the Import From field, select either Inventory Data or Comma Separated File.

If you select Inventory Data, the email addresses found in an inventory scan will be imported. If you select Comma Separated File, specify the file location in the Email Address File field. Use the first name,middle name,last name,email address format to save the CSV file.

For example, if the name is Wen Zeng Hong and the email address is wzh@gmail.com, specify the file location as Wen,Zeng,Hong,wzh@gmail.com. If there is no middle name, Zeng, save the CSV file as Wen,,Hong,wzh@gmail.com.

More details available on Novell Documentation at https://www.novell.com/documentation/zenworks11/zen11_inventory/?page=/documentation/zenworks11/zen11_inventory/data/baopx2p.html#bapemub

With the above steps you configured the SMTP server details and email addresses in the ZENworks server system. Now we are going to enable / schedule the SMTP/email notifications.

Enabling email notification in Centralized Message Logging:

  1. In ZENworks Control Center, click Configuration.
  2. Click on Centralized Message Logging in Event and Messaging.
  3. Goto the email notification panel
    • Enable the check box to send the log messages through email
    • Select the severity in the drop down list.
    • Provide the required details to send the mail notification

Email notification at patch Management:

Email notifications will be sent when new patches are discovered.

  1. In ZENworks Control Center, click Configuration.
  2. Click on email notification in Patch Management.
  3. Provide required details to send the mail notification.

Email notifications for Reports:

Customized reports shared to required contacts based on the configuration.

  1. In ZENworks Control Center, click Reports.
  2. Select any report in Inventory Standard/Custom reports.

    For Ex: Taking the BIOS and System Details under Hardware Components in Inventory Custom Reports.

  3. Click on Schedule/Notification at the bottom.
  4. Provide the required details to send the mail notifications i.e. start date, frequency, output, sender, recipients etc.,

Conclusion:

This document will help ZENworks Administrator(s) to set up and configure a SMTP server for email notifications.

VN:F [1.9.22_1171]
Rating: 0.0/5 (0 votes cast)

Tags: ,
Categories: Technical, ZENworks

Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

Comment

RSS