Convert CE Command Center to EE

This document has been created to assist in the transition from a Community Edition Command Center to an Enterprise Edition Command Center.

Assumptions

A customer has deployed a Community Edition (CE) Command Center (CC) and would like to transition it to a fully licensed Enterprise CC. In order to disable the "phone home" function and to enable features which are disabled within CE (e.g. exporting), a script needs to run to disable the the "phone home" function.  This script is run after the new customer specific license has been applied. 

Requirements

A customer specific license has been supplied to the customer and installed on the system.  The new license needs to be installed first to allow the support bash functionality; support bash is not allowed on Community Edition Command Centers.

Instructions for obtaining and installing a license can be found here: Activate the License

Both SSH and SFTP may be required to access the Command Center. These protocols must be available from a workstation (or jump server, e.g.) to the Command Center to be transitioned. Additionally, if these protocols are not available from a workstation command line, then software like Putty or an SFTP client must be installed on the workstation to facilitate access and transfer of files. If SFTP is not available from the workstation to the CC, then SSH may be used and the functions within the script must be executed manually (e.g. typed in, or copied and pasted).

Establish a Connection and Ensure Proper Privileges 

Root log in is disabled for remote connections. When connecting via SSH, the admin account can be used, and then escalated to root. In order to transfer a file via SFTP, admin can be used but, because privilege escalation can be difficult with SFTP clients, the transfer can be made to the /tmp directory. Root users will need to transfer the script file from the /tmp folder to working directory for it to function. 

Option A: Scripted Commands

The following are a list of commands that can be run manually in the event that only SSH is available. 

Establish an SSH connection (see Requirements above)

Using SSH, log into the system as admin:

  • Type support bash to obtain a shell prompt

  • type su - and supply the root password to obtain a root prompt

    • Type rpm -qa | grep mssp

    • type rpm -e Asset Manager-mssp-ccap-#.#-##.x86_64 where #.#-## is the version number supplied in the above grep mssp output

    • type /bin/sed -i '/send.py/d' /var/spool/cron/root

    • type /sbin/service crond restart

    • type /sbin/service Asset Manager-webapp restart

Option B: Run the Script

A script has been created that will run the above 9 scripted commands in 1 step.

Establish an SSH connection (see Requirements above)

Establish an SFTP connection (see Requirements above)

  • Copy remove-mssp.sh to the /tmp directory of the Command Center

  • Using SSH, log into Command Center as admin:

    • Type support bash to obtain a shell prompt

    • type su - and supply the root password to obtain a root prompt

    • type cd /tmp       

    • type chmod 775 ./remove-mssp.sh

    • type ./remove-mssp.sh

Complete the Process

To verify, type rpm -qa | grep mssp

The command will return no output if script was successful

Type exit to exit the root shell

Type exit again to return to the Asset Manager CLI

If the rpm grep above indicates that the mssp function is still running, please contact Asset Manager Support.