CXM 4.5 Deployed on Windows Chad Adams October 28, 2009

Transcription

1 CXM 4.5 Deployed on Windows 2008 By Chad Adams October 28, 2009

2 This document describes issues and resolutions encountered when testing CXM on Windows 2008 (32-bit) and Windows 2008 (64-bit). CXM on Windows bit Member Server Server Configuration The remaining content of this section comes from testing CXM on the CXM45_2K8 virtual machine on my desktop. Following are the details of this virtual machine: Domain: TESTBED Machine name: CEVMCXM452K8 OS: Windows 2008 (32-bit) SQL Server 2005 Local users for this machine are cxmservices (password: Stapler2000) and tightass (password: Stapler2000). Cxmservices is in the local Administrators Group. SQL Authentication for the database is sa (password: Stapler2000). IIS 7.0 Crystal Reports 2008 UAC and Installers With this server configuration, typically the CXM servers will exist in the customer s domain, and CXM will run under a local account on the server(s). This local account, which will be referred to as the cxmservices account throughout this document, must be configured correctly. The cxmservices account must be a member of the local, or machine s, Administrators Group. However, even though cxmservices is a member of the local Administrators Group, you will not be able to successfully run the CXM_45_Web_Application Installer nor the CXM_45_Services Installer. These installers run custom actions that require elevated rights. The built-in local administrator account has these elevated rights. Thus, the CXM_45_Web_Application Installer and the CXM_45_Services Installer will run successfully when ran under the built-in local administrator account. If the client refuses to let CXM log-in as the local administrator, then the cxmservices account can be configured to allow us to run the CXM installers. The client will need to log-in as the local administrator, and do the following: turn off UAC, disable Admin Approval Mode, disable UAC from prompting for credentials to install applications, and change the elevation prompt behavior for administrators. To turn off UAC:

3 1. Click Start, and then click Control Panel. 2. In Control Panel, click User Accounts. 3. In the User Accounts window, click User Accounts. 4. In the User Accounts tasks window, click Turn User Account Control on or off. 5. If UAC is currently configured in Admin Approval Mode, the User Account Control message appears. Click Continue. 6. Clear the Use User Account Control (UAC) to help protect your computer check box, and then click OK. 7. Click Restart Now to apply the change right away, or click Restart Later and close the User Accounts tasks window. To disable Admin Approval Mode: 1. Click Start, click All Programs, click Accessories, click Run, type secpol.msc in the Open box, and then click OK. 2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.. 3. From the Local Security Settings console tree, double-click Local Policies, and then double-click Security Options. 4. Scroll down and double-click User Account Control: Run all administrators in Admin Approval Mode. 5. Select the Disabled option, and then click OK. 6. Close the Local Security Settings window. To disable UAC from prompting for credentials to install applications: 1. Click Start, click All Programs, click Accessories, click Run, type secpol.msc in the Open text box, and then click OK. 2. From the Local Security Settings console tree, click Local Policies, and then Security Options. 3. Scroll down and double-click User Account Control: Detect application installations and prompt for elevation. 4. Select the Disabled option, and then click OK. 5. Close the Local Security Settings window. To change the elevation prompt behavior for administrators: 1. Click Start, click Accessories, click Run, type secpol.msc in the Open box, and then click OK. 2. From the Local Security Settings console tree, click Local Policies, and then Security Options. 3. Scroll down to and double-click User Account Control: Behavior of the elevation prompt for administrators. 4. From the drop-down menu, select the following setting: Elevate without prompting (tasks requesting elevation will automatically run as elevated without prompting the administrator). 5. Prompt for consent (default setting for administrators) 6. Click OK. 7. Close the Local Security Settings window.

4 After CXM installers are ran, then the above settings can be set back by the local administrator, and CXM will still function correctly running under the cxmservices account. Machine name not appearing in logon dialogs The following issue was encountered during testing on this configuration: the logon information dialogs do not show the computer name. Thus, the logon accounts for the web applications and the services cannot be set to MACHINE\cxmservices. In order for these dialogs to work correctly, the computer browser service must be running. If the computer browser service will not start, then either turn off the windows firewall or disable File and Print sharing services for the network connection. Give the system about 5 minutes before again running the installers. CXM Media Player Application Pool The CXM_45_Web_Application installer will create the following application pool: CXMMediaPlayerAppPool. The CXM Media Player Web Service runs in this app pool. In order for this web service to use the CXM4 DSN, the CXMMediaPlayerAppPool will need to run under the local system account. Even though the CXM_45_Web_Application installer sets this app pool to run under the local system account, it is important to know for troubleshooting purposes.

