Changes
no edit summary
::: I mean, does the "\\server\path\script.cmd" produce a lot of output when started from cmd.exe? If so, add >nul in the install cmd to silence it; probably yu are using /quiet flag, which enables logging to Event Log, and it is getting full. See also [[FAQ]].
:::: There is no difference wether /quiet is set or not. But with ''@echo off'' at the beginning of the script and ''>null'' added to the cmd statement, everything is fine now.