Replace get-cluster -name "DMZ-AMD-CLUSTER" with get-folder -name "FOLDER NAME" or get-host -name "HOSTNAME"

I think you've pretty much answered your own question. I think you can just add where-object {$_.osfullname -like "Windows"} | to the second line:

$updList = get-cluster -name "DMZ-AMD-CLUSTER"|get-vm | where-object {$_.powerstate -eq "PoweredON"} | where-object {$_.osfullname -like "Windows"} |% {get-view $_.ID} |where {$_.guest.toolsstatus -match "toolsOld" }

freefall: that was the problem I was having too. Still can't make it work, dunno why it works for some but not us. =(

moose: The problem is, that osfullname is not a property of the VM object, I have to Get-VMGuest after the Get-VM in order to check the OS type. That's why I need help - how can I look inside the Guest object, check if its windows, then pop back out to the VM object, since Get-View needs to be piped a VM object (not a VMGuest object)?

I had run into similar issues with trying to update tools with Powershell, so I came up with a version that uses more of a batch script and then psexec to execute it on remote machines. It requiers a little bit of setup but is very easy to pull of once its all set.

First, you'll want to put the list of VM's you want to upgrade (Windows only) in a text file. (*list.txt*)

===== list.txt =====
VM1
VM2
VM3
etc...
===== /list.txt =====

You'll want to copy the VMtools install files to a network share that all computers can access. You can get these by mounting the VMTools in the VM and copy all the files off the mounted cdrom.

Now, you'll want to create the batch file that will run on each computer. (*vmtools.bat*)

===== vmtools.bat =====
\\location_of_tools\setup.exe /s /v"/qn REINSTALLMODE=voums REINSTALL=ALL REBOOT=REALLYSUPRESS"
===== /vmtools.bat =====

Make sure list.txt and vmtools.bat are in the same directory and run the following command from that directory:

===== CMD =====
psexec @list.txt -d -u <domain\account> -p <password> -c vmtools.bat
===== /CMD =====

This will copy the vmtools.bat to the remote computer and then run it. Make sure you run this from a DOS/CMD window and not a Powershell prompt. Powershell will attempt to interpret the @ and will prevent the command from running properly.

I've logged it.