Hey Dirk,
Thanks of the update, this is great news. If you do not mind, please can
you share your puppet manifests and chocolatey package?
My puppet manifests for the windows part (this far) is relatively straight
forward:
package{'pe-agent':
ensure =>
hiera('puppet_enterprise_agent_upgrade::pe::agent::version'),
provider => 'chocolatey',
source => $source,
}
More over how do you, if you have to, deal with the .net4 issue that I
posted?
Thanks,
Jason.
On Monday, December 8, 2014 9:32:26 AM UTC-5, Dirk Heinrichs wrote:
>
> Am 05.12.2014 um 19:03 schrieb Rob Reynolds:
>
> Trying to upgrade Puppet with Puppet on Windows is harder because
> Windows locks files that are in use instead of letting you replace them in
> place.
>
>
> That's not true. Upgrading Puppet with Puppet on Windows works just fine.
> Downgrade is a different story, depending on the versions involved. I've
> alread done upgrades from 3.2.1 to 3.4.3 and I'm currently in the process
> of upgrading ~150 Windows agents from 3.4.3 (32bit) to 3.7.3 (64bit) and I
> don't see any problems related to file locks.
>
> Bye...
>
> Dirk
> --
>
> *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
> *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
> *Tel*: +49 2226 1596666 (Ansage) 1149
> *Email*: [email protected] <javascript:>
> *Skype*: dirk.heinrichs.recommind
> www.recommind.com
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/2ae4e66f-3aaa-4d4e-8c6b-66ee82c8ff8f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
