Script Repository

Update list of property values in Property Pattern based on search results

September 17, 2019

The script updates the list of values allowed for a property in a Property Pattern based on search results.

To execute the script, create a Scheduled Task configured for Domain-DNS Object type.


  • $propertyForList - specifies the property value of which will be added to the list of allowed values in the Property Pattern;
  • $propertyForSearch - specifies the property values of which will be used for search;
  • $valuesForSearch - specifies the values of the property specified in the $propertyForSearch variable;
  • $patternName - specifies the name of the Property Pattern that will be used to specify a list of possible values for the property. By default, a built-in Property Pattern named User Pattern is applied to all users.
  • $propertyToUpdate - specifies the property for which the list of allowed values will be updated in a Property Pattern;
  • $isPropertyRequired - specifies whether the property should be set as required in the Property Pattern.

Edit Remove
# Search settings
$propertyForList = "distinguishedName" # TODO: modify me
$propertyForSearch = "description" # TODO: modify me
$valuesForSearch = @("Value1", "Value2") # TODO: modify me

# Property Pattern settings
$patternName = "User Pattern" # TODO: modify me
$propertyToUpdate = "manager" # TODO: modify me
$isPropertyRequired = $True # TODO: modify me

function SearchObjects($filter, $properties, $baseObjectPath, $virtualRoot)
    $searcher = $Context.BindToObject($baseObjectPath)
    $searcher.SearchFilter = $filter
    $searcher.SearchScope = "ADS_SCOPE_SUBTREE"
    $searcher.PageSize = 500
    $searcher.ReferralChasing = "ADS_CHASE_REFERRALS_NEVER"
    $searcher.VirtualRoot = $virtualRoot
        $searchResultIterator = $searcher.ExecuteSearch()
        $searchResults = $searchResultIterator.FetchAll()
        return ,$searchResults
        # Release resources
        if ($searchResultIterator){ $searchResultIterator.Dispose() }

# Search Property Pattern
$propertyPatternsPath = $Context.GetWellKnownContainerPath("PropertyPatterns")

$searchResults = SearchObjects "(&(objectClass=adm-PropertyPattern)(name=$patternName))" @() $propertyPatternsPath $False
if ($searchResults.Length -eq 0)
    $Context.LogMessage("Property Pattern '$patternName' not found.", "Warning")
elseif ($searchResults.Length -gt 1)
    $Context.LogMessage("Found more than one Property Pattern with the following name: '$patternName'.", "Warning")
$propertyPatternPath = $searchResults[0].AdsPath

# Build search filter for users
$filter = New-Object "System.Text.StringBuilder"
$filter.Append([Softerra.Adaxes.Ldap.FilterBuilder]::CreateOrred($propertyForSearch, [System.String[]]$valuesForSearch))

# Search users
$searchResults = SearchObjects $filter.ToString() @($propertyForList) "Adaxes://RootDSE" $True

$values = New-Object "System.Collections.ArrayList"
foreach ($searchResult in $searchResults)

# Update Property Pattern
$pattern = $Context.BindToObject($propertyPatternPath)

foreach ($item in $pattern.Items)
    if ($item.PropertyName -ieq $propertyToUpdate)

if ($values.Count -eq 0)

# Create a new item
$item = $pattern.Items.Create()
$item.PropertyName = $propertyToUpdate
$item.IsPropertyRequired = $isPropertyRequired

$constraints = $item.GetConstraints()
$constraint = $constraints.Create("ADM_PROPERTYCONSTRAINTTYPE_VALUERANGE")
$constraint.AreValuesDenied = $False
$constraint.Values = $values.ToArray()

# Save the changes

Comments ( 4 )
Jul 22, 2019
Is it possible to adapt this for use with a Custom Command drop-down list parameter?
Jul 23, 2019

Hello Ryan,

Yes, it is possible. Could you, please, clarify what will be specified in the drop-down parameter and how it should be used in the Custom Command?

Jun 26, 2020
Would be cool to provide a copy of this script that reads a CSV file for the listing of possible values. We are going to use this for phone numbers and would be cool to point it at the extract from our phone system for the info instead of copying and pasting the values into Powershell.
Jun 26, 2020


Do we understand correctly that you need the script to just import values to a Property Pattern from a CSV file instead of specifying the values to search manually in the script? If that is not what you need, please, describe the desired behavior in all the possible details with live examples.

Leave a comment