Applies to: Windows Server 2019, Windows Server 2022, and Windows Server 2025.
SMB encryption protects file traffic from interception without requiring IPsec.
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
- Confirm client compatibility and select the sensitive share.
- Enable encryption on the individual share.
- Test access from every supported client.
- Monitor SMB server events and performance.
Commands
Set-SmbShare -Name "Finance" -EncryptData $true
Get-SmbShare -Name "Finance" | Select Name,EncryptDataVerification
The share reports EncryptData True and approved clients can read and write files.
Rollback
Set EncryptData to false only after restoring another approved transport-protection control.
Security notes
- Use least privilege and record the change.
- Review relevant event logs after implementation.
- Test before production rollout.
Validate encryption on the client connection
SMB encryption protects file traffic in transit; it does not encrypt the stored files on disk or replace share and NTFS permissions. Confirm that every required client supports the negotiated SMB dialect and the encryption requirement before enabling it on a busy share. Older devices or applications can lose access when they do not meet the policy.
Capture the current EncryptData value, identify pilot users and test an actual file open, edit and save. Reconnect the pilot SMB session when needed so the result reflects the new policy, then inspect Get-SmbConnection on the client for the negotiated connection and encryption state. Reading the share configuration alone shows intent, not every client’s live behaviour.
Measure the application’s normal file workload after the change. Do not diagnose all slowness as encryption overhead without checking storage, network and workload evidence. Keep the previous setting and a defined exception-review path, rather than weakening encryption permanently for an unidentified legacy client.
For release-specific security behaviour, review Microsoft’s SMB client encryption controls. Distinguish a per-share server setting from a requirement configured on the connecting client.
Related resources
Canadian Windows VPS and RDS hosting: managed Windows VPS hosting. Refer to Microsoft Windows Server documentation.