Skip to main content
Click here if you are having trouble viewing this site
Older versions of Internet Explorer will not support certain site features. Chrome, Safari, Firefox, and Edge will provide the best experience.
Resources
Spok

Smart Suite Accounts and Maintenance

  1. Last updated
  2. Save as PDF

This article contains frequently asked questions about the Smart Suite accounts.  

USERS AND PASSWORDS

You may change the passwords to a few accounts, but you must inform us of the change.  You may remove some accounts only in certain circumstances.

The following accounts must be kept:

               root

               amcom

               oracle

               admin

 

The following account can be removed:

               auditor

 

If you are not downloading files from the server to the operator workstations (for example, if you are  copying Smart Console .cfg files or .wav files manually), the following accounts can be removed:

               appman

               wpkg

               wpkclient

 

Otherwise, these accounts must remain open and accessible on the servers.

Spok is not responsible for issues which may arise due to the removal of the default accounts that are created in our setup (including auditor).  If these accounts are removed,  the Smart Suite system will be severly impacted and could render the system non-functional.  

While possible, changing the passwords of the built-in Smart Suite database users is discouraged.  Issues may arise if the passwords are updated and the proper steps are not made to ensure the connection of these users from every application that might use them.  

Changing the passwords of the wpkg and wpkgclient users (operating system and database) requires changes to each of the operator PCs as well. 

Even if you disable access to the amcom account and require individual logins, access must still be given to the amcom account.  

To support the Red Hat Linux operating system, Spok requires “root” access. If the root password is changed, please notify Spok immediately. Any alterations to the Linux OS may break the Spok Warranty and Spok’s ability to support it. 

               In order to provide full support for your solution, Spok requires the following login access to

               your various third‐party operating systems and Oracle database:

               • Linux servers: root access

               • Windows servers: Local administrator access

               • Oracle database: A user with 'sysdba' privileges

               • SQL Server: A user with 'SA' privileges

 

For additional information, please refer to Spok's Service Level Expectation Guide. 

 

 

KB41737