Microsoft Windows Server 2008 R2 SP1 staging - Cisco

Microsoft Windows Server Staging This section does not provide step-by-step instructions for all tasks related to Microsoft Windows. For such information, see the corresponding Microsoft documentation.

Note

Important

In the current release, you must deploy Unified ICM/CCE & Hosted in a virtualized environment. See the Virtualization for Unified CCE pages on the DocWiki for more information. • Drive Partition Guidelines, page 1 • Windows Setup Guidelines, page 2 • Join Standalone Servers to Domain in Windows Server , page 4 • Network Card Settings, page 5 • Persistent Static Routes, page 6 • Collect Existing SNMP Properties, page 6 • Display Settings, page 8 • System Properties, page 8 • Configure Event Viewer, page 9 • Connectivity Validation, page 9

Drive Partition Guidelines Create drive partitions for the servers being built according to settings in the Unified ICM/Cisco Unified Contact Center Enterprise System Design Specification. Format C drive as NTFS.

Staging Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted, Release 10.0(1) 1

Microsoft Windows Server Staging Logger or Administration and Data Server Partition Guidelines

Note

You might need to use the manufacturer's drive partitioning/RAID array software to set up the partition.

Logger or Administration and Data Server Partition Guidelines For servers hosting a Logger or Administration & Data Server (Historical Data Server (HDS)), use the following guidelines for partitioning: • Use the C drive for the operating system, virtual memory paging file space, core Unified ICM, Microsoft SQL Server, and Microsoft SQL Server's log and temp files. • Use the D drive to store the Logger or Historical Data Server database.

Note

Keep the Microsoft SQL Server temp and log files on the C drive to maximize database performance.

Partition Guidelines for Other Contact Center Components For servers hosting a Router, Peripheral Gateway, Administration & Data Server (non-Historical Data Server), CTI Server, and CTI OS Server, use a single partition C drive for the operating system, virtual memory paging file space, core Unified ICM software, the Administration & Data Server database, Microsoft SQL Server, and Microsoft SQL Server's log and temp files.

DVD Drive Assign the letter Z to the DVD drive. While this is not mandatory, it provides consistency.

Windows Setup Guidelines Note

For additional information on installing Microsoft Windows Server, see the Windows Server homepage. Use the following guidelines when setting up a Windows Server for Unified ICM: • When setting the time zone, ensure all Central Controller systems are set for the same time zone regardless of their physical location. • Ensure the time zone is set the same on PG A and PG B for all peripheral gateway pairs to enable synchronization of Unified ICM Message Delivery Service (MDS) processes. • For Network Settings, enter the server's respective IP and DNS data according to the System Design Specification. • For the Public Ethernet Card, perform the following tasks:


Microsoft Windows Server Staging Enable SNMP Management on Windows Server

◦To enter the data for visible IP addresses, subnet mask, default gateway and preferred and alternate DNS servers for the server, click Start > Control Panel > Network and Sharing > Change Adapter Settings and then right-click on the Visible network Properties > Internet Protocol version 4 (TCP/IPV4), and select Properties. ◦In the Advanced tab, enter the “high” visible addresses. ◦In the DNS tab, for DNS suffix for this connection, enter the name of the local DNS zone for the server and check Register. ◦If the server requires access to resources in a different trusting or trusted domain or DNS zone, select append these DNS suffixes (in order) and enter the local DNS zone for the server first, then add the other secondary zones which represent the trusting or trusted domain. • If the server has more than one network interface card, for the Private Ethernet Card click Start > Control Panel > Network and Sharing > Change Adapter Settings, right-click on the Private network and select Properties, and perform the following tasks: ◦Uncheck the Client for Microsoft Networks and the File and Print Sharing options. ◦For TCP/IP properties, enter the private IP address and subnet mask for the server. Leave the default gateway field blank. ◦In the Advanced tab, enter the “high” private addresses. ◦In the DNS tab, leave the address space empty and uncheck Register. • Because the ICM does not support IP V6, disable IPV6 on all the Ethernet cards. On the Adapter Settings dialog, right-click the card and select Properties. Uncheck Internet Protocol Version 6 (TCP/IPV6). Related Topics Enable SNMP Management on Windows Server, on page 3 Persistent Static Routes, on page 6

