Views:
PortalProtect must have access to the following SQL Server database sources:
  • PortalProtect Configuration Database
  • SharePoint Databases
To access these databases, PortalProtect requires the following database access accounts:
  • PortalProtect Configuration Database Access Account
  • SharePoint Database Access Account
Note
Note
These database access accounts must support either Windows Authentication or SQL Server Authentication.
If an access account is configured with SQL Server Authentication, the access account password will be saved and encrypted in the registry.
If an access account is configured with Windows Authentication, it will be used as the PortalProtect service log on account.
If both access accounts use Windows Authentication, they must be the same account, and will be used as the PortalProtect service log on account. The following table shows the PortalProtect service log on account.

PortalProtect service log on account

PortalProtect Configuration Database Access Account
SharePoint Database Access Account
PortalProtect Service Startup Account
Windows Authentication
Windows Authentication
Both access accounts must be the same. PortalProtect will use these for the service startup account
Windows Authentication
SQL Server Authentication
PortalProtect Configuration Database Access Account
SQL Server Authentication
Windows Authentication
SharePoint Database Access Accounts
SQL Server Authentication
SQL Server Authentication
Local System
If the access account is configured with SQL Server Authentication, the password will be saved under the following registry key:
HKLM\Software\TrendMicro\PortalProtect\CurrentVersion
This registry key also contains SharePoint behavior; the password is encrypted.
Note
Note
  • Trend Micro highly recommends you use Windows Authentication. Windows Authentication provides a more stable environment and does not require you to save your password in any form.
  • If SQL server authentication is used by both PortalProtect and SharePoint databases, Web content scan and manual scan in PortalProtect will not work due to feature limitations.
  • The PortalProtect service startup account must have permanent local administrator privileges. Otherwise, the installation will fail.
Related information