Jens Trier Rasmussen

The odd bit of information about Lync Server 2013, Lync 2010, Exchange 2013, SharePoint Server 2013, Exchange 2010 SP1, OCS 2007 R2, Exchange 2010 and OC 2007 R2

How to get SEFAutil running?

How to get SEFAutil running?

  • Comments 21
  • Likes

(Feb 27, 2013 - The Lync 2013 ResKit, which includes a new version of SefaUtil, is available here http://www.microsoft.com/en-us/download/details.aspx?id=36821)

(Updated with pointer to UCMA 3.0 documentation and also only describing using SEFAutil on a dedicated server. We recommend installing trusted applications on dedicated servers. However using Lync Server Management Shell cmdlets you can configure CsTrustedApplicationPool on a server already running EE/SE or Director)

 

SEFAUtil (secondary extension feature activation) enables Lync Server 2010 administrators and helpdesk agents to configure delegate-ringing and call-forwarding settings on behalf of a Lync Server user. This tool also allows administrators to query the call-routing settings that are published for a particular user. SEFAutil is a utility part of the Microsoft Lync Server 2010 Resource Kit Tools. It is a UCMA 3.0 application and in order for it to work you need to configure a trusted application. For more information about this look here.

The trusted application pool is related to a registrar and you need to find the SiteId of the site in which the registrar is located. You can use the PS cmdlet Get-CsSite to find the SiteId. In my case the site is called Søborg, so the cmdlet I used is the following:

  • $Site=Get-CsSite –Identity Søborg

You then need to create the trusted application pool. In my lab it is running on a dedicated server (jenstr31.inframss.dk) and the registrar is cs1.inframss.dk. The PS cmdlet to create the trusted application pool is:

  • New-CsTrustedApplicationPool –id jenstr31.inframss.dk –Registrar cs1.inframss.dk -site $Site.SiteId

After having create the trusted application pool you then need to create a trusted application representing SEFAutil. The PS cmdlet to do this is:

  • New-CsTrustedApplication –ApplicationId sefautil –TrustedApplicationPoolFqdn jenstr31.inframss.dk –Port 7489

The ApplicationId needs to be sefautil, but the Port number can be whatever number you would like. After having added the trusted application pool and trusted application you need to enable the topology by issuing the PS cmdlet Enable-CsTopology.

When you run SEFAutil on a dedicated server you then need to install Lync Server 2010 on the server. The setup steps you need to perform are the following:

  • Install or Update Lync Server System
  • Install Local Configuration Store
  • Request, Install or Assign Certificates
  • Start Services

Now the infrastructure is ready and you can continue with installing the Lync Server 2010 Resource Kit Tools. When it is installed start a command prompt and run SEFAutil. The Word document describing the Microsoft Lync Server 2010 Resource Kit Tools has a good description on how to run SEFAutil.

Comments
  • This is great information. I was looking for this as I could not get sefautil working on a SE server. After following these instructions it is now working. Have you tested sefautil out of the box on a SE / EE server if its working?

    Jens: Thanks! Yes, I've done a quick test on a EE/SE pool and it did work. However please remember our recommendation is a dedicated server.

  • This is great information. really useful. I eagerly wait for your blogs to come out, very good information which we will never have in documents

    Thanks,

  • Wilfried, Jens, could You, please, clarify, what you have done to make sefautil work on SE Front End Server?

    Jens: I used the PowerShell cmdlets in the post and referenced the SE server instead of my dedicated server.

  • Beware the bug in the examples in the Reskit Doco:

    If you issue the command to change a user's settings as "sip:katarina@contoso.com" the command WON'T make any change to the user's account. Re-issue the command as just "katarina@contoso.com" and you'll be fine.

    Sadly SEFAUtil doesn't report an error, just fails to make the change.

    The syntax as described in SEFAUtil.exe /? is correct.

    - G.

  • Again you saved the day :) Thanks.

  • Is there a way to set simultaneous ring using SEFAUtil to a telephone number instead of a delegate? Please specify the syntax too. Thanks :-)

    Jens: No, unfortunately it is not possible to set that setting via SEFAutil.

  • Ouch!!! That hurts :-(

  • Jens, great blog post thank you!

  • FYI, if you are doing this on a Lync Enterprise Edition Pool, the -Identity of the ApplicationPool should be the lync pool FQDN, not the server FQDN.

    Figured I'd pass that bit of info along!

  • Hi Jens, Could you please let us know if there will be a new SEFAutil for Lync 2013 or the one for Lync 2010 can also work with Lync 2013?

    Thank you!

    Jens>Hi Peter, there will be a new version available with the Lync 2013 ResKit, when it ships. Don't know when that is :-)

  • Hi Jens, Could you describe the permissions required to use SEFAutil?  We would like to delegate this ability to a front-line group but are struggling to make it work.

    Thanks.

    Jens>Hi Ben. I got it working by making the user member of CsUserAdministrator and RtcUniversalUserAdmins

  • Forwarding to a number rather than a delegate is possible with SEFAutil.  From the documentation:

    SEFAUtil.exe /server:lyncserver.contoso.com sip:katarina@contoso.com /enablefwdnoanswer /callanswerwaittime:30 /setfwddestination:+14255550126@contoso.com;user=phone

    The magic is the suffix appended to the E.164 telephone number.

    Ben

  • Hello, can i run sefautil on a SBA too?

    Jens>Yes, that is possible.

  • should the 2010 version work on a 2013 server ? i have it installed without error but it crashes everytime I run a command

    Jens>No, I wouldn't expect that to work. Use the Lync 2010 version on a 2010 server.

  • Hi Jens, great blog! I'm trying to use SEFAUtil to a 2010 server. Do I install in the new 2013 Tool Kit or use the 2010 Tool Kit? Thanks!

    Jens>Hi. I would use 2010 to 2010 and 2013 to 2013.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment