What Exchange Delegation and Lync do?

This was something that I have wanted to share with you all. There were more queries from Service desk and desktop team about what “people I manage call for” do and how to remove/manage them from the Lync client.

The “People I manage calls for” is part of the delegation model. If the user in question is responsible for scheduling Lync/OCS meetings for the person in their “People I manage calls for” group, no you cannot remove them because removing them will remove their ability to schedule meetings as well. If that’s not the intention, and they ended up being a delegate by accident of exchange permissions then yes they can be safely removed.

There is a resource kit utility called SEFAUtil.exe that has the ability to add/remove delegations from Lync server manually.

Normally, Lync gets its delegate information from permissions settings in exchange. For the example, I’m going to use Boss and Admin instead of delegator and delegate because I find the latter confusing

For the admin to be able to schedule Lync meetings for the boss, the boss sets either “Editor” or “Author” rights on his calendar to his admin

Both the boss and the admin have the csclientpolicy –EnableExchangeDelegateSync set to $true

When the boss’s Lync client boots up it checks with exchange to see what permissions the boss has granted other people. It will find he’s granted his admin “Editor” or “Author” rights to his calendar and the Lync client will send a message to the Lync server to grant delegation permission to the admin.

When the Admin restarts their client, it will contact the Lync server and pull down the users that the admin has been granted permission for. The admin will then be able to schedule Lync meetings inside the boss’s calendar.

This is the normal process.

Exchange 2010 SP2 RTM

Did you all know that Exchange Server 2010 Service Pack 2 (SP2) has been released last night, raising the Exchange version number to You can download Exchange 2010 SP2 here.

For those still unaware, the 530Mb+ file (1,3 GB extracted) contains the full set of binaries; you can use it to upgrade existing RTM or SP1 installations or deploy new Exchange 2010 SP2 installations.

Besides the usual set of hotfixes, SP2 introduces the following features:

Address Book Policies
Address Book Policies, also known as GAL segmentation, ABPs are meant to segmented the address book, giving users a certain view of the address book like Address List Segregation did for Exchange 2003/2007. ABPs were already announced back in January. I wonder how this affects for instance MailTips, as MailTips might report on organization-wide figures (sending mail to X users) while the end user may only see a small fragment of the population. Also, be advised that clients bypassing the CAS server for directory lookups, e.g. LDAP queries, don’t benefit from ABPs. Think Outlook for Mac but also multifunctionals, fax solutions etc.

OWA mini
This will be a lightweight browser like OMA in the past, meant for simple browsers.

Hybrid Configuration
This wizard is to make the configuration of an on-premise Exchange and Office 365/Exchange Online more simple, reducing the steps required from 49 to 6.

OWA Cross-Site redirection
This will allow clients to be silently redirected to the proper site if they log on to a CAS server located in a site different than the site where their mailbox is hosted and externalURL has been specified there. This greatly increases the single sign-on experience.

The releases notes are not available at this time.