Scheduled Task wi/Business Unit as activity scope...

Question

I created a scheduled task (to export data) with a domain as its activity scope, runs perfectly. I modified it to use a Business Unit as its activity scope, now it doesn't run. There are no exceptions and there is no log summary, which makes it appear the task didn't even 'fire'. I also tried initiating it manually using "Run Now" and I can see attempts to run, but still not output nor are any entries/exceptions created in the log. I thought maybe in the "Assignment Options", the property "This Business Unit object" under "Make the task effective for" should be checked, but the property is not editable in the dialog.

Comments

Hello,

Can you post here or send us the Membership Rules of your Business Unit?

---

(|(&(sAMAccountType=805306368)(employeeType=*Contractor*))(&(sAMAccountType=805306368)(employeeType=*WC Employee*))(&(sAMAccountType=805306368)(employeeType=*Agency Temp*))(&(sAMAccountType=805306368)(employeeType=*Volunteer/Partner*))(&(sAMAccountType=805306368)(!(termFlag=*))(!(userAccountControl=*Disabled*))))

---

Hello,

OK, understood, so the Business Unit is query-based. And what about the scope of the query? Is it set to All Domains or to a particular domain, OU or Container?

---

It's set to All Domains

---

Hello,

Hmm ... That's strange. What version of Adaxes (including the build number) are you running? Can you post here or send us a screenshot of the actions / conditions and assignments of your Scheduled Task?

Also, can you make sure that the task wasn't triggered by checking its Activity History? For information on how to view the Activity History of a Scheduled Task, see the following help article: http://www.adaxes.com/help/?ManageSched ... story.html.

---

Here is how the task is configured.

This is what the task is doing

Import-Module Adaxes
$filePath = '<filepath here># TODO: modify me

# Get domain name
$domainName = $Context.GetObjectDomain('%distinguishedName%')

# Get all users in the target OU and export properties to a file
Get-AdmUser -Filter * -SearchBase '%distinguishedName%' -SearchScope Subtree -AdaxesService localhost -Server $domainName -Properties employeeID, mail, department, wctitle, displayName, telephoneNumber, superUID, buildingName, locationFloor, roomNumber | `
    Select-Object -Property DistinguishedName, employeeID, mail, ssn, department, wctitle, displayName, telephoneNumber, superUID, buildingName, locationFloor, roomNumber | Export-Csv $filePath -NoTypeInformation

Here's the Adaxes console version (does that equate to the version of Adaxes that's running)?

Yes, I had already checked the Activity History and despite its schedule, there are no entries for any runs since I ran it manually on 03/23/2015.

---

The previous image was from the client running on my machine. Here's what's installed on the server.

Answer 1

The reason why your Scheduled Task is not triggered is because it is configured for the Domain-DNS object type, but your Business Unit includes Users only.

Based on the LDAP filter that you use for your Business Unit, it doesn't include any domains, and thus there is not a single Domain-DNS object in the Business Unit that the Scheduled task can be triggered on.

The best way to resolve the issue would be not to use a Business Unit, but rather have the LDAP filter hard-coded directly in the script. If you are OK with such a solution, we'll help you to modify your script.

Comments

Ahhh, this task has gone through a few iterations of design. Initially I designed to task to just see if I could export all users in two domains (one is a 'child') by using the DomainDNS. When I discovered Business Units, I thought that would be an easy way to filter. I guess not.

So I wouldn't be able to select Business Unit instead of Domain-DNS as the object instead of Domain-DNS? Please explain how to use one Task get all users fitting the criteria in the query from two domains.

---

Hello,

We suggest changing the script used in your Scheduled Task. The following version of your script generates a report on all members of the Business Unit whose name is specified by $businessUnitName with properties specified in $propertiesToExport and saves the report into a CSV file specified by $csvFilePath.

$businessUnitName = "My Business Unit" # TODO: modify me
$csvFilePath = "\\Server\share\report.csv"
$propertiesToExport = @(
    "distinguishedName", 
    "employeeID", 
    "mail", 
    "ssn", 
    "department", 
    "wctitle", 
    "displayName", 
    "telephoneNumber", 
    "superUID", 
    "buildingName", 
    "locationFloor", 
    "roomNumber"
) # TODO: modify me

# Find the Business Unit
$businessUnitsPath = $Context.GetWellKnownContainerPath("BusinessUnits")
$searcher = $Context.BindToObject($businessUnitsPath)
$searcher.SearchFilter = "(&(objectCategory=adm-BusinessUnit)(name=$businessUnitName))"
$searcher.PageSize = 500
$searcher.SearchScope = "ADS_SCOPE_SUBTREE"

try
{
    $searchResult = $searcher.ExecuteSearch()
    $objects = $searchResult.FetchAll()

    if ($objects.Length -gt 1)
    {
        $Context.LogMessage("Found more than one Business Unit with name '$businessUnitName'.", "Warning")
        return
    }
    if ($objects.Length -eq 0)
    {
        $Context.LogMessage("Business Unit '$businessUnitName' does not exist.", "Error")
        return
    }

    # Get the Business Unit Members
    $unit = $Context.BindToObject($objects[0].AdsPath)
    $members = $unit.Members()

    $report = @()
    for ($i = 0; $i -lt $members.Count; $i++)
    {
        $member = $members.GetObject($i)
        $reportRecord = New-Object PSObject
        foreach ($propertyName in $propertiesToExport)
        {
            try
            {
                $value = $member.Get($propertyName)
            }
            catch
            {
                $value = "" # The property is empty
            }

            $reportRecord | Add-Member -Name $propertyName -Value $value -MemberType NoteProperty
        }
        $report += $reportRecord
    }
}
finally
{
    $searchResult.Dispose()
}

$report | Export-Csv $csvFilePath -NoTypeInformation

You can leave your Scheduled Task configured for the Domain-DNS object type and include any of your domains in the Activity Scope of your Task. The domain that you include in the Activity Scope is irrelevant, because the script generates a report on members of a Business Unit, and the Business Unit name is hard-coded in the script. The users that will be included in the report will be determined by membership in the Business Unit, and a domain is necessary merely to trigger the Scheduled Task.

---

Results look good!!! I'll let it run scheduled a few times and then I can further tweak it for similar exports. Thanks so much for your assistance.

---

Well I commented too soon. The output is off by two (console vs. CSV).

---

Hello,

The output is off by two (console vs. CSV).

What do you mean exactly? Does the Administration Console show 2 more members of the Business unit that do not show up in the CSV file, do we get you right?

---

It's the reverse, the output contains more than the Console. I ran it again and now it's one off. I'm going to do a comparison to determine which user is missing, and also test with another BU.

---

I tested with a different OU and the number of output results were the same. Closing this thread, but I'll log the output discrepancy on the other business unit as a support request. Thanks for the assistance.