Modular Messaging. Release 4.0 Service Pack 4. Whitepaper: Support for Active Directory and Exchange 2007 running on Windows Server 2008 platforms.

Transcription

1 Modular Messaging Release 4.0 Service Pack 4 Whitepaper: Support for Active Directory and Exchange 2007 running on Windows Server 2008 platforms. April 2009

2 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document might be incorporated in future releases. Documentation disclaimer Avaya Inc. is not responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. Customer and/or End User agree to indemnify and hold harmless Avaya, Avaya s agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation to the extent made by the Customer or End User. Link disclaimer Avaya Inc. is not responsible for the contents or reliability of any linked Web sites referenced elsewhere within this documentation, and Avaya does not necessarily endorse the products, services, or information described or offered within them. We cannot guarantee that these links work all the time and we have no control over the availability of the linked pages. Copyright Except where expressly stated otherwise, the Product is protected by copyright and other laws respecting proprietary rights. Unauthorized reproduction, transfer, and or use can be a criminal, as well as a civil, offense under the applicable law Trademarks Avaya and the Avaya Logo are trademarks of Avaya Inc. and might be registered in certain jurisdictions. Unless otherwise specified, all trademarks identified by and are registered trademarks or trademarks, respectively, of Avaya Inc. Microsoft is a registered trademark of Microsoft Corporation. All other trademarks are the properties of their respective owners. Aria, AUDIX, Avaya, DEFINITY, INTUITY, and Serenade are registered trademarks of Avaya Inc. COMPAS and Mailbox Manager are trademarks of Avaya Inc. All non Avaya trademarks are the property of their respective owners. Avaya support Avaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone number is in the United States. For additional support telephone numbers, see the Avaya Support Web site: 2 Avaya Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy.

3 Purpose of this document This whitepaper addresses the issues and the suggested resolutions for customers of Modular Messaging who are wishing to install Active Directory and Exchange 2007 SP1 on Microsoft Windows Server 2008 platforms. Support for this configuration has been announced with the release of MM4.0 Service Pack 4 Patch 2. April

4 Known Issues The following issues have been identified and solutions discussed in the sections below: Upgrading Exchange Server 2007 from Windows Server 2003 to Windows Server 2008 Limitation of NSPI connections Active Directory schema updates Subscriber Administration Troubleshooting TUI and WSO for logon failures Upgrading Exchange Server 2007 from Windows Server 2003 to Windows Server 2008 Modular Messaging uses Microsoft Exchange server as a unified message store. Microsoft Exchange Server 2007 Service Pack 1 includes many new features and improvements; one new improvement is support for the Windows Server 2008 operating system. Problem Description An existing Exchange 2007 server running on Windows Server 2003 cannot be upgraded to Windows Server 2008 by doing an in place upgrade of the operating system. Exchange 2007 SP1 can be installed on Windows Server 2008, but Windows Server 2008 cannot be installed on Exchange 2007 SP1. This means that all computers running Exchange 2007 SP1 must have Windows Server 2008 already installed before Exchange can be installed on the system. Resolution To resolve this issue, there are two supported processes for migrating a computer that is running Exchange 2007 SP1 on Windows Server 2003 to Windows Server 2008: installing a new server and then migrating the data, or rebuilding the existing server from scratch and migrating or restoring the data. 1. Installing a New Server or Cluster This process involves building a new server or cluster and then using data migration mechanisms, such as mailbox moves and public folder replication, to migrate the data from the old server to the new server. 2. Rebuilding the Existing Server or Cluster from Scratch a. Stand alone server : For a stand alone server, this process involves preserving existing data, removing any third party applications, uninstalling Exchange, uninstalling Windows PowerShell, upgrading Windows Server 2003 to Windows Server 2008, installing PowerShell and other 4 Avaya Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy.

