If Windows Normal Servers are not getting updated:
- Check if the following services are started on the NS:
- Remote Registry service
- RPC service
- Verify the following:
- Ping the NS from IS and vice versa using both IP address and host name.
- Access the C$ drive from NS to IS and vice versa. Make sure the following ports are open in the firewall.
For IS:
For the NSs:
- TCP: 135, 139, 443, 3628, 4899, 5168, 5005-5014
- UDP: 137, 138 , 139, 3000-3009
- TCP: 135, 139, 443, 3628, 4899, 5168
- UDP: 137, 138 , 139
- Check the TCP/IP configuration on IS.
- Make a backup of TmRpc.ini file found in the ..\Program Files\Trend\SProtect directory.
- Check if all the listed NS has a value of "2". For example, 10.10.10.10=2.
- Check if EventMsg2.dll is located in the ..\SProtect folder and ..\winnt\system32 folder of NS.
- Check the security policy settings in the NS side.
- Open the Local Group Policy Editor (gpedit.msc).
- Navigate to Computer Configuration > Administrative Templates > System > Remote Procedure Call > Restrict Unauthenticated RPC clients / Enable RPC Endpoint Mapper Client Authentication.
- Check and set the above options for this setting to "Not Configured".
- Make sure the registry values for EnableAuthEpResolution and RestrictRemoteClients under Rpc do not exist, or the value is 0. The registry path is HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Rpc.
- Verify that the Windows account used on NS has administrator permission.
- Restart Trend ServerProtect service on NS after RPC configuration is updated.
- Check if the latest ServerProtect patch has been installed.
- Verify that a task on IS is deploying the pattern to NS on a regular basis.
- Open the management console.
- Click the NS or domain and click Task > Existing Task to view the tasks assigned to a server.
- Click View to see the contents of a task.
If pattern files are still not deployed, collect and send the following files to Trend Micro Technical Support:
- SPNT.log
To get this file:- Open the SPNT management console.
- Select the NS that is unable to receive the pattern update.
- Click Do > Create Debug Info.
- Select Enable debug log on the Debug Log Management page.
- Select Trace all messages, then select Normal Server.
- Select Output to a debug file, then type the path and filename of the log in the Directory field.
- Click OK > Apply.
- Deploy the pattern file and collect the SPNT.log file.
- Disable the debug log.
- Tmudump.txt located under the ..\Program Files\Trend\SProtect\AC_Up-Rb.tmp\AU_Log directory.
- IS Update log
To get this file:- On the IS, select the NS that is unable to receive the pattern update.
- Click View Log on the left side of the console.
- Select Update as the log type and specify the date range when the issue occurred.
- Click Export and save the Update log to a CSV file.