We are seeing problems with the web editor not detecting change to the files outside of the site using VS Code or PS ISE. This is also true for the configuration files and it also seems to be the same problem with the auto deploy function.
Our PSU service is running under a managed service account (gMSA) and it have got the permissions to read and edit the folders where the script and dashboard files are located. It is also a member of the local policy ‘Back up files and directories’ which should give the necessary permissions to use the FileSystemWatcher. We have also tried giving it full administrator permission on the server which also doesn’t work.
So i decided to test the FileSystemWatcher using the managed service account with the asynchonous script found at Monitoring Folders for File Changes - powershell.one to see if it worked.
I started powershell as the managed service account using PSExec and then ran the FileSystemWatcher script.
PSExec64.exe -i -u domain\gMSA$ -p ~ powershell.exe
Then editing some file and instantly i see the script detect that there was change to the files.
This leads me to believe there is a issue in PSU that needs to be fixed.
I haven’t got a GIT account, so i cannot post this as an issue there.
I made a similar post regarding the auto deploy feature last year which also have information on how we run PSU.
Auto Deploy feature doesn’t work - PowerShell Universal - Ironman Software Forums
Product: PowerShell Universal Version: 3.7.6