Hello.

I actually use powershell to manage lync users. I don't have difficulties with the user objets, policies and others, but i want to manage more properties, and I started to test the possibilities offered by the Powershell commands Export-CsUserData, Import-CsUserData and Update-CsUserData, changing the contacts, and other values of the user.

But I have problems setting the call forward parameters. I export the xml, modify it and re-import, but my modifications are not always reflected in the Lync client (restarting it after each change). I can't see what makes the changes valid or not.

I have seen that the <publication> tag has version properties and date properties, and tried to make changes in it, but it doesn't seems to change something.

If it can help, something strange occurs with the following steps :

1- I try to set a call forward to a user without. => Not working

2- I set the version to a higher number and import again => Not working

3- I set a simultaneous call forward to the user with the client => Ok

4- I import again the previous xml file (step 2) => Ok

Is there documentation somewhere for this kind of actions ? What are the rules in import/export of user data xml files ? Is there another way to programmaticaly set the call forward of a user (not sefautil) ?

Thanks.

Hi

For this I recommend you use SEFAUtil which can be used to set call forwarding. http://blogs.technet.com/b/meacoex/archive/2011/04/23/configure-simultaneous-ring-delegate-ringing-and-call-forwarding-settings-on-behalf-of-a-lync-server-2010-user.aspx

http://support.risualblogs.com/blog/2014/03/21/change-call-forwarding-number-via-sefautil-in-lync-2013/

Thanks

Hi

I would prefer not to use SEFAUtil as it's an external tool and I cannot force my clients to install and configure it. My scripts will be used by various clients on multiple systems with different environnements.

So, I have the same script in a sense, and updating the version number is necessary.  Use update-csuserdata, not import-csuserdata.   The client won't reflect it typically until a log off or on, sometimes it seems to pop in but I haven't spent too much time timing it and figuring out when.  Sefautil is an external tool, but it's a Microsoft tool and the only supported way to get this in at an administrative level. 

There is no documentation, and hacking up that XML leaves you outside of the supported boundaries.  It is possible to corrupt a user and get strange entries this way so you have to be EXTREMELY careful.