Changes
no edit summary
:: Only something like ''Executing script.cmd ...'', when client is configured with /debug-Option (and of course /synchronize). The script itselfs contains several ''shortcut.exe''-statements to create shortcuts in a certain folder. Shortcut.exe itselfs produces messeages to the commandline, but they do (unfortunatly) not apear on the consle of WSH.
::: 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]](or here: [[FAQ:en]]).
:::: 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.