Comments on: Office Communicator 2007 and Outlook 2007 Integration Errors http://blog.insideocs.com/2009/05/22/office-communicator-2007-and-outlook-2007-integration-error-an-update/ Microsoft Office Communications Server - Tips, Tricks, and Insight Fri, 30 Jul 2010 19:21:03 -0400 http://wordpress.org/?v=2.8.3 hourly 1 By: Om http://blog.insideocs.com/2009/05/22/office-communicator-2007-and-outlook-2007-integration-error-an-update/comment-page-1/#comment-2892 Om Fri, 02 Jul 2010 10:14:51 +0000 http://blog.insideocs.com/?p=345#comment-2892 Some user specific SQL query to extract specific information from the Database are available at the below link: http://techtips.opdubey.info/office-communicator/office-communicator-queries Some user specific SQL query to extract specific information from the Database are available at the below link:

http://techtips.opdubey.info/office-communicator/office-communicator-queries

]]> By: John Smith http://blog.insideocs.com/2009/05/22/office-communicator-2007-and-outlook-2007-integration-error-an-update/comment-page-1/#comment-2313 John Smith Fri, 23 Apr 2010 10:58:24 +0000 http://blog.insideocs.com/?p=345#comment-2313 Clarification: outlook DOES need to have been running a few minutes before you start communicator. (This may have been fixed in R2) Clarification: outlook DOES need to have been running a few minutes before you start communicator. (This may have been fixed in R2)

]]> By: ted http://blog.insideocs.com/2009/05/22/office-communicator-2007-and-outlook-2007-integration-error-an-update/comment-page-1/#comment-2101 ted Mon, 01 Mar 2010 18:21:32 +0000 http://blog.insideocs.com/?p=345#comment-2101 fixmapi works to clear the error message, "Integration Errors". Click start->Run->type fixmapi This works for xp client system. fixmapi works to clear the error message, “Integration Errors”. Click start->Run->type fixmapi

This works for xp client system.

]]> By: Impact of Changing a User's SIP Address « Inside OCS http://blog.insideocs.com/2009/05/22/office-communicator-2007-and-outlook-2007-integration-error-an-update/comment-page-1/#comment-1375 Impact of Changing a User's SIP Address « Inside OCS Thu, 17 Dec 2009 04:33:23 +0000 http://blog.insideocs.com/?p=345#comment-1375 [...] does not match the primary SMTP email address in their Outlook profile (see previous post “Office Communicator 2007 and Outlook 2007 Integration Errors”), so the primary email address will need to be updated to avoid this error. If the primary email [...] [...] does not match the primary SMTP email address in their Outlook profile (see previous post “Office Communicator 2007 and Outlook 2007 Integration Errors”), so the primary email address will need to be updated to avoid this error. If the primary email [...]

]]> By: Curtis Johnstone http://blog.insideocs.com/2009/05/22/office-communicator-2007-and-outlook-2007-integration-error-an-update/comment-page-1/#comment-1259 Curtis Johnstone Wed, 09 Dec 2009 21:39:19 +0000 http://blog.insideocs.com/?p=345#comment-1259 I have seen this behavior is two deployments. It is my understanding that you can get rid of it, but I have not been successful yet, and it is on my list of issues to research more and blog about. In the meantime, here is some information and references that should help: There are 2 possibilities for external (non-domain) Communicator authentication pop-ups: 1) Access to Exchange 2007 Web Services to retrieve Calendar and Out-of-Office settings for your contacts, and, 2) Access to the OCS external web farm to provide Communicator with Address Book Download and Group Distribution Expansion functionality. I believe the solution lies in the authentication settings in the respective IIS applications for #1 and #2 above, and/or ISA authentication settings (specified in the web publishing rules when configuring the ISA to allow external access to the internal OCS web component role for access to the Address Book and Group Expansion). The 2 blog entries below are good and have some solutions to try – the comments at the end of both entries are more applicable to the non-domain (external) case. <strong>Why is Communicator prompting me for credentials?</strong> http://blogs.msdn.com/scottos/archive/2008/10/16/why-is-communicator-prompting-me-for-credentials.aspx <strong>OCS 2007 - Continuous prompts for Address Book download</strong> http://communicationsserverteam.com/archive/2007/12/17/52.aspx In one deployment, the two prompts I have seen are both for access to Exchange 2007 (one for a mailbox role, and the other for a cas role). Stay tuned and let me know if anything works for your case. I have seen this behavior is two deployments. It is my understanding that you can get rid of it, but I have not been successful yet, and it is on my list of issues to research more and blog about.

In the meantime, here is some information and references that should help:

There are 2 possibilities for external (non-domain) Communicator authentication pop-ups:
1) Access to Exchange 2007 Web Services to retrieve Calendar and Out-of-Office settings for your contacts, and,
2) Access to the OCS external web farm to provide Communicator with Address Book Download and Group Distribution Expansion functionality.

I believe the solution lies in the authentication settings in the respective IIS applications for #1 and #2 above, and/or ISA authentication settings (specified in the web publishing rules when configuring the ISA to allow external access to the internal OCS web component role for access to the Address Book and Group Expansion).

The 2 blog entries below are good and have some solutions to try – the comments at the end of both entries are more applicable to the non-domain (external) case.

Why is Communicator prompting me for credentials?
http://blogs.msdn.com/scottos/archive/2008/10/16/why-is-communicator-prompting-me-for-credentials.aspx

OCS 2007 – Continuous prompts for Address Book download
http://communicationsserverteam.com/archive/2007/12/17/52.aspx

In one deployment, the two prompts I have seen are both for access to Exchange 2007 (one for a mailbox role, and the other for a cas role).

Stay tuned and let me know if anything works for your case.

]]> By: ewright http://blog.insideocs.com/2009/05/22/office-communicator-2007-and-outlook-2007-integration-error-an-update/comment-page-1/#comment-1156 ewright Fri, 04 Dec 2009 14:46:08 +0000 http://blog.insideocs.com/?p=345#comment-1156 Great Article! I have been searching for quite some time. However I do have a question. For the scenario you describe in option 6, is there a way to prevent the popup for authentication? This only happens when users are external. When the same users are internal, this authentication popup does not happen. Is this a configuration setting within the ISA Listener that prevents this? Great Article! I have been searching for quite some time. However I do have a question. For the scenario you describe in option 6, is there a way to prevent the popup for authentication? This only happens when users are external. When the same users are internal, this authentication popup does not happen. Is this a configuration setting within the ISA Listener that prevents this?

]]> By: ewright http://blog.insideocs.com/2009/05/22/office-communicator-2007-and-outlook-2007-integration-error-an-update/comment-page-1/#comment-1155 ewright Fri, 04 Dec 2009 14:39:48 +0000 http://blog.insideocs.com/?p=345#comment-1155 We are seeing the error you describe in 6) above in both our production as well as lab environments. When the users login on net (within the domain) the system does not prompt for credentials. It only happens (consistantly) when users are external. Is there an ISA setting that will allow the credentials to be passed properly? We are seeing the error you describe in 6) above in both our production as well as lab environments. When the users login on net (within the domain) the system does not prompt for credentials. It only happens (consistantly) when users are external. Is there an ISA setting that will allow the credentials to be passed properly?

]]>