Linux Management

Reduce downtime with quick and easy start/stop/restart of Linux server apps

Package Details

• Vendor: Linux
• Target Platform: Linux
• Package Type: Server and Workstation Management

Why use this

Remote control over Linux server apps

Simplify Linux server admin by letting Hornbill users start, stop, and restart Linux services with just a few clicks. Service desk agents can get services back online within seconds.

How to get it

• You can try out ITOM for free (not for production use, limited runs) by installing the ITOM application from the Hornbill App Store.
• If you would like to explore ITOM and consider subscribing, please contact your account manager here.

Requirements

• Install the Hornbill Site Integration Server inside your firewall (if you don’t already have it).

Authentication

When creating jobs for operations contained within this package, they need to be run on the target machine as a user who has the correct privileges within your environment. To create and securely store keys:

• In the Configuration area of your Hornbill instance, navigate to Platform Configuration > Security > KeySafe;
• Click on the + Create New Key button, then select Username + Password;
• Give the KeySafe Key a Title (this is the name/identifier for the account as you will see it when creating an IT Automation Job, or adding an IT Automation node to a Workflow);
• Optionally add a Description;
• Populate the Username field with the username for the account being used on the target machine;
• Populate the Password field with the password for the above account;
• Select Create Key to save.

Once you have created your KeySafe Key, you can then use it to populate the Credentials > Admin or Run As inputs when creating IT Automation Jobs from this package.

Credentials

Accounts used when executing jobs against operations contained within this package must adhere to the following requirements:

• The target machine must have a local admin user that will be used for running the operations;
• SSH Remote Login must be enabled for the user above user
• Configuration for the user must be added to the sudoers file on the target machine, to allow the above user to sudo without a password (example: someadminuser ALL = (ALL) NOPASSWD:ALL).

Package Automations