• State Verified Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 61 subscribers
  • Views 14299 views
  • Users 0 members are here
Options
Related
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

Active Roles AD How is this licensed?

nytramuk
over 7 years ago

Hi

I need to know how the licensing is worked out for Active Role


Is it per user? If so, is that enable user only ALL users?  What about other objects do they need a license?

 

Thanks in advance

 

 

Parents
  • 0 over 7 years ago

    I would suggest you have a read through the AdminGuide (starting on pg 563 for version 6.9) where there is discussion of "Managed Object Statistics".

    To quickly summarize:

    1) There is a built-in scheduled task called "Managed Object Counter" that counts managed objects

    2) You can choose to exclude objects (i.e. their OUs) from being counted by the Statistics process by applying the policy called "Built-in Policy - Exclude from Managed Scope" to the OU(s).  So to your point about your "leavers", you could apply the above policy to the OU(s) containing these objects and your statistics would no longer count them.

    3) If you would like to be warned when you are reaching your managed objects limit (as determined by you), you can configure notification of this by a built in workflow called "Notification of managed object excess (Template)" found in Configuration | Policies | Workflow | Builtin

Reply
  • 0 over 7 years ago

    I would suggest you have a read through the AdminGuide (starting on pg 563 for version 6.9) where there is discussion of "Managed Object Statistics".

    To quickly summarize:

    1) There is a built-in scheduled task called "Managed Object Counter" that counts managed objects

    2) You can choose to exclude objects (i.e. their OUs) from being counted by the Statistics process by applying the policy called "Built-in Policy - Exclude from Managed Scope" to the OU(s).  So to your point about your "leavers", you could apply the above policy to the OU(s) containing these objects and your statistics would no longer count them.

    3) If you would like to be warned when you are reaching your managed objects limit (as determined by you), you can configure notification of this by a built in workflow called "Notification of managed object excess (Template)" found in Configuration | Policies | Workflow | Builtin

Children
No Data