I'm a first time user that just installed Puppet 3.1.0 over the weekend and
hit a road block that I can't seem to get across. I have a Linux master
(Mageia 2) and two Windows 7 clients. I was able to get basic recipes
working by putting the resources directly in the node definitions. Now I'm
I have a module for windows nodes that is defined like:
class ast_win {
Class['ast_win::env'] ~> Class['ast_win::restart'] -> Class['ast_win']
ast_win::env contains a bunch of scripts that modify the environment on the
host machine. Mostly the PATH variable, but also other variables (e.g.
ht
Master: RHEL6 running Puppet 3.2.2
Node: Windows 7 x64 Running Puppet 3.2.3
I have the following rule defined on my Puppet master to push Python to
client workstations:
package { 'Python 2.7.5 (64-bit)':
ensure => installed,
source =>
'\\server\share\Puppet\win64\Python
On Wednesday, July 17, 2013 10:24:15 AM UTC-6, Rob Reynolds wrote:
> Perhaps this could be a permissions error?
>
> Can you validate that the user the service runs under can access the
> c:\Python27 folder and that it can see the registry settings?
>
>
It is running as the SYSTEM account. so it s
On Wednesday, July 17, 2013 10:39:51 AM UTC-6, Josh Cooper wrote:
>
>
> Based on http://www.python.org/download/releases/2.5/msi/ I think python
> is only being installed for the current user, not all users. You'll have to
> specify ALLUSERS=1 to get that behavior. I don't see this explicitly c
On Wednesday, July 17, 2013 1:56:42 PM UTC-6, Josh Cooper wrote:
>
> Another user had to modify the NTFS and Share permissions for 'Domain
> Computers' to access the share (map the drive)[2]. This is because
> LocalSystem doesn't have any credentials with which to access the network.
>
> Josh
>
I installed Cygwin on some Windows 7 x64 client nodes (v3.2.3) and was in
the process of removing it. Because I cannot modify CIFS/SAMBA shares or
change the puppet service to run as a domain user, I'm basically reduced to
getting the installers for each package on the machine prior to installi
On Tue, Jul 23, 2013 at 10:57 PM, Josh D
> > wrote:
>
>> I installed Cygwin on some Windows 7 x64 client nodes (v3.2.3) and was in
>> the process of removing it. Because I cannot modify CIFS/SAMBA shares or
>> change the puppet service to run as a domain user, I'm
On Tuesday, February 19, 2013 8:48:43 AM UTC-7, jcbollinger wrote:
>
>
>
> On Monday, February 18, 2013 8:41:53 AM UTC-6, Josh D wrote:
>>
>> I have a module for windows nodes that is defined like:
>>
>> class ast_win {
>> Class['ast_win::env&#
I'm trying to deploy IE11 through puppet. I've created a custom MSI using
the IE Administration Kit that supports silent installs. The problem is,
IE is "built into" Windows, so rather than showing up in the installed
programs list, it winds up in Windows Features. I figured this would cause
in the future though. I just
> want to explore alternatives first.
>
>
> On Fri, Dec 13, 2013 at 1:06 AM, Josh D
> > wrote:
>
>> I'm trying to deploy IE11 through puppet. I've created a custom MSI
>> using the IE Administration Kit that supports silent in
Some of my users are having difficulty installing the Puppet client on
their 64-bit Widows machines. The installation will get get to the point
where everything is installed and it attempts to start the service. The
service fails (see relevant information from install log from /l*v below)
and
On Friday, January 24, 2014 1:02:59 PM UTC-7, Rob Reynolds wrote:
>
> The supported way of making it work is to update to at least 3.3.1.
>
Just tried installing the 3.4.2 client and had the same problem; service
fails to start and the installation is rolled back. The log is *slightly*
differen
On Monday, January 27, 2014 10:34:36 AM UTC-7, Rob Reynolds wrote:
>
> Josh,
> Can you try something for me? With the install, can you add the following
> to it?
>
> msiexec /qn /i themsilocation.msi PUPPET_AGENT_STARTUP_MODE=Manual
>
> And tell me if it installs okay?
>
>
Yep, one step ahead
On Monday, January 27, 2014 4:15:12 PM UTC-7, Rob Reynolds wrote:
>
> You should be able to take ownership of the directory you cannot delete as
> an administrator. Once you have done that you should be able to move
> forward with deleting those. I think the prior install attempts might have
>
On Wednesday, January 29, 2014 12:41:06 AM UTC-7, Rob Reynolds wrote:
>
> Josh,
> I'm glad we were able to get you going. However it is slightly troubling
> to see that the service flips to automatic after running puppet agent.
>
> Also are you overriding the user the agent installed as to a
16 matches
Mail list logo
