GitHub puppet-vmwaretools
Puppet module to manage VMware Operating System Specific Packages for VMware tools installation.

Metadata Valid
No translation
Correct Puppet Version Range
Supported Puppet version range is %{PUPPET_VERSION_RANGE}
With Puppet Version Range
Puppet version range is present in requirements in metadata.json
With Operatingsystem Support
No translation
Supports Only Current Centos
No translation
Supports Latest Centos
No translation
Supports Only Current Ubuntu
No translation
Supports Latest Ubuntu
No translation
In Modulesync Repo
No translation
In Plumbing
Is in plumbing
Has Secrets
Has a .sync.yml file
Has a .msync.yml file
Has Modulesync
Is present in voxpupuli/modulesync_config/managed_modules.yml
Is in modulesync_config and in forge releases.
Reference Dot Md
The repository has a It needs to be generated / puppet-strings documentation is missing.

Open Pull Requests

fix deprecated apt:source parameters

fix spec tests to use new format

Update apt dependency

Update apt module dependency to <5.0.0

add symlinks for pam-modules for proper function
waiting on submiter

The rpms provided by vmware install a PAM-Service. This pam-service references modules not provided by RH. See
This extension creates symlinks to make the service working again or at least to prevent error messages.

Update apt module

APT version_requirement has now allowed newer versions to be used.
Current testing is with legacy 2.4.1 version of the module until @razorsedge decides to deprecate Puppet 3 support.
When fixture is updated to apt > 2.x all Puppet 3 tests will fail as expected.

I was having the same issue. I changed lines 319-322 in vmwaretools\m…
waiting on submiter

Services we're not starting on RHEL 6.8

Update …anifests\init.pp from:

start => "/sbin/start ${service_name_real}",
stop => "/sbin/stop ${service_name_real}",
status => "/sbin/status ${service_name_real} | grep -q 'start/'",
restart => "/sbin/restart ${service_name_real}",


start => "service ${service_name_real} start",
stop => "service ${service_name_real} stop",
status => "service ${service_name_real} status",
restart => "service ${service_name_real} restart",

It now works properly.

Update zypprepo dependency to new owner

Given the zypprepo module has also changed ownership, it makes sense to update the dependency to reference the new owner.

Vmware has deprecated and removed DSA key - Only include RSA GPG key

as per #67 we need to no longer reference the DSA key for RHEL based OS's for vmware tools installs, this PR removes the references the DSA keys that give the 404 error

Remove 4x vmwaretools when installing 5x
waiting on submiter

I'm trying to use your module to upgrade my existing infrastructure from vmwaretools 4x to 5x but sadly it doesn't work without removing the vmwaretools 4x explicitly first because its not recognized as an upgrade (package names changed). That's why I try to work around the problem by removing the old package with yum remove. I tried using package absent or package purged but that will lead to either not removing the packages because of dependencies or when using purged to "Package created" messages on on all next runs (
I'm using the kmod module for yum remove because the if you'd use the vmware-tools-nox it would only remove that and not the other vmware 4x packages, when removing the kmod package all others get removed because they depend on it.

I've tested it on rhel 6.


Update repo.pp to fix #49 and #40
waiting on submiter

VMware have changed the layout of necessitating a change to this module to use the new location for the latest package releases. This PR could however break users who are specifying releases before version 10, so you might want to build a more complicated change which checks the specified version if there is one and selects either esx/$version or releases/$version...