This refers to Premier Support case no. 117030115391796.
As Premier Support could not give us a solution they recommended to post the idea here: https://connect.microsoft.com/site1321/feedback/details/3123004/network-printer-unable-to-use-with-secured-printer
After discussing it with Microsoft D365FO CAT team they asked me to insert my comment into this forum as well - please check Connect to find other customers facing the exact same problem as we do (and I assume that number of customers having this problem will increase in near future).
We are trying to print documents e.g. reports directly from Dynamics 365 for Operations. The routing agent within Dynamics 365 for Operations is changing the owner of the printing document to the service account name of the sever that the printing agent is installed on making it impossible to use with a secure printing solution where a document within a centralized print queue has to be identifiable per user. The user identifies himself with a badge at the printer and can select his document to be printed out. This applies to >4'000 users across the country.
We tried to install routing agent as a service and as an application, plus run service under a dedicated account but what we know by now from Microsoft is, that we can not configure it to work as expected within our environment.
Please advise if Microsoft is planning to enhance the bulk printing solution for D365FO to be capable to work with a secure printing solution.
Comments
Is there an update for this 'Under Review' status?
Category: Reporting and Analytics
I'm assuming this has not been resolved yet by the way we are having this issue. Our print controller is Papercut
Category: Reporting and Analytics
We are today using an output management systemen (ISV) called Lasernet to handle document and printing.
The solution is installed on an on-prem server and gets messages from D365 to print documents.
There is a small Java code added to Lasernet that inserts the D365 userid into the printjob, before it is sent to our FollowMe printer.
And in FollowMe admin, we register the D365 userId as an alias on a user, and that way we get the Follow Me function to work.
If we would remove this Lasernet solution (it's in the plan to do this) and replace it with DRA, we would have problem with our FollowMe solution. So I hope for a solution from MS
Category: Reporting and Analytics
Hi,
+1 for me too.
I'm facing the similar issue and same answer from Microsoft support, my client is using PaperCut.
How did you solved it ?
Sébastien
Category: Reporting and Analytics
This is something we've been experiencing trying to figure out implementation. How is this not part of core functionality?
Check printers have been secure for decades now, environments that need to comply with HIPAA are going to require some user authentication for printing records. This should be addressed quickly. Given this ticket has been open since 2017, I'm assuming MS isn't prioritizing this in any way.
Category: Reporting and Analytics
We have run into this issue multiple times, and it has left our clients frustrated every time.
The other issue we would be able to resolve with the user's id being included as the print user, would be the ability to restrict access to certain printers; i.e. a cheque printer where there should be limited access.
Every auditor has flagged this as a concern.
Category: Reporting and Analytics
+1 for this request.
DRA is not applicable with Secured Printing solutions.
Category: Reporting and Analytics
Bump. Pretty much EVERY customer we're deploying D365 for Finance and Operations to is using Secure Printing in some form or other, so would be good to know if support is on the roadmap or not.
Category: Reporting and Analytics
Just to clarify, this is not relevant just for batch/bulk printing. The DRA needs to be able to bring the user's credentials on any print job to the DRA and pass it along to the printer/print server. There is no downside to this for anyone who does not need this feature, but a huge/important upside to those who do (like us).
Category: Reporting and Analytics