Common PDF template repository

[mjongens]

I work for an org with approx 120 employees. We are looking to create a common PDF template folder that everyone has read only access to. Is there a method whereby we can automate inserting that folder location via registry or group policy against all users with PDF Xchange license? I did look into "Add a Place" in the File -> Open menu and navigated to the common folder on our server. This saves a bookmark which effectively does the job. However every user would need to do this and from a maintenance perspective, if the folder were to change etc, it would be preferable to establish and maintain the folder location from admin side against all users. Is there a simple way this can be done? thanks

[Paul - Tracker Supp]

Hi mjongens,

while we do not have a tool specifically for this, the settings are stored in the Windows registry and it is relatively easy to pull the associated keys by exporting keys for the Editor before and after using the GUI to Add a Place.

Code: Select all

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\SOFTWARE\Tracker Software\PDFXEditor\3.0\Settings\Places\999999]
"t.FS"="default"
"t.ID"="839b7e12-d081-4d9b-9a5bc95f7201bcc5"
"t.Url"="\\\\fileserver\\data\\files\\Temp"

Maps a temp folder from a file server SMB share. Some things to note;

• t.ID can be the same for all users.
• the key has a numeric value. I used 999999 to ensure it does not conflict with any existing "Places" the users may have added themselves. Places added start with 000000 and increment by one for each new place.
• it doesn't matter how you push the reg key, Group Policy, sneakernet, as long as it's in the registry when the Editor starts it should "see" the place.

I hope that helps.

[IT Guy]

I've tried the above method, but over time it results in the user have the same repository repeated over and over:

image.png (12.09 KiB) Viewed 138 times

It seems that once the reg key is in place and called, like the example here "99999", when the application opens or closes that key is renamed to the next number available:

Before running:

image(1).png (2.17 KiB) Viewed 138 times

After closing:

image(2).png (2.13 KiB) Viewed 138 times

Result:

image(3).png (4.82 KiB) Viewed 138 times

Is this expected behaviour? This makes deploying this key via group policy problematic.

[Paul - Tracker Supp]

Hi, IT Guy

I spoke top the development team about this and the cause has been identified and fixed. Thanks for brining it to our attention.

In the next release we will change how we handle the array that stores the "Places" and it will not do this anymore. As long as you stick with the current set up, the next build on first start will remove all elements with the same ID excepting the last one and you should not see repeats again in future.

One caveat that has me saying do not change your reg keys, this is what the dev said about this:

For sure that fix will work only when his reg file uses the same place-ID each time when launched.

So I expect this to actually "clean itself up" after you update to 10.1.1.381 which at this juncture looks like being ready some time next week.

I hope that helps. I am keen to hear how this goes when the time comes.

Kind regards,
Paul - Tracker Supp

[IT Guy]

Great news, thanks for the super-quick resolution.

[TrackerSupp-Daniel]