Powercli error while updating tools

[setpalan]

Hi, i am trying to update tools for multiple VMs, here is my code below, i have tried in two different ways but still i am getting error

for each($vm in $vms){

     get-vm $vm | Update-Tools - Noreboot

}

another way

foreach ($vm in $vms)

{

     get-vm $vm | Mount-Tools

     get-vm $vm | update-tools -Noreboot

     get-vm $vm | Dismount-Tools

}

Please help me on this, what i am missing?

But i am getting below error

The Operation of the entity VirtualMachine-vm-12573 with following message:"Error Upgarding vmware Tools"

[LucD]

What does it say in the vmware.log of this VM?
And which PowerCLI version are you using?

[setpalan]

apologies for late response

my powercli version is 4.0, i have attached the vmwarelog as well.

[LucD]

Looks like you might be having an issue with the CD on that VM.

If possible remove the CD from the Settings, then add a new CD to the VM.

Now try the VMware Tools upgrade again.

You might also try to power off/power on the VM (not the guest OS), before doing the above.

PS: you are running a very old version of PowerCLI.

Any particular reason why you can't upgrade?

[setpalan]

yes, there is a restriction in my office we cant upgrade however i will try to upgrade, and i will try removing CD drive

[setpalan]

I tried removing the drive and adding it again. but still getting same error

I can mount the tools but i cannot update it. have attached the screenshot of that error

[LucD]

You could try to upgrade the tools from within the guest OS.

• mount the ISO
• start the upgrade manually from within the guest OS

Curious to know if that would work.

[setpalan]

Manually mounting the ISO tools and installing the tools via installation wizard is working. But i have to update tools for hundreds of server.

Manually installing is too much effort. so i am trying through powercli script, but though powercli its not installing.

[LucD]

And is Update-Tools failing on all the VMs on which you tried it?

[setpalan]

yes its failing in all vms

[LucD]

Might you be hitting the issue described in KB2007298?

Can you try the solution proposed in that KB on one the VMs?