Set AD account expiration date via orchestration

[Shannon Burns]

I tried setting the account expiration date of an AD account via orchestration, but am getting an error

I can confirm via workflow context that the userid field is the username in AD and the 'end' variable is set to a date in MM/DD/YYYY format.

Anyone know what I'm doing wrong?   The error I'm getting is

Thanks,
Shannon

[Mihir Mohanta]

Please go through the below link

Runbook Automation - RBA - Setting the AccountExpires Date field in AD

[Shannon Burns]

OK, that makes sense as to why I'm getting the syntax error.

I figured out how to make the custom powershell activity, but the output is always null.   So I guess I made some mistake there as well. I tried using the scratchpad as the input and tried just entering a date manually.   No errors were returned, but both still evaluate to null.

Thanks,

Shannon

[Shannon Burns]

I've now got syntax that works when I paste it into the server iteself.   But when I do it from the custom powershell activity, it tells me invalid credentials.   But considering I'm using the same credentials that I successfully use to add/remove from groups and to disable accounts, it's not that the password is wrong.

Anyone know why I might successfully use those activities that are built in for Powershell, but then not be able to use the same credentials for a custom Powershell?

Thanks,

Shannon

[Steven Parker]

Did you figure this out?   I really don't want to have to run Powershell just to convert a date to a Windows File Time, but is that the only option?