- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've updated four hosts and my custom productLocker location on shared vmfs datastore was preserved on each host after reboot. Can confirm this issue has been FIXED!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Confirmed - its fixed with VMware ESXi 7.0 Update 3f Release Notes
ty
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have followed these steps but my VMs are still not detecting the new vmtools versions in our productlocker location. Do I need to reboot the host as the final step? I cannot upgrade the host to v7 u3f yet.
1- SSH to the host
2- rm /productLocker -rf
3- ln -s <vmtoolpath> /productLocker
4- esxcli system settings advanced set -o /UserVars/ProductLockerLocation -s <vmtoolpath>
5- /sbin/auto-backup.sh (to keep settings after reboot)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
AFAIK, vm tool version is only checked against the ProductLocker version on these two events: 1) the vm is v-motioned to a different host that also has the new value, or 2) you restart mgmt agents on the current host. Naturally a host reboot would fulfill #2, but since you are not on 7.03uf your setting will not be preserved across reboots, so you would need to set it manually after the host comes up from its reboot BEFORE moving any vm's back to this host. Probably easiest just to restart mgmt agents per https://kb.vmware.com/s/article/1003490
Oh, and upgrade to 7.0u3f (or preferably7.0.3g build-20328353) ASAP and be done with this giant headache.