I ran into this same problem, and pe_compliance was the culprit-- took 120
seconds. Removing this class from the default group and re-running puppet
made it run quickly again.
On Monday, October 1, 2012 2:08:08 PM UTC-6, Josh Cooper wrote:
On Mon, Sep 3, 2012 at 2:07 AM, David Schmitt
On Mon, Sep 3, 2012 at 2:07 AM, David Schmitt da...@dasz.at wrote:
On 03.09.2012 09:45, Jan Ziegler wrote:
Hi,
We have 18 Windows Server in the same environment. All Windows Server
are build with an individual Windows Image, we created before, which
means, that all Windows Machines have the
Hi,
We have 18 Windows Server in the same environment. All Windows Server are
build with an individual Windows Image, we created before, which means,
that all Windows Machines have the same configuration except ip/mac address
and hostname.
17 of those Windows Server run Puppet within 120
On 03.09.2012 09:45, Jan Ziegler wrote:
Hi,
We have 18 Windows Server in the same environment. All Windows Server
are build with an individual Windows Image, we created before, which
means, that all Windows Machines have the same configuration except
ip/mac address and hostname.
17 of those
