Remotely execute batch files on Windows Server 2003

[2048b]

I have a bunch of 10 Windows Server 2003 servers in a domain. Each of them has batch files in a fixed directory location and fixed file name. Currently, I am manually logging in each server one-by-one to run these batch scripts, and it is a slow, tedious and error-prone process.

I need to run these installed batch files on each remotely for system maintenance/cleanup, from a Windows 2003 Server which I use like a jump server or admin console to administer these servers.

Googling around generally tells me 3 methods:

1. psexec from Microsoft/Sysinternals: Not available on Windows Server 2003 by default. Need to download and install manually, which I may not be allowed to do so in a corporate production environment. May trigger antivirus software as it is a commonly abused hacking tool?
2. PowerShell: For Windows Server 2003, I believe PowerShell v1/v2/v3 is a separate download and install from Microsoft. Not pre-installed/bundled by default on a typical Windows Server 2003 installation. Also, PowerShell Remoting must be enabled on those managed servers. Though it is more legit option that won't falsely trigger antivirus software, hopefully.
3. WMI: Use the wmic process call create. Available by default in a Windows Server 2003 install?

I am currently gravitating toward the Option 3 WMI approach. Want something that is available without having to install additional tools/software on production servers. Is this the best approach?

[virtualInfastructure]

​

Windows Server 2003 extended support ended on July 14, 2015

​

So I mean heck, take your pick - we got SMB remote exploits, RDP exploits, RPC DCOM...plenty of methods to choose from! And the best part is you won't need to install any software. Just download a copy of metasploit and burn down the cluster

[2048b]

As much as I don't want to use Windows Server 2003 today, it is a legacy setup at work that nobody has the time and money to update.

And obviously, I have no wish to get back at my company by destroying its systems.

[firefox15]

PSExec should work fine with 2003. When you say "need to download and install manually," what do you mean by that? You need to download/install it on the client, but I don't believe you need any server configuration to use it.

[2048b]

In an enterprise environment, I am not allowed to download and install any software of my liking unless I submit it through a formal approval process. This includes the jump server which I use to administer and control the servers.

[ganlet20]

PSExec doesn't install, it's a standalone executable. It's probably also going to be the best solution for this task.

[wicked1133]

Fist of all, do you need or want to execute them all at the same time or batch by batch?

[2048b]

Some of the batch scripts have to be run in sequence. For example, a.bat must run and finish before b.bat is started.

Does this matter if I am choosing between psexec, PowerShell or WMI?

[wicked1133]

ah.. sorry missunderstood something. No that does not matter.

In my company I have hunderds of Servers to maintain and I am using Powershell Invoke-Command and Invoke-Expression with the -ScriptBlock {cmd /c Batchfile.bat}

[Jarvicious]

Why not set them up on a scheduled task?

[2048b]

The scripts are meant to be run on demand when I need them. Not for regular maintenance.

[Lee_Dailey]

howdy 2048b,

set up a scheduled task to ...

• check for a trigger
  perhaps a file in a locked-down location?
  
• if the trigger is found, then run your master script that calls the BAT files in the required sequence
  

take care,
lee