Comment # 7 on bug 1162435 from John Wolfe

Hi Michael,

(In reply to Michael Krapp from comment #5)
> 
> just for clarification, we never tried VMwaretools, but only open-vm-tools
> and only the latest update in the SLES12SP4 channel shows this behaviour.

Nor would I have expected you to use VMware Tools.  That is a VMware internal
build of the same source that uses a Perl script to install the vmtools from a
tar file - based on the version of Linux encountered.  It was a quicker way to
get a debug version of 11.0.x tools onto the SLES VM without having to play
with the packaging repository links on the guest.

All our QE release and reqression testing uses the appropriate RPM built from
the open-vm-tools source.

Last evening I registered my SLES 12 SP4 Desktop VM and after refreshing the
repository information I installed the SUSE OVT 11.0.0 packages.

       open-vm-tools-11.0.0-4.18.3.x86_64
       open-vm-tools-desktop-11.0.0-4.18.3.x86_64
       libvmtools0-11.0.0.4.18.3-x86_64

Testing with the SUSE OVT 11.0.0 did not repro the problem.