Scheduled jobs, password hell....

[cgilley]

So I'm the poor schmuck that gives a crap about backups. I have scripts that are supposed to run every night, but due to IT corporate domain nonsense they make me change my password. The scripts are run from a local admin account (non-domain) but every time I change my network password, all the scripts stop running. The last month, I have thrown MS under the bus where all clowns belong. I've never dealt with so much CF from them.

My corporate IT support is lacking, so I'm out here looking for a "stupid, this is how you fix it" answer. I'm the stupid guy. I'm certain it's a password issue, but I'm angry. These things (backup scripts) should run without this much crap going on. Yes, I have the "use local password" set, but it doesn't work. I'm over in the task scheduler, and when I fix the snapshot tool (Thanks Microsoft brandon ) that an update killed off.. I'll post screen shots if necessary.

fwiw, I'm over in the task scheduler. The tasks are supposed to run under local user account. I'm on a server but I know it's physically connected to the RAID. There is no network access involved - all backups are effectively local on the hardware.

Ideas or suggestions? I have to be missing something obvious. I'm up for "stupid, click this button" suggestions.

 

[ChatGPT]

It sounds frustrating to deal with password-related issues affecting your scripts. Here are some steps you can take to adjust your Task Scheduler tasks to account for password changes: 1. Reconfigure Task Scheduler: - Open Task Scheduler and navigate to your task. - Right-click on the task and select "Properties." - Go to the "General" tab and click "Change User or Group." - Re-enter your username and updated password. 2. Local Admin Account: - Ensure the Task Scheduler is set to run under a local admin account that is not affected by domain password changes. 3. Adjust Credential Storage: - If the tasks are running under a specific user account, update the task settings to save the current credentials for the task. 4. Check Task Triggers: - Verify that the task triggers and conditions do not conflict with the password changes. Ensure they are set to start when specific conditions are met. 5. Review Task Actions: - Confirm that the actions in the task are set to use the local admin account and that the correct credentials are stored. 6. Task Condition Updates: - If the task only runs when the user is logged in, try changing this condition to see if it helps ensure the task runs without the need for an active session. 7. Consider Script Adjustments: - Depending on the scripts and tools used, you might need to modify them to store encrypted credentials or ensure they function correctly after the password change. By reviewing these settings and adjusting where necessary to accommodate password changes, your Task Scheduler tasks should be able to run seamlessly even after you update your network password. Let me know if you need further assistance or encounter any specific issues during this process.