Quote:
Originally Posted by
lloyd mcclendon 
I'm sorry but that's kind of stupid on your part. Logging into 60 machines manually one at a time.

heck even 6 machines, that's a bad process - not only is it a waste of time, it's also a good window for inconsistencies to sneak in. What if you type the command wrong on machine #46? At the very least you can use ssh in a for loop

... But you probably want to look at puppet or cfengine
http://projects.puppetlabs.com/ http://cfengine.com/ ... stop doing the same thing over and over
I'll add that _good systems administrators are always seeking ways to streamline and improve the mundane tasks, and not just accepting it as part of the job. That's no way to go through life.
Regardless that I don't, because it can all be done with a mouse click, I'm just painting a picture that some things need to be done manually. Also, how would you script mounting the VMware CD and then performing an untar then install with install options? The only way I could think of to do this with a script (attached to a command center or something similar) is to have the data there with the script and mount a cifs or nfs or something, and then run the installation files. Even then, it's a lot of work to create a script that will answer all the questions that arise during the installation all while making sure it's waiting for the porper prompts. And that assumes you don't have oddball systems that require different settings on the Vmware tools.
Also, as for typing the wrong command, it's actually rather hard to do it with auto completion in bash. Untar, run installation perl, and answer questions. I end up doing it quite frequently with new VM's since our template was created months ago, and they have release 3 iterations of the tools since then.