We're running PULIST here as part of a batch file (PULIST comes from MS in the resource toolkit). On some machines, the PULIST fails to be outputted to a file or as a pipe, while on others it works fine.
pulist | findstr /I /C:test.exe && ECHO FOUND & GOTO endit
ECHO NOT FOUND
Works on some machines fails on others (even when test.exe is outputted from pulist normally).
pulist > test.txt
Fails on some computers, it just creates a blank test.txt file (overwriting what is in there), but contains nothing... Any ideas?