At a high level, these steps are as follows:
Install and configure Dell OpenManageÃ¢ÂÂ¢ Essentials, including device discovery.
Configure Service queue in KACE
Create an E-mail Alert action in OME
Test E-mail Alert action in OME
Install and Configure Dell OpenManageÃ¢ÂÂ¢ Essentials.
Dell OpenManageÃ¢ÂÂ¢ Essentials is a Windows-based systems management console that replaces Dell IT Assistant. A physical or virtual server running Windows Server 2008 will be required to run OME. This installation is quite simple and largely self-contained. The one exception is if you plan to manage a large environment. OME includes Microsoft SQL Server Express for small deployments, but supports use of Microsoft SQL Server Enterprise if you plan to manage a larger deployment. The software may be downloaded here. YouÃ¢ÂÂll find installation instructions and other documentation here.
Once you have OME installed, launch the OME console and select Manage -> Discovery and Inventory.
In the left pane, select Discovery Ranges-> Add Discovery Ranges to define an IP range for discovering your servers.
Enter the IP address / range or a list of DNS hostnames for the machines you want to monitor and click [Finish].
Configure Service desk and Service queue in KACE
The next step is to create your K1000 service desk queue so it can receive emails from OME. WeÃ¢ÂÂll set this up before configuring the email alert in OME since we need the email address for the service desk queue to complete the OME configuration. To simplify this task you can download a sample queue as a kpkg here and upload it to your K1000 as follows:
Connect to the clientdrop network share on your K1000. On Windows, do this by going to \\< your K1000 host >\clientdrop and logging into the share using the password you have configured for the share within the K1000.
Copy the downloaded Queue-110.kpkg file to you clientdrop share.
Log into your K1000 and go to Settings-> Resources-> Import K1000 Resources.
From the dropdown on the left, select Choose Action ->Import Resources(s) from SAMBA Share.
Pick Queue-110.kpkg from the list of files and select [Import Resources].
YouÃ¢ÂÂll now see a Queue resource listed called OME that is imported into your K1000.
Now go to Service Desk-> Configuration-> Queues. YouÃ¢ÂÂll see the OME queue listed there. Select the queue by clicking on the name.
Note the email address of the queue. This is the email address that will be recognized within the K1000 as the queue to receive email tickets from OME. If you wish to use a different email address that is externally defined in your email environment, and then forwarded to this address, you may specify that in the Alt. Email Address. For the purposes of this article, weÃ¢ÂÂll assume that the queueÃ¢ÂÂs Email Address is being used. When you configure the email alert in OME, this email address will be the TO: address in the OME Email alert action.
Also note that there is no specification for Ticket Owners by Label. This is simply because user labels and the assigned users will be specific to your environment and cannot be assumed for the imported queue. Everything within the imported queue may be customized to meet your requirements.
To define custom fields, from within this Service Desk Configuration page select the Customize Fields and Layout link. Notice that the Category Values have the same set of default values supplied in the initial installation of OME. These category values may be used to manage ticket routing to different owners or to other queues depending on how to want to process incoming alert tickets. If you change or add categories within the OME console, you will want to make a corresponding change here to reflect the new category value by selecting the + button to create a new value, or the edit icon (pencil) next to a particular value if that value has changed.
Also note that the Priority Values have been modified to match the Severity values provided by OME. Now when these values get mapped from the OME alert action weÃ¢ÂÂll create next, weÃ¢ÂÂll get the same values in the service desk ticket that were generated from OME.