Buy Now Stamps

[KerriTeam]

I did a network deployment of the newest version of the Viewer which applied an .mst to include the license key. When I open Viewer it tells me that it is the Pro edition and it has the correct key in the registration information. However, we still have PDFs created that have the Free version promo stamps on them.

What can I do to clear this up?

[Will - Tracker Supp]

Hi KerriTeam,

Thanks for the post - could you please upload a sample PDF that displays the watermarks? Also, could you tell me whether the application is still placing watermarks when using PRO features, or are you looking to remove existing watermarks?

Cheers,

[KerriTeam]

The watermarks appear when cutting a page out of one .pdf and pasting it into a new one (in the uploaded case), and also when creating a new .pdf using the print driver.

I just want the watermarks to stop appearing when we save .pdfs - we can redo the documents once the issue has been resolved.

[Will - Tracker Supp]

Hi KerriTeam,

Thanks for that - could you please email support@pdf-xchange.com with you serial key, so that they can validate it there?

Please do NOT enter your key here, as we will be forced to block it.

Cheers,

[KerriTeam]

The new key is working thank you.

I do have concern over the key deployment however. As I was checking on some of the users I noticed that they were using the Pro version, but they had keys that were replaced long ago.

I distribute the key by transform file using Orca to create it. Is there some place I should put it in other than adding the key row in the "Property" section? I know the users are getting the update because the version changes, but they do not get an updated key. (I also changed up the USERNAME and ORGANIZATION properties to see if they would change and they did not.)

Perhaps it is an old location in the registry that should be removed because it conflicts?
Maybe the transform file is not the best method to deploy it via Active Directory?

[Paul - PDF-XChange]

HI KerriTeam,

a transform on the msi is a good way to deploy over AD. Can I ask you to send me the transform file (zip it to upload or email to support@pdf-xchange.com).

Which msi are you using (file name)? Just the Viewer? Is there a reason not to deploy the Editor? The Editor has now formally replaced the Viewer.

looknig forward to seeing your msm

[KerriTeam]

PXCViewer_x86.msi is the file I am using. I attached the Transform. We use the viewer (both x86 and 64bit) and the print driver

As to Editor, we have handed it to a few of our engineers to test run since they use more features than anyone else. The initial feedback was this:

Liked the simplification of the interface.
Could not find how to create markup pallets
Could not find how to import and export preferences via .dat file
Could not make custom toolbars or custom commands for the toolbars
Could not find command line interface to run Java scripts within Viewer

Granted, The answers to these concerns may be in a help file, but another complaint was that the offline help file did not seem to exist and the online help did not return results for these things.

[Paul - PDF-XChange]

HI KerriTeam,

thanks for providing that. When we first ran this it also appeared to fail, then we realised that we had used the wrong command line to use the transform. When we changed it to

Code: Select all

msiexec /i PXCViewer_x86.msi TRANSFORMS="PDFXChangex86.mst"

it worked. Can you check your install string to see that you used TRANSFORMS="PDFXChangex86.mst"?

Regards the Editor feedback,

Could not find how to create markup pallets
Could not find how to import and export preferences via .dat file
Could not make custom toolbars or custom commands for the toolbars

These were all added in the last build. It should be available if you use the current installer 3.0.307.1

Could not find command line interface to run Java scripts within Viewer

In both the Viewer and Editor this is toggled using CTRL+J or View --> Show --> Show JavaScript console.

I hope that helps.

[KerriTeam]

I do not use an install string to apply the transform to the .msi, I use the Modifications tab in the Active Directory GPM Editor to add the transform.

Maybe this is the problem - though it has worked in the past...

I do it this way so that I do not need to create new installation files for every update - just put the update in the correct folder and deploy using the ready transform file.

Another note - on new installations, it adds the correct user, organization, and key correctly. It does not always work for the updates though which is why I was wondering if the key was lingering other places.

[Paul - PDF-XChange]

Hi again KerriTeam,

I do not use an install string to apply the transform to the .msi, I use the Modifications tab in the Active Directory GPM Editor to add the transform.
Maybe this is the problem - though it has worked in the past...

I'm not sure what to say here, I can confirm that your transform is good and that it works with the msi, I don't know what we can do here to help you to determine why it's not being applied the way it used to.

Another note - on new installations, it adds the correct user, organization, and key correctly. It does not always work for the updates though which is why I was wondering if the key was lingering other places.

When the installer runs it does so per machine - not per user, this means it puts the values in HKLM and does not touch HKCU.

When a user logs in and starts the software, it will look for keys in HKCU, if it does not find them it will copy the one from HKLM. If there is however a key already in there then the new key will not be copied.

This is by design. The simplest solution is to use a runonce logon script after you've pushed your update and in this script manually update or remove the serial key in the HKCU registry. That way when they start the app it will either already have the updated values or none in which case it will pull it from HKLM.

Does that help?

[KerriTeam]

When a user logs in and starts the software, it will look for keys in HKCU, if it does not find them it will copy the one from HKLM. If there is however a key already in there then the new key will not be copied.

This is exactly what I wanted to know thank you. I will try the suggested login script for updating the key.

Also, I have sent the testing engineers the newest version of Editor. Maybe they will be happier with the updates.

Thank you for you help.

[Will - Tracker Supp]