> 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/configuration-client/site-management/reports/automatically-generated-reports/configuring-printers-for-reports-automatically-generated-via-macros.md).

# Configuring Printers for Reports automatically generated via Macros

### Introduction

The issues surrounding printing scheduled reports using macros will depend on the type of printer being used (local or network) and the operating system the FT Command Centre service is running on.

**Important details to know:**

* Network printers are only installed for the logged on user, unless deployed machine wide.
* Macros are run from the Command Centre server, even if started from a workstation.
* Macros are run using the logon user account configured for the FT Command Centre service.
* If the report is to be configured from the workstation, the same printer will need to be installed on the workstation and server. Otherwise the printer will not be able to be selected from the report drop down list on the workstation.
* Authentication could also become an issue. The User Account configured as the logon for the FT Command Centre service will need print rights on the shared printer.

This is why a report may print successfully when run manually, (from the Command Centre report properties, which is run under the logged on user). To resolve these issues, follow one of the procedures below appropriate for your operating system:

### METHOD 1

To install a network printer machine wide, deploy the printer using Rundll32, PrintUI.dll function as follows:

1. Log on to the Command Centre server.
2. Open a command prompt, run as an administrator, and enter:

   `RUNDLL32 PRINTUI.DLL,PrintUIEntry /ga /n\Server_name\Printer_sharename`
3. The Command Centre Server will need to be restarted as the printer is installed at login.
4. When the server has restarted, check to see the new printer is installed by opening a command prompt and entering:

   `RUNDLL32 PRINTUI.DLL,PrintUIEntry /ge`

Create and configure the Report (see [Creating a new report](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/reports/creating-a-new-report.md)) and Macro (see [Creating a new Macro](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/macros/creating-a-new-macro.md)).

### METHOD 2

The logon account that the FT Command Centre service runs under needs to be changed to a local user or administrator account.

1. From the **Start** menu, click **Run…**, and type in services.msc
2. Double-click the FT Command Centre Service.

   The FT Command Centre Service Properties window displays.
3. Click the **Log On** tab, and select the **This account** radio button.
4. Either click the **Browse…** button to locate the account name, or type in the account name, and enter the password for this account.
5. Click the **Apply** button.

   **Note:** The service needs to be restarted to take effect.

**Note:** These steps will need to be repeated if Command Centre is upgraded again, as the FT Command Centre service logon will revert to the Local System account each time Command Centre is upgraded.

Now that the service has been changed the printer needs to be installed for this user. This can be done by either:

* logging in as the user and installing the network printer, or
* installing the network printer as a local printer.

  **Note:** Local printers are installed for all users, not just the logged in user.

To install a network printer as a local printer:

1. From the **Start** menu, click **Printers and Faxes**.
2. Click **File** from the menu bar, then **Add Printer**.

   The Welcome screen of the “Add Printer Wizard” displays.
3. Click the **Next** button.
4. Click the **Local printer attached to this computer** radio button, and then uncheck the **Automatically detect and install my Plug and Play printer** option under it.
5. Click the **Next** button.
6. Click the **Create a new port** radio button.
7. From the **Type of port** drop-down list select either:
   * **Local Port** if the printer is shared from another machine on the network, (i.e. \XP\_workstation\_name\Printer\_share\_name), or
   * **Standard TCP/IP Port** if the printer is a true network printer with an IP address, (i.e. 192.168.1.200).
8. Continue with the printer install as normal, selecting the printer drivers, a name for the printer, printing defaults, etc.

Create and configure the Report (see [Creating a new report](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/reports/creating-a-new-report.md)) and Macro (see [Creating a new Macro](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/macros/creating-a-new-macro.md)).


---

# 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/configuration-client/site-management/reports/automatically-generated-reports/configuring-printers-for-reports-automatically-generated-via-macros.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.
