Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a scheduled job that runs each night using ntbackup which copies a folder on my HDD to a network share.

The problem is that every time I'm required to change my Windows password I have to remember to change it in ntbackup aswell, otherwise the backup fails silently i.e. I get no warning that the backup isn't being done.

Is there a way to schedule this job so it will automatically pick up my new Windows password, or somehow not be tied to my main login?

My user account type is Debugger, not full Administrator, so I'm not sure if that would restrict me in any way, e.g. still forcing a four-weekly password change on a dedicated user account for this. The PC runs XP SP2 on a Windows Server 2003 R2 domain.

share|improve this question

You should be able to specify the account that ntbackup runs under when you set up the scheduled task.

I'm not running XP on this machine so I can't double check where the options are, but on the new task dialog there should be an option for specifying the user. See this guide (which is for a defragmentation, but the same logic applies) for the various screens.

You'll probably have to log in as an administrator to create the account. The new account still needs a password (obviously), but you could make this a pass phrase as you only need to type it when you set up the task. Oh yes, I should make it clear that the password on this account is set to never expire.

If you feel you need extra security then you can give this user no access to folders on the hard drive except for those it needs to backup, to which you give it just read access. You then just give it write access to the network share drive. It will need execute access to the folder containing the ntbackup of course.

share|improve this answer
Thats exactly the way we used to od it at my old work. We had an account that only ran all the scheduled jobs that the password was never changed on. Saves the tiresome changes to all the scheduled jobs when User passwords need to be changed. – Joe Taylor Mar 10 '10 at 10:09
Thanks, seemed to work with my debugger account. I didn't realise I would be allowed to create a local account with higher privileges than my own domain account. – Lunatik Mar 10 '10 at 10:49
@Lunatik - you might be a local admin on your machine, which might give you the right to create a new account. I'm not 100% sure though. – ChrisF Mar 10 '10 at 11:00
Nope, this didn't work for some reason. The backup failed and the 'run as' user had changed back to my normal login when I checked. Wierd. – Lunatik Mar 11 '10 at 7:27
@Lunatik - something else must be going on then as this should work - we used it all the time at my last-but-one job. – ChrisF Mar 11 '10 at 8:53

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .