Even better, if your application is written within the limitations of CMD batch files, it'll be trivial for any admin who cares and has a copy of notepad to pick it apart, if needed.
I've spent years of my working life writing and maintaining batch files, from synchronizing multi-threaded jobs to the polymorphic (you realize cmd.exe stores the next command as a byte offset into whatever is on disk when it goes to read at that offset?). It's true cmd.exe is ubiquitous and easy to modify at first, but "within the limitations of CMD" will come back to bite you.
Version one:
if "%var%" == "false" goto endif_var
echo Something
call :something :endif_var
Version two ("hey, cmd has multi-line if statements!"):
if "%var%" == "false" (
echo Something
call :something
)
Version three ("this looks simple to understand, let me modify it"):
if "%var%" == "false" (
echo Something
rem something else because something is borked
call :somethingelse
)
Wham! Innocent admin can't figure out what the heck happened to the batch file, it doesn't work any more.
One day he may realize that his statement was turned into:
if "%var%" == "false" ( echo Something & rem something else because something is borked & do somethingelse )
The innocent comment killed everything after it.
You said it.
-Malloc