The Packaged Contact Center Enterprise (PCCE) installation wizard requires a dedicated domain user account, referred to as the Service Account, to perform its automated deployment tasks. This account is granted local administrator privileges on all servers within the PCCE deployment (e.g., CCE Data Servers, CVP, Finesse). The wizard uses the credentials of this Service Account to log in to each machine, create and configure databases, enable necessary protocols and interfaces, and establish the services that will run under this account's security context. This ensures consistent permissions and access across the distributed environment.

A. Setup login: This is a generic, non-standard term. Cisco documentation specifically refers to the required account as a domain Service Account.

B. Windows login: This term is too broad. The wizard requires a specific type of domain account with administrative rights, not just any Windows login.

C. Local administrator login: This is incorrect because the wizard must access and configure multiple servers, which necessitates a domain-level account, not a local one.

1. Cisco Packaged Contact Center Enterprise Installation and Upgrade Guide

Release 12.6(1)

Chapter: "Prepare for the Installation"

Section: "Active Directory Domain"

Subsection: "Create Service User Account".

This section explicitly states

"The domain user account for Cisco services is the account under which you install the Packaged CCE components. This account is also the service account for the central controller and other components." It details that this account must be a domain user and a member of the local Administrators group on each target server

which is precisely what the wizard uses.

2. Cisco Packaged Contact Center Enterprise Administration and Configuration Guide

Release 12.5(1)

Chapter: "Deployment"

Section: "PCCE Deployment".

This guide describes the deployment process which relies on the Unified CCE Web Administration tool and its wizards. The prerequisites for this process consistently highlight the need for a pre-configured domain service account with specific permissions to execute the installation and configuration steps across all solution components.