We have a cmd script on a server which we access through a UNC path like
\\machine\some_path\x.cmd. (Specifically, it is a wrapper around a customized cygwin installation with the goal to have identical installations on all clients. The installation destination needs admin rights.)
It has worked as intended for a number of users, but today several attempts on one machine failed (even though the prerequisites, like the destination folder, exist). This was during a remote session, which I cannot immediately replicate, which is why I'm asking here: Only after the fact did we realize that we probably started it differently than the other users.
Procedure 1: Open a console as administrator and execute
\\machine\some_path\x.cmd. This has worked in the past.
Procedure 1: Open an explorer, change to
\\machine\some_path, and right-click
x.cmd. Choose "Run as administrator". A console opens, the installation starts, and then fails with failures to create files.
The errors could obviously be permission issues, but I would find that surprising: I started the "root process" as administrator and would expect child processes to inherit the privilege. Is that not so?