Free tools Windows power users keep installed
One-click scans. No signup required.
Use Ansible’s /usr/bin/ansible command with an inventory pattern, a module, and module arguments to run one task across many servers: ansible <pattern> -i <inventory> -m <module> -a "<module arguments>". The inventory defines which machines exist, the pattern narrows the targets, and Ansible runs the task in parallel over SSH. This guide shows how to build the inventory, select hosts precisely, control concurrency, use privilege escalation, choose safe modules, diagnose failures, and recognize when an ad hoc command should become a playbook.
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
What an Ansible ad hoc command does
An ad hoc command is a one-off invocation of the /usr/bin/ansible command-line tool that performs a single task on one or more managed nodes. Ansible’s official documentation describes it as a way to automate one task without creating a playbook first. The command is evaluated from your control machine, connects to each selected host over SSH, invokes a module, and reports a result for every host.
As an Amazon Associate I earn from qualifying purchases.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchThe canonical form is:
ansible <pattern> -i <inventory> -m <module> -a "<module arguments>"
For example, this starts the HTTP service on every host in the webservers group:
ansible webservers -i inventory.ini -m ansible.builtin.service -a "name=httpd state=started"
Ad hoc execution is useful for an occasional check, a controlled emergency action, or a small administrative change. It is not a replacement for a playbook when the operation must be repeated, reviewed, parameterized, ordered, approved, or audited.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Build an inventory that represents your servers
An inventory is the source of truth for managed hosts and their groups. It can be a file, a directory of inventory sources, or another inventory expression supported by your Ansible installation. The -i option selects that source.
Minimal INI inventory
[webservers]
web01.example.com
web02.example.com
web03.example.com
[dbservers]
db01.example.com
The names on the left are inventory hostnames. They can be DNS names, IP addresses, or aliases. A group is the text in square brackets followed by its member hosts. A host may belong to more than one group, which lets you create operational views such as production, staging, web, or database cohorts.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Validate that Ansible sees the expected hosts
Before changing anything, ask Ansible to list the hosts selected by a pattern:
ansible webservers -i inventory.ini --list-hosts
Check the resulting list for spelling, group membership, and accidental inclusion of a production system. This is especially important when a pattern contains wildcards or exclusions.
Keep connection details separate from the target pattern
The pattern answers “which hosts?”; connection options answer “how do I reach them?” Keep those concerns distinct. For example, an inventory can identify web01.example.com, while inventory variables or command-line options define the SSH user, port, key, or Python interpreter. A correct pattern cannot compensate for invalid credentials or an unreachable network.
Select several servers with Ansible patterns
Patterns are expressions evaluated against inventory hosts and groups. They let you move from a single-machine test to a carefully bounded fleet without rewriting the module command.
| Pattern | Targets | Typical use |
|---|---|---|
all |
Every host in the inventory | Fleet-wide fact gathering or a deliberately global check |
web01.example.com |
One named host | First-run validation or a targeted repair |
host1,host2 |
Those comma-separated hosts | A small ad hoc set without creating a group |
webservers |
Every host in one group | Routine work on the web tier |
webservers:dbservers |
Hosts in either group | A task spanning two roles |
webservers:&staging |
Hosts common to both groups | Only staging web servers |
webservers:!phoenix |
Web servers except members of phoenix |
Exclude a host or maintenance cohort |
| Wildcard expression | Matching inventory hostnames or IP addresses | Target a naming range when the match is unambiguous |
Always preview a complex expression with --list-hosts. A typo can produce an empty match, while an overly broad wildcard can reach machines you did not intend to touch.
Run a read-only command first
Establish connectivity and identity before making a change. The default ad hoc module is ansible.builtin.command, which executes a command without invoking a remote shell.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
- Check the selected hosts. Run
ansible webservers -i inventory.ini --list-hostsand confirm the count. - Test SSH and the remote identity. Use
ansible webservers -i inventory.ini -m ansible.builtin.command -a "id". - Inspect a harmless system value. For example,
ansible webservers -i inventory.ini -m ansible.builtin.command -a "uname -a". - Review each result.
SUCCESSmeans the module completed;UNREACHABLEindicates a connection or authentication problem;FAILEDmeans the module ran but returned an error.
Do not proceed to a state-changing command until every intended host has the expected login account and operating-system context.
Control parallel execution with forks
Ansible communicates with multiple hosts in parallel. The official ad hoc example uses five simultaneous processes by default. If a target group is larger than that, Ansible works through it in batches unless you raise the fork count with -f (or --forks).
ansible webservers -i inventory.ini -m ansible.builtin.command -a "uptime" -f 10
The documented example uses ten forks for a group named atlanta:
ansible atlanta -a "/sbin/reboot" -f 10
Five and ten are operational defaults or examples, not performance guarantees. A larger fork count can reduce wall-clock time when hosts respond quickly, but it also increases concurrent SSH sessions, controller CPU and memory use, network traffic, and load on the managed machines. Storage operations, package managers, service restarts, and rate-limited APIs may become slower or less reliable when launched simultaneously.
Choose a value your controller, network, and servers can sustain. Start with the default, observe completion time and load, then increase gradually. If a change must be serialized for safety, use a playbook with a controlled batch size rather than assuming that an ad hoc command will run one host at a time.
Provide the correct SSH user and privilege
Select the remote login account
Use -u to select the account Ansible should use for SSH:
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →ansible webservers -i inventory.ini -u deploy -m ansible.builtin.command -a "id"
The account must have a valid SSH key or password method, a working shell, and permission to run the requested module. Verify that the same account works on every host in the pattern; mixed account configuration is a common reason for partial success.
Escalate with become when root privileges are required
Do not log in directly as root merely to make a command work. Ansible’s become mechanism logs in as the specified user and then requests the configured privilege escalation method:
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
ansible webservers -i inventory.ini -u deploy --become -m ansible.builtin.command -a "id"
To prompt for the escalation password, add --ask-become-pass or its short form -K:
ansible webservers -i inventory.ini -u deploy --become -K -m ansible.builtin.command -a "id"
The remote account must be allowed to escalate through the host’s sudo or other configured become policy. A successful SSH login does not prove that escalation is permitted. Test with id before attempting a package, service, or file operation.
Choose the module that matches the task
Modules provide argument parsing and, where supported, declarative state handling. Selecting the narrowest suitable module reduces quoting mistakes and makes the requested state clearer.
| Module | Use it for | Example | Important limitation |
|---|---|---|---|
ansible.builtin.command |
A normal executable with arguments | -a "uname -a" |
No shell pipes, redirects, wildcard expansion, or shell operators |
ansible.builtin.shell |
Commands that genuinely need shell syntax | -a "df -h | sort -k5" |
Shell parsing increases quoting and injection risk; use only when required |
ansible.builtin.copy |
Copying content or a file to targets | -a "src=/etc/hosts dest=/tmp/hosts" |
Destination permissions and parent directories still matter |
ansible.builtin.service |
Ensuring a service state | -a "name=httpd state=started" |
Service name and init-system support vary by operating system |
ansible.builtin.setup |
Gathering system facts | No -a argument required |
Fact collection can be slower on a large inventory |
Use command for simple executables
ansible webservers -i inventory.ini -m ansible.builtin.command -a "uptime"
Because command does not start a shell, a pipe such as | is passed as an argument rather than interpreted. That behavior is intentional and safer for ordinary commands.
Use shell only for shell-specific syntax
ansible webservers -i inventory.ini -m ansible.builtin.shell -a "cat /var/log/httpd/access.log | tail -n 20"
Quote the complete argument string so your local shell does not expand variables, redirects, or wildcards before Ansible sends them. Treat any data inserted into a shell command as untrusted unless it has been safely constrained.
Copy a file to every target
ansible webservers -i inventory.ini -m ansible.builtin.copy -a "src=/etc/hosts dest=/tmp/hosts"
The source path is read on the control machine; the destination path is created or updated on each managed host. Use become when the destination requires elevated permissions.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Ensure a service is running
ansible webservers -i inventory.ini -m ansible.builtin.service -a "name=httpd state=started"
A service module expresses the desired state rather than blindly issuing a restart command. Where the module supports it, Ansible can detect that no change is needed.
Gather facts from all hosts
ansible all -i inventory.ini -m ansible.builtin.setup
Fact gathering returns structured information such as operating-system, network, and hardware details. On a large inventory, limit the pattern or gather only the hosts needed for the immediate decision.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Preview and apply changes safely
Use check mode where the module supports it
Check mode previews a module’s intended action without applying it when that module implements check-mode support. For example:
ansible webservers -i inventory.ini -m ansible.builtin.copy -a "content=foo dest=/root/bar.txt" --check
The short option is -C. The copy example reports what would change, but check mode cannot guarantee a preview for every module or arbitrary command. A raw command may execute immediately because it has no general way to predict its side effects.
Expand the target set in stages
- Start with one host, such as
web01.example.com. - Run the command in check mode if the module supports it.
- Review the result and confirm the expected state manually.
- Run against a small group or intersection such as
webservers:&staging. - Only then widen to the complete production group.
This progression limits the blast radius of an inventory mistake, an incorrect argument, or an unexpected platform difference.
Prefer idempotent, purpose-built operations
Modules such as copy and service describe a desired end state and can avoid unnecessary changes. Replacing them with a shell command that always writes a file or restarts a daemon makes repeated runs harder to predict. Use shell only when no suitable module expresses the operation.
Common multi-server workflows
Check kernel and uptime across a group
ansible webservers -i inventory.ini -m ansible.builtin.command -a "uname -a"
ansible webservers -i inventory.ini -m ansible.builtin.command -a "uptime"
These read-only checks are useful for spotting a host that is running a different kernel or has an abnormal load before a maintenance operation.
Run a command across web and database groups
ansible webservers:dbservers -i inventory.ini -m ansible.builtin.command -a "hostname"
Use this only when the command is valid on both roles. If the operation differs by role, separate commands or a playbook with role-specific tasks are clearer.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteExclude a maintenance host
ansible webservers:!phoenix -i inventory.ini -m ansible.builtin.service -a "name=httpd state=started"
Confirm that phoenix is actually represented as an inventory group or host expression; an exclusion that matches nothing will not protect a similarly named machine.
Troubleshoot failures by result type
UNREACHABLE: SSH, DNS, or network failure
- Confirm the hostname resolves from the control machine.
- Test SSH manually with the same user and key.
- Check firewall rules, bastion or proxy requirements, and the SSH port.
- Verify that the inventory name maps to the intended address.
Do not treat an unreachable host as successfully processed; Ansible will report results independently for the hosts that did connect.
Best Value
FAILED: the module ran but could not complete
- Read the module’s returned message and inspect the exact argument string.
- Check whether the executable, service name, source file, or destination directory exists on that operating system.
- Retry with the correct
-uaccount or add--becomewhen permissions are the cause. - Run the same operation against one host to isolate a platform-specific difference.
No hosts matched
Use --list-hosts with the exact pattern and inventory path. Common causes are a misspelled group, using a hostname that is not an inventory alias, or forgetting the comma in a one-off host list such as host1,.
Unexpected shell behavior
If a pipe, redirect, variable, or wildcard is being interpreted by the wrong shell, decide which shell should expand it. Use command for a literal executable invocation; use shell only when remote shell parsing is intentional; and quote the argument so the local shell does not consume it first.
Slow completion or overloaded hosts
Reduce -f if the controller or servers are saturated. A higher fork count is not inherently faster, particularly when the task contends for the same disk, package database, service lock, or external API.
Check mode shows nothing useful
Check whether the selected module supports check mode. For modules or commands that cannot predict changes, use a read-only probe, test one host, and create an operational rollback plan before applying the command.
Know when an ad hoc command should become a playbook
An ad hoc command is intentionally transient. Move the work into a playbook when any of the following is true:
- The task will be run again on a schedule or by another administrator.
- You need variables, conditionals, loops, handlers, task ordering, or different behavior by operating system.
- The operation requires approvals, a documented change record, or a predictable audit trail.
- You need controlled batches, pauses, serial execution, or a defined rollback sequence.
- Several ad hoc commands must be run in a precise order.
| Concern | Ad hoc command | Playbook |
|---|---|---|
| Target selection | One pattern supplied at invocation | Hosts and groups declared with task structure and variables |
| Concurrency | -f controls controller forks |
Can express serial batches and orchestration logic |
| Privilege | -u, --become, and -K on the command line |
Privilege settings can be documented with the tasks |
| Repeatability | Command text must be reconstructed | Versionable, reviewable file |
| Complexity | Best for one occasional task | Supports variables, conditions, handlers, and ordered procedures |
| Change preview | Depends on module check-mode support | Can combine check mode with a broader workflow review |
The concepts transfer directly: inventory still defines the servers, patterns still select them, modules still perform the work, and become still controls privilege. The playbook adds a durable structure for everything that should not depend on a remembered one-line command.
Recommended Free Tools
A repeatable runbook for managing a server group
- Confirm scope. Write down the intended group, exclusions, and change window.
- Inspect inventory membership. Run
ansible <pattern> -i inventory.ini --list-hosts. - Verify access. Run the
idcommand with the intended-uvalue. - Test privilege. Add
--becomeand-Kif the operation needs elevation. - Choose the narrowest module. Prefer a purpose-built module over
shell. - Preview. Use
--checkwhen the module supports it. - Canary the change. Apply it to one host, inspect the result, and verify the service or file.
- Scale carefully. Expand the pattern and select a fork count that the environment can handle.
- Record the outcome. Keep the exact command, inventory revision, affected hosts, and failures.
- Promote recurring work. If the runbook will be repeated, encode it as a reviewed playbook.
This process preserves the speed of an ad hoc command while making target selection, access, concurrency, and recovery explicit.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.




