We want to enable new users for Lync as they are provisioned. I understand that this requires the use of the Powershell cmdlets. My question is, how does one do this using only the Synchronization Service?  We do not license the F

Hi,

You can use the Powershell MA to run from Soren Granfeldt : http://blog.goverco.com/p/powershell-management-agent.html

Regards,

Can anyone provide an example?  I have created an MA and written the provisioning code to create a new connector, but I can't see that the Export run on the MA extension is actually calling the PowerShell 'export' script.

Also, not being a PowerShell guy, any tips to writing the PS script would be very much appreciated.  Is there a way to attach a PowerShell debugger to the FIM service so that I can actually see if/when it is being called?

T

AFAIK there is no way to attach a PS debugger to the FIM Sync Service. But you could test the export script just using the PS command line. If you're using my MA and have enabled "Export Simple Objects", you actually just getting PSCustomObject objects in the pipeline, each one of them having a attribute values as properties.

So create a custom object and pipe that object into the export script and test. Also enable logging for the PSMA to see any script errors (http://blog.goverco.com/p/psmalogging.html) - that may also give you a hint of any errors.

There are plenty of download samples on my blog as well to help you get started.

In the near future, I'm doing Lync provisioning using this MA at a customer, and I may just blog about it and post some sample scripts for download.

Thanks, Soren. It would be great if you could post some more about this.

After quite a while, I finally put some scripts online for download - http://blog.goverco.com/2015/02/lync-sample-scripts-for-psma-55.html

I have done this with just setting LDAP attributes.   I used this URL as a reference:

http://www.andrewparisio.com/2012/09/auto-provision-lync-2010-users-via-ldap.html

This is dangerous. You will always be playing catch-up with microsoft Lync upgrades and changes from Lync 2010 to 2013 to 2015 etc.. Mixed Lync versions in use could become a major maintenance headache.

Much better to use the Lync cmdlets one way or another.

With or without FIM I dont see a problem with a start of day PS script to examine AD and see if user has a mailbox and has no proxyaddress starting sip: if these conditions are met run the Enable.CsUser cmdlet.