Executing Bash and BAT Scripts Across VMware Virtual Machines Using vRealize Orchestrator

Managing a handful of virtual machines is relatively straightforward. Managing hundreds of Linux and Windows virtual machines spread across multiple ESXi hosts is an entirely different challenge. Routine operational activities such as password rotation, security patch deployment, application maintenance, or scheduled reboots quickly become time-consuming, repetitive, and prone to human error.

In many enterprise data centers, infrastructure teams are expected to execute these changes during tightly controlled maintenance windows. Completing the work manually over SSH or Remote Desktop sessions is rarely practical when hundreds of systems are involved. Administrators require a centralized orchestration platform capable of executing standardized tasks consistently across the environment.

This is where VMware vRealize Orchestrator (vRO) becomes an essential operational tool. Rather than logging into every virtual machine individually, administrators can design reusable workflows that remotely execute Bash scripts on Linux systems or Batch and PowerShell scripts on Windows servers from a single orchestration engine.

This article demonstrates how enterprise operations teams can leverage VMware vRealize Orchestrator to automate large-scale administrative tasks across hundreds of virtual machines while maintaining consistency, repeatability, and auditability.

The Operational Challenge in Large VMware Environments

A typical enterprise VMware environment rarely consists of a single cluster or a few dozen virtual machines. It commonly includes multiple vCenter Servers managing thousands of virtual machines distributed across production, development, quality assurance, disaster recovery, and testing environments.

A typical inventory might resemble the following.

Environment	Virtual Machines
Production	420
UAT	110
Development	165
Disaster Recovery	140
Shared Infrastructure	85

Total managed virtual machines often exceed 900 systems.

Although virtualization simplifies infrastructure provisioning, operating system administration continues to require repetitive maintenance activities.

Typical operational requests include:

Changing root passwords after quarterly audits
Rotating application service account passwords
Deploying updated SSH configuration
Installing security RPM packages
Updating antivirus agents
Restarting middleware services
Cleaning temporary directories
Synchronizing configuration files
Updating monitoring agents
Rebooting application servers during maintenance windows

Consider a security team requesting an immediate password change across every Linux server after privileged credentials are exposed.

The traditional approach involves:

Connecting to every server using SSH.
Authenticating with administrative credentials.
Executing the password update.
Recording the result.
Proceeding to the next server.

Even if an administrator spends only two minutes per machine, updating 300 servers requires approximately ten hours of uninterrupted effort. In practice, network latency, authentication failures, and unexpected issues extend the maintenance window significantly.

The situation becomes even more challenging when multiple administrators perform the same activity simultaneously, increasing the risk of inconsistencies, missed systems, or accidental configuration drift.

Windows environments present similar operational overhead. Security updates, application installations, registry modifications, and service restarts often require administrators to establish Remote Desktop sessions or use remote management tools individually.

The operational problems become evident:

Excessive manual effort
Human error
Inconsistent execution
Difficulty tracking progress
Extended maintenance windows
Limited auditability
Poor scalability

Organizations needed a better approach—one that centralized execution while allowing administrators to reuse standardized procedures across the infrastructure.

VMware vRealize Orchestrator addressed this requirement by providing a workflow-driven automation platform capable of integrating directly with vCenter Server and executing remote administrative tasks across both Linux and Windows virtual machines.

Why Tradititle: “VM Management Automation (Part 1)”

category: “VMware”Not Enough

Prior to adopting orchestration platforms, administrators relied on shell scripting, scheduled tasks, SSH loops, or third-party utilities such as PsExec.

Although effective in small environments, these methods introduced several operational limitations.

Standalone Shell Scripts

A Bash loop can easily iterate through a list of servers.

for host in $(cat servers.txt)
do
    ssh root@$host "/root/update.sh"
done

While simple, this approach lacks:

centralized logging
workflow approvals
retry mechanisms
credential management
reporting
integration with vCenter inventory

Windows Batch Files

Administrators often maintained BAT files similar to:

for /f %%i in (servers.txt) do (
    psexec \\%%i C:\Scripts\Patch.bat
)

Again, execution depended heavily on network connectivity, administrative shares, and manual monitoring.

Failures typically required rerunning the script or manually identifying failed systems.

Manual SSH Sessions

