Step 1

Select the host in the vSphere client.

Step 2

Choose File > Deploy OVF Template.

Step 3

Browse to the location on your local drive where you stored the OVA.

Step 4

On the Select a name and folder page, enter a name for the virtual machine and then choose the location for the virtual machine.

Step 5

Click Next.

Step 6

On the Select a compute resource page, select the destination compute resource. Click Next.

Step 7

On the Review details page, verify the OVF template details.

Step 8

On the Configuration page, select the applicable configuration from the available list. Click Next.

Step 9

On the Select storage page, ensure that the virtual disk format is Thick provision Lazy Zeroed and then choose a datastore on which you want to deploy the new virtual machine. Click Next.

Step 10

On the Select networks page, confirm that the network mapping is correct for the Unfied CCE Rogger and PG:

1. For the Unifed CCE Rogger and PG:

2. • Map Public to UCCE Public Network

   • Map Private to UCCE Private Network

3. For all other servers, map Public to UCCE Public Network.

Step 11

On the Network Mapping page, select the appropriate network from the Destination drop-down list.

Step 12

On the Ready to complete page, click Finish to create the VM.

Step 1

Log in to the DNS server.

Step 2

In Windows, navigate to Administrative Tools > DNS. This opens the DNS Manager.

Step 3

In the Forward lookup zone, navigate to your deployment's domain name.

Step 4

Right-click the domain name and select New Host (A or AAAA).

Step 5

In the New Host dialog box, enter the computer name and IP address (IPv4) of VOS components.

Step 1

Add a virtual drive as follows:

1. Right-click the virtual machine and click Edit Settings.

2. In the Hardware tab, click on Add.

   The Add Hardware window appears.

3. You can select the type of device you wish to add. Select Hard Disk, and then click Next.

4. Select the Create a new virtual disk option, and then click Next.

5. In the Capacity section, use the Disk Size box to assign the desired disk space, and then click Next.

   Note

   Virtual machine templates for Logger, Rogger, AW, and HDS servers do not have a SQL database drive preprovisioned. The following reference table must be used to assign disk space to the virtual machine based on the type of validation errors will occur: Virtual Machine Template Default Second Disk Size Logger 500 GB Rogger 150 GB AW-HDS-DDS 750 GB AW-HDS 500 GB HDS-DDS 500 GB You can custom size the SQL database disk space to meet the data retention requirements on an external AW-HDS-DDS server only, as calculated by the Database Estimator tool.

6. On the Disk Provisioning section choose Thick provision Lazy Zeroed format. Click Next.

7. In the Advanced Options section, retain the default options and then click Next.

8. In the Ready to Complete section, click Finish to create the hard disk.

9. Click OK to confirm the changes.

   The Recent Tasks window at the bottom of the screen displays the progress.

1. Right-click the virtual machine and click Edit Settings.

2. In the Virtual Hardware tab, click on Add New Device.

3. You can select the type of device you wish to add. Select Hard Disk. The new hard disk appears. Assign the desired disk space to the hard disk.

4. Configure the required parameters as specified below:

   Note

   Virtual machine templates for Logger, Rogger, AW, and HDS servers do not have a SQL database drive preprovisioned. The following reference table must be used to assign disk space to the virtual machine based on the type of validation errors will occur: Virtual Machine Template Default Second Disk Size Logger 500 GB Rogger 150 GB AW-HDS-DDS 500 GB AW-HDS 500 GB HDS-DDS 500 GB You can custom size the SQL database disk space to meet data retention requirements on an external AW-HDS-DDS server only, as calculated by the Database Estimator tool.

5. On the Disk Provisioning section, choose Thick provision Lazy Zeroed.

6. In the VM Options > Advanced Options section, retain the default options.

7. Click OK to confirm the changes.

   The Recent Tasks window at the bottom of the screen displays the progress.

Step 2

In Windows, navigate to Disk Management.

Step 3

Right-click on the Disk 1 box and select Online.

Step 4

Initialize Disk 1 as follows:

1. Right-click on the Disk 1 box and select Initialize Disk.

2. Check the Disk 1 checkbox.

3. Select the MBR (Master Boot Record) radio button.

4. Click OK.

Step 5

Create a new disk partition as follows:

1. Right-click the graphic display of Disk 1 and select New Simple Volume.

2. Click Next on the first page of the New Simple Volume Wizard.

3. On the Specify Volume Size page, retain the default volume size. Click Next.

