This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

User Provisioning without the AD object created by AR

Hi there, just after some help please. 

Active Roles 7.0

We currently use another Oracle based system to create user objects in AD.  Is there a way to still use the User provisioning Active Roles policy even tho it didn't created the AD object?  AR would effectively need to run the policy over an object it didn't create.  I cannot see a method to do this easily but want to make sure before looking at other options.

 

It would be great if it could because I can take advantage of all the mailbox creations and notifications etc...

 

Cheers

 

Jason

 

 

  • Please take a look at the below previous posts. Even though they are from a few years ago, they are still relavent. You won't really be able to utilize the provisioning policies as defined because it is script modules added to a policy object that can be queued off of actions done in AD outside is ARS.

    www.quest.com/.../dirsync-connector


    www.quest.com/.../activeroles-policies
  • My idea is following:
    Process1) automated independent of AR create “staged” “blank” AD users (no mbx, no/few properties populated) in OU=StagedUsers
    Process2) Scheduled script calls AR enumerated OU=StagedUsers, and sets edsaCreateMailbox =$true and read/resets Department, Title, Company and pother attributes which triggers AR Policy to take an effect.
  • Hi there, some of the links within the links you provided no longer work. I am still finding it difficult to move froward with this. I'm new to AR. Any other help would be appreciated.
  • Hi there, some of the links within the links you provided no longer work. I am still finding it difficult to move froward with this. I'm new to AR. Any other help would be appreciated.
  • Aidar's suggestion was a good one. If you really need help on implementing specific use cases, you will have to tell us what they are. For example:

    When a new user gets provisioned, we need to:

    1) Create a mailbox for the user (is this on-prem or Cloud?)
    2) Put the user into specific groups based on (for example), their Department
    3) Populate the Manager attribute based on ?

    etc. etc.