Hi All,

I'm very new to the FIM world, so please pardon this newbie question :)

Are there any examples for FIM management agents which can provision users to Lync by reading them from AD? I know there are a few examples using PowerShell, but I would like to know if it is possible using VB or C#? Basically I want to write the extension without relying on external scripts (ideally)

As a backup plan (i.e. using powershell), I read this forum http://social.technet.microsoft.com/Forums/en-US/ilm2/thread/39724bcb-8d1d-447e-8cd2-77624d6a4476 but I'm not sure how to call powershell cmdlets from my extension. Is it a simple case of calling powershell scripts from C# code which will do the provisioning, or is there a way to use powershell cmdlets directly in C#?

Thanks

Powershell MA for rescue http://blog.goverco.com/p/powershell-management-agent.html

Thanks for your reply.

I have come across this MA, but this MA relies on powershell cmdlets and also that what I really need is the code which gets the Lync Schema and does the provisioning etc.

Essentially, any way of provisioning users etc into Lync using C#? :)

Correct me if I'm wrong, but the only supported way to do Lync provisioning is through the PS CmdLets; if it's OCS, it's another story where I believe you have something like the Exchange RUS to finalize OCS attribute population. Lync and OCS guys, please correct me if I'm wrong.

For the Lync implementations, I've always used my PowerShell MA and the appropriate Lync CmdLets

Soren, you are correct.  You can populate the required OCS attributes via the provisioning code (i.e. msRTC... there are four required), but for Lync, you must provision via PowerShell.  Such is the case whether or not you use FIM processing or manual as the console is simply PowerShell in the background.

you have to use the cmdlets, to use them in c# you create a powershell runspace, load the libraries you need to use and fire the command.

The powershell management agents (there are more than one) do already provide an interface where you can execute the commands in script form.

So, as Soren points out there is no way to do this from code directly.

Soren, you are correct.  You can populate the required OCS attributes via the provisioning code (i.e. msRTC... there are four required),

With this in mind, what are the 4 required attributes?  If I wanted to provision the sip: address, which we use, what are the 4 attributes we want to provision with FIM that it can then be seen in the Lync console to be enabled?  Currently simply provisioning the msRTCSIP-PrimaryUserAddress has the result of hiding the user from within the console.

The four required OCS attributes to initialize in the metaverse extension should look like the following:

csentry("msRTCSIP-UserEnabled").BooleanValue = True
csentry("msRTCSIP-OptionFlags").IntegerValue = 256
csentry("msRTCSIP-PrimaryUserAddress").Value = "sip:username@yourdomain.com"
csentry("msRTCSIP-PrimaryHomeServer").Value = "<<DN of user account>>"

Hope this helps.

We have been successfully provisioning Lync via FIM through AD for over a year now with success.  (Sorry I did not close this thread out.)

Using FIM we push out the above attribute values - provided by Jose.  We do this at user object provisioning only.  At this point the Lync account is NOT provisioned, but the AD attributes exist.

I do not fully know the process that actually provisions the user in Lync, but I presume it is similar to the update-recipient Exchange command that we leverage for Mail-Users.

I can say, however, that we are not directly provisioning the user via FIM - Lync is.  We are filling out the attributes in AD that Lync then uses to provision.

Any thoughts would be appreciated around that process.

Mateo