Another email question from an SE that might be useful for the forum:
Q. The customer was shying away from automatic provisioning, it may be due to licensing implications. Are there ways to ‘control’ automatic provisioning in an easy fashion, something that a service desk could handle? I had a read of the feature here but it seems that ASP can be controlled only by filtering LDAP attributes?
http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/collaboration/10-5/provisioning/guide/Cisco_Prime_Collaboration_Provisioning_Guide_10_5_and_10_5_1/Cisco_Prime_Collaboration_Provisioning_Guide_10_5_chapter_010.html
A. A few thoughts on this…
Automatic Service Provisioning (ASP) is not an all or nothing thing. You enable it where you want it. You might use it for some Domain groups, for some roles and not in others.
When a user is added manually and a role is assigned that has ASP capability, the choice to do ASP or not is controlled by a check box in the Add User popup. Help desk can make that choice.
Roles may or may not have ASP functionality turned on. An executive role may have it disabled because at some company every executive will be provisioned with custom servcies and settings. It might be enabled for a regular employee, contractor or exec admin role because the IT group wants a consistent set of services and settings for users in these roles.
Filtering for LDAP import of new users can be controlled through the query to better pick users for import or role assignment. PCP 10.6 has new LDAP fields to select from that were not in older revisions.
Filtering for LDAP import and the roles assigned, can control which users are just imported, imported with a standard set of services or imported and get full sets of services. Templates can be automatically applied at that time.
Users can be added to PCP that are only local to PCP so do not count against CUCM licensing. During LDAP import, batch import, manual creation, etc. users can be brought into PCP only. When the time comes to give them services on CUCM the help desk can give them at least one service, which triggers the user to be added to CUCM and then consumes a user license.
If you are creating fake (pseudo) users in PCP for conference rooms or open space areas, for example, the templates automatically applied or manually applied allow the owner UserID to be set to the userID, some other specific userID or anonymous. I believe anonymous is either not counted or may count against cumulative excess endpoint licensing.
There is a lot of flexibility once you get to know how each of the mechanisms works.
