Deploying microsoft office communicator 2007 r2

Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Sign in to vote. I get Outlook Integration error in Office Communicator and could not update status information. Tuesday, February 23, PM. We're working on it and it will be rectified in next release. Regards Ashish. Wednesday, February 24, AM. I only have one Outlook profile on my computer. Yesterday I test with another computer with Office and everything works well. Thanks Ola.

Any ideas? Thursday, April 22, PM. Friday, April 23, PM. I also am experiencing this same error in Communicator. So Do We! Monday, April 26, PM. We have the same error too Office Communicator R2 3. As I understand it, the behavior that you are seeing can occur if if the client cannot get to Exchange Web Services which would be the case with bit.

That aside, this functionality is expected to work if you have the latest Cumulative Update installed. Thanks, Vitor. Thanks for the feedback Vitor, aplogize it did not work. The functionality is definitely in that update. I am asking a peer on the Communicator team to follow up on this and get back to you. The last and pretty rare manifestation of this error can look like this:.

Tuesday, April 27, AM. Same problem after installing the update. Everything was working fine with Office , with x64 not working even after update. Wednesday, April 28, PM. Thursday, April 29, PM. We are using On-premise exchange.

Monday, May 3, PM. I will recheck my setups for Autodiscover. Does that go through the web services or the MAPI interface? Tuesday, May 4, PM. Is that a possible scenario, or do we have to migratie the customer towrds Exchange online too. After the update is installed, the global version of this update has the file attributes, or a later version of the file attributes, that are listed in the following table:. For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:.

Summary This article describes the Microsoft Office Communicator R2 issues that are fixed in the update for Communicator R2 that is dated June This article describes the following items about the update: The issues that the update fixes. The prerequisites for installing the update. Whether you must restart the computer after you install the update.

Whether the update is replaced by any other update. Whether you must make any registry changes. The files that the update contains. For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base: Description of the update for Live Meeting Conferencing Add-in for Outlook: July Description of the update package for Office Communications Server R2: July, This cumulative update also includes the following previously released update: An Automatic Update download is not initiated on a computer that is running Office Communicator R2 build 3.

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base: How to obtain Microsoft support files from online services Microsoft scanned this file for viruses.

Prerequisites There are no prerequisites for installing this update package. Restart requirement You may have to restart the computer if certain dependencies of Office Communicator are still running when the update is applied. More Insider Sign Out. Sign In Register. Sign Out Sign In Register. Latest Insider. Check out the latest Insider stories here. This is to make sure that changes that are made by the administrator before the latest update are not lost as part of the update.

Follow these steps to update theABServer. Open the ABServer. In the ABServer. Note If you do not make this change, an unnecessary surge in bandwidth may occur when the contact information in Communicator R2 changes. For example, a surge in bandwidth will occur if a company moves to a different location. This causes a change in the address information for all the employees in the company. Note The setting for the redirect key in the appsetting section in the Web.

This causes the handler to redirect traffic to a virtual directory that points to the underlying file share. Therefore, IIS sends the files. In the Value data box, type 1, and then click OK. If you are planning to implement the resolution for situation 4 that is listed in the Symptoms section of this KB article then be sure to read the following Technet information in regard to BITS group policy configurations. For more information about the how to configure BITS 2. Symptoms In Microsoft Office Communicator R2, you experience network performance issues in one or more of the following situations: The Global address list GAL file download is triggered in client computers in different scenarios.

The download of files uses a large network bandwidth.