locked
EnableExchangeContactSync set to False not working RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hey guys,

    I figure I'll edit my original post instead of making a new one.

    I'm having a problem where the client policy EnableExchangeContactSync is not working when I set it to False. Below is my testing:

    1. Run set-csclientpolicy -EnableExchangeContactSync $False

    2. Run get-csclientpolicy and see that it is set to False

    3. Remove contact from Lync contact list and from Outlook Contacts

    4. Close Lync and Outlook for approx 15 minutes and re-open

    5. Add contact to Lync contact list from GAL

    6. Within 1 minute contact is added to Outlook Contacts

    Is there any additional testing I can do or anything else I can check to make sure it is working properly? Will it take a long time for the policy to go into place? Anything I can do additionally to test would be appreciated.

    Sidenote: I did notice that there is a bug (to be fixed in CU4) regarding "Unable to exclude contacts in outlook from showing in the search results utilizing the ExcludedContactFolders property of the client policy" if it's related and matters at all.

    Thanks everyone,

    Shawn

    If you find my post helpful, please hit the "Vote as helpful" button so that others may see that it is helpful as well.

    • Edited by Shawn.Wilfong Wednesday, October 19, 2011 2:48 PM Different issue than original
    Wednesday, October 19, 2011 2:23 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    ouch, don't change the question on us. Now we answered 2. best style would be to ask the next question below or new question, but no worries...

    appears a bug.

    The way to see the bug exhibited sooner is:

    http://blog.schertz.name/2010/09/updating-the-lync-2010-address-book/

     

     

    +Say thanks and observe basic forum courtesy:
    +If this post answered your question, Mark As Answer
    +If this post was helpful, Vote as Helpful

    windowspbx blog: my thots/howtos
    see/submit Lync suggestions here: simple and public
    • Edited by Matt LandisMVP Wednesday, October 19, 2011 2:56 PM
    • Proposed as answer by Sean_Xiao Tuesday, October 25, 2011 8:23 AM
    • Marked as answer by Sean_Xiao Monday, October 31, 2011 1:41 AM
    Wednesday, October 19, 2011 2:54 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Shawn,

    Please run the cmdlets Get-CsManagementStoreReplicationStatus and verify if Front-End servers' UpToDate is True.

    It looks like if the FE server UpToDate is false, the policy can not work for client. 

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Proposed as answer by Sean_Xiao Tuesday, October 25, 2011 8:23 AM
    • Marked as answer by Sean_Xiao Monday, October 31, 2011 1:41 AM
    Friday, October 21, 2011 3:07 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    If you run as verbose, does it note if the action was a success?
    +Say thanks and observe basic forum courtesy:
    +If this post answered your question, Mark As Answer
    +If this post was helpful, Vote as Helpful

    windowspbx blog: my thots/howtos
    see/submit Lync suggestions here: simple and public
    • Marked as answer by Shawn.Wilfong Wednesday, October 19, 2011 2:29 PM
    • Unmarked as answer by Shawn.Wilfong Wednesday, October 19, 2011 2:39 PM
    Wednesday, October 19, 2011 2:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Actually, I just noticed that someone must have created a second identity besides global (we only had global at the time) and I was reading the values for that identity.  Our global value is fine.  Sorry for your trouble :)
    If you find my post helpful, please hit the "Vote as helpful" button so that others may see that it is helpful as well.
    Wednesday, October 19, 2011 2:28 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    great Shawn, glad its sorted.
    +Say thanks and observe basic forum courtesy:
    +If this post answered your question, Mark As Answer
    +If this post was helpful, Vote as Helpful

    windowspbx blog: my thots/howtos
    see/submit Lync suggestions here: simple and public
    Wednesday, October 19, 2011 2:29 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Bumping to address the actual issue than initial issue I thought it was.
    If you find my post helpful, please hit the "Vote as helpful" button so that others may see that it is helpful as well.
    Wednesday, October 19, 2011 2:49 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    ouch, don't change the question on us. Now we answered 2. best style would be to ask the next question below or new question, but no worries...

    appears a bug.

    The way to see the bug exhibited sooner is:

    http://blog.schertz.name/2010/09/updating-the-lync-2010-address-book/

     

     

    +Say thanks and observe basic forum courtesy:
    +If this post answered your question, Mark As Answer
    +If this post was helpful, Vote as Helpful

    windowspbx blog: my thots/howtos
    see/submit Lync suggestions here: simple and public
    • Edited by Matt LandisMVP Wednesday, October 19, 2011 2:56 PM
    • Proposed as answer by Sean_Xiao Tuesday, October 25, 2011 8:23 AM
    • Marked as answer by Sean_Xiao Monday, October 31, 2011 1:41 AM
    Wednesday, October 19, 2011 2:54 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Well technically no one answered my initial question ;)

    OK, so the two policies are kind of hand-in-hand and we just need to wait for a fix for both issues (ExcludeContactFolders and EnableExchangeContactSync)?

     

    We've already had the pleasure of setting Lync to perform auto sync/download per that article :)

    If you find my post helpful, please hit the "Vote as helpful" button so that others may see that it is helpful as well.
    Wednesday, October 19, 2011 2:59 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    no sweat, sounds good.
    +Say thanks and observe basic forum courtesy:
    +If this post answered your question, Mark As Answer
    +If this post was helpful, Vote as Helpful

    windowspbx blog: my thots/howtos
    see/submit Lync suggestions here: simple and public
    Wednesday, October 19, 2011 3:35 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Shawn,

    Please run the cmdlets Get-CsManagementStoreReplicationStatus and verify if Front-End servers' UpToDate is True.

    It looks like if the FE server UpToDate is false, the policy can not work for client. 

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Proposed as answer by Sean_Xiao Tuesday, October 25, 2011 8:23 AM
    • Marked as answer by Sean_Xiao Monday, October 31, 2011 1:41 AM
    Friday, October 21, 2011 3:07 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi,

    let's bring this to top again, because there is still an annoying bug within the latest versions of the client (.7577.4103 and .7577.4098).

    If you use EnableExchangeContactSync and set it to $false, the checkbox on the client gets greyed out (.enabled=false in VB), but NOT the value of the checkbox. So the contacts are still being synced with your Outlook, and you can't change the value of the checkbox because it is greyed out.

    If you want to disable syncing the contacts you have to do the following: set EnableExchangeContactSync to $True, uncheck the checkbox within your client (once per user), and then set EnableExchangeContactSync to $False again.

    Marc

    • Proposed as answer by m a c h Tuesday, June 18, 2013 2:54 PM
    • Unproposed as answer by m a c h Tuesday, June 18, 2013 2:54 PM
    • Proposed as answer by Stephen OwenMVP Tuesday, February 3, 2015 2:50 PM
    Thursday, June 21, 2012 8:10 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Marc,

    how did u get this problem solved or is this still an issue?

    Tuesday, June 18, 2013 2:53 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Could it be that this issue has beend fixed in on of the last lync client updates?

    Marc

    Friday, June 21, 2013 11:36 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Marc,

    actually we us Lync Client Version 4.0.7577.4384 and the problem is still there!


    • Edited by m a c h Monday, June 24, 2013 3:02 PM grammar
    Monday, June 24, 2013 2:58 PM