How can I resolve mission control 3.0 install failures due to ElasticSearch forbidding Root user to run it?

Subject 

How to resolve mission control 3.0 install failures due to ElasticSearch forbidding Root user to run it

Affected Versions

JFrog Mission Control 3.0+

Description

Some environments use Root user to perform installs.  ElasticSearch 6.1.1 has several bootstrap checks that prevent Root from executing elasticSearch.  
The install script uses the logged-in-user that executes the script, and as such will fail when it tries to start Elasticsearch if Root ran the install.

Resolution

  1. create service ID (AD) *
  2. add service ID to sudo wheel group
  3. login as step #1 service ID
  4. Run this command to install Mission Control: ‘sudo [service ID] ./path to mission control installation script/installJFMC-redhat.sh –‘

Mission control can then be run as any qualified user, as ElasticSearch will now use an internal MissionControl user.