When the Trend Micro Safe Lock Intelligent Manager was installed in legacy Windows XP or Windows Server 2003, you may not be able to remotely install the agent in Windows 10 Fall Creators Update. The folllowing error may occur:
Unable to copy files. Unable to establish a file sharing connection. The endpoint cannot connect or store files because of network problem (Windows Error 64).
This article explains how to perform remote installation of Trend Micro Safe Lock agent using SLrst.exe.
Trend Micro Safe Lock Intelligent Manager in legacy Windows XP or Windows Server 2003 uses the Server Message Block (SMB) version 1 (SMBv1). Before installing the Safe Lock agent, the SMBv1 must be enabled and the SMBv3 must be disabled in Windows 10 Fall Creators Update.
Based on Microsoft Support, it is not recommended to disable SMBv2 or SMBv3. Note that disabling SMBv2 or SMBv3 is only used as a temporary troubleshooting measure. Do not leave SMBv2 or SMBv3 disabled after doing this procedure.
For more details, please refer to this article: How to detect, enable and disable SMBv1, SMBv2, and SMBv3 in Windows and Windows Server.
To remotely install the agent:
- On the "Turn Windows features on or off" screen, enable SMB 1.0/CIFS File Sharing Support in Windows 10 Fall Creators Update and reboot the targeted systems.
- Run the Windows PowerShell as administrator.
- Detect the status of SMBv1 Protocol by running the following command:
Get-WindowsOptionalFeature –Online –FeatureName SMB1Protocol
- Execute the command below to disable SMBv2 or SMBv3 Protocol:
Set-SmbServerConfiguration –EnableSMB2Protocol $false
- Detect the status of SMBv2 or SMBv3 by running the following command:
Get-SmbServerConfiguration | Select EnableSMB2Protocol
- Remotely install the Trend Micro Safe Lock agent by running the SLrst.exe file from the Safe Lock Intelligent Manager.
- Once the installation is completed, make sure to disable the SMBv1 and enable SMBv3 in Windows 10 Fall Creators Update.