PDF Conversion - Local Admin Rights

[eavesw]

****o! I Have installed PrimoPDF Converter onto several pcs all of which the users are set up as Power Users. Upon performing a conversion from a Word document to a PDF, it complains with an error message 'Internal Adboe Reader Error'. However this works fine if I set all of the users to have local administrator rights, which I dont want to do. Is there any way around this? :confused:

Thanks for your help!!

[Philibert]

Even after installing PrimoPDF on a standalone Win XP Home PC I find that one must have Admin rights else one gets the Adobe error message. For this reason and the absence of any response to the mulitple requests regarding options 1 and 2 during the installation (see postings elsewhere in this forum) I am having to cast PrimoPDF aside. This I regret as I have used it for many months - but now must tighten permissions on my PC due to my grandson's need for access.

[MACscr]

I am finding this to be very disappointing as well. Its been complained about for over a year now, status?

[MACscr]

Anyone? This is pretty important as I am having to stall on my network migration until this issue is resolved.

[Chuqau]

I maintain desktops on a network where the users do not have local admin rights - not even power user rights - and the few people who have started using the software do not have this problem. This is just using the FreePrimoPDF.exe installer downloaded from the website, with the standard install options - nothing fancy.

[Deanb]

Not sure wether this is related, but we had issues running Primpdf when users werent local admins, after choosing print, nothing happened, the popup didnt come up. The fix was to remove the tick from "Run As User".
Run as user must try run the process as Sytem or something like that, and it cant unless the user is a local user.
You could also try and turn off the option to open the PDF when its created.

[philedmonds]

Not sure wether this is related, but we had issues running Primpdf when users werent local admins, after choosing print, nothing happened, the popup didnt come up. The fix was to remove the tick from "Run As User".
Run as user must try run the process as Sytem or something like that, and it cant unless the user is a local user.
You could also try and turn off the option to open the PDF when its created.


Was having exactly the same problems here - and it comes down to a common problem with many programs. Namely that they want to write files in 'their' folder in the 'Program Files' folder. Admin users can do this - normal 'users' do not have write or modify permissions in the 'Program Files' directory.

The fix is to give write/modify permissions to the PrimoPDF folder to 'users'. If you wanted to tighten security you could find out which files the software needs to write to and set permissions on individual files. If you are particularly concerned in this area I would at least not allow Users to modify the .exe files in the folder (as then any trojan/virus type nasty running with the current users rights won't be able to do anything bad to the executable.)

Maybe a request to the developers to write settings and temp files to the more 'correct' location somewhere in the users Profile directory is in order for the next version of the software. (It's not just small developers who are guilty of 'limited user' account unfriendliness - I could name some big names are equally guilty.)