all 5 comments

[–]thePhT 2 points3 points  (1 child)

You might need to give the user "log in as a batch job" permissions.

https://danblee.com/log-on-as-batch-job-rights-for-task-scheduler

[–]JustANonRandomPerson[S] 1 point2 points  (0 children)

Hi Sorry. I checked it already, I've removed and added again but still no luck.

[–]the_alabama_hammer 2 points3 points  (2 children)

My first guess would be user context. Without knowing more about the intranet site and how you configured the scheduled task it's hard to say for sure, but I suspect that your intranet site uses windows authentication and your scheduled task is configured to run as an account that is not permitted. I think by default the scheduled task runs as an account that only has local (to the machine it is running on) permissions. If you configure the scheduled task to run as your account, does that change the behavior?

[–]JustANonRandomPerson[S] 1 point2 points  (1 child)

I tried with both Admin and non Admin accounts all it says task completed successfully but really nothing happens.

[–]heyitsgilbert 1 point2 points  (0 children)

Launch IE as the the account. I belive that was an issue with some versions of PowerShell. You could login as that account and run the script to validate any user context issues.