From c5a94b8d1711eb5d172c8627a8c4a2835bfe62ca Mon Sep 17 00:00:00 2001 From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com> Date: Tue, 2 Mar 2021 22:07:16 +0530 Subject: [PATCH] corrected command as peruser report issue #9224 , so i corrected the error and added correct command. so i took below site for reference **https://docs.microsoft.com/sql/relational-databases/security/using-service-sids-to-grant-permissions-to-services-in-sql-server?view=sql-server-ver15** --- .../create-an-inbound-program-or-service-rule.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/windows-firewall/create-an-inbound-program-or-service-rule.md b/windows/security/threat-protection/windows-firewall/create-an-inbound-program-or-service-rule.md index a47d50ae43..bd01350eee 100644 --- a/windows/security/threat-protection/windows-firewall/create-an-inbound-program-or-service-rule.md +++ b/windows/security/threat-protection/windows-firewall/create-an-inbound-program-or-service-rule.md @@ -65,7 +65,7 @@ To create an inbound firewall rule for a program or service To set a SID type on a service, run the following command: - **sc** **sidtype** *<Type> <ServiceName>* + **sc** **sidtype** *<ServiceName> <Type>* In the preceding command, the value of *<Type>* can be **UNRESTRICTED** or **RESTRICTED**. Although the command also permits the value of **NONE**, that setting means the service cannot be used in a firewall rule as described here. By default, most services in Windows are configured as **UNRESTRICTED**. If you change the SID type to **RESTRICTED**, the service might fail to start. We recommend that you change the SID type only on services that you want to use in firewall rules, and that you change the SID type to **UNRESTRICTED**.