What's new 
I’m testing custom scripts on a Windows device and I’m confused by the status shown in Hexnode. A program installation policy showed Success, but the program did not install. I also tried a file creation policy to create a text file in a few folders, and that also showed Success even though no file appeared. There were no obvious Windows Event Viewer errors either.
To check whether scripts were really running, I tried a very simple PowerShell script with a non-zero return code, but Hexnode still marked it as Success. I also tested a script that writes marker files to locations like Windows Temp, ProgramData, Public Desktop, and Public Documents, then prints the result with Write-Output.
Does Success in Hexnode mean the script logic completed successfully, or only that the script was launched? Also, does the script need to already exist locally on the Windows machine before using Execute Custom Script?
40 Views