5 CXM on Windows bit domain controller Server Configuration The remaining content of this section comes from testing CXM on the machine TESTBEDWEBSTORE. Following are the details of this machine: TESTBEDWEBSTORE is the domain controller for the domain TESTBED.local Administrator password for the TESTBED domain is C0nexus Regular user account for the TESTBED domain is cxmservices (password: Stapler2000) OS: Windows 2008 (64-bit) SQL Server 2008 installed System Administrator (sa) password for SQL is Stapler2000 Another sql account is cxmdb (password: Hiphop2000) TESTBED\cxmservices has rights to the CXM4 db Local administrator password is Stapler2000 IP Address is Mite lip recorder is installed and configured IIS 7.0 Crystal Reports 2008 Granting TESTBED\cxmservices rights to CXM4 db In SQL Server 2008, do the following: 1. Go to Security -> Logins. 2. Right-click Logins, and select New Login 3. For the Login name, use the Search dialog to select TESTBED\cxmservices account. 4. Make sure Windows authentication is selected. 5. Under Select a page, click User Mapping. 6. Under Users mapped to this login:, check the CXM4 database. 7. Under Database role membership for: CXM4, check db_owner and public. 8. Click OK. Current identity does not have rights issue Opening the CXM user-interface, you get the following screen:

6 To resolve, navigate to the web.config and comment out the impersonate tag. When any of the CXM web applications are running in IIS 7.0, the impersonate tags in the web.configs are no longer needed. The CXM_45_Web_Application installer comments out the impersonate tag when ran on Windows This issue is noted for troubleshooting purposes, and this issue could occur on Windows 2008 (32-bit); this issue is not specific to Windows 2008 (64-bit). Crystal Reports Registry Key Permission Issue Running a report yields:

7 Currently, this issue appears to only happen on Windows 2008 (64-bit) servers. To resolve: 1. Open up IIS 7.0 and expand the main node. 2. Click Application Pools. 3. Right-click on the application pool that crystal reports is running under. This should be the CXMUIAppPool. 4. Select Set Application Pool Defaults 5. Set Enable 32-bit Applications to True. Below is this setting from TESTBEDWEBSTORE: Currently, the CXM_45_Web_Application installer does not set this. Further research is needed. Cannot Add Event with CXM Media Player CXM Media Player displays the following when trying to add an event to a call:

8 This error is caused by the identity impersonate tag in the web.config for the CXM Media Player web service. To resolve this issue, comment out this tag. The web.config file for the CXM Media Player web service can be found at c:\inetpub\wwwroot\cxmmediaplayerservice. After completing the above, you may now get the following: To resolve: 1) Create a new application pool in IIS 7.0 named something like CXMMediaPlayerServiceAppPool. 2) Under Application Pools, click the app pool, then click Set Application Pool Defaults 3) In the properties dialog under the Process Model, set Identity to LocalSystem. The CXM_45_Web_Application installer creates this application pool with the correct settings. The description of this issue is provided for troubleshooting purposes. CXM Live Monitor Will Not Connect Clicking connect in CXM Live Monitor, a client application, results in the following:

9 This error occurs because port 5670 on the CXM Webstore is blocking packets sent by the CXM Live Monitor client application. To resolve, from the CXM webstore do the following: 1. Go to Windows Firewall with Advanced Security. 2. Right-click Windows Firewall with Advanced Security on Local Computer. 3. On the Domain Profile tab, for State, set inbound connections to Allow. Following will work too, and is probably the recommended way: 1. Go to Control Panel, then go to the Network and Sharing Center. 2. Click on the Windows Firewall link (Under See Also). 3. In windows firewall, click Allow a program through Windows Firewall. 4. In Windows Firewall Setting dialog, click the Exceptions tab.

10 5. Click Add Port and you should see the selected dialog below: 6. Add a port as follows: Name: cxmlivemonitor Port number: 5670 Protocol: TCP Note: the audio stream goes out over udp ports 30,000 to 31,000. CXM_45_Services Installer hangs If running the services installer and the Avaya DMCC recorder is selected to install, then the installer may appear to hang during the execute sequence of the install. Actually, the windows installer dialog is blocking an Avaya CT setup dialog, and the execute sequence will not continue until the Avaya CT dialog is completed. To resolve, select the windows installer dialog and drag it out of the way, then complete the Avaya dialog. This is a known issue, specific to Windows 2008.

11 Not All Services Uninstall Uninstalling services via Add/Remove may not uninstall all services. This is a known issue. Please use srvinstw.exe to uninstall the services that are not removed. More Testing Following scenarios, among others, still need to be tested: 1. Separate recorder on Windows 2008, particularly to see how MSMQ will behave. 2. Screen capture server on Windows 2008 (64-bit). 3. Client applications on a Windows 7 desktop, not virtual machine. 4. Archiving on TESTBEDWEBSTORE. 5. Brightstor 12 on Windows 2008 (64-bit). 6. LDAP authentication against TESTBEDWEBSTORE.

12 Sources Configuring UAC and elevated rights: