no more access to ccm 4.0

Answered Question
Feb 2nd, 2007

Hi,

we have a test setup with a callmanager 4.0 - ipcc and unity.

in the callmanager user directory, we deleted the administrator user, and now can't access this anymore. any ideas on how to access the callmanager administration pages? ( we can logon to the server )

thanks

I have this problem too.
0 votes
Correct Answer by gogasca about 9 years 8 months ago

We deleted the administrator user.

You should have deleted Administrator account.

Officially, we are not supporting changing the administrator account. Not all of the AVVID products can handle the change, like some of the services, which logs in using the administrator account. An example is Extension Mobility, which logs in using the administrator account. Call Manager upgrades will not function correctly if the logged on user is not 'administrator'.

The adminutility (used to change services passwords) uses the "administrator" name and this can't be changed so you will need to change the administrator name back to original (also some services might not work properly).

Therefore if the account was renamed you will be forced to rename it back o 'administrator' to upgrade. So we dont support it.

On the CallManager, take a look in the Utils directory on the C: drive of the CallManager itself. The file C:\Utils\SecurityTemplates\CCM-OS-OptionalSecurity-Readme.htm gives tools, scripts, and recommendations. It contains information about optional security capabilities which customers may enable as desired. Most of the optional scripts have associated caveats, which is why they are not done by default. I've cut/pasted the section on renaming the admin account below.

6.3. Rename Administrator Account and Create a Decoy Administrator Account Caveat(s):

* Cisco CallManager installations and upgrades currently require "Administrator" account to be used. Before you install or upgrade Cisco CallManager, you will need to rename the decoy administrator account and name the real administrator account back to "Administrator" on all Cisco CallManager servers in the cluster.

* Cisco CallManager version 3.3(4) and below or 4.0(1) includes a version of the Admin Utility, used to reset the passwords on the Cisco CallManager created user accounts, that requires you log in as the "Administrator" account. Before you run the AdminUtil.exe, you will need to rename the decoy administrator account and name the real administrator account back to "Administrator" on all Cisco CallManager servers in the cluster.

6.3.1. Choose Start > Programs > Administrative Tools > Computer Manager Local Users and Groups > Users.

6.3.2. Right click the Administrator user and choose Rename.

6.3.3. Enter a new administrator account name like NotAdmin, MyAdmin, Cisco CallManagerAdmin, or whatever your corporate standard is.

6.3.4. Right click the DisabledGuest account and choose Rename.

6.3.5. Enter Administrator as the new name.

6.3.6. Close the Computer Management window.

6.3.7. If the Multilevel Administration (MLA) feature of CallManager 3.3 is installed the new administrator name needs to be updated in IIS. Do not do this step if MLA is not installed. Do not do this step for CallManager 4.0 or greater.

6.3.7.1. Choose Start > Programs > Administrative Tools > Computer Manager > Services and Applications > Internet Information Services >

Cisco will NOT support changing the names of the administrator accounts or any other service accounts that are used by CallManager. This is due to the number of

dependencies required the CallManager subsystem and SQL associations.

You may try enabling MLA directly in DB.

and see if that helps, this iwll require resetting password for CCMAdministrator.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (2 ratings)
Loading.
Correct Answer
gogasca Fri, 02/02/2007 - 07:22

We deleted the administrator user.

You should have deleted Administrator account.

Officially, we are not supporting changing the administrator account. Not all of the AVVID products can handle the change, like some of the services, which logs in using the administrator account. An example is Extension Mobility, which logs in using the administrator account. Call Manager upgrades will not function correctly if the logged on user is not 'administrator'.

The adminutility (used to change services passwords) uses the "administrator" name and this can't be changed so you will need to change the administrator name back to original (also some services might not work properly).

Therefore if the account was renamed you will be forced to rename it back o 'administrator' to upgrade. So we dont support it.

On the CallManager, take a look in the Utils directory on the C: drive of the CallManager itself. The file C:\Utils\SecurityTemplates\CCM-OS-OptionalSecurity-Readme.htm gives tools, scripts, and recommendations. It contains information about optional security capabilities which customers may enable as desired. Most of the optional scripts have associated caveats, which is why they are not done by default. I've cut/pasted the section on renaming the admin account below.

6.3. Rename Administrator Account and Create a Decoy Administrator Account Caveat(s):

* Cisco CallManager installations and upgrades currently require "Administrator" account to be used. Before you install or upgrade Cisco CallManager, you will need to rename the decoy administrator account and name the real administrator account back to "Administrator" on all Cisco CallManager servers in the cluster.

* Cisco CallManager version 3.3(4) and below or 4.0(1) includes a version of the Admin Utility, used to reset the passwords on the Cisco CallManager created user accounts, that requires you log in as the "Administrator" account. Before you run the AdminUtil.exe, you will need to rename the decoy administrator account and name the real administrator account back to "Administrator" on all Cisco CallManager servers in the cluster.

6.3.1. Choose Start > Programs > Administrative Tools > Computer Manager Local Users and Groups > Users.

6.3.2. Right click the Administrator user and choose Rename.

6.3.3. Enter a new administrator account name like NotAdmin, MyAdmin, Cisco CallManagerAdmin, or whatever your corporate standard is.

6.3.4. Right click the DisabledGuest account and choose Rename.

6.3.5. Enter Administrator as the new name.

6.3.6. Close the Computer Management window.

6.3.7. If the Multilevel Administration (MLA) feature of CallManager 3.3 is installed the new administrator name needs to be updated in IIS. Do not do this step if MLA is not installed. Do not do this step for CallManager 4.0 or greater.

6.3.7.1. Choose Start > Programs > Administrative Tools > Computer Manager > Services and Applications > Internet Information Services >

Cisco will NOT support changing the names of the administrator accounts or any other service accounts that are used by CallManager. This is due to the number of

dependencies required the CallManager subsystem and SQL associations.

You may try enabling MLA directly in DB.

and see if that helps, this iwll require resetting password for CCMAdministrator.

Actions

This Discussion