title: Run a PowerShell script in Task Scheduler that is located on network location
body: <p>I'm trying to administer PowerShell scripts on a central shared location. At the moment the .ps1 scripts are all stored on many different servers.</p>
  
  <p>The scripts are used in Scheduled Tasks with the 'Action' specifics:</p>
  
  <ul>
  <li>Program/script: powershell.exe</li>
  <li>Add arguments (optional): G:..\scriptABC.ps1</li>
  <li>Start in (optional): C:\Windows\System32\WindowsPowerShell\v1.0\</li>
  </ul>
  
  <p>Now the goal is to have them all on a shared location:</p>
  
  <ul>
  <li>\\domain\root..\scripts\scriptABC.ps1</li>
  </ul>
  
  <p><strong>Problem:</strong>
  When I update the 'Add arguments' field to "\\domain\root..\scripts\scriptABC.ps1" and try to start the task, it'll say Running for a few seconds and than Ready again, but nothing happened. So it works like a charm when a local drive is specified, but not when a UNC path is specified.</p>
  
  <p>Additional info:</p>
  
  <ul>
  <li>Working on Windows Server 2012 R2</li>
  </ul>
  
  <p>Any thoughts?</p>