Collaboration is preconfigured with a default web client administrator user
called globaladmin; globaladmin is a superuser who can access both the Prime
Collaboration Assurance and Prime Collaboration Provisioning UIs.
Specify a password for
globaladmin when you configure your virtual appliance (for either stand-alone
products or converged application. You need to use these credentials when you
launch the Prime Collaboration web client for the first time.
Prime Collaboration Assurance
and Prime Collaboration Provisioning servers support these CLI users: admin and
You cannot create CLI users
using the web client UI. CLI users are created during OVA configuration. By
default, the username is admin; the password is specified during OVA
configuration and is used to log into the CLI to check the application status
and perform backup and restore.
We recommend that you write
down the root password as it cannot be retrieved.
defined in the Prime Collaboration web client are different from the users
defined on the Prime Collaboration server (CLI).
CLI users are
not listed on the Prime Collaboration User Management page.
root follow same set of password validation rules, but the rules for admin are
different. See the
Cisco Prime Collaboration 10.0 Quick Start
Guide for password validation rules for these users.
If you are logging in for the
first time to the Prime Collaboration Assurance or Prime Collaboration
Provisioning web client, log in as
You, as a globaladmin, must
create other administrators using real user-IDs as they can be tracked in Audit
Trail and in the Prime Collaboration Provisioning order tracking system.
You must not create a user
with the name: globaladmin, pmadmin and admin.
When you integrate the Prime Collaboration Provisioning
application with Prime Collaboration Assurance, you can import users with
domain-specific and global Provisioning roles (who do not have Self-Care roles
associated) to the Prime Collaboration Assurance application using the “Import”
functionality in the
Administration > User Management page. You must
refresh the “User Management” page to see the list of imported users.
You cannot import a Prime
Collaboration Provisioning Self-Care user to the Prime Collaboration Assurance
You can then check the
/opt/emms/emsam/log/importedprovisioninguser.log file, by logging in as a root
user, to find the users who were not imported into Prime Collaboration
Assurance database due to several reasons such as duplicate usernames
(usernames already used in Prime Collaboration Assurance), usernames with no
passwords and so on.
However, when you integrate a freshly
installed Prime Collaboration Provisioning application (that contains no user
data) with the Prime Collaboration Assurance application, and you wish to
create a common user for both Prime Collaboration Assurance and Prime
Collaboration Provisioning, you must perform the following tasks as
The users thus created
via Add User feature are associated with the web client only and cannot log in
to the Prime Collaboration Assurance or Prime Collaboration Provisioning server
through the CLI.
The Prime Collaboration
Assurance and Prime Collaboration Provisioning applications do not share
inventory database. You must manage the devices separately to perform the
assurance and provisioning-related tasks. See
Managing Devices to
perform device management tasks using the Prime Collaboration Assurance
Cisco Prime Collaboration 10.0 Provisioning
Guide to perform device
management and provisioning tasks using the Prime Collaboration Provisioning