• State Verified Answer
  • Locked Locked
  • Replies 7 replies
  • Subscribers 93 subscribers
  • Views 6869 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

ITOperating Data UID_ADSContainer assigned based on Dynamic Role

pacman_d
over 6 years ago

Hola,

Ok so I have commandeered a custom property on the person to be a list item with (3) values:

  1. Employee
  2. Consultant
  3. AvisoryMember

I have created corresponding dynamic roles to match the above. Lets take employees as our example.

Couple of notes:

  1. Person records that have the value "Employee" in the custom property are appropriately assigned to the Dynamic Role called "Employees"

  2. Every employee gets: 

    • A standard user account definition (Works fine)
    • A standard Mailbox (Standard user account as required account def. works fine as well)

  3. The "Employee" dynamic role has IT Operating Data assigned against the Standard user Account Definition that should assign the OU of the ADSAccount based on the value.

    • Example: TSBAccountDef:Standard User Account (DOMAIN) - ADSAccount.UIDADSContainer
      • The selected OU is "Employees"

  4. The ADSAccount.UID_ADSContainer template is configured as follows:

    • '$FK(UID_Person).UID_Department$
'$FK(UID_Person).UID_Locality$
'$FK(UID_Person).UID_ProfitCenter$
#If ORG Then
'$FK(UID_Person).UID_Org$
#End If
If CBool(Connection.Variables.Get("FULLSYNC")) = False Then
Select Case ($FK(UID_TSBBehavior).ITDataUsage:Int$)
	Case 0:'do not get data from employee
	Case -1:'fill property initially from the ITData of the employee
		If Not $[IsLoaded]:Bool$ Then
			Value = TSB_ITDataFromOrg($UID_Person$, $UID_TSBAccountDef$, Base.TableDef.Columns("UID_ADSContainer")) 
		End If
	Case 1:'update property depending on ITData of the employee
		Value = TSB_ITDataFromOrg($UID_Person$, $UID_TSBAccountDef$, Base.TableDef.Columns("UID_ADSContainer"))
	
	End Select
End If


The issue is that while the dynamic role assignments work great, the corresponding ADSAccount does not move into the OU. I presume that I am missing something as this seems to be a rather straight forward use case.

What am I doing wrong here?

Thanks!

Parents
  • +1 over 6 years ago

    I believe the obvious thing here is wrong. I m quoting from the online manuals here:

    An employee is assigned to one primary location, one primary department, one primary cost center or one primary business role. The necessary IT operating data is ascertained from these assignments and used in creating the user accounts. Default values are used if valid IT operating data cannot be found over the primary roles.

    So, you have two options,

    • Option 1: Your IT Operating data has to rely on the primary memberships of your employee (Department, Cost center, Location, Business Role).
    • Option 2; Overwrite the script TSB_ITDataFromOrg with your own version that uses the secondary memberships as well. Please keep in mind, that a employee can have more than one secondary memberships in each of the role types. That can potentially lead to contradictory IT operating data, depending on your configuration data.
Reply
  • +1 over 6 years ago

    I believe the obvious thing here is wrong. I m quoting from the online manuals here:

    An employee is assigned to one primary location, one primary department, one primary cost center or one primary business role. The necessary IT operating data is ascertained from these assignments and used in creating the user accounts. Default values are used if valid IT operating data cannot be found over the primary roles.

    So, you have two options,

    • Option 1: Your IT Operating data has to rely on the primary memberships of your employee (Department, Cost center, Location, Business Role).
    • Option 2; Overwrite the script TSB_ITDataFromOrg with your own version that uses the secondary memberships as well. Please keep in mind, that a employee can have more than one secondary memberships in each of the role types. That can potentially lead to contradictory IT operating data, depending on your configuration data.
Children
No Data