Jira (PUP-3979) Windows Package Should Switch between Execute and Install Mode
Title: Message Title Etienne Lacombe commented on PUP-3979 Re: Windows Package Should Switch between Execute and Install Mode loglevel = debug does get rid of the output but the run still gets recorded as if it had changed something on the node. unless - not sure how I would implement this. I would need to run the package first to know if it will need to install, if it does, then before installing it, then I need to run the exec but if it won't install anything (because it's already installed) then I don't need to run the exec. What I see more workable, but that means changing the windows package provider is that either through a parameter or on its own volition, it runs those commands to change the mode if it determine that it will install the package. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3979) Windows Package Should Switch between Execute and Install Mode
Title: Message Title Etienne Lacombe commented on PUP-3979 Re: Windows Package Should Switch between Execute and Install Mode Just a correction, this is not only when the administrator is running Puppet from an RDP session. According to MS documentation, that is the way to install applications on an RDP server - regardless of whether you are, as admin, accessing the server through RDP or local console. https://technet.microsoft.com/en-us/library/cc742815.aspx To ensure that an application is installed correctly to work in a multiuser environment, you must put the RD Session Host server into a special installation mode before you install the application on the RD Session Host server. This special installation mode ensures that the correct registry entries and .ini files that are needed to support running the application in a multiuser environment are created during the installation process. This applies only to a server with the RDP feature installed. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-716) Puppet 3.7.1 Agent on Windows blocks for 20 seconds trying to connect to ec2 metadata service on xen hypervisors
Title: Message Title Etienne Lacombe commented on FACT-716 Re: Puppet 3.7.1 Agent on Windows blocks for 20 seconds trying to connect to ec2 metadata service on xen hypervisors Is there any work around I can apply for this issue? I'm trying to run Puppet 3.7.3 on a Win2008R2 server (64 bit) and it's painfully slow and seems to be what is covered here. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
