Business Development Manager at a tech services company with 11-50 employees
Reseller
Top 10
Apr 9, 2025
We use Puppet ( /products/perforce-puppet-reviews ) for automated configuration management, patch management, and general IT operations automation. It is an automation tool used for configuring servers efficiently.
I use Puppet Enterprise in many projects that require a full control on the Device and make it compliant with the Security regulations of the Company. Puppet Enterprise provides an autonomous Delivery solution and agent-server Architecture that was really helpful on our case for Internet base Device Management.
Until last year, we were using the enterprise version — Puppet 4 —; however, we recently switched to the open-source version — the community edition. We are using a product called Foreman as a front end for Puppet open source. We used Puppet solely for Linux. At first, we had around 200 plus Linux servers that were managed by Puppet. It was like infrastructure as a code. If we had to build a new server or update a server, then we just had to commission a new server, apply Puppet control, and it would configure everything for us. That was one of our main use cases. We also used it for compliance. We had some security products and policies that we needed to implement. This solution made sure that they're always there, that nobody was messing with them. Regarding security compliance, take CrowdStrike for example, it's supposed to be installed on every server — running and reporting properly. Puppet checks that a service is running every 15 minutes. If it's not, it starts it and if it's missing, it installs it. Although we started with Linux, we are moving towards adding Windows servers as well.
Senior Unix Engineer at a financial services firm with 10,001+ employees
Real User
Oct 23, 2020
Our use case is provisioning and then configuration management for on-prem servers primarily. We use it for applications as well. We were using Puppet for database configuration management. Basically, we mainly use it for configuration management for on-prem servers of infrastructure and then use it a bit on the application side as well.
Co-Founder and Consulting Engineer at a tech services company with 1-10 employees
Real User
Sep 25, 2018
I think deploying computer direction changes over production environments. The main purpose for this automation tool would be: * Deploying * Controlling * Ordering Change for the System * IT Infrastructure
Perforce Puppet provides robust features for configuration management, compatible with Linux, Windows, and UNIX. It simplifies infrastructure management with automation and role-based access control, though it requires mastering command-line operations due to limited GUI.Perforce Puppet utilizes a hub-spoke architecture to enhance automation across production environments, excelling in provisioning and configuration management for on-prem servers. Its infrastructure as code approach eases...
My main use case for Perforce Puppet is for configuration management.
We use Puppet ( /products/perforce-puppet-reviews ) for automated configuration management, patch management, and general IT operations automation. It is an automation tool used for configuring servers efficiently.
We use public configurations for all nodes. This includes configurations for integrations, networks, packages, software, etc.
I use Puppet Enterprise in many projects that require a full control on the Device and make it compliant with the Security regulations of the Company. Puppet Enterprise provides an autonomous Delivery solution and agent-server Architecture that was really helpful on our case for Internet base Device Management.
Until last year, we were using the enterprise version — Puppet 4 —; however, we recently switched to the open-source version — the community edition. We are using a product called Foreman as a front end for Puppet open source. We used Puppet solely for Linux. At first, we had around 200 plus Linux servers that were managed by Puppet. It was like infrastructure as a code. If we had to build a new server or update a server, then we just had to commission a new server, apply Puppet control, and it would configure everything for us. That was one of our main use cases. We also used it for compliance. We had some security products and policies that we needed to implement. This solution made sure that they're always there, that nobody was messing with them. Regarding security compliance, take CrowdStrike for example, it's supposed to be installed on every server — running and reporting properly. Puppet checks that a service is running every 15 minutes. If it's not, it starts it and if it's missing, it installs it. Although we started with Linux, we are moving towards adding Windows servers as well.
Our use case is provisioning and then configuration management for on-prem servers primarily. We use it for applications as well. We were using Puppet for database configuration management. Basically, we mainly use it for configuration management for on-prem servers of infrastructure and then use it a bit on the application side as well.
I think deploying computer direction changes over production environments. The main purpose for this automation tool would be: * Deploying * Controlling * Ordering Change for the System * IT Infrastructure