4. On the Assign Drive Letter or Path page, assign drive letter (E). Click Next.

5. On the Format Partition page, format the partition as follows:

   1. Select the Format this volume with the following settings radio button.

   2. Click Format Disk.

   3. Select File System as NTFS and click Start.

   4. Select Default from the Allocation unit size drop-down menu.

   5. Enter a value in the Volume label field.

   6. Check the Perform a quick format checkbox.

   7. Click Next.

6. Click Finish.

   A popup window displays a message that you need to format the disk before you can use it.

   The format is complete when the status changes to Healthy.

Step 6

Format the disk.

1. Click Format disk.

2. Click Start.

   A popup displays a warning that formatting will erase all data on the disk.

3. Click OK.

4. When the format is complete, click OK to close the popup window.

Step 1

Mount the Microsoft Windows Server ISO image to the virtual machine.

Step 2

Power on the VM.

Step 3

Enter the Language, Time and Currency Format, and Keyboard settings. Click Next.

Step 4

Click Install Now.

Step 5

If prompted, enter the product key for Windows Server and click Next.

Step 6

Select the Desktop Experience option for the Windows Server and click Next.

Step 7

Accept the license terms and click Next.

Step 8

Select Custom: Install Windows only (advanced), select Drive 0 to install Microsoft Windows Server, and then click Next.

Step 9

Enter and confirm the password for the administrator account, and then click Finish.

Step 10

Enable Remote Desktop connections as follows:

1. Navigate to Control Panel > System and Security > System.

2. Click Remote Settings.

3. Click the Remote tab.

4. Select the Allow remote connections to this computer radio button. The Remote Desktop Connection dialog displays a notification that the Remote Desktop Firewall exception is enabled. Click OK.

Step 11

Install VMWare tools. See Install VMware Tools.

Step 12

Open the Network and Sharing Center, and in the View your basic network info and set up connections section, click Ethernet.

Step 13

In the Ethernet Status window, click Properties.

Step 14

In the Ethernet Properties dialog box, configure the network settings and the Domain Name System (DNS) data:

1. Uncheck Internet Protocol Version 6 (TCP/IPv6).

2. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.

3. Select Use the following IP Address.

4. Enter the IP address, subnet mask, and default gateway.

5. Select Use the following DNS Server Address.

6. Enter the preferred DNS server address, and click OK.

Step 1

Mount the Microsoft SQL Server ISO image to the virtual machine. For more information, see Mount ISO Files.

Step 2

Select Installation in the left pane and then click New SQL Server stand-alone installation or add features to an existing installation. Click OK.

Step 3

On the Product Key page, enter the product key and then click Next.

Step 4

Accept the License Terms and then click Next.

Step 5

Optional: On the Microsoft Update page, check the Use Microsoft Update to check for updates check box, and then click Next.

Step 6

On the Install Rules page, click Next.

Step 7

On the Feature Selection page, select only the following, and click Next:

Step 8

On the Instance Configuration page, select Default Instance and click Next.

Step 9

On the Server Configuration page, click the Services Account tab.

1. Associate the SQL services with the virtual account.

   • For the SQL Server Agent service, in the Account Name field, select NT Service\SQLSERVERAGENT. If you have enabled Outbound Option High Availability, this account must have the system administrator privilege.

   • For the SQL Server Database Engine, in the Account Name field, select NT Service\MSSQLSERVER.

   Note	While you can use the Network or Local Services account instead of the Virtual account, using the Virtual account provides security.

2. For the remaining services, accept the default values.

3. In the Start Up Type column, for the SQL Server Agent service account, select Automatic from the list.

4. Enable Grant Perform Volume Maintenance Task privilege to SQL Server Database Engine Service.

   Note	Unified ICM Installer automatically enables the Grant Perform Volume Maintenance Task for the NT service account.If it is not enabled automatically then you must enable Grant Perform Volume Maintenance Task privilege to SQL Server Database Engine Service manually on the SQL server.

Step 10

On the Server Configuration page, click the Collation tab.

1. In the Database Engine section, click Customize.

2. Select the Windows Collation designator and sort order radio button.

