On Wednesday, October 1, 2014 2:30:36 PM UTC-6, Brian Morris wrote: > > Hello all, > > There may come a need for me to perform a wide deployment of the Puppet > client to Windows servers. I am curious to know how others have > accomplished this. > > Concerns I have: > > - No other tools are in place that readily come to mind for pushing the > client out. VCM is in play, but is difficult at best to deploy other > applications with. The client could certainly be placed on a central file > share, but pulling rather than pushing sounds like it will require direct > Sysadmin involvement. > > I privately verified that VCM=vCenter Configuration Manager so... when using vCM, you could push puppet via remote command. You could also use the built-in vCM windows package manager (similar to chocolatey). The former will push puppet.msi, the latter will pull it. You could also use ad group policy or sms as someone mentioned.
It would be nice if PE supported similar discovery and deployment features that exist in vCM. This would be a huge win. Though, I have to ask, if you have vCM and its agent, why do you need puppet? > - To ease the pain I could set the Puppet Master to auto-sign certificates > for a small window of time, but am unsure if this would be worthwhile. > > - I can imagine a "patch party" where a bunch of Sysadmins each get a list > of servers to go hand perform the installation on, but I am hoping for > something much cleaner than this. > With the right food and beverages, this could be a viable option, too. ;-) -- 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 puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/2392a8f5-7a85-4c9c-a483-89ee73597e26%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