Many enterprise teams continued using terminal emulators with saved sessions.

Host01
Host02
Host03
Host04
...
Host250

While manageable for a few servers, this approach quickly became impractical as environments expanded.

Why Enterprises Adopted VMware vRealize Orchestrator

Rather than focusing solely on remote command execution, VMware vRealize Orchestrator introduced workflow-based automation tightly integrated with VMware infrastructure.

Instead of writing separate scripts for every maintenance activity, administrators could build reusable workflows that accepted different inputs while maintaining consistent execution logic.

For example, a single workflow could accept:

A VM folder
A resource pool
A cluster
A custom attribute
A list of virtual machines
A project name

The workflow would then automatically:

Discover matching virtual machines.
Verify power status.
Validate guest operating system.
Authenticate securely.
Execute the required script.
Capture command output.
Log success or failure.
Generate an execution report.

This significantly reduced operational complexity while improving repeatability and auditability.

Solution Architecture – ESXi + vCenter + vRealize Orchestrator

At the heart of the solution is VMware’s centralized orchestration model, where vRealize Orchestrator acts as the automation engine responsible for coordinating administrative tasks across the virtual infrastructure.

Instead of connecting directly to each virtual machine manually, administrators interact only with vRO. The orchestration engine communicates with vCenter Server to identify target virtual machines and then executes remote commands using the appropriate protocol for each operating system.

The high-level architecture consists of the following components:

                +--------------------------------+
                |        Administrator           |
                +---------------+----------------+
                                |
                                |
                        Launch Workflow
                                |
                                v
                +--------------------------------+
                | VMware vRealize Orchestrator   |
                |      (Workflow Engine)         |
                +---------------+----------------+
                                |
                 VMware Plugin / vCenter API
                                |
                                v
                +--------------------------------+
                |         VMware vCenter         |
                +---------------+----------------+
                                |
        ---------------------------------------------------------
        |                      |                      |
        v                      v                      v
+---------------+      +---------------+      +---------------+
| ESXi Host 01 |      | ESXi Host 02 |      | ESXi Host 03 |
+-------+-------+      +-------+-------+      +-------+-------+
        |                      |                      |
   Linux & Windows        Linux VMs             Windows VMs
   Virtual Machines      Application Tier      Database Tier

The administrator never needs to establish individual SSH or Remote Desktop sessions during routine maintenance. Instead, the workflow handles the entire execution lifecycle.

Workflow Execution Sequence

A typical maintenance workflow follows a predictable sequence.

Administrator
      |
      |
Select Workflow
      |
      v
Choose Target Virtual Machines
      |
      v
Validate Credentials
      |
      v
Identify Guest Operating System
      |
      +-----------------------------+
      |                             |
      | Linux VM                    | Windows VM
      |                             |
SSH Command                  WinRM / PowerShell
      |                             |
      +-------------+---------------+
                    |
             Collect Output
                    |
                    |
             Success / Failure
                    |
                    v
           Generate Execution Report

Because every execution follows the same workflow, operational consistency improves dramatically regardless of whether the target environment contains twenty virtual machines or several hundred.

Operational Advantages

Implementing vRealize Orchestrator for remote script execution delivers several practical benefits that become increasingly valuable as infrastructure grows:

Centralized workflow execution from a single console
Standardized automation across Linux and Windows
Reduced maintenance window duration
Consistent execution logic
Improved auditability with execution logs
Easier delegation of routine operational tasks
Reduced risk of human error
Ability to reuse workflows for future maintenance activities

Perhaps the greatest advantage is the ability to transform one-off administrative scripts into reusable operational workflows that can be executed repeatedly with minimal modification.

Rather than creating a new script for every maintenance activity, administrators build a library of reusable workflows that become part of the organization’s operational toolkit.

Coming Up in Part 2

In the next section, we will move from architecture to implementation by preparing the environment for automation. This includes integrating VMware vRealize Orchestrator with vCenter Server, configuring authentication, enabling secure communication with Linux and Windows virtual machines, and designing a reusable workflow capable of executing Bash, Batch, and PowerShell scripts across hundreds of systems.

Part 1 - Enterprise Script Automation with VMware vRealize Orchestrator: Architecture and Operational Challenges