3. Select the appropriate collation. Typically, you choose the SQL Server collation that supports the Windows system locale most commonly used by your organization; for example, "Latin1_General" for English.

   Note	See the Contact Center Enterprise Compatibility Matrix at https://www.cisco.com/c/en/us/support/customer-collaboration/unified-contact-center-enterprise/products-device-support-tables-list.html for details about collations used for other languages.

   The database entry is related to the collation that you select. For example, if you set the collation for Latin1_General, but you select Chinese language at sign-in. When you enter field values in Chinese, the application displays the unsupported character error, because the database does not support the characters.

   Important

   It is critical to select the correct collation setting for the language display on your system. If you do not select the correct collation during installation, you must uninstall and reinstall Microsoft SQL Server.

4. Check the Binary check box.

5. Click OK, and then click Next.

Step 11

On the Database Engine Configuration page:

1. On the Server Configuration tab, click the Mixed Mode radio button.

2. Enter the password for the SQL Server system administrator account, and confirm by reentering it.

3. Click Add Current User to add the user who is installing the SQL Server as an administrator.

4. On the TempDB tab, set the Initial size and Autogrowth for Rogger, Logger, AW-HDS-DDS, AW-HDS, and HDS-DDS. For information about values for respective components Increase Database and Log File Size for TempDB.

   For more information about the SQL Server TempDB Database and its use, see the Microsoft SQL Server documentation.

5. Click Next.

Step 12

On the Ready to Install page, click Install.

Step 13

On the Complete page, click Close.

Step 14

Enable Named Pipes and set the sort order as follows:

1. Open the SQL Server Configuration Manager.

2. In the left pane, navigate to SQL Native Client 11.0 Configuration (32bit) > Client Protocols.

3. In the right pane, confirm that Named Pipes is Enabled.

4. Right-click Client Protocols and select Properties.

5. In the Enabled Protocols section of the Client Protocols Properties window, use the arrow buttons to arrange the protocols in the following order:

   1. Named Pipes

   2. TCP/IP

6. Check the Enable Shared Memory Protocol and then click OK.

7. In the left pane, navigate to SQL Server Network Configuration > Protocols for MSSQLSERVER.

8. In the right pane, right-click Named Pipes and select Enable.

Step 15

Set the SQL Server's default language to English as follows:

1. Launch SQL Server Management Studio.

2. In the left pane, right-click the server and select Properties.

3. Click Advanced.

4. In the Miscellaneous section, set the Default Language to English.

5. Click OK.

Step 16

Restart the SQL Server service as follows:

1. Navigate to the Windows Services tool.

2. Right-click SQL Server (MSSQLSERVER) and click Stop.

3. Right-click SQL Server (MSSQLSERVER) and click Start.

Step 17

Ensure that the SQL Server Browser is started, as follows:

1. Navigate to the Windows Services tool.

2. Navigate to the SQL Server Browser.

3. Right-click to open the Properties window.

4. Enable the service, change the startup type to Automatic, and click Apply.

5. To start the service, click Start, and then click OK.

Step 1

Navigate to Control Panel > System and Security > System.

Step 2

Click Change Settings.

Step 3

In the Computer Name tab, click Change.

Step 4

Change the name of the computer from the name randomly generated during Microsoft Windows Server installation. The name does not contain underscores or spaces.

Step 5

Select the Domain radio button to change the member from Workgroup to Domain.

Step 6

Enter qualified domain name and click OK.

Step 7

In the Windows Security dialog, enter the domain credentials and click OK.

Step 8

On successful authentication, click OK.

Step 9

Reboot the server and sign in with domain credentials.

Step 1

Identify the MAC addresses and labels for the network adapters as follows:

1. From vSphere, select and right-click the VM.

2. Select Edit Settings. In the Hardware tab, click Network adapter 1. In the right panel, write down the last few digits of MAC addresses and note whether the label is PCCE Public or PCCE Private. For example, Network adapter 1 may have a MAC address that ends in 08:3b and the network label PCCE Public.

3. Repeat for Network adapter 2, noting its MAC address and label.

4. From the VM console, type ipconfig /all from the command line. This displays the adapter names and physical addresses.

5. Note the adapter names and physical addresses and match them with the MAC addresses and labels that you noted in VMware. For example, in ipconfig/all, Local Area Connection 2 may have a physical address that ends in 08-3b.

6. Match the MAC address of the network adapter that VMware identified as PCCE Public with the corresponding physical address of Local Area Connector. In this example, the physical address of Local Area Connection 2 (08-3b) matches the MAC address (08-3b) of Network adapter 1. This means that Local Area Connection 2 is PCCE Public.

   Note	Adapters may have a different name than Local Area Connection.

