---
title: Advanced Configuration
slug: advanced-configuration
docTags: 
createdAt: 2025-11-06T19:50:48.073Z
---

This document outlines advanced configuration techniques and troubleshooting steps for Activate Security Group Compliance Manager (SGCM). It is intended for administrators and engineers managing complex or high-scale environments.

# Advanced Configuration

SGCM offers flexible configuration options to extend monitoring scope, integrate with other Activate products, and fine-tune event processing.

# Extending the Schema

The default SGCM connector schema can be extended to include additional Active Directory attributes. This allows organisations to monitor and respond to changes beyond the standard set.

**To extend the schema:**

1. Open **Activate Studio**. 
2. Navigate to Resources > Active Directory. 
3. Locate and edit the **Schema** parameter. 
4. Add a new column definition using the following format: 

:::BlockQuote
\<column name="extensionAttribute1" type="varchar(256)" default="''" />
:::

After editing the schema, run the **Regenerate Schema** task to apply changes, then reimport data using the **Import Workflow**.

# Adjusting Polling and Event Sensitivity

SGCM’s polling frequency and event thresholds can be adjusted to balance performance and responsiveness.

| Parameter               | Description                                                      | Default       |
| ----------------------- | ---------------------------------------------------------------- | ------------- |
| **Connector\_PollTime** | Sets how often the Orchestrator checks for changes (in seconds). | 600           |
| **maxChanges**          | Limits the number of rows processed per cycle.                   | 0 (unlimited) |
| **retry/timeout**       | Defines how long failed changes should be retried.               | +2 days       |

For high-change environments, consider increasing Connector\_PollTime or setting maxChanges to a practical limit.

# Event Handler Customisation

Event handlers can be customised to include additional logic, such as department-specific alerts or dynamic role lookups.

**Example: Department-Based Notification**

:::BlockQuote
\<events>
&#x20; \<update>
&#x20;   \<notify>
&#x20;     \<users>=//Roles/Departments/%=//Current/department%\</users>
&#x20;     \<message>
&#x20;       \<subject>Departmental Group Change Detected\</subject>
&#x20;       \<body>\<!\[CDATA\[
&#x20;         A change to group membership was detected in the %=//Current/department% department.
&#x20;         Object: %=//Current/displayName%
&#x20;       ]]>\</body>
&#x20;     \</message>
&#x20;   \</notify>
&#x20; \</update>
\</events>
:::

# Performance Tuning

To optimise SGCM performance:

- Run the **FullWorkflowWithGroups** workflow at intervals suitable for your environment.&#x20;
- Avoid unnecessary attribute monitoring by disabling the @monitor flag on low-priority columns.&#x20;
- Regularly clean up historical compliance data using scheduled maintenance tasks.&#x20;
- Ensure the Activate Orchestrator service has sufficient memory and processing capacity.&#x20;

# Common Issues and Solutions

| Issue                          | Possible Cause                                    | Resolution                                                                                                    |
| ------------------------------ | ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| **Polling not running**        | Orchestrator service stopped or misconfigured     | Confirm Activate Orchestrator is running and parameters are correctly set.                                    |
| **No AD changes detected**     | Incorrect domain controller or missing permission | Verify the Connector\_ADServer parameter and ensure the account has *Replicate Directory Changes* permission. |
| **Import fails or incomplete** | Schema mismatch                                   | Regenerate schema and reimport. Ensure new attributes exist in both AD and the connector schema.              |
| **Slow processing**            | High change volume or low system resources        | Increase Connector\_PollTime or optimise database performance.                                                |
| **Duplicate notifications**    | Multiple workflows configured for same event      | Review event definitions to avoid overlapping Connector\_Events configurations.                               |

# Diagnostic Tools

Use the following methods to diagnose SGCM issues:

- **Activate Logs** – Review Orchestrator logs for event and workflow errors.&#x20;
- **Connector Data View** – Inspect pending or failed change rows under Resources > Active Directory.&#x20;
- **Audit History** – Check the audit log for recorded remediation actions or notifications.&#x20;
- **SQL Queries** – Analyse connector tables to verify import status or object counts.&#x20;

# Maintenance Recommendations

To maintain long-term stability and accuracy:

- Perform a full reimport after significant AD structural changes.&#x20;
- Archive or purge historical connector data regularly.&#x20;
- Verify background polling workflows weekly.&#x20;
- Schedule periodic restarts of the Activate Orchestrator during maintenance windows.&#x20;

# Escalation and Support

If internal troubleshooting does not resolve the issue:

- Collect relevant log files from the Activate Orchestrator.&#x20;
- Export event configurations from the affected domain resource.&#x20;
- Contact your Activate Support representative with the error details, workflow configuration, and Orchestrator logs.&#x20;

# Summary

Advanced configuration allows SGCM to adapt to diverse organisational structures and compliance requirements. With proper schema management, performance tuning, and event customisation, SGCM ensures continuous, accurate, and efficient monitoring of Active Directory environments.