RPC: Enable RPC over named pipes
Controls RPC over named pipes support. Keep enabled for compatibility but combine with authentication settings. MSPs monitor this for security posture.
- Policy path
- Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options
- Supported on
- Windows 10, Windows 11, Windows Server 2016 and later
Controls RPC over named pipes support. Keep enabled for compatibility but combine with authentication settings. MSPs monitor this for security posture. Security baselines recommend setting it to 1.
Description
RPC: Enable RPC over named pipes is a Windows Group Policy setting located under Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options. It applies to the Computer Configuration branch and is classified as a Informational-level policy in the RPC & DCOM Security category.
Controls RPC over named pipes support. Keep enabled for compatibility but combine with authentication settings. MSPs monitor this for security posture.
Microsoft sets the default value to 1 while industry security baselines (CIS, NIST, DISA STIG) recommend 1.
Under the hood, this policy is enforced through the Windows registry at HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters using the value name EnableRPCOverNamedPipes. Modifying the value directly through regedit.exe or PowerShell produces the same effect as configuring the GPO, but going through Group Policy is preferred so that the setting is centrally managed and survives reboots, image rebuilds, and policy refresh cycles.
In-depth explanation
This is primarily an operational or user-experience setting. It does not directly raise or lower the security posture, but it standardizes behavior across the fleet, which is important for predictable support, training, and troubleshooting in an MSP-managed environment.
The policy is grouped under RPC & DCOM Security, which means it is typically applied through a domain-wide GPO linked at the OU level. In a multi-tenant MSP context, scope it through WMI filters or security group filtering rather than linking at the domain root, so that you can roll out progressively (pilot OU → wider rings → all production).
The setting takes effect after the next Group Policy refresh (gpupdate /force for immediate testing, or by default within ~90 minutes for workstations and ~5 minutes on domain controllers). For computer-side policies a reboot may be required; for user-side policies, a sign-off/sign-on cycle is enough.
Use cases
- Apply organization-wide hardening of rpc & dcom security on all domain-joined Windows endpoints.
- Roll out a CIS Benchmark-aligned baseline targeting 'RPC: Enable RPC over named pipes' via a dedicated GPO.
- Reduce attack surface for accounts that handle privileged credentials or sensitive data.
- Standardize the configuration across multiple customer tenants for an MSP-managed fleet.
Security implications
This control is primarily about consistency and supportability rather than security. The main risk of leaving it unconfigured is divergence between machines, which makes troubleshooting and standardized imaging harder, especially across multiple customer tenants in an MSP context.
How to configure
- Open Group Policy Management Console (
gpmc.msc) on a domain controller or a workstation with RSAT installed. - Create or edit a GPO linked to the OU containing the target computer configurations. We recommend a dedicated baseline GPO (e.g. SEC – RPC & DCOM Security) instead of editing Default Domain Policy.
- Navigate to
Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options. - Open RPC: Enable RPC over named pipes and set it to
1. - Click OK and close the editor.
- On the target endpoint, run
gpupdate /force(or wait for the next refresh cycle), then verify withrsop.mscorgpresult /h report.html.
Direct registry path: HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters\EnableRPCOverNamedPipes. You can apply the same change with PowerShell:
New-Item -Path 'HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters' -Force | Out-Null
Set-ItemProperty -Path 'HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters' -Name 'EnableRPCOverNamedPipes' -Value <value> -Type DWordRegistry mapping
HKLM\System\CurrentControlSet\Services\LanmanServer\ParametersEnableRPCOverNamedPipesREG_DWORD11