Step 2

Locate and rename the network adapters in Windows as follows:

1. In Windows, open the Control Panel > Network and Sharing Center and click Change adapter settings.

2. Right-click Local Area Connection and select Rename. Rename it to PCCE Public or PCCE Private, based on the matching you did above.

3. Right-click Local Area Connection 2 and select Rename. Rename it to PCCE Public or PCCE Private, based on the matching you did above. In the example above, Local Area Connection 2 is renamed to PCCE Public.

Step 3

Set the Properties for PCCE Public as follows:

1. Right-click PCCE Public and select Properties.

2. In the Networking tab, uncheck Internet Protocol Version 6 (TCP/IPv6).

3. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.

4. In the General tab for Internet Protocol Version 4, select Use the following IP address and enter IP address, Subnet mask, Default gateway, and DNS servers.

5. Click OK and Close to exit.

Step 4

Set the Properties for PCCE Private as follows:

1. Right-click PCCE Private and select Properties.

2. In the Networking tab, uncheck Internet Protocol Version 6 (TCP/IPv6).

3. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.

4. In the General tab for Internet Protocol Version 4, select Use the following IP address and enter IP address and Subnet mask.

5. Click Advanced.

6. Click the DNS tab and uncheck Register this connection's addresses in DNS.

7. In the DNS server, add a new A record that resolves to the private IP address. Also, create an associated pointer record for reverse lookups.

   Note	For hostnames in A records, append the letter p to indicate that it is a private address.

8. Click OK to exit.

Step 5

Assign an interface metric value for the network adapter:

1. Select the network adapter and right-click Properties.

2. In the Networking tab, select the appropriate Internet Protocol version and click Properties.

3. In the Internet Protocol Version Properties dialog box, click Advanced.

4. In the IP Settings tab, uncheck the Automatic metric checkbox and type a low value in the Interface metric text box.

   Note	A low value indicates a higher priority. Make sure that the Public Network card should have a lower value compared to the Private Network card. By default, the value of the Interface Metric property for a network adapter is automatically assigned and is based on the link speed.

5. Click OK to save the settings.

   Repeat the steps to assign an interface metric value for the internal/private cluster communication network adapter.

Step 1

Locate and rename the network adapter in Windows as follows:

1. In Windows, open the Network and Sharing Center and click Change Adapter Settings .

2. Right-click Local Area Connection and select Rename. Rename it to UCCE Public.

Step 2

Set the Properties for UCCE Public as follows:

1. Right-click UCCE Public and select Properties.

2. In the Networking dialog box, uncheck Internet Protocol Version 6 (TCP/IPv6).

3. In the Networking dialog box, select Internet Protocol Version 4 (TCP/IPv4) and select Properties.

4. In the General dialog box for Internet Protocol Version 4, select Use the following IP address and enter the IP address, the Subnet mask, the default gateway, and DNS servers.

5. Click OK and Close to exit.

Step 1

On each Rogger, or PG VM, run ipconfig /all.

Step 2

On each of these VMs, run route print –4.

Step 3

On each of these VMs, run route add <destination subnet> mask <subnet mask> <gateway IP> IF <interface number> -p to add a persistent static route for the remote Private Network.

Go to Settings > Update & Security and run Microsoft Windows Update.

Step 1

Login as a user with administrative privileges.

Step 2

Mount the Cisco Unified CCE ISO image to the virtual machine. See Mount ISO Files.

Step 3

Run setup.exe from the D:\ICM-­CCE Installer directory.

Step 4

Follow the InstallShield procedures to install Cisco Unified CCE.

Step 5

When the installation completes, restart the computer when prompted.

Step 6

Before applying any ES, you must run the mandatory update for Packaged CCE, if a fresh install is being performed on Windows Server 2016. You can download the CCE 12.0 Mandatory Update for Fresh Install/Tech Refresh from https://software.cisco.com/download/home/268439622/type/280840583/release/12.0(1).

Step 7

Unmount the ISO image.

Step 1

Open the ICMDBA tool and click Yes to any warnings.

Step 2

Navigate to Servers > <Logger Server> > Instances > <Unified CCE instance> > LoggerA. Right-click the instance name and select Database > Create.

Step 3

On the Stop Server message, click Yes to stop the services.

Step 4

In the Create Database dialog box, click Add to open the Add Device dialog box.

Step 5

