There is no connector for Lync Server. Thus you need to define custom tasks for Lync enablement . For the actual enablement , add additional tasks on exchange process. These tasks would call out a remote manager script to set the appropriate values in the user in AD for lync enablement.1 person found this helpful
You can also create a separate RO for the same depending on your requirements.
AFAIK, for Lynch you need to update few more user attributes in AD.1 person found this helpful
Find out such attributes in AD (Manually create Lynch and capture the changes at AD end)
Use OOTB AD Connector for AD provisioning
Don't forget to update the thread.
The last time I checked AD connector (184.108.40.206) with R1 (220.127.116.11) did not support those attributes. The only way I could do it was via a remote script.1 person found this helpful
Thanks for the replies.
I could either use remote manager, which would mean separate installation to manage. This would need a new RO to be defined.
Or in the After create script of exchange execute the below
#Provisioning a user
$DistinguishedName = “DN of the user”
$Pool = “regional pool defined above”
$SipAddress = “SIP:emailAddress“ by example sip:firstname.lastname@example.org
Enable-CSUser –Identity $DistinguishedName –registrarPool $pool –SipAddress:$Sip
Will post the approach soon.
We have to do the Lync Enablement with OIM 11gr2 as well.
so you able to do that ? Could you please share the approach.
Also AD Connector 18.104.22.168 does not support the Lync attributes?
for enabling a user what are all the necessary and minimum parameters required.... other than sip in proxyaddresses
thanks a lot!