Enabling OCS users programatically RRS feed

  • Question

  • Hi guys!

    I'm working on a provisioning application wich is responsible for creating the user´s Active Directory accounts, create the user´s mailbox and enable the user for OCS 2007 R2.

    Until now I'm not sure the best way to enable users for OCS. My dream would be an managed API for enabling users for OCS, wich don´t need to run at the same machine of OCS Server.

    I've found out some ways doing that:

    1 - Set the 'Communications' properties directly in Active Directory User Account, using the System.DirectoryServices namespace. But I'm not sure that it is going to work.

    2 - Use the Office Communications Server Provider API (Microsoft Provisioning System - MPS) interfaces, but couldn´t find any information saying the is possible to use this interface outside the OCS server machine.

    I'll make some tests over the both scenarios and post the result back.

    I'd appreciate if someone post another easy way to enable the ocs users programatically.

    Thanks in advance!
    Monday, March 23, 2009 5:44 PM

All replies

  • Darlan,

    Take a look at this blog post where I detail how to do it via directly manipulating AD attributes:
    Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
    Wednesday, March 25, 2009 12:09 PM
  • I have used this technique to try and provision OCS enabled users, but I am having issues with "OCS User Replicator Error Event ID 30014" in my Event Viewer.  These users are not able to log in via Communicator 2007.  I have tried to explain my problem in the following thread in the "User Replicator & Address Book" section of the forums.  The link to the post is:


    I have also reproduced this by not using a script, and just populating the values using only AdsiEdit.  Is this a problem using this approach, or perhaps its a problem with my environment somehow?
    Tuesday, April 21, 2009 7:19 PM
  • I read through that post and it don't beleive it's a problem with the process but the fact that you have lockdowned permissions throughout your Active Directory.  It appears that either the accounts your are administrating with or the RTCservice accounts (or both) do not have suffcient rights to the specific OUs (or OU tree) to read or modify the objects your are attempting to enable.
    Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
    Wednesday, April 22, 2009 1:10 PM