The following is a list of issues known to exist with regards to agents at the time of Quest release:InTrust 9.5.
Computers that are supposed to run InTrust Server must be configured to allow for incoming connections on the TCP port on which your InTrust Servers are configured to communicate with agents (TCP port 900 by default).
For example, InTrust Server cannot be installed on a computer running Windows XP Service Pack 2 with default settings which do not allow for agent registration (in particular, Personal Firewall with blocked incoming connections).
If an agent has been installed manually, then you cannot uninstall it from InTrust Manager. Uninstall the agent manually, as described in the Deploying Agents section of the Quick Start Guide.
You may have to uninstall the agents manually, if the InTrust Server to which the agents belonged is uninstalled. To avoid this, uninstall the agents from InTrust Manager prior to removing the server.
When agents are used to gather audit data, the following error may occur:
Agent has not yet established connection to the InTrust Server (0x8adc2c09).
This situation may occur due to network problems, or when InTrust services have just been restarted, and agents have not communicated to the InTrust Server yet.
You may get several agent errors, if there's no free disk space on the computer where the InTrust agent is installed. For example:
ADC Error: User not found (0x8adc3207), (0x8adc2c05)
If InTrust agent is installed via Group Policy to a Windows XP Professional computer where the logon optimization is on, remember that software installation policy is applied only at next logon. Thus, the following message will appear in the event log:
The assignment of application Quest InTrust Agent from policy <policy> failed. The error was: The group policy framework should call the extension in the synchronous foreground policy refresh. For more information, see Help and Support Center.
After the next logon, the installation of the InTrust Agent from policy will be completed. For details, refer to the Microsoft KB article
305239 "Description of the Windows XP Professional Fast Logon Optimization Feature"
If an attempt to manually register an agent on an InTrust Server fails with the error message
'Cannot register agent on the InTrust server <...> No connection could be made because the target server actively refused it. <Win32 Error 10061>.'
check if the Quest InTrust Agent service is running and not stopped on the agent computer. If the service is stopped, start it and try registering the agent again.
Installation of an agent on a computer under an account from a trusted domain may fail with an error message stating that the 'Logon as a service' right cannot be granted to the agent account. This happens if the specific account has never logged on to that computer before. To prevent the problem, log on to the target computer under that account before installing the agent.
When you are installing an InTrust agent by running the agent installation package (adc_agent*.msi), a Command Prompt window pops up. This window neither requires any input nor indicates of any problem with the agent installation.
If you manually uninstall an InTrust agent from a computer and try to install it again later, agent setup prompts you to repair or remove the agent as if it was still installed.
InTrust agents do not support the jp_JA.SJIS locale on Linux.
If you use InTrust Manager to unregister an InTrust agent residing on a computer that has no connection to the InTrust Server, then you may get errors trying to register the agent again with InTrust Manager after the connection is restored. If this happens, use the agent command with the -add parameter on the target computer.
If agent recovery takes place on a site for which the Prohibit automatic agent deployment on site computers option is enabled, the InTrust Server log may contain incorrect messages stating that the recovery was successful.
You may receive the following error in the InTrust log when deploying agents to an InTrust site that includes InTrust Server computer(s):
Cannot install the agent on '<server_name>' because of an error. Error text: Cannot stop agent service (A stop control has been sent to a service that other running services are dependent on. (Win32 error: 1051) )..