Deploying Papercut

[protocol]

How does everyone deploy Papercut across their network? After Papercut was installed on the network but not configured I've got Papercut set up how I want but I want to deploy the client to all computers on the network so prints can be charged to departments and staff and students can check their remaining balance etc. However I'm having trouble getting the client installer to install.

 

Following their instructions I've created a GPO with a user start up logon .bat file with the following in it: (server name removed)

 

cmd /c "start \\server\PCClient\win\pc-client-local-cache.exe --silent --cache "C:\Program Files\PCClient""

 

However on the test machine the GPO is applied to, even if I log in as a domain admin neither the folder is created nor is the software installed. The only way I can get it to work is to run the .bat file myself as an administrator.

 

Any ideas? I'd also like a way to have a backup solution for if the script fails to run. Like a desktop shortcut or an entry on start menu but my scripting skills are a bit limited. It's a Windows 7 domain if that matters.

 

Thanks for any help.

[Steve21]

No idea what that cache exe is :s But ours is one of two ways depending how we feel

 

Run pc-client.exe direct, or copy it locally to the machines and run it locally as it doesn't need installing if you copy the config file with it

 

Steve

[newpersn]

No idea what that cache exe is :s But ours is one of two ways depending how we feel

 

Run pc-client.exe direct, or copy it locally to the machines and run it locally as it doesn't need installing if you copy the config file with it

 

Steve

 

We use the cache mode via the gpo. If the computer looses network connection it won't crash out. It will wait for network connection to reconnect.

[Dos_Box]

Moving to Enterprise Software forum.

[Steve21]

We use the cache mode via the gpo. If the computer looses network connection it won't crash out. It will wait for network connection to reconnect.

 

Ah that's pretty cool So what's the downside of using it? As in why wouldn't they make it default or just due to needing to create that folder locally?

 

Steve

[newpersn]

Ah that's pretty cool So what's the downside of using it? As in why wouldn't they make it default or just due to needing to create that folder locally?

 

Steve

 

No idea. Just swapped to using that when I recreated our gpo.

[protocol]

No idea what that cache exe is :s But ours is one of two ways depending how we feel

 

Run pc-client.exe direct, or copy it locally to the machines and run it locally as it doesn't need installing if you copy the config file with it

 

Steve

 

Does that not mean users have to run it manually themselves or am I misunderstanding? (Which is quite possible)

 

pc-client.exe launches the client directly off the network share. The "local-cache" version (pc-client-local-cache.exe), is a smarter version that first copies itself and associated files to the local drive and launches itself from there. The local-cache version has the advantage that any future start ups use the local copy, which minimizes network traffic. The cache is self-managing and kept up-to-date ensuring that any new versions of the client are automatically and transparently copied down to the client.

 

Using pc-client-local-cache.exe is recommended on large networks. It does, however, require a globally writable cache directory. By default, the cache is created in a directory on the system drive (normally C:\Cache). You can specify an alternate cache with the --cache command-line switch. Administrators should ensure that standard users have write access to the system drive, or manually create the cache directory if required.

 

Even if I try to deploy the pc-client.exe via batch file it doesn't run on login. The batch file itself works if I run it as admin, I just can't get it to run.

 

@newpersn do you mind explaining further how you done it? You way sounds like how I want it set up here.

 

Off topic but how is the tag system supposed to work? I always have to get the URL of the user and then link to it and not even sure it notifies of the tag.

[Steve21]

Registry key to make it run But yes it could be launched manually via shortcut too as backup/if someone closes it (or GPO or what not)

 

Steve

[gh5000]

How about deploying the MSI by GPO/SCCM etc? Does the manual not recommend that way?

[PotNoodleTech]

Just had papercut installed.

 

I'm running the pc-client.exe file directly off the papercut server through a GPO. The GPO that allocates the printer "Follow Me" also runs a batch file in the background to run \\servername\PCClient\win\pc-client.exe. This seems to work great, no client install needed, and if papercut server is updated and a new client on the server all workstations will immediately get the new client the next time a user logs on.

[Edu-IT]

Just had papercut installed.

 

I'm running the pc-client.exe file directly off the papercut server through a GPO. The GPO that allocates the printer "Follow Me" also runs a batch file in the background to run \\servername\PCClient\win\pc-client.exe. This seems to work great, no client install needed, and if papercut server is updated and a new client on the server all workstations will immediately get the new client the next time a user logs on.

Does the client reconnect if connectivity is lost? This used to be an issue.

[lostsoul]

We also run the client directly off the network via GPO, been doing it for years and never had an issue.

[aarongulley]

Use GPO to install the software and add it to startup using gpo?

[ITGURU]

We run papercut - in the logon script I just pointed to the .exe file and it runs when the user logs in automatically.

However, several months ago I just change the location to the cached version and it copies the program to the local C:\ drive and it runs the app from there avoiding the need to pull over the network each time.

 

There shouldn't be any need to physically deploy/install the software on clients, as the cache version works find on our laptops.

[Sir]

Same as ITGURU here. No problems with the logon script. Or just add it to startup folder on machines pointing to the print server paper cut pc client share.