Things to look for:
- The account you are using needs to be a local admin account and not a domain account with local admin rights.
- Go to the local Security Policy and under User Rights Assignment make sure the user is assigned to the “Log on as a batch job” policy.” Is assigned to the user you are trying to use.
- Under, local policies/security options make sure the “Network Access: Do not allow storage of passwords and credentials” is DISABLED
One of those or a combination of the 3 should resolve your issue.
I use a Domain Account with admin rights, but I had to add the domain account to the local administrators group.
When specifying the acccount name, I use the following syntax:
This works for me in both NCM6.1 and 7.0.3
Only a local admin account is supported, so regardless that a domain account has worked on this or any version, it has never been a supported account.
Often, changing it to a local account has resolved such issues.
More to the point, NCM jobs are basically setup as normal OS jobs in task scheduler.
As a test, you can simply open the OS task scheduler and create a job, if you get the same error, the issue is permission within your OS or security and not really anything within NCM.
That being said, I suspect your issue is more security policy related and not really account related.
Have you looked at options B and C stated above?
a. I have both accounts... both a local Admin account, and a domain account in local Admin group... it has always worked, but we're moving to new hardware with v10.
b. Yep... assigned correctly.
c. This is Enabled... I have requested that it be disabled...
So, now we'll have to see, once I get that disabled.
I will return with results.
It looks like option C was the correct answer...
When I DISABLED the “Network Access: Do not allow storage of passwords and credentials” under local policies/security options... I AM ABLE to schedule jobs just fine!
Thank you for all your help!
<This post was corrected to state it was DISABLED, not Enabled!>
You are welcome, but I think you meant to say when you "DISABLED" it.
Correct! I edited the post to reflect that.
I am now able to schedule tasks with LOCAL accounts as well as DOMAIN accounts.