I just realized that operating system command execution does not work on Windows console if the IRIS service is started using a different user than Local System account (the default).
I always change the user configured in the IRIS service and I believe this is a standard good practice, particularly in "real" environments (be it production, stage, test or development) that are part of Windows Active Directory Domain.
When IRIS service starts using any user, including Administrators members, using "!" or "$" from the terminal prompt to run a OS command fail, nothing happen.
.jpg)
.jpg)
.jpg)

.png)
.png)
.png)
.png)


