Friday, 1 March 2013

Administratively Configuring Lync Call Forwarding

The Lync Server 2010 Resource Kit includes a tool called SEFAUtil (the Secondary Extension Feature Activation utility).  There have been a few good guides written for getting the tool to work (there are quite a few steps required), and once it's working correctly you can use it to modify call forwarding settings of Lync-enabled accounts.

You can download the Lync Server 2010 Resource Kit from here:
http://www.microsoft.com/en-us/download/details.aspx?id=21165

And to get started with SEFAUtil I recommend taking a look at these blog posts:
http://blogs.technet.com/b/jenstr/archive/2010/12/07/how-to-get-sefautil-running.aspx
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

Through some trial and error I found that to delegate the ability to use SEFAUtil you need to grant these permissions:
  • Membership in the "RtcUniversalUserAdmins" Active Directory security group
  • Membership in the "RTC Local Read-only Administrators" local security group on the machine where SEFAUtil is being run
Assuming at this point you (and your delegates) can use SEFAUtil at the command prompt, you may find this script useful.

The script provides a wrapper around SEFAUtil in order to make configuring and disabling call forwarding simpler - you just need to pass in a username and a destination.

To use the script in your environment you must at least change the $LyncServer and $SipDomain defaults in the script, or pass in your own values as parameters. You'll also need the Lync Management Shell module available.

The script supports several options:
  • Forward to manager
  • Forward to a phone number
  • Forward to a SIP address
  • Disable forwarding