> If you wish to undertake "Guest Customization" reliably then you must interact correctly with the interfaces provided by the guest OS. These will of course change from release to release of the guest OS, so in general it is always necessary to adapt interactions as required by new guest OS releases. Therefore your customers should not expect any new guest OS release to function correctly with your Guest Customization feature prior to receiving such an update from you.
> It sounds like this problem will go away as soon as you release your fixed vSphere update?
Yes,this is reason we always test "Guest Customization" on new guest os daily/beta build before it's released to catch such failure due to guest os change. If the fix is on vSphere side, customer will have to wait for the next vSphere release which contains the fix and must upgrade to it to get the fix. While if guest side(at least in guest os GA build) can fix it, customer will not encounter the failure at all. Certainly, where the fix goes to is case by case.
> If you wish to undertake "Guest Customization" reliably then you must interact correctly with the interfaces provided by the guest OS. These will of course change from release to release of the guest OS, so in general it is always necessary to adapt interactions as required by new guest OS releases. Therefore your customers should not expect any new guest OS release to function correctly with your Guest Customization feature prior to receiving such an update from you.
> It sounds like this problem will go away as soon as you release your fixed vSphere update?
Yes,this is reason we always test "Guest Customization" on new guest os daily/beta build before it's released to catch such failure due to guest os change. If the fix is on vSphere side, customer will have to wait for the next vSphere release which contains the fix and must upgrade to it to get the fix. While if guest side(at least in guest os GA build) can fix it, customer will not encounter the failure at all. Certainly, where the fix goes to is case by case.