Papercut Local Msi or Network Exe

[keyboards]

Hi

 

Just want to gauge what people are doing for papercut, installing the MSI via GPO or logon script with a network share, as currently got a few sites doing different things and want to uniform it, I was leaning towards installing the local Msi everywhere. It looks like some of the repo companies setup the local network logon scripts

 

Thoughts?

 

Sorry meant client

Edited April 7, 2020 by keyboards

[MatthewL]

Presume your on about the client?

 

Neither is right or wrong, do what is best for your network, personally I would go MSI route.

[keyboards]

Yeah, sorry meant client, yeah I'm veering to towards the MSI route, just seeing if anyone has any pros or cons, as in my view I would go MSI, it's just some of the sites have been setup logon script network share wise but personally I would always go MSI

[thimon]

We use a user logon script that runs the exe from the network, that way the client is always up to date (as long as your PaperCut server application is up to date).

[FishCustard]

Would generally go for the "run from network" option as it ensures the client is up to date everywhere.

[psydii]

MSI based - for the same reasons we don't have any software run from network shares: 1 - because computers are mobile, and not necessarily connected to the network when they restart; 2 - Running applications over a wireless connection puts unnecessary load on the wireless network.

[Arthur]

MSI based - for the same reasons we don't have any software run from network shares: 1 - because computers are mobile, and not necessarily connected to the network when they restart; 2 - Running applications over a wireless connection puts unnecessary load on the wireless network.

^ Exactly this for me too!

[thimon]

To be fair, having the computers not on the network when they restart doesn't affect user logon experience. It's also a tiny .exe, which should help.

[MatthewL]

Don't forget that once it is installed it needs to be set to run on user login as its not automatic.

[eddyc]

MSI based - for the same reasons we don't have any software run from network shares: 1 - because computers are mobile, and not necessarily connected to the network when they restart; 2 - Running applications over a wireless connection puts unnecessary load on the wireless network.

 

MSI based here too. We update the MSI when we we update the server. We found the network based EXE too temperamental

[mullet_man]

MSI here too, just be careful when upgrading the MSI as I had an issue once where the client was left in a strange installed but not installed state.

[Anonymous2000]

Exe run from network for me. 1 version to look after in 1 place

[jezi55]

We run EXE over a network on a logon script, yes it has its dropouts now and then but saves having to keep rolling out a new client each time there is an update. Plus if it does drop out i have put a shortcut on the desktop so staff/students can quickly get printing again without having to logoff/logon again.