Click Data, and choose the drive on which you want to create the database, for example, the E drive. In the database size field, you can choose to retain the default value or enter a required value.

Step 6

Click OK to return to the Create Database dialog box.

Step 7

In the Add Device dialog box, click Log. Choose the desired drive. Retain the default value in the log size field and click OK to return to the Create Database dialog box.

Step 8

In the Create Database dialog box, click Create, and then click Start. When you see the successful creation message, click OK and then click Close.

Step 1

Navigate to Control Panel > Network and Internet .

Step 2

Click Network and Sharing Center, and then click Change adapter settings in the left panel.

Step 3

Right-click the adapter and select Rename. Change the name to UCCE Public.

Step 4

Right-click UCCE Public and select Properties.

Step 5

In the Networking dialog box, de-select Internet Protocol Version 6 (TCP/IPv6).

Step 6

In the Networking dialog box, select Internet Protocol Version 4 (TCP/IPv4) and select Properties.

Step 7

In the General dialog box for Internet Protocol Version 4 , select Use the following IP address and enter the IP address, the Subnet mask, the default gateway and DNS servers.

Step 8

Click OK and Close to exit.

Step 1

Log in to your system as a user with administrative privileges.

Step 2

Mount the Unified CVP ISO image to the virtual machine. For more information, see Mount ISO Files.

Step 3

Run setup.exe from the D:\ CVP\Installer_Windows directory.

Step 4

Follow the InstallShield wizard to Run setup.exe from the D:\CVP\Installer_Windows directory:

1. Accept the license agreement.

2. In the Select Packages screen, check the type you are adding.

3. Click Next.

4. On the Voice Prompt Encode Format screen, select the codec according to your requirement.

5. In the Choose Destination Location screen, accept the default. Click Next.

6. In the X.509 certificate screen, enter the information that you want to include in the certificate.

7. In the Ready to Install screen, click Install.

8. Select the option to restart the computer after installation. Click Finish.

Step 5

If Unified CVP Engineering Specials are available, copy them to the local drive. Follow the InstallShield wizard to install them.

Step 6

Unmount the ISO image.

Step 1

Navigate to Start > Administrative Tools.

Step 2

Choose Server Manager option navigate to Manage > Add Roles and Features.

Step 3

Goto Installation Type tab, choose Role based or featue based installation option and click Next.

Step 4

On Server Selection window, select server from the list and click Next.

Step 5

Check Web Sever(IIS) check box to enable IIS and click Next.

Step 6

No additional features are necessary to install Web Adaptor, click Next.

Step 7

Click Next.

Step 8

Ensure that the web server components listed below are enabled.

Step 9

Click Next.

Step 10

Ensure that your settings are correct and click Install.

Step 11

After installation click Close.

Step 1

Select Start > Administrative Tools.

Step 2

Select Server Manager and click Manage.

Step 3

Select Add Roles and Features and click Next.

Step 4

In the Installation Type tab, select Role-based or feature-based Installation and click Next.

Step 5

Select required server from the list and click Next.

Step 6

On the Server Roles page, expand Web Server (IIS).

Step 7

Check FTP Server and click Next.

Step 8

On the Features page, click Next.

Step 9

On the Configuration page, click Install.

Step 1

Go to Start > Programs > Administrative Tools> Server Manager.

Step 2

Expand Roles in the left panel of the Server Manager window.

Step 3

Expand Web Server (IIS) and select Internet Information Services (IIS) Manager.

Step 4

In the Connections panel:

1. Expand the CVP server to which you are adding the FTP site.

2. Right-click on Site and choose Add FTP Site.

Step 5

Enter the FTP Site Name.

Step 6

From the Physical Path field, browse to C:\Inetpub\wwwroot and click Next.

Step 7

Choose IP Address of CVP from the drop-down list.

Step 8

Enter the port number.

Step 9

Select the No SSL check box and click Next.

Step 10

Select the Anonymus and Basic check boxes in Authentication panel.

Step 11

Choose All Users from Allow Access To from the drop-down list.

Step 12

Select the Read and Write check box and click Finish.

Step 1

Log in to your system as a user with administrative privileges.

Step 2

Mount the Unified CVP ISO image to the virtual machine. For more information, see Mount ISO Files.

Step 3

Run setup.exe from the DVD drive located at the CVP\Installer_Windows directory.

Step 4

Follow the InstallShield wizard to Run setup.exe from the D:\CVP\Installer_Windows directory:

