Microsoft office communicator cannot sync address book


















This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question Report abuse. Details required :. Cancel Submit. I have an email address of dmurphyATionaglobal I tried changing my outlook profile to use dmurphyATionaglobal but that didn't seem to help. I originally wanted to set the standard of people using sAMaccount domain. I think I'm going to have to use email address as the login so I'll get the iona.

Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. If all else fails, try this.

This helped me with my issues with OCS communication between client and address book. We are getting a "cannot synchronize address book information" error but we can still go add contacts and all of the contacts are listed.

We just have a yellow triangle with an exclamation point that worries some of our users. Any ideas on how to fix that. Copy the Cert of your local CA or whichever CA you are using to the client machine and see if that helps. If that works, you can use Group Policy to distribute that certificate to everyone.

This file doesn't exist where you said it should be. I've tried "Abserver -syncnow. What else can I check. Go to the properties of each and make sure they are pointing to the correct location as well as using the. The permissions should be set up correctly on the remote server, if indeed.

Do I need to create this account? If so, what groups does this account need to be a part of? Also, we are using Exchange Server I saw an article that stated that you may need Exchange for OCS to work properly.

I don't remember manually adding it anywhere when I was setting up OCS. If you download the documentation, it goes into great detail on setting this up - multiple steps required. I'm also pretty sure I was working with the beta back when I wrote this answer - so I'm not sure if things changed for these settings as well.

But it is always a good idea to check the service accounts and make sure the passwords have not expired. And certficiates - on both servers if running MTLS - the 2nd server usually gets you I only can find the Universal Groups you mentioned. No user accounts and all the groups are all empty. I created a user called RTCService before the initial setup. I generally print out the Planning and Deployment guides before implementing these products I finished setting up OCS and the first few clients were great.

I thought I was done and could go home, but noticed that our receptionist couldn't sync the address book - same errors and all the fixes suggested didn't do a thing. I know that seems too simple, but it might save somebody a few hours of searching for the needle in the proverbial haystack. Once I changed those settings, everything else has worked great! Another possible solution: Communicator clients would not sync address book and the web components validation tool failed for the address book.

Clients now download the files using SSL, without anonymous authentication. I hope this helps someone else! Click to clear the Use Guessmart check box, and then click to clear the Secure Guessmart Authentication check box.

The webpage should contain lots of XML data. The figure below depicts an example of the information that should be displayed in Internet Explorer. Still need help? Go to Microsoft Community. The information and the solution in this document represent the current view of Microsoft Corporation about these problems as of the date of publication.

This solution is available through Microsoft or through a third-party provider. Microsoft does not specifically recommend any third-party provider or third-party solution that this article might describe. There might also be other third-party providers or third-party solutions that this article does not describe. Because Microsoft must respond to changing market conditions, this information should not be interpreted to be a commitment by Microsoft. Microsoft cannot guarantee or endorse the accuracy of any information or of any solution that is presented by Microsoft or by any mentioned third-party provider.

Microsoft makes no warranties and excludes all representations, warranties, and conditions whether express, implied, or statutory. These include but are not limited to representations, warranties, or conditions of title, non-infringement, satisfactory condition, merchantability, and fitness for a particular purpose, with regard to any service, solution, product, or any other materials or information.

Microsoft is in no way liable for any third-party solution that this article mentions. Office for business More Need more help? Expand your skills.



0コメント

  • 1000 / 1000