Enable SNMP Management on Windows Server Unified ICM/CCE/CCH SNMP support automatically installs during the course of normal setup—you do not need to take extra steps during setup to enable SNMP support. The Microsoft Windows SNMP service is disabled as part of web setup and is replaced by the Cisco Contact Center SNMP Management service to process SNMP requests in its place. However, you must install Microsoft Windows SNMP optional components on Unified ICM/CCE/CCH servers for any SNMP agents to function. The Microsoft SNMP components are required for Cisco SNMP support, and you must be install these components before you install any Unified ICM/CCE/CCH components that require SNMP monitoring. To install Microsoft SNMP components:


Microsoft Windows Server Staging Join Standalone Servers to Domain in Windows Server

Procedure Step 1 Step 2 Step 3

Choose Start > Control Panel then click Programs. Click Turn Windows features on or off and select the necessary Management and Monitoring Tools by clicking Features in the left pane, and then clicking Add Features in the right pane. Check SNMP Services: The following are selected: • SNMP Service • SNMP WMI Provider

Step 4

Click Next then Install.

Related Topics Collect Existing SNMP Properties, on page 6

Join Standalone Servers to Domain in Windows Server The following components must be installed on servers that are members of the domain: • Logger • CallRouter • Administration & Data Servers

Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6

Click Start, right-click Computer and choose Properties. In the section “Computer name, domain, and workgroup settings” click Change settings. Click Change. In the “Member of” section, select Domain then enter the Fully Qualified Domain Name and click OK. Enter the Domain Administrator's username and password. Reboot the server and sign in to the domain.


Microsoft Windows Server Staging Network Card Settings

Network Card Settings Note

Consult your Microsoft Documentation for Windows Server. Also see the Virtualization for Unified CCE DocWiki

Procedure Step 1 Step 2 Step 3

From the menu bar, click Start > Control Panel > Network and Sharing. Right-click on each type of network and rename each Local Area Connection to “private”, “visible”, and “san” (Signaling Access Network) as required. Use the following guidelines to configure network card settings: • Right-click on the network card and select Properties. • Select the Configure tab, and in the Advanced tab of the connection properties, configure the network (link) speed and duplex mode as follows: ◦100 Mb NIC: set both the NIC and the switch to 100/Full ◦100 Mb switch: set both the NIC and the switch to 100/Full ◦100 Mb NIC and 100 Mb switch: set both to 100/Full ◦Gigabit NIC and Gigabit switch: ensure both are set to Auto/Auto

Step 4

Use the following guidelines to configure binding: • Click Start > Control Panel > Network and Sharing. • From the menu bar (press CTRL+N to display the advanced menu), select Advanced > Advanced Settings. The Advanced Settings dialog box appears. • In the Advanced tab, perform the following tasks: ◦In the Connection section of the Adapters and bindings tab, sort the section so that the Visible connection is at the top, the Private connection is second, and any remaining connections follow. ◦For the Private connection, uncheck File and Printer Sharing for Microsoft Networks and Client for Microsoft Networks. ◦Move any disabled Bindings for all connections to the bottom of the list.

Step 5

Use the following guidelines to enable the NETBIOS setting: • Click Start > Control Panel > Network and Sharing > Change Adapter Settings. • Right-click on the visible network and select Properties. • Uncheck Internet Protocol Version 6 (TCP/IPV6). • Highlight Internet Protocol version 4 (TCP/IPV4) and select Properties.


Microsoft Windows Server Staging Persistent Static Routes

• Click the Advanced tab. • Click the WINS tab. • Click Default on the Netbios setting to ensure it is enabled (causing LicenseAdmin.exe for CAD to launch). • Confirm that Register this connection's addresses in DNS is unchecked if this is the Private NIC.

Persistent Static Routes For geographically distributed Unified ICM Central Controller sites, duplexed CallRouter, Logger, and Peripheral Gateway components have a Private IP WAN connection, used to communicate between Side A and Side B. Because Windows only allows one default gateway for each server (which sends the Private Network traffic to the Visible Network), you must add a set of Static Routes to all the servers running the CallRouter, Logger, and Peripheral Gateway. On CallRouter, Logger, and Peripheral Gateway servers, enter route add mask -p. For example: • On Side A servers, enter route add 192.168.142.42 mask 255.255.255.192 192.168.141.126 -p. On Side B servers, enter route add 192.168.141.64 mask 255.255.255.192 192.168.142.126 -p. • Where: ◦The network number of the remote Private Network is 192.168.142.42 ◦The subnet mask for this remote network is 255.255.255.192 ◦The gateway address for the Private Network Adaptor is 192.168.141.126

