Troubleshooting domain cache issues on a CCS Windows agent using ProcMon tool

Products

• Control Compliance Suite
• Control Compliance Suite Standards Server
• Control Compliance Suite Standards Module

Issue/Introduction

Control Compliance Suite (CCS)

The domain cache on a CCS Windows agents is not being created and you would like to determine if what might be causing the problem.

Environment

All supported versions of CCS

Windows agent using Agent-Based data collection

Resolution

See the steps below to download Process Monitor (ProcMon) tool from Microsoft and then use it to collect information from the Windows server.

Download the ProcMon tool

1. Download Process Monitor tool (ProcMon) from Microsoft
   • https://learn.microsoft.com/en-us/sysinternals/downloads/procmon
2. Copy the ProcessMonitor.zip file to the Windows server that has the CCS agent with the domain cache issues.
   
   
3. Unzip the ProcessMonitor.zip file to the desktop.
   
   

Use the ProcMon tool to capture information on the CCS Scan

1. On the agent server, run Procmon64.exe
   
   
2. By default when ProcMon is started, it will begin capturing information from the Windows server.  Click the 'Capture' icon to stop it from collecting information.
   
   
   
3. Click on the 'trash can' icon to clear any information it may have gathered.
   
   
   
4. Just before running the CCS job to duplicate the issue in CCS, click the 'Capture' icon to have ProcMon start capturing information on the Windows agent server.
   
   
   
5. On the Application Server, run the CCS job and duplicate the issue.
   
   
6. When the CCS job completes, on the agent server click on the 'Capture' icon to stop ProcMon from capturing data.
   
   
   
7. To save the information that was captured in ProcMon, click on File and then Save
   
   
   
8. In the Save to File window, select the All Events bullet option, and then in the path specify where you would like the file to be saved. Name the file whatever you wish, but keep the .PML extension.
   NOTE: The file may be very large in size (1+ Gig), so make sure you have disk space to save the file.
   
   
   
9. Zip up the <filename>.PML file to reduce the size of the file, and upload it to the Broacome Support case for review.