Welcome to the Microsoft Office Communications Server 2007 Release Notes. Refer to this file for information regarding known issues about Setup, management, and Office Communications Server 2007 server roles, including Communicator Web Access (2007 release).
© 2007 Microsoft Corporation. All rights reserved.
This document contains important information that you should know before you deploy and use Microsoft Office Communications Server 2007 and Communicator Web Access (Office Communications Server 2007 Release). For detailed information about Office Communications Server 2007, refer to the Office Communications Server 2007 documentation.
Issue: QFEs are required for Office Communications Server 2007.
Resolution: Install the available hotfixes. See the following Microsoft knowledge base for more information for installing QFEs on all Office Communications Server:
http://support.microsoft.com/kb/923028
http://support.microsoft.com/kb/917949 (This fix is included in Windows 2003 SP2 and later.)
http://support.microsoft.com/kb/920606 (This fix is included in Windows 2003 SP2 and later.)
http://support.microsoft.com/kb/894070 (This fix is included in Windows 2003 SP2 and later.)
For Office Communications Server 2007 and Live Communications Server 2005 with Service Pack 1 coexistence, the following QFEs are required on all Live Communications Server 2005 SP1 servers http://support.microsoft.com/default.aspx?scid=kb;EN-US;911996 and http://support.microsoft.com/kb/921543/.
Issue: When you try to activate a newly created service account, activation fails. Activation of the server fails if the account has not finished Active Directory Domain Services replication.
Workaround: Create the service accounts that you want to use before you run Setup. Ensure that you allow enough time for replication of the Active Directory Domain Services to complete. If you created the service account during the activation process, retry activation after allowing time for Active Directory replication to complete.
Issue: In an evaluation version of Office Communications Server, on the Deployment Wizard home page, if you click Install Standard Edition or Install Enterprise Edition in setup and click Save in the File Download Dialog, the following error is displayed:
Unable to launch Office Communications Server 2007 Deployment Tool – The system cannot find the file specified
Resolution: Click the installation link and choose Run instead of Save.
Issue: Microsoft Internet Acceleration and Security Server (ISA) requires that the subject name appear as the first entry in the list of subject alternate names (SAN) list in a certificate. However, the Office Communications Server Certificate Wizard does not put the subject name as the first entry in the SAN list. If your organization uses ISA as the reverse proxy for external user access, and you use the Office Communications Server Certificate Wizard on the pool or Standard Edition Server configured to redirect and authenticate client sign-in requests to generate the certificate request for a Web Components Server, the certificate request generated does not include the Web Components Server FQDN as the first entry in the Subject Alternate Name list. Hence, ISA is not able to connect to the Web Components Server and any external scenarios that require access to the HTTP reverse proxy (address book download, distribution group expansion and access to meeting content, or Communicator Web Access) may not work.
Resolution: None.
Workaround: When you generate a certificate request for the Web Components Server using the Office Communications Server certificate wizard, make sure that the Subject Name is the first FQDN in the Subject Alternate Name list, or that the Subject Alternate Name list is blank.
Issue: You can run the Create Pool wizard or command line option on a Front End Server if the SQL client tools are available on that server. When you do so, on a Front-End Server with Microsoft SQL Server 2000 client tools installed and attempt to connect to a SQL Server 2005 back-end database, the dbsetup script terminates abnormally, and the pool creation fails.
One of the following errors are displayed:
An error occurred during the pool backend detection:
Pool backend discovery failed.
SQL Server 2005 Backwards Compatibility Pack must be installed on this machine for connecting to SQL Server 2005 SP1 or later.
OR
An error occurred during the pool backend detection:
Pool backend discovery failed. [hr=0xC3EC79FA]
This can happen due to network or credential problems. Please make sure network is good and logon has sufficient permissions.
Resolution: Choose one of the following:
· Run the Create Pool task on the SQL Server back-end database
· Install the SQL Server 2005 Backward compatibility toolset on the Front-End Server.
Issue: Setup may fail if the destination folder name has non-ASCII characters (including UNICODE, double byte character set (DBCS), UTF-8, and UTF-16). Also, Setup will succeed, but the server will not start if non-ASCII characters are contained in the following:
· Computer name
· Domain name
· User name
Prevention: Use only ASCII characters in the destination folder name, domain name, and user name.
Issue IIS has a security measure that prevents loopback. When you use the fully qualified domain name (FQDN) or a custom host header to browse a local Web site that is hosted on a computer that is running Microsoft Internet Information Services (IIS) 5.1 or IIS 6, you may receive an error message that is similar to the following:
HTTP 401.1 - Unauthorized: Logon Failed
Resolution: This issue occurs when the Web site uses Integrated Windows Authentication and has a name that is mapped to the local loopback address. If you are using a load balancer for your pool and attempt to validate Web Component Server functionality, if you do not add the load balancer FQDN as a allowed FQDN for loopback, you receive the above error and validation fails. For more information, see http://r.office.microsoft.com/r/rlidOCS?clid=1033&p1=KBloop.
To allow FQDN of the VIP of your load balancer that is mapped to the loopback address and can connect to Web sites on your computer, follow these steps:
1. Click Start, click Run, type regedit, and then click OK.
2. In Registry Editor, locate and then click the following registry key:
3. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
4. Right-click MSV1_0, point to New, and then click Multi-String Value.
5. Type BackConnectionHostNames, and then press ENTER.
6. Right-click BackConnectionHostNames, and then click Modify.
7. In the Value data box, type the FQDN of your load balancer VIP, and then click OK.
8. Quit Registry Editor, and then restart the IISAdmin service.
You can remove this FQDN after the validation wizard completes.
Issue: Changing the FQDN of a server that is part of an Office Communications Server 2007 Standard Edition or Enterprise Edition pool deployment is not supported. There are various dependencies in the deployment, including servers not functioning correctly and homed users not being able to connect.
Workaround: Deactivate and uninstall the Office Communications Servers, change the FQDN of these servers as desired, and then install and activate the Office Communications Servers with the new name.
Issue: The documentation included on the product CD for the dbimpexp tool contains an error for importing. It reads as follows:
On a Standard Edition Server
dbimpexp.exe /import
/hrxmlfile:"c:\SavedUserData.xml"
For an Enterprise pool:
dbimpexp.exe /import
/hrxmlfile:"c:\SavedUserData.xml" /sqlserver:<sql server host
name>
Workaround: Use the command with the import switch:
On a Standard Edition Server
dbimpexp.exe /import
/hrxmlfile:"c:\SavedUserData.xml"
For an Enterprise pool:
dbimpexp.exe /import
/hrxmlfile:"c:\SavedUserData.xml" /sqlserver:<sql server host
name>
Issue: When running SQL 2005 SP2 on the back-end server of an Enterprise pool, over time performance can degrade and the total CPU usage increases. This is a known issue with SQL Server 2005 SP2. For more details, see http://support.microsoft.com/default.aspx/kb/927396
Workaround: Use one of the following two options:
Option 1
Use the following steps to add a SQL trace flag for T4618
1. Open SQL Server Configuration Manager: Point to Start, point to All Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Configuration Manager.
2. Select RTC SQL server instance in SQL Server 2005 Services, right click on the instance and then click Properties.
3. Click the Advanced Properties tab and Edit Startup Parameters.
4. Append ;-T4618 to the end of the Startup Parameters list (note that startup parameters are separated by semicolons).
Option 2
Or manually add the following registry value:
Name | Value
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\{0}\MSSQLServer\Parameters\SQLArgN | -T4618
(where N is the next SQL parameter number and {0} is the SQL instance name found under the following key below that maps to the RTC instance)
Name | Value
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL
Issue: Office Communications Server 2007 will not operate correctly if there are too many trusted root certification authorities (CAs) installed on an Office Communications Server. As a result communications between Office Communications Server components fails.
This issue is caused by an optional Microsoft Update release entitled Root Certificates Update.
Resolution: If you have installed this update, do the following to remove unnecessary trusted root CAs:
1. Click Start, point to Run, and then type MMC.
2. Press Enter.
3. On the File menu, click Add/Remove Snap-in.
4. Click Add.
5. Select Certificates, and then click Add.
6. Select Computer account, and then click "Next".
7. Choose Local computer and click Finish.
8. Click OK.
9. In the Certificates snap-in, navigate to Trusted Root Certification Authorities\Certificates.
10. Carefully inspect the list of trusted CAs and delete those that aren't needed.
11. Restart your server for these changes to be applied.
Issue: The Office Communications Server 2007 administrative snap-in, the Office Communications Server 2007 snap-in in Computer Management, and the Office Communications Server 2007 snap-in in Active Directory Users & Computers are not available on 64-bit operating systems by default.
Resolution: If you are using the Office Communications Server 2007 administration tools snap-in, click Start, point to Run, and then type mmc -32. This command starts the mmc.exe as a 32-bit application. Use the Add/Remove snap-in option to add the Office Communications Server 2007 administration tools snap-in.
If you are using the Computer Management snap-in (on an Edge Server for example), click Start, point to Run and then type mmc -32 compmgmt.msc. This command starts the Computer Management snap-in as a 32-bit application.
If you are using the Active Directory Users & Computers snap-in, click Start, point to Run and then type mmc -32 dsa.msc. This command starts the Active Directory Users & Computers snap-in as a 32-bit application.
Issue: Office Communications Server 2007 performance monitor counters are not available on 64-bit operating systems by default.
Resolution: Click Start, point to Run, and then type perfmon -32. This command starts the Performance Monitor as a 32-bit application. By default, the Performance Monitor runs as a 64-bit application on 64-bit operating system.
Issue: When performing cross-forest moves through Active Directory (and using a tool such as ADMT), a contact might be deleted during a move from one forest to another in either of the following scenarios:
· In a central forest in an Office Communications Server deployment if a User object is moved without carrying over the SIDHistory.
· In a Microsoft Exchange cross-forest scenario where GalSync is used to replicate users as contacts.
In both scenarios the Contact object in the central forest is deleted and recreated. This causes all the user data (SIP contacts, permissions, and contact groups) to be deleted from the “Live” Server database and a new SIP user to be created in its place. This deletion will also cause the user to be deleted from that user’s watchers contact lists.
Prevention: Before you use the Move operation, use the Dbimpexp.exe tool to export the user's data from the Office Communications Server database. Then import the user's data after the Move operation. The export/import step needs to be performed on the pool that homes the user. Watchers of the user will be prompted to re-add the user to their contact list after the user has logged on following the move.
The Dbimpexp.exe tool and documentation can be found in the %systemdrive%\Program Files\Microsoft Office Communications Server 2007\Server\Support directory.
Issue: Audio is distorted and can be unintelligible when it is transmitted by an A/V Conferencing Server that is running on a computer with multiple processors, multiple cores, or hyperthreading technology.
Resolution: Install the Windows hotfix described in the knowledge base (KB) article 896256: http://support.microsoft.com/?id=896256.
Issue: You may experience a degradation of media quality due to known issues with some hardware devices.
Resolution: See the following Microsoft Knowledge base article for a list of known issues on specific devices: http://r.office.microsoft.com/r/rlidOCS?clid=1033&p1=mediakb.
Issue: When an Office Communications Server user sets his or her presence to Do Not Disturb (DND) in Office Communicator, users on the Yahoo! public IM networks can still send instant messages and these users do not know that the Office Communications Server user cannot see these messages.
Workaround: No resolution until these issues are fixed by the Yahoo! network.
Issue: When an Office Communications Server user has an IM conversation with Yahoo! user, the Yahoo! user may see more than one pop-up window.
Workaround: No resolution until this issue is fixed by Yahoo! network.
Issue: Users hosted on public IM networks (MSN, AOL and Yahoo!) cannot join IM conferences that are hosted by Office Communications Server.
Workaround: None.
Issue: Users of Microsoft Office Communicator 2007 can invite users of previous versions of Communicator, Microsoft Windows Messenger, and Microsoft Windows Live Messenger to IM conferences. However, if a Tablet PC or other device capable of sending Tablet PC ink sends an ink-based message in the conference, the users of previous versions of Communicator and Windows Messenger will not receive the ink-based message. There is no feedback that indicates the ink-based message was not sent or received successfully.
Resolution: None in this release.
Issue: User cannot make PC to phone calls when encryption is on. This setting is controlled by the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Communicator\PC2PCAVEncryption policy is set to require encryption (with a value of 1) then PC to phone calls will fail.
Workaround: Set this registry key value to 0 or 2.
Issue: In some complex Office Communications Server 2007 topologies, such as those with multiple pools and many domains, in the VoIP properties, on the Location Profiles tab, the location profile list is not updated when you add a new location profile. When you attempt to add a new location profile and click Apply, the entry disappears.
Resolution: After adding (and saving) the location profile, close and re-open the VoIP Property Page. The data will be refreshed and the newly added entry will be visible.
Issue: You cannot install Communicator Web Access in a domain with a fully qualified domain name that contains non-ASCII characters.
Workaround: None in this release.
Communicator Web Access Activation Wizard Error
Issue: When attempting to activate a Communicator Web Access Server, you receive the following error message:
Setup has not detected Microsoft Office
Communications Server 2007 in the Domain
Workaround: Verify that you have completed all necessary prerequisites listed in the Deployment Wizard and run the wizard again.
Issue: You cannot use an underscore in the fully qualified domain name of Communicator Web Access if you are using Integrated Windows Authentication and Windows Internet Explorer Internet browser for your Communicator Web Access users.
Workaround: None. Internet Explorer does not support host names with an underscore in their FQDNs.
Issue: Signing in to Office Communications Server 2007, Communicator Web Access from an Internet Explorer 6 with Service Pack on a computer running Windows 2000 can cause the browser to stop unexpectedly. This is caused by Communicator Web Access’s use of the AlphaImageLoader filter to scale images. refer to the following knowledge base article for more details: http://support.microsoft.com/default.aspx?scid=kb;EN-US;824463.
Resolution: Apply the Internet Explorer 6.0 SP1 hotfix available at http://www.microsoft.com/downloads/details.aspx?FamilyId=FE29CEBB-6877-4409-AAFF-06E7EBCC16DC&displaylang=en.
Issue: When legacy redirection is configured on Communicator Web Access (2007 release), and a user (Alice) who is homed on Live Communications Server 2005 with SP1 attempts to sign in to Communicator Web Access (2007 release), Alice will be prompted again for her credentials before she is redirected to Communicator Web Access (2005 release).
Workaround: None.
Issue: It is possible to get the IIS MMC and the Communicator Web Access Manager (2007 release) out of synch. One way to do this is to stop the virtual server in the Manager, and perform an iisreset at the command line. However, the virtual server still shows a stopped status in the Manager. Also, the Start menu item from the virtual server right-click menu in the Manager is disabled.
Workaround: The workaround is:
1. Close the IIS MMC and the Communicator Web Access Manager (2007 release).
2. Open the Services MMC.
3. Right-click the World Wide Web Publishing Service and click Restart.
4. Close the Services MMC and reopen the Communicator Web Access Manager (2007 release), right click the virtual server, and select Start.
5. The IIS MMC and the Communicator Web Access Manager (2007 release) will now be back in synch.
Issue: When a user configures options to Play sounds and Display alerts, alert sounds are not audible when Communicator Web Access is minimized.
Workaround: None.
Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
© 2007 Microsoft Corporation. All rights reserved.
Microsoft, Windows, Windows Live, Active Directory, Internet Explorer, MSN, Outlook, and SQL Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.