Refer to the exhibit. You need to ensure that all data transmitted over SMB between your file server and domain-joined clients is encrypted. You set the configuration to True, but users report connectivity issues. What is the most likely cause?
SMB encryption was introduced in version 3.0. Clients attempting to connect using SMB 2.1 or earlier cannot perform the required cryptographic handshake when encryption is enforced globally. Consequently, the server terminates the connection attempt, preventing the client from accessing files, which explains the reported connectivity issues during the migration.
Why this answer
Enabling SMB encryption globally forces all connections to use encryption. Older clients or non-Windows systems that do not support SMB 3.0 or higher will fail to negotiate a connection, resulting in access errors. This transition requires careful planning, often involving auditing first or using per-share encryption instead of global settings to maintain backward compatibility while securing sensitive data transfers across the network infrastructure.