When running the CLI commands to return status from TPAM 2.5 (such as "GetStatus -db") it is seen that the SQLSERVERAGENT is not running. Should this agent be running?
Example output from 'GetStatus -db' command:
The Current State of SQLSERVERAGENT is Stopped
In previous releases such as 2.3/2.4, this agent must be running for the appliance to perform many critical tasks.
TPAM 2.5 does report the status of the SQLSERVERAGENT; however this is a remnant of previous releases. This SQLSERVERAGENT is not used in TPAM 2.5 releases as it was used in previous versions.
The SQLSERVERAGENT being stopped in TPAM 2.5 has no impact on TPAM 2.5 operations.