When i decide to use RHEL based repo style for vmwrae tools, i take a step back, reason is it does not allow me to do, Update-Tools –NoReboot -RunAsync, pls correct me if wrong
I belive that works only when we have the tools installed using the traditinal mount cd-rom
Also this is big limitation, Vmware release the new patches every 2 to 3 months, now if we have repo in a central nas mount we need to upgrade that repo often then if you have say chef recipies you need to update them etc, so Update-Tools is much more easy with, Update-Tools is much easy & does not need , updating repo & updating chef recipies ( for that matter puppet stuff ) , any inputs or suggestion , or i am missing anything here ?
thanks
Afaik, that is correct.
The RHEL based repository is intended for VMs that run a Linux guest OS.
And yes, you'll have to maintain that repository.
The advantage would be that you can install/update VMware Tools in your Linux VMs in the same way as other SW packages.
The Update-Tools cmdlet will only work from the ESXI ISO files.
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Afaik, that is correct.
The RHEL based repository is intended for VMs that run a Linux guest OS.
And yes, you'll have to maintain that repository.
The advantage would be that you can install/update VMware Tools in your Linux VMs in the same way as other SW packages.
The Update-Tools cmdlet will only work from the ESXI ISO files.
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference