My name is Walt Whitman and I am a Sr. Support Escalation Engineer on the Forefront Identity Team,

A topic that we receive many calls on is how do I flow Lync-enabled objects via FIM.  I have written another wiki article on this topic on provisioning Lync enabled objects via PowerShell.  Let me first say that the supported methodology for creating Lync-enabled objects is to use "Enable-CSUser."

The following article is a guide that you may find useful to create a Lync-enabled object without PowerShell.  The content is meant to be used as a guide and by no means an exact step-by-step for creating Lync-enabled users without PowerShell; I cannot stress this enough.

There are a few things that you need to keep in mind.  First, you need to have users in the domain or domains in question.  Typically when I see this scenario there is an acquisition and the FIM administrator is tasked with creating a GALSync environment to resolve mail-enabled objects between the two domains.  If the GALSync environment is built, then the next step is to flow the necessary attributes between the two domains

A Lync user requires the following attributes that are detailed here, but the attributes are as follows:

User and Contact Attributes

 sn (surname)
 l (city)
 st (state)

Group and Contact Objects

Distinguished name (DN)

Once you configure your LYNC environment in both domains you should be able to flow the attributes between the two domains to be able to resolve the LYNC enabled users between both domains.



Synchronizing Attributes in Cross Forests for Lync Server 2010
FIM-TROUBLESHOOTING: Problem firing powershell script to Lync Enable users from within a FIM Workflow