Sometimes the acs forwarder doesn’t connects successfully to the acs server and states in the operations manager event log, that you have to activate debugging to see more details.
You can activate it by following this instruction:
- Browse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AdtAgent\Parameters
- Create DWORD value = TraceFlags
- Edit the TraceFlags entry and enter decimal value 524420
- Restart the AdtAgent service
(Source: http://helpmemanage.blogspot.com/2007/05/enable-detailed-logging-for-acs.html)
You can find the log under c:\windows\temp
One cause can be that the acs cannot operate over forest borders or from a workgroup (kerberos authentication – some reason for the scom agent).
The workaround is a little bit mor complicated that a simple certificate exchange.
A good and working explanation can be found here:
