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
- Review domain policy and application compatibility.
- Require signing on a pilot file server and client group.
- Refresh policy and reconnect sessions.
- Measure authentication and file-transfer behavior.
Commands
Set-SmbServerConfiguration -RequireSecuritySignature $true -EnableSecuritySignature $true -Force
Get-SmbServerConfiguration | Select RequireSecuritySignature,EnableSecuritySignatureVerification
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.
Related resources
Canadian Windows VPS and RDS hosting: networkmanager.info. Refer to Microsoft Windows Server documentation.