Skip to content

How to Configure SMB Signing on Windows Server Print

  • 0

Applies to: Windows Server 2019, Windows Server 2022, and Windows Server 2025.

SMB signing protects the integrity of file-service communication and reduces relay attack risk.

Prerequisites

  • Administrative access and an approved change window.
  • A verified backup and documented rollback plan.
  • A pilot environment or low-risk target for validation.

Step-by-step procedure

  1. Review domain policy and application compatibility.
  2. Require signing on a pilot file server and client group.
  3. Refresh policy and reconnect sessions.
  4. Measure authentication and file-transfer behavior.

Commands

Set-SmbServerConfiguration -RequireSecuritySignature $true -EnableSecuritySignature $true -Force
Get-SmbServerConfiguration | Select RequireSecuritySignature,EnableSecuritySignature

Verification

New SMB connections negotiate signing and application tests complete successfully.

Rollback

Restore the documented previous server and client signing policy, then reconnect sessions.

Security notes

  • Use least privilege and record the change.
  • Review relevant event logs after implementation.
  • Test before production rollout.

Separate signing, encryption and version defaults

SMB signing provides message integrity and helps protect against tampering and relay attacks. It is different from encryption, which protects the confidentiality of data in transit. Decide which server and client requirements apply to your environment rather than treating the two settings as interchangeable switches.

Windows Server releases have different SMB hardening defaults, and Group Policy can govern the effective configuration. Inspect the installed release and current settings before changing them. A local command that is later overwritten by policy is not a durable deployment method.

Pilot the requirement with Windows clients, scanners, NAS devices and application integrations that use the share. If a client fails, determine whether it supports the required security mode and whether its authentication is correctly configured. Guest-only or outdated devices need a supported remediation plan, not a blanket exception for all shares.

Verify an actual client session and application file operation after reconnection. Record the previous policy and the specific affected device if rollback is needed. Consult Microsoft’s SMB signing overview when checking the effective behaviour of the server and client versions you operate.

Related resources

Canadian Windows VPS and RDS hosting: managed Windows VPS hosting. Refer to Microsoft Windows Server documentation.


Was this answer helpful?

« Back