On Thu, Mar 7, 2013 at 7:55 AM, Paul Tötterman <paul.totter...@gmail.com>wrote:
> As someone who generally hates using execs unless I absolutely have to, I
>> would recommend using the Puppet Labs registry module. I can dig out some
>> examples tomorrow if you like.
>
>
> I'm a bit wary about prodding in the registry behind the back of windows
> firewall, but please tell me if it works. I wrote some idempotent
> powershell to control the firewall rules in windows.
>
The registry data looks straightforward in HKLM/System/CurrentControlSet/
(search FirewallRules):
v2.10|Action=Allow|Active=TRUE|Dir=In|Protocol=6|LPort=1433|Name=SQL|
But the problem is generating the name:
{4DBAC415-6138-489A-B647-7FAA20709582}
You can't arbitrarily name it SQL. This would be straightforward as a
define type wrapping around registry if someone knows how to generate the
registry name. Adam?
I'm also using exec with netsh firewall to open a port for SQL server for
now, but a type and provider would be much more robust. However I would
like to hear some Windows expert chime in, before trying to write a
type/provider around netsh advfirewall.
Thanks,
Nan
--
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