5 prerequisites for Windows Server 2008, installing Exchange 2007 SP1, using database portability or backup and restore to migrate the data, reconfiguring the server, and finally reinstalling third party applications. b. Clustered mailbox server: For a clustered mailbox server, this process involves uninstalling Exchange and Windows PowerShell from a passive node in the cluster, and then evicting that node from the cluster. When the node has been evicted, you can perform a fresh install of Windows Server 2008, install the prerequisites, and then create a new failover cluster with that node. For complete details on how to perform the Exchange Server 2007 migration activity, refer to: us/library/cc aspx NSPI Connections The Name Service Provider Interface (NSPI) Protocol provides messaging clients a way to access and manipulate addressing data stored by a server. The NSPI server implemented on Windows Server 2008 limits the number of simultaneous NSPI connections from a single client. Problem Description When the NSPI connection from Outlook fails, the server returns the following error: MAPI_E_LOGON_FAILED. In some cases, a credential dialog box may appear when the error is encountered. This behavior occurs because Windows Server 2008 only allows for a default maximum of 50 concurrent NSPI connections per user to any domain controller. Additional NSPI connections are rejected with a MAPI_E_LOGON_FAILED error. Microsoft has issued a Knowledge Base Article, KB949469, regarding NSPI connection failures from Outlook clients to a Windows Server 2008 based domain controller. Resolution To resolve this issue, the number of allowed NSPI connections must be increased. You can change this by modifying the registry on Domain Controller.! CAUTION: You will have to reinstall your Windows operating system if you modify the registry incorrectly by using Registry Editor or by using another method. To change the concurrent NSPI connections per user, you can change the default limit. To do this, perform the following steps: 1. Log on to the domain controller. 2. Click Start > Run. Type regedit and click OK. April

6 3. In the Registry Editor, locate and click the following registry key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS 4. From the Edit menu, select New > Key. 5. Type Parameters, and press ENTER. 6. Select the Parameters key. 7. From the Edit menu, select New > DWORD Value. 8. Type NSPI max sessions per user, and press ENTER. 9. Double click NSPI max sessions per user, type the value as 0xffffffff, and then click OK. 10. Exit the Registry Editor. 11. Perform the steps 1 to 10 on each 2008 Domain Controller in the domain. For complete details on how to increase the number of NSPI connections, refer to: Active Directory Schema Update As part of installing the Modular Messaging product for the first time in any Active Directory forest, the Active Directory schema is modified to allow replication of basic Modular Messaging subscriber data to all Global Catalog servers. Refer to the Updating the Active Directory and data schema procedure from Chapter 4: Preparing to install Modular Messaging software of the Modular Messaging for Microsoft Exchange Release 4.0 Installation and Upgrades guide. This guide is available here: Problem Description The Modular Messaging setup executable fails when you run the Active Directory Schema updates option on the Windows Server 2008 based domain controller. The scenario on which Active Directory Schema Update fails is as follows: 1. Active Directory installed and configured on Windows Server 2008 machine. 2. Execute Setup.exe to perform Active Directory schema updates. 6 Avaya Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy.

7 3. This causes the crash of Setup.exe. April

8 Resolution To resolve this issue, you must do the Active Directory Schema update from any other machine in the domain; it can even be a Windows Server 2008 member server without the domain controller role. To complete this update, perform the following steps: 1. Log on to the system using an account that has permission to do Active Directory and data schema administration. This is usually the Windows domain administrator account. The account must have both Domain Admin and Schema Admin rights. 2. Insert the Avaya Modular Messaging Application Server Software media (disk 1) into the DVD drive of the system. 3. Run the Modular Messaging Installation Wizard as follows: 8 Avaya Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy.

