Background process using local system account

Hi All

I am running a background process and having issues running from Orchestrator. From Investigation, found out that the Local System Account needs to have access to the shared drive. Now because of security issue, the option to give local system account access is not possible. Is there any other options available so that i could run background processes from Orchestrator and give users the flexibility to change the config files and have access to log files that the bot creates.

@Senshil_Kumar - you can try create a network drive workaround option manually…

  • do a map network drive
  • select a drive letter, and provide shared path
  • check connect using different credentials
  • click on finish and provide user credentials who is having an access.