Issue
If you are using Windows computers (Windows 7/8/10) with the SMB1 protocol disabled, the remote deployment of actions in Server Tasks in ERA Web Console is performed using the SMB2 protocol. You must enable SMB2 on the ERA Server Virtual Appliance so that these actions can be carried out.
Solution
To deploy ERA Agent from the ERA Server Virtual Appliance (VA) using the Server Task (remote deployment), follow these steps:
- Make sure the client computer is visible from the ERA Server on the network.
- Disable UAC remote restrictions.
Visit this Microsoft Knowledgebase article for instructions to disable UAC remote restrictions. The article pertains to Windows Vista but is also applicable to later versions of Windows.
- Open the Terminal on your ERA VA Server.
Figure 1-1
- On the ERA VA, edit the deployment script
UnixWindowsNetworkRemoteInstall.sh
located at (the below command should be in one line):nano /var/opt/eset/RemoteAdministrator/Server/Scripts/UnixWindowsNetworkRemoteInstall.sh
- Edit the following line to enable the usage of SMB2:
Original line (the below text should be in one line):
LANG= mount -t cifs -o "${mount_domain_option}username=$ERA_RD_WN_USERNAME" "$remote_cifs_share" "$local_cifs_mount"
Edited line (the below text should be in one line):LANG= mount -t cifs -o "${mount_domain_option}username=$ERA_RD_WN_USERNAME,vers=2.0" "$remote_cifs_share" "$local_cifs_mount"
-
Run the following command to restore the SELinux context (which was changed by the modification of the script file in the previous step):
/sbin/restorecon -F -R -v /var/opt/eset/RemoteAdministrator/Server
- In ERA VA Web Console, run the Agent Deployment Server Task to remotely deploy ERA Agent on the selected Windows computer(s).
- After the successful deployment of ERA Agent, enable UAC remote restrictions on the client Windows computer (see step 2 above).
Add a comment
Please log in or register to submit a comment.