1. Accept the license agreement.

2. In the Select Packages screen, check Reporting Server.

3. In the Choose Destination Folder screen, select the folder location for the CVP installation folder.

4. In the X.509 certificate screen, enter the information that you want to include in the certificate.

5. In the Choose the database data and backup drive screen, enter the drive letter (typically, E).

6. In the Database size selection screen, select Premium (438 GB).

7. In the Ready to Install screen, click Install.

8. Enter the Reporting Server password when prompted.

9. Select the option to restart the computer after installation. Click Finish.

Step 5

If Unified CVP Engineering Specials are available, copy them to the local drive. Follow the InstallShield wizard to install them.

Step 6

Unmount the ISO image.

Step 1

Create a virtual machine for your VOS-based contact center application using the OVA.

Step 2

Mount the ISO image for the software to the virtual machine.

Step 3

Select the virtual machine, power it on, and open the console.

Step 4

Follow the Install wizard, making selections as follows:

1. In the Disk Found screen, click OK to begin the verification of the media integrity.

2. In the Success screen, select OK.

3. In the Product Deployment Selection screen:

   • If you are installing Finesse or Unified Communications Manager, select OK.

   • If you are installing Unified Intelligence Center, select Cisco Unified Intelligence Center with Live Data and IdS, and then select OK. The Cisco Unified Intelligence Center with Live Data and IdS option installs Cisco Unified Intelligence Center with Live Data, and Cisco Identity Service (IdS) on the same server.

4. In the Proceed with Install screen, select Yes.

5. In the Platform Installation Wizard screen, select Proceed.

6. In the Apply Patch screen, select No.

   Finesse does not have this step.

7. In the Basic Install screen, select Continue.

8. In the Timezone Configuration screen, use the down arrow to choose the local time zone that most closely matches where your server is located. Select OK.

   Note	For Live Data servers, use the same timezone for all the nodes.

9. In the Auto Negotiation Configuration screen, select Continue.

10. In the MTU Configuration screen, select No to keep the default setting for Maximum Transmission Units.

11. In the DHCP Configuration screen, select No.

    Finesse does not have this step.

12. In the Static Network Configuration screen, enter static configuration values. Select OK.

13. In the DNS Client Configuration screen, click Yes to enable DNS client.

14. Enter your DNS client configuration. Select OK.

    Important

    DNS client configuration is mandatory for Finesse. If you do not perform this step, agents cannot sign in to the desktop and you must reinstall Finesse.

15. In the Administrator Login Configuration screen, enter the Platform administration username. Enter and confirm the password for the administrator. Select OK.

16. In the Certificate Information screen, enter data to create your Certificate Signing Request: Organization, Unit, Location, State, and Country. Select OK.

17. In the First Node Configuration screen, select Yes.

18. In the Network Time Protocol Client Configuration screen, enter a valid NTP server IP address and select OK.

    Important

    Proper NTP configuration is essential.

19. In the Security Configuration screen, enter the security password and select OK.

20. In the SMTP Host Configuration screen, select No.

    Finesse does not have this step.

21. Unified Communications Manager only: On the Smart Call Home Enable screen, select Disable All Call Home on System Start.

22. In the Application User Configuration screen, enter the application username. Enter, and confirm the application user password. Select OK.

23. In the Platform Configuration Confirmation screen, select OK. The installation begins and runs unattended.

    • There is a reboot in the middle of the installation.

    • The installation ends at a sign-in prompt.

Step 5

Unmount the ISO image.

Step 1

Direct a browser to the URL https://<hostmame>:8443/oamp, where <hostname> is the hostname of your Cisco Unified Intelligence Center publisher.

Step 2

Sign in using the system application user ID and password that you defined during installation.

Step 3

From the section in the left, select Device Configuration.

Step 4

Click Add Member.

Step 5

On the Device Configuration fields for the Subscriber, enter a name, the hostname or IP address , and a description for the device.

Step 6

After you complete the cluster configuration, restart the publisher.

Step 1

