Deploy print queues but not the monitoring tool

The Direct Print Monitor tool automatically controls and tracks the printing on queues deployed by Print Deploy, and is bundled with the Print Deploy client by default.

If you don’t want to control and track printing, you can configure the Print Deploy client installer to skip the Direct Print Monitor installation.

Some examples of why you might not want to control and track printing are:

You’re using other mechanisms (such as via an LPD/LPR service) to point to the PaperCut Print Server instead of the Direct Print Monitor (monitoring queue). If the DPM was installed, jobs would be tracked twice.
You’re managing environments where there are:
- multiple servers with the same set of queues.
- multiple servers for redundancy.
You don’t use “direct printing” and print exclusively via PaperCut Mobility Print or traditional print servers.

Server changes

The Print Deploy Client’s auto-update process will automatically install the Direct Print Monitor during the update process.

To prevent this you must modify the DPMUpgradesEnabled configuration option in the client.conf.toml file, located in [application-server-path]\providers\print-deploy\[os]\data\config on your PaperCut NG/MF Server

Set DPMUpgradesEnabled = true to DPMUpgradesEnabled = false

Then Restart the Print Deploy Server service

Client changes

Windows

Run the MSI installer with the SKIP_DPM=true option.

msiexec /i <installer>.msi SKIP_DPM=true

When this version of the installer runs, it won’t install the Direct Print Monitor.

Mac

To update the installer to not install the Direct Print Monitor, create and save a .plist file on the machine.

Open a terminal and issue the following command:

defaults write ~/Documents/com.papercut.printdeploy.client skip_dpm true

This creates the .plist file that the installer uses for all the configuration values.
Supply a hostname. Issue the following command, but replace <hostname> with the FQDN (Fully Qualified Domain Name) from the ‘.dmg’, for example, print-server.company.lan

defaults write ~/Documents/com.papercut.printdeploy.client server_host <hostname>

For example

defaults write ~/Documents/com.papercut.printdeploy.client server_host print-server.company.lan
Convert the ‘.plist’ file into XML format using the following command:

/usr/bin/plutil -convert xml1 ~/Documents/com.papercut.printdeploy.client.plist
Display the contents of the new ‘.plist’ using the following command:

defaults read ~/Documents/com.papercut.printdeploy.client.plist

The output should be:
```
{
"server\_host" = <hostname>;
"skip\_dpm" = true;
}`
```
Before you start to deploy Print Deploy on a single machine, copy the plist file to: /Library/Managed Preferences/com.papercut.printdeploy.client.plist.

For more information about using JAMF to distribute the plist file in a large environments, take a look at Deploy print queues using Jamf and Print Deploy.

Linux

Run the .deb or .rpm installer with the SKIP_DPM=true option.

For .rpm based distributions: sudo SKIP_DPM=true yum localinstall <client-installer>\[<hostname>\].rpm
For .deb based distributions: sudo SKIP_DPM=true dpkg -i <client-installer>\[<hostname>\].deb