I am testing using a centralized scheduling server. I have created
a job that simply opens notepad. It ran locally on the Master server
just fine, but when I tried to run in on the server running the Remote
Agent it fails with an error code of -1, unless I set it run as current
user. When I put in the information for my account in the Run as
Another User section the job fails. I checked the log and found error
1385 - The user has not been granted the requested logon type at this
computer. While I run it, I am logged into both machines with the account
that I am trying to run the job as.

Any suggestions why it is working this way? This appears to be the reverse
of everything I have read previously in this forum.

That user needs "Logon as a batch job privilege" which is missing. It can be granted locally or using Active Directory. By default that privilege is turned off for everybody including admins.

: I am testing using a centralized scheduling server. I have created
: a job that simply opens notepad. It ran locally on the Master server
: just fine, but when I tried to run in on the server running the Remote
: Agent it fails with an error code of -1, unless I set it run as current
: user. When I put in the information for my account in the Run as
: Another User section the job fails. I checked the log and found error
: 1385 - The user has not been granted the requested logon type at this
: computer. While I run it, I am logged into both machines with the account
: that I am trying to run the job as.

: Any suggestions why it is working this way? This appears to be the reverse
: of everything I have read previously in this forum.

This appears to have corrected the problem for jobs just running JAL scripts.
When I tried to launch Notepad on the host server using a job, I got the same
error again. I then logged in locally using the service account that I was using
to run the job and Notepad was listed in the list of recently launched
applications.

I created a batch file with the command "dir d: > d:\test.txt". I can run the
batch file when locally logged in with the service account, but I get the same
1385 login error when I try to run it from the scheduling server.

: That user needs "Logon as a batch job privilege" which is missing.
: It can be granted locally or using Active Directory. By default that
: privilege is turned off for everybody including admins.

You still have the same problem. Did you grant permissions to the right account? Please also note that security settings are cached. I certain cases like this one you may need to restart your computer or logoff/logon after changes.

JAL jobs don't have anything to do with RunAs user option unless you rn them using 24x7 /JOB command

: This appears to have corrected the problem for jobs just running JAL scripts.
: When I tried to launch Notepad on the host server using a job, I got the same
: error again. I then logged in locally using the service account that I was
: using
: to run the job and Notepad was listed in the list of recently launched
: applications.

: I created a batch file with the command "dir d: > d:\test.txt".
: I can run the
: batch file when locally logged in with the service account, but I get the
: same
: 1385 login error when I try to run it from the scheduling server.

It appears that there is also a "Logon as a Service" permission. Once that
permission was added to the account I was able to run the batch job normally.

: You still have the same problem. Did you grant permissions to the right
: account? Please also note that security settings are cached. I certain
: cases like this one you may need to restart your computer or logoff/logon
: after changes.

: JAL jobs don't have anything to do with RunAs user option unless you rn them
: using 24x7 /JOB command