Lync 2010 - How to disable the saving of Lync contacts in personal contacts via GPO

With lync, by default there is an option to Save Lync contacts into the personal contacts folder on the exchange server.       This can be turned off from the user options.   What I am looking for is a method to turn this off and possibly disable this feature for all our domain users via GPO or some other solution.  

We use a public folder for company contacts for a sync up with our blackberries.   This copy into personal contacts is creating duplicate contacts for the end users, and an inability for me to update employee contact info for everyone on the fly if people have old contacts with possibly bad phone numbers, etc...
LVL 33
Who is Participating?
globetrotterConnect With a Mentor Commented:
Hi Mike,

Microsoft has decided to move away from Group Policy and use inband provisioning to set client policies. This way you can ensure that people get the settings even if they are located outside the domain or have a number of different Endpoints.

I think the setting you are looking for is EnableExchangeContactSync which you can set in the Lync Management Shell. As you say you want to tuirn it off for everyone you can use the global policy to set this:

   Set-CsClientPolicy -EnableExchangeContactSync $False     --- this will make the change in your global policy - or you can create a new policy which you can assign to a site or a group of users.
   New-CsClientPolicy -Identity MyClientPolicy -EnableExchangeContactSync $False
   Grant-CsClientPolicy -Identity "testuser" -PolicyName MyClientPolicy

To see a full list of the client settings you can influence run "get-csclientpolicy | get-member"

 When set to True (the default value) Lync 2010 creates a corresponding personal contact in Microsoft Outlook for each person on a user’s Lync 2010 Contacts list.
MikeKaneAuthor Commented:
Excellent, this is what I was looking to find.  

Do you know of any method to disable the control within the Lync client so that it can not be enabled at all?    I understand that this policy will be applied to the user, but nothing will keep a user from enabling and running in the same issue.
MikeKaneAuthor Commented:
So, there doesn't seem to be a way to disable it altogether, so this is good enough.   Thanks.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.