Views:

This issue happens due to the changes in Windows 2008 R2, which affect the RPC binding between the SPNT Normal Server and Information Server. These are the changes in the NTLM Authentication regarding session security and the NTLM fallback for System Services.

Since this issue has been isolated to happen only on Windows 2008 R2, this will not occur when the Information Server is hosted on a Windows 2003 or 2008 server.

You can refer to this article for additional information about this topic:

Changes for Identity and Authentication in Windows Server 2008 R2

To resolve this issue, please do the following:

  1. Go to Control Panel > Administrative Tools > Local Security Policy .
  2. Under Local Policies, go to Security Options .
  3. Change the following settings:
    • Network Security: Allow "Local system" to use "Computer identity" for NTLM. Set this value to "DISABLED".
    • Network Security: LAN Manager authentication level - Set this value to "Send LM & NTLM". Use NTLMv2 session if needed.
    • Network Security: Minimum session security for NTLM SSP-based (including secure RPC) clients. Disable "Require 128-bit encryption" if it is enabled. If the configuration is "No minimum", then do not change this setting.
    • Network Security: Minimum session security for NTLM SSP based (including secure RPC) servers. Disable "Require 128-bit encryption" if it is enabled. If the configuration is "No minimum", then do not change this setting.
    • Network access: Let the "Everyone" permission apply to "anonymous users". Set this value to "ENABLED".

After completing the changes on the ServerProtect IS hosted on a Windows 2008 R2 server, the following functionalities will work:

  • Installation for a new ServerProtect Normal Server from the management console
  • Addition of an existing ServerProtect Normal Server from the management console
  • Deployment of product update/upgrades from the management console

If the above steps did not resolve the issue, then do the following:

  1. Download and run the CDT utility on the Information Server.
  2. Collect the following logs:
    • CDT logs
    • ServerProtect Basic Log
    • Communication Issue
  3. Send the logs to Trend Micro Technical Support or contact your Technical Account Manager (TAM) for further analysis.
Keywords: remote install error,failed to complete operation