michael stump wrote: True, but one of the first troubleshooting steps I take with problems like this is VMTools. If no change, then you can dig in.
Sorry but IMO that's absurd to install VMware Tools to start a diagnostic/troubleshooting process especially if VMware Tools are not required for the feature having an issue! Image may be NSFW.
Clik here to view.
It also goes against common sense practices in that one should first investigate before arbitrarily adding additional software unless it's a known fact that additional software is need to resolve an issue, like an issue with VMware Shared Folders or Unity which require VMware Tools be installed. Not everyone uses or needs/wants to use VMware Tools for various reasons in some VM's so suggesting installing them as a diagnostic/troubleshooting measure before verifying other relevant factors first is not an acceptable practice AFAIC as the first stop on the diagnostic/troubleshooting tree unless it's issue with a feature that explicitly requires VMware Tools be installed! Image may be NSFW.
Clik here to view.