Note

The -p option sets the route as persistent.

Collect Existing SNMP Properties If you already installed and configured SNMP management support for this server, you must collect the existing configuration parameters so they can be used to configure the components installed by Web Setup. You can find these parameters on the property sheets associated with the Microsoft SNMP Service.


Microsoft Windows Server Staging Collect Existing SNMP Properties

Note

For Windows Server, to view the SNMP Agent Management snap-in, you must use the 32-bit Microsoft Management Console Snap-In. To launch the 32-bit Snap-in, run mmc /32. For detailed instructions for Windows Server, consult your Microsoft Documentation. To collect existing SNMP properties:

Procedure Step 1

On the Services MMC console, do one of the following: • Locate and select the SNMP Service in the list, or • Choose Start > Programs > Control Panel > Administrative Tools > Services.

Step 2

On the SNMP Service Properties dialog box, select the Security tab. Note the following settings and configuration data: • The state of the Send authentication trap check box. • The Accepted community names. • If Accept SNMP packets from these hosts is checked, collect the host names or IP addresses configured in the associated list box. Note

Step 3

If host names (versus IP addresses) have been configured, you need to determine the actual IP address of that host in order to configure the Cisco SNMP agents. For security reasons, using static addresses for management stations is preferred.

Select the Traps tab on the SNMP Service Properties dialog box. Collect the configured trap destinations and the associated community name. If host names were for trap destinations, you need to determine the actual IP address of that host. On the SNMP Service Properties dialog box, select the Agent tab. Collect the information from the Contact and the Location fields. Note

Step 4

What to Do Next If the server has not been configured for SNMP manageability, do the following: 1 Determine whether SNMP manageability is required. 2 Acquire the necessary configuration information to enable SNMP access. The necessary configuration information includes: • The IP addresses of the management station. • If using SNMP v1 or SNMP v2c: ◦Community names (if using SNMP v1 or SNMP v2c) ◦Trap destinations and the community name expected by each management station


Microsoft Windows Server Staging Display Settings

• If using SNMP v3: ◦Usernames ◦Authentication protocol used (if authentication is required) ◦Privacy protocol used (if privacy is required) ◦Trap destinations and the username expected by each management station The installed Microsoft Management Console Snap-In (Cisco SNMP Agent Management) is used to configure the SNMP properties. See the SNMP Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted at http://www.cisco.com/en/US/products/sw/custcosw/ps1844/products_installation_and_configuration_guides_ list.html for more details.

Display Settings Through the Windows Control Panel Display dialog box: • Ensure that no screen saver is selected. • Set the Administration & Data Server display for at least 1024 by 768 pixel resolution. • Set at least 65K colors and at least 60 MHz.

System Properties For Virtual memory settings: • Click Start > Control Panel > System > Advanced System Settings > Peformance > Advanced > Virtual Memory. • Next, select Change and set the initial and maximum total paging file sizes to appropriate values based on the system memory. See Microsoft's documentation for guidance on page file sizes. For Startup and Recovery settings: • Click Start > Control Panel > Advanced System Settings > Startup and Recovery > Settings. • Next, set the value of the Time to display list of operating systems to 3 seconds.

Note

Click Start > Control Panel > System > Advanced System Settings > Performance > Advanced and confirm that the Adjust for best performance option is set to either Programs or Background Services.


Microsoft Windows Server Staging Configure Event Viewer

Configure Event Viewer Procedure Step 1

For each type of event, set the Maximum log size to 8192 KB.

Step 2

Select Overwrite events as needed.

Note

See the Security Best Practices Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted available at http://www.cisco.com/en/US/products/sw/custcosw/ps1844/prod_technical_reference_list.html for additional information.

Connectivity Validation Before you begin the Unified ICM installation process, you must validate network connectivity for all servers that are part of the Unified ICM system. On each server: • Validate the TCP/IP properties for each network card, including the DNS settings. • Validate that you can ping each machine on the visible network. • If applicable, validate that you can ping each private network connection. • Test remote access. Related Topics System Design Specification


Microsoft Windows Server Staging Connectivity Validation
