User account issue
Posted: 11 Jun 2015 4:40
We use Control-M v8 in a Microsoft environment (Windows 2008, Active Directory, and SQL Server 2012). Our Control-M environment has a EM, Server, SQL and multiple Ctrl-M Agents deployed.
We are facing a problem with scheduled jobs. All our jobs are define with a user account in the job properties (run as parameter). We use almost 9 to 10 different Active Directory user accounts for all our jobs. For an unknown reason, some jobs use the user account to execute the task, but some others not. The tasks we are talking about consisted of file creation, file copy from one server to another, so very simply tasks.
We made a trace with the Procmon tool (systeminternal). For the job who do not use the user account define, we see they use the “NT authority System” account and we have and “Access Denied” on the task he try to do. Why jobs use the good user account and some others use the “NT authority System” ?
Anyone facing the same issue ?
Serge
We are facing a problem with scheduled jobs. All our jobs are define with a user account in the job properties (run as parameter). We use almost 9 to 10 different Active Directory user accounts for all our jobs. For an unknown reason, some jobs use the user account to execute the task, but some others not. The tasks we are talking about consisted of file creation, file copy from one server to another, so very simply tasks.
We made a trace with the Procmon tool (systeminternal). For the job who do not use the user account define, we see they use the “NT authority System” account and we have and “Access Denied” on the task he try to do. Why jobs use the good user account and some others use the “NT authority System” ?
Anyone facing the same issue ?
Serge