Launch Unified Communications Manager Publisher in a browser (https://<IP Addr of CUCM Publisher>/ccmadmin ).

Step 2

Select System > Server > Add New.

Step 3

On the Server Configuration page, select CUCM Voice/Video for the Server Type. Click Next.

Step 4

On the Server Configuration page, enter the IP Address of the subscriber.

Step 5

Click Save.

Step 1

Launch Unified Communications Manager Administration in a browser (https://<IP Address of Unified Communications Manager Publisher>/ccmadmin ).

Step 2

Create an Access Control Group, as follows:

1. Navigate to User Management > User Settings > Access Control Group.

2. Click Add New.

3. Enter a name for the Access Control Group.

4. Click Save.

   The Access Control Group Configuration page opens.

5. From the Related Links drop-down menu, select Assign Role to Access Control Group and click Go.

6. Click Assign Role to Group.

   The Find and List Roles popup window opens.

7. Click Find.

8. Check the Standard AXL API Access check box.

9. Click Add Selected.

10. Click Save.

Step 3

Create an Application User, as follows:

1. Navigate to User Management > Application User.

2. Click Add New.

3. Enter a name and password for the Application User.

4. In the Permissions Information section, click Add to Access Control Group.

   The Find and List Access Control Group popup window opens.

5. Click Find.

6. Check the check box for the Access Control Group you created.

7. Click Add Selected.

8. Click Save.

Step 1

Launch the Cisco Finesse primary node in a browser (https://<FQDN of Finesse Primary node>/cfadmin).

Step 2

Go to Home > Cluster Settings. (This path is based on the default configuration and assumes that you have not changed the page for the Cluster Settings gadget.)

Step 3

Add the hostname for the Cisco Finesse secondary node.

Step 4

Click Save.

Step 5

Restart Cisco Finesse Tomcat as follows:

1. To stop the Cisco Finesse Tomcat service, enter this CLI command: utils service stop Cisco Finesse Tomcat .

2. To start the Cisco Finesse Tomcat service, enter this CLI command: utils service start Cisco Finesse Tomcat .

Step 1

Create a virtual machine for your VOS-based contact center application using the OVA.

Step 2

Mount the ISO image for the software to the virtual machine.

Step 3

Select the virtual machine and power it on, and open the console.

Step 4

Follow the Install wizard, making selections as follows:

1. In the Disk Found screen, click OK to begin the verification of the media integrity.

2. In the Success screen, select OK.

3. In the Product Deployment Selection screen:

   • If you are installing Finesse or Unified Communications Manager, select OK.

   • If you are installing Unified Intelligence Center, select Cisco Unified Intelligence Center with Live Data and IdS, and then select OK. The Cisco Unified Intelligence Center with Live Data and IdS option installs Cisco Unified Intelligence Center, Live Data, and Cisco Identity Service (IdS) on the same server.

Step 5

Follow the Install wizard, making selections as follows:

1. In the Proceed with Install screen, select Yes.

2. In the Platform Installation Wizard screen, select Proceed.

3. In the Apply Patch screen, select No.

   Finesse does not have this step.

4. In the Basic Install screen, select Continue.

5. In the Timezone Configuration screen, use the down arrow to choose the local time zone that most closely matches where your server is located. Select OK.

   Note	For Live Data servers, use the same timezone for all the nodes.

6. In the Auto Negotiation Configuration screen, select Continue.

7. In the MTU Configuration screen, select No to keep the default setting for Maximum Transmission Units.

8. In the DHCP Configuration screen, select No.

   Finesse does not have this step.

9. In the Static Network Configuration screen, enter static configuration values. Select OK.

10. In the DNS Client Configuration screen, click Yes to enable DNS client.

    Important

    DNS client configuration is mandatory for Finesse. If you do not perform this step, agents cannot sign in to the desktop and you must reinstall Finesse.

11. In the Administrator Login Configuration screen, enter the Platform administration username. Enter and confirm the password for the administrator. Select OK.

12. In the Certificate Information screen, enter data to create your Certificate Signing Request: Organization, Unit, Location, State, and Country. Select OK.

13. In the First Node Configuration screen, select No.

14. In the warning screen, select OK.

15. In the Network Connectivity Test Configuration screen, select No.

16. In the First Node Access Configuration screen, enter the host name and IP address of the first node. Enter and confirm the security password. Select OK.

17. In the SMTP Host Configuration screen, select No.

    Finesse does not have this step.

18. In the Platform Configuration Confirmation screen, select OK. The installation begins and runs unattended.

    • There is a reboot in the middle of the installation.

    • For Cisco Unified Intelligence Center, you see a Product Licensing screen that shows the URL for obtaining the license and the Media Access Control (MAC) address. Write down the MAC address. You need this information for the license application.

    • The installation ends at a sign-in prompt.

Step 6

Unmount the ISO image.

Step 1

Open Cisco Unified CM Administration at https://<IP Address of the CUCM Publisher>/ccmadmin.

Step 2

Select Cisco Unified Serviceability from the Navigation menu and click Go.

Step 3

Select Tools > Service Activation.

Step 4

From the Server drop-down list, choose the server on which you want to activate the service, and then click Go.

Step 5

For the Publisher, check the following services to activate and click Save:

Step 6

For the Subscribers, check the follow services to activate and click Save:

Step 1

Launch Web Setup in the VM you want installed or upgraded.

Step 2

Sign in as a domain user with local administrator permission.

Step 3

Click Instance Management and then click Add.

Step 4

In the Add Instance dialog box, choose the customer facility and instance.

Step 5

In the Instance Number field, enter 0.

Step 6

Click Save.

Step 1

Log in to your primary Live Data node.

Step 2

Run the following command to set the secondary node:

Step 1

Log in to your publisher IdS node.

Step 2

Run the following command to set the subscriber node:

Step 1

Run the SQL Server installer. Consult Microsoft documentation as needed.

Step 2

Step through the wizard. As appropriate, accept the default or choose the correct instance for your deployment. Select Rebuild on the Full-Text Search Upgrade Options page.

Step 1

Launch EDMT.exe.

Step 2

In the Cisco Unified ICM/Contact Center Enterprise Enhanced Database Migration Tool that appears, click Next.

Step 3

Under Migration Type, click the Common Ground radio button and then click Next.

Step 4

In the Warning dialog box that appears, click Yes.

Step 5

From the Authentication drop down list, choose either Windows Authentication or SQL server Authentication.

Step 6

Click Refresh Database List, and select the database you want to migrate from that list.

Step 7

Click Next.

Step 8

Click Start Migration.

Step 9

Click Exit after the data migration is complete.

Step 1

Take back up of conf folder from c:\cisco\cvp\conf.

Step 2

Stop all services such as CVP Call Server, CVP VXML Server, and CVP WebServiceManager.

Step 3

From C:/Cisco/CVP/bin/TAC, run reimage.bat as reimage.bat 2>Error.txt.

Step 4

Restart the CVP Server machine.

Step 1

Take back up of conf folder from c:\cisco\cvp\conf.

Step 2

Stop all services such as CVP Call Server and CVP WebServiceManager.

Step 3

From C:/Cisco/CVP/bin/TAC, run reimage.bat as reimage.bat 2>Error.txt.

Step 4

Restart the CVP Server machine.

Step 1

Copy the new image from the remote TFTP server into flash memory, making sure that you specify your own TFTP server's IP address and Cisco IOS filename.

Step 2

Verify that the new image was downloaded.

Step 3

Boot using the new image. Update the gateway config to boot using the new version.

Step 4

Reload the gateway to use the new image.

Step 1

Open a browser window on the PG machine.

Step 2

Enter the URL for the Unified Communications Manager Administration utility: http://<Unified Communications Manager machine name>/ccmadmin.

Step 3

Enter the username and password that you created while installing and configuring the Unified Communications Manager.

Step 4

Choose Application > Plugins. Click Find.

Step 5

Click the link next to Download Cisco JTAPI for Windows.We recommend you to download the 64 bit version. However, if you have already downloaded the 32 bit version, you can proceed to step 7.

Step 6

Choose Save and save the plugin file to a location of your choice.

Step 7

Open the installer.

Step 8

In the Security Warning box, click Yes to install.

Step 9

Choose Next or Continue through the remaining Setup screens. Accept the default installation path.

Step 10

When prompted for the TFTP Server IP address, enter the CUCM IP address.

Step 11

Click Finish.

Step 12

Reboot the machine.

Step 1

Use Unified CCE Service Control to stop the Logger and Distributor services.

Step 2

Login to SQL Server Management Studio and run the following queries on the primary database.

Step 3

Restart the SQL Services.

Step 4

Start the Logger and Distributor services.

Run the following command to enable trace flag 692 on HDS database server :

Step 1

Launch the vSphere Web Client using the browser.

Step 2

Log in to the vCenter Server.

Step 3

Right-click on the VM, and select the menu option Compatibility > Upgrade VM Compatibility.

Step 4

In the Compatible with field, select ESXi 6.0 and later.

Step 5

Click Ok.

Step 6

Power on the VM.