Batch is great for very simple tasks, but if you want any significant control flow it will be simpler in powershell. Powershell also seems a lot more expressive and does not rely on that huge amount of external applications as a batch script does if you want to control stuff other than "start something with these arguments".
For my server I wrote a few scripts, that lints over my mods sources, "pboizes" the necessary files, puts together a server environment folder, updates, starts, stops and monitors the server. Once I have them in a presentable state, I'd be happy to share them.
My point is that, when a script gets bigger, more functional, the complexity increases a lot faster in batch, than it does in powershell.
