You would always just stop it from reporting.
1 of 1 people found this helpful
Yes, Reader X still does it. No, I haven't found a workaround. Note that it happens with FireFox also, in our case when printing to a TCP/IP printer port the file name listed is the name of the printer port (IP_aaa.bbb.ccc.ddd).
you could ....However this would stop all reporting for the rule correct? I do not know of a way to remove the reporting on just this specific action that is triggering the rule alert....
This said - we do a lot of PDF Printing & I am inclined to remove the Alert Reporting for this specific rule.
I believe you can also add the calling process name to the VSE access protection common standard protection exception list. Although, that's imperfect (not checking the hash on the calling process) it's not too bad. We switched to HIPS for this detection since the exception rules are more granular.
Adobe released an article the same year ...
In a Terminal Server or Citrix environment it is not possible to restart the machine, as there may be other users logged on. Therefore you may use one of the following workaround files.
There are 2 methods used in Acrobat/Reader to create these temp files for the fonts. In the first acroct.ini file we disable one of these methods, and this has brought positive results in most cases. In the second acroct.ini file we disable both methods, so that no temp files for the fonts are generated anymore, and therefore cannot be locked.
1. close Adobe Reader/Acrobat
On Terminal Server this should then install the .ini file in each user profile under C:\Documents and Settings\<user>\Windows.
Please note that using these .ini files will reduce the quality of the printed output, as the printed fonts can no longer render exactly as shown on screen. Therefore it is more desirable to use the first acroct.ini (diables only one method) if it solves the issue, rather than the second acroct.ini (disables both methods). You should verify the printed output using these files and decide which one works best for you.
Following our testing we have discovered that the issue does not occur in Windows 7, or Windows 2008 Server.
It seems that the updated versions of Windows provide a solution to this issue. We would therefore recommend updating your OS if possible.