how to Enable these Windows Firewall rules using powershell?












2














I have a few servers where I see a blue question mark on the sql server service, as per the picture below.



enter image description here



This is the solution:




Enabling these Windows Firewall rules did the trick for me



Windows Management Instrumentation (WMI-In)



Windows Management
Instrumentation (DCOM-In)




Is there a way I could achieve this via powershell?










share|improve this question



























    2














    I have a few servers where I see a blue question mark on the sql server service, as per the picture below.



    enter image description here



    This is the solution:




    Enabling these Windows Firewall rules did the trick for me



    Windows Management Instrumentation (WMI-In)



    Windows Management
    Instrumentation (DCOM-In)




    Is there a way I could achieve this via powershell?










    share|improve this question

























      2












      2








      2







      I have a few servers where I see a blue question mark on the sql server service, as per the picture below.



      enter image description here



      This is the solution:




      Enabling these Windows Firewall rules did the trick for me



      Windows Management Instrumentation (WMI-In)



      Windows Management
      Instrumentation (DCOM-In)




      Is there a way I could achieve this via powershell?










      share|improve this question













      I have a few servers where I see a blue question mark on the sql server service, as per the picture below.



      enter image description here



      This is the solution:




      Enabling these Windows Firewall rules did the trick for me



      Windows Management Instrumentation (WMI-In)



      Windows Management
      Instrumentation (DCOM-In)




      Is there a way I could achieve this via powershell?







      sql-server sql-server-2014 connectivity powershell windows-server-2012






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Dec 28 '18 at 20:59









      marcello miorellimarcello miorelli

      5,6311961129




      5,6311961129






















          2 Answers
          2






          active

          oldest

          votes


















          6














          You would use the Enable-NetFirewallRule cmdlet:



          Enable-NetFirewallRule -Name "WMI-WINMGMT-In-TCP", "WMI-RPCSS-In-TCP"


          In order to find the relevant rule names (in order to enable it), you can search existing firewall rules by name by using the Get-NetFirewallRule cmdlet, for example:



          Get-NetFirewallRule -Name "*WMI*"


          This uses wildcards to final all the rules that contain "WMI" as an example.






          share|improve this answer























          • Small note, you can shortcut the command by providing both names together. So Enable-NetFirewallRule -Name 'WMI-WINMGMT-In-TCP','WMI-RPCSS-In-TCP' would have the same effect.
            – Shawn Melton
            Dec 31 '18 at 16:56










          • @ShawnMelton Thanks! I don't use PowerShell super often these days, and always forget exactly what syntax to use for passing lists like that. So I just default to multiple commands =) I've updated the answer.
            – jadarnel27
            Dec 31 '18 at 17:08










          • Oh, it works either way. Some prefer to use multiple for readability when they are just glancing....as long as it gets the job done.
            – Shawn Melton
            Jan 1 at 18:01



















          0














          I have the same problem and manually enabled these two rules on the firewall and then did a server restart of the SQL server but this did not get rid of the blue question mark icon.



          I also tried to do it via a PowerShell script followed by a server restart but this did not work either.



          This is not a show stopper as I can connect to the SQL server from my PC with SSMS 17.9.1 and access the database, but it is annoying and slightly worrying.



          Any other suggestions?





          share








          New contributor




          Billy The Mexican is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.


















            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "182"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f225944%2fhow-to-enable-these-windows-firewall-rules-using-powershell%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            6














            You would use the Enable-NetFirewallRule cmdlet:



            Enable-NetFirewallRule -Name "WMI-WINMGMT-In-TCP", "WMI-RPCSS-In-TCP"


            In order to find the relevant rule names (in order to enable it), you can search existing firewall rules by name by using the Get-NetFirewallRule cmdlet, for example:



            Get-NetFirewallRule -Name "*WMI*"


            This uses wildcards to final all the rules that contain "WMI" as an example.






            share|improve this answer























            • Small note, you can shortcut the command by providing both names together. So Enable-NetFirewallRule -Name 'WMI-WINMGMT-In-TCP','WMI-RPCSS-In-TCP' would have the same effect.
              – Shawn Melton
              Dec 31 '18 at 16:56










            • @ShawnMelton Thanks! I don't use PowerShell super often these days, and always forget exactly what syntax to use for passing lists like that. So I just default to multiple commands =) I've updated the answer.
              – jadarnel27
              Dec 31 '18 at 17:08










            • Oh, it works either way. Some prefer to use multiple for readability when they are just glancing....as long as it gets the job done.
              – Shawn Melton
              Jan 1 at 18:01
















            6














            You would use the Enable-NetFirewallRule cmdlet:



            Enable-NetFirewallRule -Name "WMI-WINMGMT-In-TCP", "WMI-RPCSS-In-TCP"


            In order to find the relevant rule names (in order to enable it), you can search existing firewall rules by name by using the Get-NetFirewallRule cmdlet, for example:



            Get-NetFirewallRule -Name "*WMI*"


            This uses wildcards to final all the rules that contain "WMI" as an example.






            share|improve this answer























            • Small note, you can shortcut the command by providing both names together. So Enable-NetFirewallRule -Name 'WMI-WINMGMT-In-TCP','WMI-RPCSS-In-TCP' would have the same effect.
              – Shawn Melton
              Dec 31 '18 at 16:56










            • @ShawnMelton Thanks! I don't use PowerShell super often these days, and always forget exactly what syntax to use for passing lists like that. So I just default to multiple commands =) I've updated the answer.
              – jadarnel27
              Dec 31 '18 at 17:08










            • Oh, it works either way. Some prefer to use multiple for readability when they are just glancing....as long as it gets the job done.
              – Shawn Melton
              Jan 1 at 18:01














            6












            6








            6






            You would use the Enable-NetFirewallRule cmdlet:



            Enable-NetFirewallRule -Name "WMI-WINMGMT-In-TCP", "WMI-RPCSS-In-TCP"


            In order to find the relevant rule names (in order to enable it), you can search existing firewall rules by name by using the Get-NetFirewallRule cmdlet, for example:



            Get-NetFirewallRule -Name "*WMI*"


            This uses wildcards to final all the rules that contain "WMI" as an example.






            share|improve this answer














            You would use the Enable-NetFirewallRule cmdlet:



            Enable-NetFirewallRule -Name "WMI-WINMGMT-In-TCP", "WMI-RPCSS-In-TCP"


            In order to find the relevant rule names (in order to enable it), you can search existing firewall rules by name by using the Get-NetFirewallRule cmdlet, for example:



            Get-NetFirewallRule -Name "*WMI*"


            This uses wildcards to final all the rules that contain "WMI" as an example.







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Dec 31 '18 at 17:07

























            answered Dec 28 '18 at 21:16









            jadarnel27jadarnel27

            3,8541330




            3,8541330












            • Small note, you can shortcut the command by providing both names together. So Enable-NetFirewallRule -Name 'WMI-WINMGMT-In-TCP','WMI-RPCSS-In-TCP' would have the same effect.
              – Shawn Melton
              Dec 31 '18 at 16:56










            • @ShawnMelton Thanks! I don't use PowerShell super often these days, and always forget exactly what syntax to use for passing lists like that. So I just default to multiple commands =) I've updated the answer.
              – jadarnel27
              Dec 31 '18 at 17:08










            • Oh, it works either way. Some prefer to use multiple for readability when they are just glancing....as long as it gets the job done.
              – Shawn Melton
              Jan 1 at 18:01


















            • Small note, you can shortcut the command by providing both names together. So Enable-NetFirewallRule -Name 'WMI-WINMGMT-In-TCP','WMI-RPCSS-In-TCP' would have the same effect.
              – Shawn Melton
              Dec 31 '18 at 16:56










            • @ShawnMelton Thanks! I don't use PowerShell super often these days, and always forget exactly what syntax to use for passing lists like that. So I just default to multiple commands =) I've updated the answer.
              – jadarnel27
              Dec 31 '18 at 17:08










            • Oh, it works either way. Some prefer to use multiple for readability when they are just glancing....as long as it gets the job done.
              – Shawn Melton
              Jan 1 at 18:01
















            Small note, you can shortcut the command by providing both names together. So Enable-NetFirewallRule -Name 'WMI-WINMGMT-In-TCP','WMI-RPCSS-In-TCP' would have the same effect.
            – Shawn Melton
            Dec 31 '18 at 16:56




            Small note, you can shortcut the command by providing both names together. So Enable-NetFirewallRule -Name 'WMI-WINMGMT-In-TCP','WMI-RPCSS-In-TCP' would have the same effect.
            – Shawn Melton
            Dec 31 '18 at 16:56












            @ShawnMelton Thanks! I don't use PowerShell super often these days, and always forget exactly what syntax to use for passing lists like that. So I just default to multiple commands =) I've updated the answer.
            – jadarnel27
            Dec 31 '18 at 17:08




            @ShawnMelton Thanks! I don't use PowerShell super often these days, and always forget exactly what syntax to use for passing lists like that. So I just default to multiple commands =) I've updated the answer.
            – jadarnel27
            Dec 31 '18 at 17:08












            Oh, it works either way. Some prefer to use multiple for readability when they are just glancing....as long as it gets the job done.
            – Shawn Melton
            Jan 1 at 18:01




            Oh, it works either way. Some prefer to use multiple for readability when they are just glancing....as long as it gets the job done.
            – Shawn Melton
            Jan 1 at 18:01













            0














            I have the same problem and manually enabled these two rules on the firewall and then did a server restart of the SQL server but this did not get rid of the blue question mark icon.



            I also tried to do it via a PowerShell script followed by a server restart but this did not work either.



            This is not a show stopper as I can connect to the SQL server from my PC with SSMS 17.9.1 and access the database, but it is annoying and slightly worrying.



            Any other suggestions?





            share








            New contributor




            Billy The Mexican is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.























              0














              I have the same problem and manually enabled these two rules on the firewall and then did a server restart of the SQL server but this did not get rid of the blue question mark icon.



              I also tried to do it via a PowerShell script followed by a server restart but this did not work either.



              This is not a show stopper as I can connect to the SQL server from my PC with SSMS 17.9.1 and access the database, but it is annoying and slightly worrying.



              Any other suggestions?





              share








              New contributor




              Billy The Mexican is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.





















                0












                0








                0






                I have the same problem and manually enabled these two rules on the firewall and then did a server restart of the SQL server but this did not get rid of the blue question mark icon.



                I also tried to do it via a PowerShell script followed by a server restart but this did not work either.



                This is not a show stopper as I can connect to the SQL server from my PC with SSMS 17.9.1 and access the database, but it is annoying and slightly worrying.



                Any other suggestions?





                share








                New contributor




                Billy The Mexican is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.









                I have the same problem and manually enabled these two rules on the firewall and then did a server restart of the SQL server but this did not get rid of the blue question mark icon.



                I also tried to do it via a PowerShell script followed by a server restart but this did not work either.



                This is not a show stopper as I can connect to the SQL server from my PC with SSMS 17.9.1 and access the database, but it is annoying and slightly worrying.



                Any other suggestions?






                share








                New contributor




                Billy The Mexican is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.








                share


                share






                New contributor




                Billy The Mexican is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.









                answered 3 mins ago









                Billy The MexicanBilly The Mexican

                11




                11




                New contributor




                Billy The Mexican is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.





                New contributor





                Billy The Mexican is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.






                Billy The Mexican is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Database Administrators Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f225944%2fhow-to-enable-these-windows-firewall-rules-using-powershell%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Liste der Baudenkmale in Friedland (Mecklenburg)

                    Single-Malt-Whisky

                    Czorneboh