An update is available to clean up the bad state information of a user who uses an Office Communicator client to log on to a Lync Server 2010 server

Applies to: Lync Server 2010 Standard EditionLync Server 2010 Enterprise Edition

Symptoms


This article describes an update that is available to clean up the bad state information of certain Microsoft Office Communicator 2007 R2 users. When users log on to a Lync Server 2010 server by using Office Communicator 2007 R2, the presence information is sent to public instant message (IM) clients, such as Windows Live Messenger, AOL, or Yahoo.

Resolution


A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft website:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.



Important To run the hotfix for cleaning up Public Internet Connectivity (PIC) access-control entries (ACEs) that is incorrectly assigned to the user containers from a Microsoft Lync Server 2010 database, follow these steps:
  • To determine the number of users who will be affected by the cleanup, open a command prompt, type the following command, and then press ENTER:
    containercleanuptool.exe /verifycount [/dbname:value] [/sqlserver:value]
  • To clean up the user containers, open a command prompt, type the following command, and then press ENTER:
    containercleanuptool.exe /clean [/dbname:value] [/sqlserver:value]
Note
  • dbname: The name of the database to connect to. The argument value is a string. By default, the argument value is rtc.
    Note Enclose the string in double quotation marks if the value contains any spaces.
  • sqlserver: The instance of the SQL Server to connect to. The tool tries to connect by using Windows Authentication. By default, the argument value is the local machine's rtc instance.
  • verifycount: Returns the number of users whose container configuration will be changed when the tool is run.
  • clean: Cleans PIC ACEs incorrectly assigned to user containers. This changes the container configuration for any users who have a PIC ACE configured on any of their containers.
    • The tool will put the user database in offline mode while the cleanup is in progress. All user endpoints in the pool enter resiliency mode when the database goes offline.
    • When the user endpoints leave resiliency mode when the database comes back online, they must re-enable their publications and reestablish their subscriptions. Any remote subscriptions will be out-of-date until they are refreshed.

Note The update should be applied on both the Lync Server 2010 server and the Office Communicator 2007 R2 client. Additionally, apply the update that is mentioned in Microsoft Knowledge Base (KB) article 2571546 to the Lync Server 2010 server, and also apply the upcoming update for Office Communicator 2007 R2.

More Information


For more information about the issue where present information is sent to public IM clients, click the following article number to view the article in the Microsoft Knowledge Base:
2577957 A public IM user can send instant messages to an internal Office Communicator 2007 R2 user in a Lync Server 2010 environment