Timeline for Robocopy with Task scheduler in invisible mode for KIOSK mode or alternative
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 21, 2023 at 2:41 | comment | added | TSS | I tried robocopy directly and it behaved the same way. Our setup is : Service account dedicated for KIOSK purpose will be using that application in KIOSK mode on Windows 10 on a production computer. Service account have write access on network drive where it saves all test data at the end of the test, however as back up we will be saving it locally in case of network outage. Now, we want to automate the local drive content to network drive and scheduling with robocopy was one approach but the cmd, powershell takes up focus which leads to issue on the manufacturing Software. | |
| Nov 18, 2023 at 15:14 | comment | added | Chris Keydel | In order to run robocopy directly, in a command prompt, enter "where robocopy" and it gives you the path, normally "C:\Windows\System32\Robocopy.exe". If you call it with full path it should work. Also, on the permissions issue, AFAICS your kiosk user only needs access to the ressources that are being copied, i.e. the local drive and the network drive that you are copying to, not so? | |
| Nov 17, 2023 at 23:50 | comment | added | TSS | 1. We cannot use that option to run when user is logged in as we are using a service account dedicated for KIOSK computer. In order to run whether user is logged or not, we would have to give permission to the service account to log on as a batch user which could open other can of worms. 2. I was not able to run robocopy directly, perhaps I am not sure what the syntax is? Can you please help with that? On related to this, I did try to run as powershell script but that behaved the same way as batch file. | |
| S Nov 17, 2023 at 8:08 | review | First answers | |||
| Nov 17, 2023 at 8:20 | |||||
| S Nov 17, 2023 at 8:08 | history | answered | Chris Keydel | CC BY-SA 4.0 |