> 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/troubleshoot/command-centre-connection-issues/command-centre-connection-issues-print.md).

# Printing - Macros or Scheduled Printing not working

[Command Centre - Connection Issues](/knowledge-hub/products/cc-software/troubleshoot/command-centre-connection-issues.md) › Printing - Macros or Scheduled Printing not working

When printing from a Macro or a scheduled print job, the account used is the Windows account that the **Command Centre Service** is running as, and that account needs permission to access the printer the report prints to.

This is different from interactive workstation printing, which uses the logged-in operator's Windows account. See [Printing - Windows User Accounts](/knowledge-hub/products/cc-software/troubleshoot/command-centre-connection-issues/command-centre-connection-issues-p-2.md) for the account overview.

![Printing report requirements from the Command Centre Server](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-737ab205eb67025570a21d9ecf3613fd00d8db1b%2FSECHUB-CCS-CONN-PRINT-MACROS-01.png?alt=media)

## Network printing (Macro or scheduled)

If you have trouble printing a report through a **networked** printer from a Scheduled or Macro-driven print job, the account the Command Centre service runs as needs access to the printer. On a corporate network, it may be worth **changing the user the Command Centre service runs as** to one that has the required printer access.

***

🔗 **Related**

* [Printing - Windows User Accounts](/knowledge-hub/products/cc-software/troubleshoot/command-centre-connection-issues/command-centre-connection-issues-p-2.md). Which account prints, and diagnosing a printing failure.


---

# 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/troubleshoot/command-centre-connection-issues/command-centre-connection-issues-print.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.