Windows 10: Accessing NAS from task scheduler to run under SYSTEM

Discus and support Accessing NAS from task scheduler to run under SYSTEM in Windows 10 Network and Sharing to solve the problem; I'm trying determine if a (non-Microsoft) product creates a security exposure. In order to do this I need to run a task under "NT AUTHORITY\SYSTEM". My... Discussion in 'Windows 10 Network and Sharing' started by pokeefe0001, Jun 22, 2018.

  1. POKEEFE0001
    pokeefe0001 Win User

    Accessing NAS from task scheduler to run under SYSTEM


    I'm trying determine if a (non-Microsoft) product creates a security exposure. In order to do this I need to run a task under "NT AUTHORITY\SYSTEM". My first step was to create a task that accesses a public share on NAS and schedule it to run under SYSTEM. (I'm not really interested in access to the public share, but I needed to make sure the task works before worrying about network credentials.) My test is to perform an RCOPY of a directory from the public share to a local drive. The RCOPY uses the UNC rather than a drive letter.

    I get "ERROR 58 (0x0000003A) Accessing Source Directory \\<server name>\Public\Test\Data\
    The specified server cannot perform the requested operation."

    If I run the task under my own id I have no problem so I know it's not the server's fault. I am not using "Run with highest authority" under either id (if that matters).

    Any idea why access to a public share would fail?

    :)
     
    pokeefe0001, Jun 22, 2018
    #1
  2. MONICA CAM
    Monica Cam Win User

    Window's Task Scheduler Not Running

    Hi,

    To assist you better, kindly provide us more details by answering the following questions:

    • Have you tried recreating the task? If so, are you getting the same issue?
    • Have you tried creating a new task?
    Meanwhile, we suggest that you ensure that the Task Scheduler is running. You can verify if the service is running by following these steps:

    • Press Windows key + R on your keyboard.
    • Type services.msc and hit Enter.
    • Under Services (Local), make sure that the Task Scheduler service's status is
      Started or Enabled.
    Should you need further assistance, feel free to get back to us.
     
    Monica Cam, Jun 22, 2018
    #2
  3. MARCINMROWIEC
    MarcinMrowiec Win User
    Scheduled tasks run with elevated privileges can't access stored Windows credentials

    It seems that after Creators update scheduled tasks run with elevated privileges ('run with highest privileges' option) can't access stored Windows credentials. Is that a bug or an intentional change and is there a recommended workaround?

    Here's one way to reproduce the behaviour:

    • Start Credential Manger and add some Windows share credentials.
    • In a console window type 'cmdkey /list', which should list the added credentials
    • Create a task in a task manager:
      • Trigger: on user logon
      • Action: run cmd.exe
      • Tick the 'run with highest privileges' option
    • Reboot the machine and log in
    • In the console window (let's call it 'console 1') opened from the scheduled task type 'cmdkey /list'. This most likely won't display the credentials added in step 1 and properly listed in step 2. ->
      This looks like a bug
    • Now, without closing 'console 1' open another console window as an administrator (let's call it 'console 2') and type 'cmdkey /list'. This will properly list credentials added in step 1.
    • Switch to 'console 1' and type 'cmdkey /list' again. This time the credentials are listed properly, unlike in step 5. It looks like an access to Windows credentials was somehow 'unlocked' by step 6.
     
    MarcinMrowiec, Jun 22, 2018
    #3
  4. ANTONETH BER
    Antoneth Ber Win User

    Accessing NAS from task scheduler to run under SYSTEM

    Unable to run Task Scheduler

    Hello Varun,

    Let's determine the cause of the issue. To get started, I'd like to get the following information:

    • Is this your first time to encounter this issue? If so, did you make any changes to your computer's configuration prior to this?
    • Are you getting any error messages?
    • Can you also please confirm the current build of your Windows 10?

      (Type winver into the Cortana search box, then hit
      Enter      .)

    Meanwhile, I suggest that you try starting the Task Scheduler through command line. To do so, please follow these steps:

    • Open Command Prompt (Admin).
    • Type this net start task scheduler and hit Enter.

    We're looking forward to your response.
     
    Antoneth Ber, Jun 22, 2018
    #4
Thema:

Accessing NAS from task scheduler to run under SYSTEM

Loading...

  1. Accessing NAS from task scheduler to run under SYSTEM - Similar Threads - Accessing NAS task

  2. Task scheduler is not running randomly

    in Windows 10 BSOD Crashes and Debugging
    Task scheduler is not running randomly: Hi, I had set up jobs in Task Scheduler in my computer but part of them are not running up as scheduled time. What's the reason to lead this issue? What if I had set up too many jobs in Task Scheulder? Is Window version too old be the reason?...

  3. Run Task Scheduler

    in Windows 10 Gaming
    Run Task Scheduler: I am trying to run a Powershell script in Windows 10 21H2 version using Task bar and the PS window pops up. Later found out that this is happening because the task is run as "Run only when user is logged on".I tried to set this to "Run whether user is logged on or not" and...

  4. Run Task Scheduler

    in Windows 10 Software and Apps
    Run Task Scheduler: I am trying to run a Powershell script in Windows 10 21H2 version using Task bar and the PS window pops up. Later found out that this is happening because the task is run as "Run only when user is logged on".I tried to set this to "Run whether user is logged on or not" and...

  5. Run Task Scheduler

    in Windows 10 Customization
    Run Task Scheduler: I am trying to run a Powershell script in Windows 10 21H2 version using Task bar and the PS window pops up. Later found out that this is happening because the task is run as "Run only when user is logged on".I tried to set this to "Run whether user is logged on or not" and...

  6. Task scheduler run as system and logged in user

    in Windows 10 Support
    Task scheduler run as system and logged in user: I have a script which must be run as system in task scheduler. But at the end should be runned an exe file in that script as logged in user withouth username and password. Is that possible? 182571

  7. Scheduled task not running

    in Windows 10 Customization
    Scheduled task not running: I use the "portable apps" platform to hold a lot of small programs I dont want installed - but even from my C: ssd its very slow to load. So I have set up a scheduled task to run it as soon as the pc becomes idle. [ATTACH] However it does not run. Even when I right-click...

  8. Task scheduled in Task Scheduler won't run from shortcut

    in Windows 10 BSOD Crashes and Debugging
    Task scheduled in Task Scheduler won't run from shortcut: I have a task set up in Task Scheduler on Win 10 Pro 64-bit and it runs correctly when run from Task Scheduler. I cannot get the task to run from a shortcut. I do not know whether this is relevant, but in the Settings window of Task Scheduler it shows the checkbox next to...

  9. Task Scheduler Not Running

    in Windows 10 BSOD Crashes and Debugging
    Task Scheduler Not Running: I've already tried and a lot of solutions for this but sadly I still don't have a solution. I've also tried these steps in this link (https://computerstepbystep.com/task_scheduler_service.html), still no luck What happened is I'm trying to update my GeForce Experience but I...

  10. Accessing NAS from task schedlued to run under SYSTEM

    in Windows 10 Support
    Accessing NAS from task schedlued to run under SYSTEM: I'm trying determine if a (non-Microsoft) product creates a security exposure. In order to do this I need to run a task under "NT AUTHORITY\SYSTEM". My first step was to create a task that accesses a public share on NAS and schedule it to run under SYSTEM. (I'm not really...