I am using PAM 3.0.1. I have the current Windows Proxy running on Windows box 2 (Windows Server 2012 R2). The service is running under the local Administrator account. It is set up / able to mange local account passwords on Windows box 1 (Windows server 2008 R2).
What is interesting, if i re-open the target account (adm1), supply a password to PAM to change the account to, then manually update the task on Windows box 1 to that password, then it will remain in sync with PAM (PAM will update the Task password along with the account password). Scratch that - it does not stay sync'd. Wondering if i am performing something out of sequence that is preventing the sync-up. The Service syncs up immediately - no problems there.
I wrote a Tech Tip on this not long ago. You should be able to download it from this page: Tech Tip: Configuring PAM to Manage Passwords for Scheduled Tasks on a Windows Server.
Yes thank you. I used that as a guide to get this far. In your document, section "Rotate the Password" is where I am getting the error. The task's password is not updated.
Make sure that the account being used for the scheduled task has the necessary rights.
So it seems there was an issue with the Windows Proxy released with 3.0.1. A patch is in the works to resolve the 3466 error. However, what is interesting is that Scheduled Task management is a little more sensitive than Service management. It seems that to take a Scheduled Task under management, the password the Scheduled Task has stored must match what is in the CA PAM credential vault. This means you may have to update the Task's password first, then discover it and take it under CA PAM management.