AR Script - Pass SamAccountName

$Request.Name contains the samaccountname of the in-process user.

If you are launching this from a Change Workflow, the whole script needs to be inside a function that your script activity calls.

$Request.Name contains the samaccountname of the in-process user.

If you are launching this from a Change Workflow, the whole script needs to be inside a function that your script activity calls.

Thanks Johnny. 

I have moved it all inside the function and updated the command below but this still does not seem to fire. 

duoSyncUser -username $Request.Name | out-file $logfile -Append

function onPostModify($Request)
{

# Connect to ARS
Connect-QADService -Service "AR-Server-Name" -Proxy
#Import Duo PowerShell Module
Import-Module Duo

#Date
$DateYear = $((Get-Date).ToString('yyyy'))
$DateMonth = $((Get-Date).ToString('MMM'))
$DateDay = $((Get-Date).ToString('dd'))
#Time
$Time = Get-Date -Format "HH-mm"

#Create Folder structure based on Date
New-Item -ItemType Directory -Path "PATH-Here\$DateYear\$DateMonth\$DateDay" -Force
New-Item -ItemType Directory -Path "PATH-Here\$DateYear\$DateMonth\$DateDay\Logs" -Force

$logfile = "PATH-Here\$DateYear\$DateMonth\$DateDay\Logs\Duo-User-Sync-$time.txt"

duoSyncUser -username $Request.Name | out-file $logfile -Append

} 

So i am seeing the script fire now as its creating the logfile but the log is empty as i dont think its passed the SamAccountName 

duoSyncUser -username $Request.Name | out-file $logfile -Append

If i hard code my SamAccountName in to the command and set the VA then the duoSyncUser runs. So not sure why this is not being passed correctly using $Request.Name  , is there any other work around method of passing this value? 

duoSyncUser -username SamAccountName | out-file $logfile -Append

Try getting it like this:

$UserSam = $DirObj.get("samaccountname")

Thanks Johnny. Thats done the trick.

Appreciate your help as always. Thank you. 

A couple of questions kind of related to this post. 

I know when running the Quest CMD we can use the command below to add a reason in to the change history. Is there away to do that when not using the Quest CMDs? 

-Control @{'OperationReason'="something something"}

Also is there a way as part of that function to obtain who it was that made request? I am thinking i could write it out to a logfile?

There is a technique for adding Change History info when using ADSI-style scripting techniques:

Here's some sample code:

# Assumes use in Change workflow script activity - otherwise just supply a distinguished name

$CurrentUser = $Request.DN

# Bind to the in process user via Active Roles

$ADObj = [ADSI]"EDMS://$CurrentUser"

# Set a property

$ADObj.Properties["Description"].Value = "A new description"

# Set the reason for the change in the change history

$ADObj.NativeObject.GetType().InvokeMember("Control","SetProperty",$null, $ADObj.NativeObject, @("OperationReason","Description modified by script")) | Out-Null
$ADObj.commitchanges()
$ADObj.close()

You can get the name of the Initiator from a $Request thus:

(Note the "by reference" syntax whereby the samaccountname and DN of the Initiator will be stored in the variables specified.)

$Request.Whoami($InitiatorSam,$InitiatorDN)

The above is documented in the SDK.

There is a technique for adding Change History info when using ADSI-style scripting techniques:

Here's some sample code:

# Assumes use in Change workflow script activity - otherwise just supply a distinguished name

$CurrentUser = $Request.DN

# Bind to the in process user via Active Roles

$ADObj = [ADSI]"EDMS://$CurrentUser"

# Set a property

$ADObj.Properties["Description"].Value = "A new description"

# Set the reason for the change in the change history

$ADObj.NativeObject.GetType().InvokeMember("Control","SetProperty",$null, $ADObj.NativeObject, @("OperationReason","Description modified by script")) | Out-Null
$ADObj.commitchanges()
$ADObj.close()

You can get the name of the Initiator from a $Request thus:

(Note the "by reference" syntax whereby the samaccountname and DN of the Initiator will be stored in the variables specified.)

$Request.Whoami($InitiatorSam,$InitiatorDN)

The above is documented in the SDK.

Correction:  $Request.Whoami([ref]$InitiatorSam,[ref]$InitiatorDN)

Thanks Johnny. Let me go search all this. Feel like i have been soaking up info recently. Thanks for the help mate.