9 a. Navigate to the Install directory on the DVD drive. b. Double click the file Setup.exe. 4. On the main screen, verify that the Configuration drop down box shows Microsoft Exchange. 5. Click the plus sign (+) to expand the Active Directory updates folder. 6. Select the following checkboxes to install the appropriate software components to support Modular Messaging: a. Enable Modular Messaging b. Enable User Administration 7. When all required components are selected, click Install. Configuration Tested The verification of the Active Directory Schema Update problem is done with the following configuration: Active Directory installed on Windows Server 2008 Exchange 2007 SP1 (64 bit) installed on Windows Server 2008 Messaging Application Server (MAS) is installed on Windows Server 2003 Active Directory Schema update executed from MAS Subscriber Administration The Subscriber Administration extensions add a Modular Messaging property page in the Active Directory Users and Computers for each user that is assigned a mailbox. This tool allows administrators to set up and administer Modular Messaging accounts, configure subscriber properties, and run the MM Client software (the Subscriber Options package). Refer to the Chapter 5: Adding Exchange extensions for Modular Messaging of the Modular Messaging for Microsoft Exchange Release 4.0 Installation and Upgrades guide. Problem Description The Modular Messaging tab does not get displayed when Subscriber Administration is installed on the Windows Server 2008 based Active Directory. The problem occurs while installing Subscriber Administration on Windows Server 2008 based Active Directory as well as after upgrading Active Directory from Windows Server 2003 to Windows Server April

10 Resolution To resolve this issue, you install Subscriber Administration on any other machine in the domain; it can even be a Windows Server 2008 member server without the domain controller role. To install Subscriber Administration, perform the following steps: 1. Logon to the system in the domain. 2. Insert the Avaya Modular Messaging Application Server Software media (disk 1) into the DVD drive of the system. 3. Run the Modular Messaging Installation Wizard as follows: a. Navigate to the Install directory on the DVD drive. b. Double click the file Setup.exe. 4. On the main screen, verify that the Configuration drop down box shows Microsoft Exchange. 5. Click the plus sign (+) to expand the Active Directory / Exchange 2000 extensions. 6. Click Subscriber Administration box and click Install. 7. When installation is finished, click Close. 8. If you are prompted to restart the system, click Restart. 9. Click Start > Programs > Administrative Tools > Active Directory Users and Computers. 10. In the left pane, click Users. 11. In the right pane, locate the MM user and double click it. 12. In the Properties window, Modular Messaging tab does get displayed. Troubleshooting TUI and WSO for logon failures: A telephone user interface (TUI) provides subscribers and callers the access to Modular Messaging, from a touchtone telephone. Web Subscription Options (WSO) is a web based interface for users to manage their mailbox configuration settings, including greetings, passwords, schedules, mobility options, notification rules, languages, time zone and personal distribution lists. Problem Description It has been noticed that in some Windows 2008 environments, the detection of the Peer Exchange server can take longer than allowed for during the start up of the MAS. If this occurs then some features will not function as expected. In such configurations following issues may occur: 1. TUI: When you login to any mailbox of subscriber using AUDIX or Serenade TUI; you will get error prompt as This call is experiencing difficulties. Please try again later. Please disconnect. 2. WSO: 10 Avaya Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy.

11 a. When you login to WSO for any subscriber the Options > Options summary page and Notification > MWI page displays error as An error occurred during last operation. Try the operation again. If the problem persists, contact your system administrator. b. When you login WSO for any subscriber the Caller Experience > Find Me page displays error as Your Class of Service does not allow access to the Find Me page. c. When you login WSO for any subscriber the Notification > Call Me page displays error as Your Class of Service does not allow access to the Call Me page. Resolution To resolve this issue, the number of minutes required for connecting MAS to the peer Exchange server must be specified in the registry.! CAUTION: You will have to reinstall your Windows operating system if you modify the registry incorrectly by using Registry Editor or by using another method. The default time for the detection of peer Exchange server while MAS start up is 3 minutes. To increase the default duration, perform the following steps: 1. Log on to the MAS. 2. Click Start > Run. Type regedit and click OK. 3. In the Registry Editor, locate and click the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Octel\Geneva\TUIServiceMgr 4. Select the TUIServiceMgr key. 5. From the Edit menu, select New > DWORD Value. 6. Type WaitForPeerToComeOnline, and press ENTER. 7. Double click WaitForPeerToComeOnline, type the value in minutes and then click OK. 8. Exit the Registry Editor. You can calculate the time required to set in the registry by referring the following guidance: The duration to be set will be the difference between the time MAS service started (Event ID: 1010) and Messaging subsystem switched to online mode (Event ID: 1320) events appear in the event logs. April