> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cc-software/configure/identity-solutions-cardholders-and-ope/active-directory/active-directory-sync-v8-50-non-domain.md).

# Run Active Directory Sync v8.50 on a non-domain Command Centre server

Configure Active Directory Sync v8.50 when the Command Centre server is not domain-joined.

You **can** run AD Sync where the **Command Centre server is not domain-joined**.

## Requirements

* The **AD Sync server** must be in the domain (so it can identify who is changing its config).
* Enable **AD Single Sign-On temporarily** until the Authorising Group Operator is configured.
* The CC server itself does not need to be in AD.

## Procedure

1. Turn on SSO in CC Server Properties to configure the Windows account names of the operators who will set up AD Sync.
2. Once the credential is in place, SSO can be turned off again.

![Operator properties — Operator Configuration with Windows logon enabled and the AD Sync operator's domain\username set](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-fa1f4c3754de880cb3d4dff683f7f064d5f8db11%2FSECHUB-AD-SYNC-23-operator-windows-logon.png?alt=media)

***

🔗 **Related**

* [Sync v8.50 - What's new](/knowledge-hub/products/cc-software/configure/identity-solutions-cardholders-and-ope/active-directory/active-directory-sync-v8-50-what-s-new.md). Why SSO authorizes the UI.
* [Single Sign-On - Setting Up](/knowledge-hub/products/cc-software/configure/identity-solutions-cardholders-and-ope/active-directory/active-directory-single-sign-on-settin.md). Enabling SSO in Command Centre.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/products/cc-software/configure/identity-solutions-cardholders-and-ope/active-directory/active-directory-sync-v8-50-non-domain.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.