Companies that deploy Lync Enterprise Voice (EV) have the ability to easily leverage the "delegate" scheduling feature. However, customers that don't deploy EV do not get to take advantage of the delegate functionality.
A delegate scheduler should be able to schedule a Lync meeting on behalf of their boss/manage even if both users are not enabled for Enterprise Voice.
We will walk through an example of delegation without EV and show how it works without administrative interaction.
In this example we have two users named Player2 (Manager) and Player3 (Delegate). As you can see in Figure 1 below, Player2 has shared his Outlook calendar with Player3.
Figure 1 - Player2 Delegation Configuration
Player3 is now eligible to create meetings on behalf of Player2.
Figure 2 - Player3 schedules a meeting for Player2
So far everything is working as expected.
The issue arises when Player3 attempts to schedule a Lync meeting on behalf of Player2.
Figure 3 - Error message when Player3 tries to schedule a Lync meeting
As you can see in Figure 3 above, Player3 receives an error that they do not have delegate permissions for Player2. These particular delegate permissions are in addition to the mailbox delegate permissions that are needed.
The issue here is that Player2 is not enabled for Enterprise voice and therefore has no ability to alter his delegates list.
The solution that we will describe in this blog post involves the Lync administrator using the SEFAUtil administrative tool to configure Player 3 as a delegate for Player2. This solution will enable Player3 to be configured as a delegate for Player2 while neither user is enabled for Enterprise Voice. This solution requires some administrative input but it is scalable and allows the configuration to be easily changed after the fact.
This configuration requires that you are running a minimum build of 8308.577 of the SEFAUTIL that is available via the following URL: http://www.microsoft.com/en-ca/download/details.aspx?id=36821.
This document will only cover the delegation configuration using SEFAUtil and it will not cover the actual Lync server configuration required to make the SEFAUtil work. For detailed steps on how to enable SEFAUtil please see this blog post (http://blogs.technet.com/b/jenstr/archive/2010/12/07/how-to-get-sefautil-running.aspx).
In this sample configuration we will start with two users named Player2 and Player3 that are not EV users and do not have delegation in Lync configured. At this point we assume that the Exchange delegation has already been completed (http://office.microsoft.com/en-us/outlook-help/allow-someone-else-to-manage-your-mail-and-calendar-HA102749417.aspx) and that the EnableExchagneDelegateSync parameter has not been set on any client policies. The reason that we choose not to use this option is that Exchange Delegate sync is a one way sync only in that when someone is removed as an Exchange delegate they are not automatically removed as a Lync delegate.
Figure 4 - Player2 signed in to Lync
Figure 5 - Player3 signed in to Lync
As you can see in Figure 4 and Figure 5 above, both users are not enabled for Enterprise voice and as a result do not have the ability to manage their call forwarding settings and the delegate access feature.
The following steps assume that you have configured the Lync infrastructure (see note earlier in this document) to support the SEFAUtil and are now ready to configure the delegate relationship between these two users.
Open a command prompt and type the following command syntax (in this example pool01.p52.local has already been configured as a trusted application pool to run the SEFAUtil application)
SEFAUtil.exe /server:pool01.p52.local email@example.com /adddelegate:firstname.lastname@example.org
Once the command completes you should see output such as what is shown below.
User Aor: sip:email@example.com
Display Name: Player2
UM Enabled: True
Simulring enabled: False
Simultaneously Ringing Delegates: sip:firstname.lastname@example.org
You should now see a change in the Lync client for both Player2 and Player3.
Figure 6 - Player2 showing Player3 as a delegate
Figure 7 - Player3 showing as a delegate for Player2
As you can see in Figure 6 above Player2 now has Player3 listed under the "Delegates" group which gets created automatically when you have delegates configured.
In Figure 7 above you can see that Player3 has Player2 listed under the "People I Manage Calls For".
As you can see in Figure 8 below Player3 is now able to schedule a Lync conference on behalf of Player2.
Figure 8 - Player3 schedules a meeting for Player2
If you decide that you want to reverse the changes made earlier you can do that with the SEFAUtil as well.
Open a command prompt and type the following command syntax (in this example pool01.p52.local has already been configured as a trusted application pool to run the SEFAutil application)
SEFAUtil.exe /server:pool01.p52.local email@example.com /removedelegate:firstname.lastname@example.org
User Ring time: 00:00:20
Call Forward No Answer to: voicemail
This blog post described how a company that has not deploy Lync Enterprise Voice (EV) can use the SEFAUtil tool to configure delegate access and allow their users to leverage the "delegate" scheduling feature.
Nice write-up, thanks for sharing!
Thanks Matt. I am glad you enjoyed it.
What is the expected execution time for the sefautil program? When we try to add a delegate to a user, the command seems to just hang most, if not all the time. Has anyone else experienced this?
Hi Andrew, I just checked on this in my lab and it took about 15 seconds for the transaction to complete. The SEFAUtil acts like a regular SIP client and signs in to the server to issue its commands. I have never seen it hang completely however.