Office Communicator Server and FIM2010
Hello all, The Goal: To automatically enable and configure OCS for a user after FIM2010 has provisioned the user in AD. Does anyone what is envolved? Would this be a powershell script triggered from the FIM side or Exchange side? If there is code available I would greatly appreciate the help. Thank you.
August 18th, 2010 5:40pm

just set all MSRTCSIP-* attributes to whatever needed and that's all. no need to run any scripts. something like this (don't know how to attach a picture): msRTCSIP-FederationEnabled,boolean,true msRTCSIP-Line,string,tel:+74952500000;ext=4346 msRTCSIP-LineServer,string,sip:4346; msRTCSIP-OptionFlags,number,273 msRTCSIP-PrimaryUserAddress,string, msRTCSIP-UserEnabled,boolean,true msRTCSIP-PrimaryHomeServer,reference,"CN=LC Services,CN=Microsoft,CN=ocspool,CN=Pools,CN=RTC Service,CN=Microsoft,CN=System,DC=fabrikam,dc=com"
Free Windows Admin Tool Kit Click here and download it now
August 19th, 2010 2:23am

Some client applications like Outlook 2003 and SharePoint 2007 read the proxyAddresses attribute to show user's OCS presence information. If you wan't to use the presence feature, add sip address to the proxyAddresses attribute in AD.
August 23rd, 2010 6:54am

well, I don't have any rules set for proxyAddresses and my sharepoint sites show user presense with no problems at all. same with Outlook 2003 - I bet it doesn't use proxyAddresses for presence information.
Free Windows Admin Tool Kit Click here and download it now
August 23rd, 2010 8:20am

Ok, so proxyAdresses is not mandatory to show the OCS presence information. But if you're missing the presence information in Outlook, adding sip address to proxyAddresses can solve the problem. I'm not that familiar how OCS works, but it seems that there are scenarios where OCS clients read the proxyAddresses attribute. For example if the primary email address is different than sip address or OCS is installed in separate resource forest.
August 24th, 2010 2:57am

The above works but does not sync the Addressbook nor does it allow the user that just had communicator enabled to look up a user by typing in the user account name.
Free Windows Admin Tool Kit Click here and download it now
September 12th, 2011 3:05pm

If I were to troubleshoot this I would analyze an AD user attribute dump using repadmin or another tool. You could perform a dump, then OCS-enable the user using the "regular" OCS console. Then dump again. Compare those two and you will likely find out what attributes are relevant and which are not.
September 13th, 2011 3:39am

while pure export of MSRTCSIP-* works for OCS, it doesn't work for Lync. you have to use powershell cmdlet to activate a user.
Free Windows Admin Tool Kit Click here and download it now
September 13th, 2011 9:04am

To which OCS groups ADMA need to added for provisioning user, in other words premission required for FIM ADMA a/c on OCS
September 27th, 2011 5:22am

you need two powershell scripts, one ps script will enable communicator for a new user but the workflow for enable a new user has to be triggered by something it doesnt have when it is first created in FIM such as domain or UID and the requestor should be the sync engine. use a powershell workflow.
Free Windows Admin Tool Kit Click here and download it now
October 29th, 2011 9:35am

Thank you all for all your input - the Exchange Admin here actually took this task off my hands :) cheers James
May 22nd, 2012 1:28pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics