Why can't I create a scheduled task using a domain account?

I don't recall running into this problem before, but I've hit a brick wall today.

I'm trying to create a scheduled task, and I'm using credentials for my domain account, which is also an Administrator account on this local machine, but I keep getting error that says 'access is denied'.

What am I missing here? If the domain account is setup as an admin account on the local machine, shouldn't it be able to fire scheduled tasks?

From serverfault Ducain

• Are you prefixing the domain name and a backslash to your username?
  For example: domain-name\username

  Ducain : Absolutely. This is a domain account I've used every day for years, and it's an admin account on this local machine. MYDOMAIN\MyUserName
  From PaulWaldman

• It's possible that a domain account can get locked out at the domain while still be logged in interactively on a workstation. This could prevent a scheduled task from being created (amongst a host of other problems with services and various layered products).

  joeqwerty : Sounds about right. My advice would be to reboot the machine in question and see if the problem persists.

  Ducain : I have rebooted the workstation - no difference. Weird stuff, and frustrating.

  squillman : @Ducain: what is it that your task will be doing?

  Ducain : @Sqillman - just starts a little VB.NET app.

  squillman : @Ducain is there a UI to it or is it a console app?

  Ducain : It would help me if I knew what you were aiming at here. Are you suggesting somehow the app is responsible for the 'access denied' permission problem when creating the scheduled task? I'm confused...

  squillman : @Ducain sorry, haven't been able to get back to this. I've seen it where a process with a UI will not start or hang in a non-interactive session and was going to look at if this could be related. I've never seen the actual creation of a task fail because of this, but...
  From squillman