Release: CCS 12.6.1
Component: CCS Agent
The message 'Descoping Asset as respective agent status is unreachable' is just a warning message indicating that a previous job run (a CCS ping, CER job, Data collection job, etc) had a problem with the agent and it has been 'descoped' from future scans, and the descoping message is saying that the asset was skipped because that agent has known problems and has been marked 'red' in the Agent view in the console. Once the issue is resolved on the agent and it is verified by a CCS Ping (in the CCS Console) or running an Agent Management Job and the agent is marked 'green' in the Console, then that asset will be included in the next scan.
To see the actual error that is being reported when a scan is run on that agent, you can export a .csv file that will give details on what might be causing the issue.
First, check the 'Available column' icon on the right-hand side and enable all the columns:
Using that information in the CSV, you can also check to see if the following might not be causing the problem:
NOTE: Once the connectivity problem to that agent has been resolved, check in the CCS console to see if the agent (Assets > Agents section) shows a green or red icon for that agent. If it still shows that the agent is red, you may have to run a 'Ping' from the CCS Console (Right-click on the agent name and select 'Ping') for CCS to check to see if it has connectivity to the agent. If the agent then shows green, it will be included in the next data collection or CER job that is run on that agent. If it is red, then there are problems connecting to that agent and it will not be included until the problem is resolved and a successful CCS Ping is run on that agent.
Retaining unreachable agents in data collection job scope
Handshake errors in CCS:
Control Compliance Suite - Handshake error occurred while authenticating the agent