Requirement for centralizing Stamp location in PDF Viewer

[synovagroup]

Hi Folks,
We have a multi-user environment that requires a centralized location for stamps.
Is there any way to make stamps available to all users without having to create them on every single machine.
This is a major PITA.
Look forward to any comments or suggestions on how this can be accomplished.
Kindest regards,
Brian

[Stefan - PDF-XChange]

Hello Brian,

You can create the stamps on one machine and then distribute them to all users.
On the machine where you created the stamps navigate to
C:\Documents and Settings\<<login_name>>\Application Data\Tracker Software\PDF-XChange Viewer\2.0\Stamps\
And you will find the file with all the custom stamps you just created.
Now simply copy that file in the same folder for all users - and they will all have the full set.

Best,
Stefan

[synovagroup]

Hi Stefan,

That I can do , and I understood that from your FAQ. Try doing that for 100 user desktops. That's the PITA.
An option to store and reference these custom stamp files in a centralized network directory is what is required.
Is that being considered for your product ?

Brian

[John - Tracker Supp]

Hi,

Not the first time we have been asked this - but despite the obvious installation benefits there are significant potential and real drawbacks with such an approach...

1: In a busy network the potential for significant traffic increases and consequential performance issues is real - every time the application opens the stamps Will be accessed and reloaded - in a larger installation this could cause real traffic and performance issues.

2: If the user is adding a stamp from the application stamps folder stored on a network and for some reason the connection is lost, issues of file corruption and the loss of the ability to add stamps at such a time may also cause errors - leading to increased support for you (and us) as an admin. The only resolution being to restart the application and possibly lose any changes made if the file cannot be saved successfully etc etc

and this is just a brief list - if forced to we could think of many more reasons for possible problems. If support for such functionality is really desirable to a significant audience we would be prepared to investigate more fully in the future - but we really would have to be convinced as for now we see the initial benefit - but the ongoing potential for problems is a real concern and we remain to be convinced the long term benefit is worth the trouble ...

HTH