Papercut Minor Issues

[ITGURU]

We have had a Papercut MF install carried out on a working smooth running network with no link issues.

Since the install we have had 2 minor irritations.

 

Firstly every now and again when users login they don't get the PC-Client tray icon. Is it just a change of changing the login script from the pc-client to the cached version, log back on and it will work from the local version from then on?

 

Also we have a virtual printer queue (Follow-Me) that doesn't always map every time. I have tried a range of deployment ways , print management , Group Policy preferences, login script, but still every now and again I get a call from users saying they cannot see the printer.

 

As with both issues, a log off and log restores normal working.

 

Anyone else had this before and found a way to work around it. Papercut tell me it's not a papercut issue and only support the product and not the deployment of it. In my eyes that's half customer service! It's like saying here's a new software product, work out for yourself how to use it.

[Big_Ted]

Hi,

 

How are you deploying the client? and how are you setting it to auto start?

 

As for the queue not mapping the fact it is a virtual queue in papercut should have no impact on it being mapped. It is a normal print queue and in papercut you make it virtual. I would double check the event logs when it does not map. It does not sound like a papercut issue, a simple test would be to turn papercut off and see if you have the same issue. It could be a network or permissions issue. What client OS are you seeing the problem on? what OS are the queues on? can you (as a test) setup a queue on another server and map that to people and see if that always shows up? Do some of the suggestions here help:

Network printers disappear in Windows 7 - Microsoft Community

[ITGURU]

Hi,

 

How are you deploying the client? and how are you setting it to auto start?

 

As for the queue not mapping the fact it is a virtual queue in papercut should have no impact on it being mapped. It is a normal print queue and in papercut you make it virtual. I would double check the event logs when it does not map. It does not sound like a papercut issue, a simple test would be to turn papercut off and see if you have the same issue. It could be a network or permissions issue. What client OS are you seeing the problem on? what OS are the queues on? can you (as a test) setup a queue on another server and map that to people and see if that always shows up? Do some of the suggestions here help:

Network printers disappear in Windows 7 - Microsoft Community

 

In the GPO for the user accounts, I have a logon script entry which is pointing to \\papercutserver\client\pc-client.exe

If it was a permission issue then it wouldn't map at all, but when the user logs off and back on it does then pull in the printer.

All clients are Windows 7 x64 and the driver for all printers part of the virtual queue are the same and include both x86 and 64 bit drivers.

The PaperCut server is running windows server 2012 R2.

[Joanne]

I had papercut installed yesterday and in order to make the client auto start I had to set up group policy to auto start on logon. Instructions are here:

 

Scroll down to step 4 on the msi deployment bit User Client

 

You have to point it to C:\Program Files\Papercut MF\pc-client.exe

 

My issue is with deploying the client itself. For some reason my GPO for installing it is applying, but not installing the MSI. When I look in logs there are no trace of it! A gpresult tells me it is being applied however... bizarre

[Joanne]

Just reading the readme file... looks like the kid was DOIN' IT RONG yesterday...

 

ZERO-INSTALL METHOD

 

The client can simply be run directly from the PCClient share setup on the

server. Two executables provide this launch functionality:

pc-client.exe

pc-client-local-cache.exe

 

 

pc-client.exe will launch 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

startups will use the local copy and hence minimize 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). An

alternate cache can be specified with the "--cache" directive (see below).

Administrators should ensure that standard users have write access to the

system drive, or manually create the cache directory if required.

 

 

Typical methods used to start the client executable include:

 

*Logon Script*

 

Start the program by adding a line in the users' logon script:

 

cmd /c "start \\servername\PCClient\win\pc-client-local-cache.exe --silent"

 

 

*Group Policy*

 

Use the group policy template to define the pc-client-local-cache.exe as a

program to be run on Logon. This is done via a policy located under:

 

Computer Config->Administrative Templates->System->Logon->Run these

programs at user logon

 

Alternatively a line can be added to the user's logon script under:

 

User Configuration->Windows Settings->Scripts (Logon/Logoff)->Logon

 

to run the program as part of the logon process.

 

Batch File:

cmd /c "start \\servername\PCClient\win\pc-client-local-cache.exe --silent"

 

VBScript:

Set WshShell = WScript.CreateObject("WScript.Shell")

WshShell.Run "\\server_name\PCClient\win\pc-client-local-cache.exe --silent"

 

 

Note: The group policy option at:

 

User Configuration -> Administrative Templates -> System -> Scripts ->

Run logon scripts synchronously

 

should be set to 'Disabled' (the default). Enabling this option may

result in the client tool being terminated before or shortly after login.

==============================================================================

 

*All Users StartUp Folder*

 

On each workstation create a shortcut to

\\servername\PCClient\win\pc-client-local-cache.exe

in the "All Users" Startup folder. This folder is usually located at

C:\Documents and Settings\All Users\Start Menu\Programs\Startup. The program

will then run whenever a user logs into the workstation.

 

*Starting via the Windows Registry (Advanced)*

 

Use a logon script or otherwise to add a registry key to each workstation.

Create a key called "UIT" with a value of

"\\servername\PCClient\win\pc-client-local-cache.exe"

in the root

HKLM/Software/Microsoft/Windows/CurrentVersion/Run

 

Special Note for Windows XP SP2: Windows XP may prevent the running of remote

executables hosted on a server's share. If users receive a security warning,

add the server to the workstation's list of "Trusted sites" via Internet Options

in the control panel and reboot.

[mthomas08]

Slightly off topic but can someone provide a copy of the latest PapercutMF.

 

Put a long story short, our reseller who goes a little slow needs to send us the link for it.

 

We've got an urgent issue that will be fixed in v16. We got the license which he sent us but still waiting for the link.

[howartp]

Slightly off topic but can someone provide a copy of the latest PapercutMF.

Papercut > About > Support > Check for updates?

 

Peter

[Joanne]

I do. PM me and I'll share it on google drive.

[mthomas08]

Thank you

 

Sorted our issue and all status quo.