Print Deploy PaperCut, having issues with MSI and Config file

[AB_IT]

Hey All,

 

So I've contacted my reseller, they don't seem to have a clue and PaperCuts response was to basically go to my reseller and I'm a bit stuck.

 

I'm trying to use Print Deploy in order to deploy our printers to Client PC's and 2 x RDS Servers. I've treated a test user and test domain joined PC to ensure it all works. I've followed the instructions on PaperCut to use the cloning tool to upload our print queues to the server and I've setup all my zones properly pointing at the IP I'm testing.

 

The issue I have is I think with the MSI. Basically there's a file located in C:\Program Files\PaperCut Print Deploy Client\data\config\client.conf.tomel which shows the server address as being a loopback address 127.0.0.1 instead of our PaperCut server address or hostname. I am deploying the MSI using Group Policy and downloading the MSI from the server, I have tried both downloading it remotely to a client computer and using this MSI and also downloading it locally on the server and using this MSI. Both install setting that file to look at the loopback address. I've also taken Group policy out of the equation and just installed the MSI manually but still no avail.

 

If I manually change the config file it all works fine and deploys the printers appropriately although I can't do this on 500+ machines.

 

The print deploy page under Enable Printing also has a settings tab with an entry point for hostname which I've tried adding but it had no effect and another for application server which likewise is the same.

 

What am I doing wrong here and does anyone know why it's not installing with our servers details in the config file? I've added some screenshots below to better explain, I'm at my wits end I'm not sure what I'm doing wrong here?

 

[Netwacky87]

Are you deploying the MSI with the server name in the filename?

 

For example: pc-print-deploy-client[print-server.company.lan].msi

[AB_IT]

Are you deploying the MSI with the server name in the filename?

 

For example: pc-print-deploy-client[print-server.company.lan].msi

Yeah, I've just checked. The MSI downloads the file with the server name in the filename.

 

I have been renaming this however to PaperCutDeploy and then deploying that, could this be the issue? I didn't think the filename would matter?

 

EDIT: Oh my god, it does apparently matter... Well now I feel stupid. Thank you ever so much for your help that's been driving me crazy all day!!

Edited June 17, 2024 by AB_IT

[Netwacky87]

Yeah, I made that mistake! Great its working!!

[PaperCutterBrenda]

Hi there AB_IT – PaperCutter Brenda here! I raised this question with our support team and they mentioned you have an active ticket chatting through solutions, so it looks like you're in the best hands possible. Let us know if we can help further!