Hi all
Has anybody had an issue printing with the new TaskAlfa range in confidential print mode with Word on windows 10. I have noticed on a few occasions when the driver is set to confidential print and to prompt the user for a pin the pin does not travel to the machine. When you are at the machine and input the correct pin it gives an authentication error. What I have found is that the pin is changed from what the user inputted at the pc to 0000 at the machine. If I do a test print in confidential mode it works as it should, the pin at the pc travels to the printer and it releases the job once it is inputted.
On the occasions I have noticed this the Print drivers were loaded on the print server and pulled down to the local users. I have downloaded the latest driver and installed it locally on a user and it seemed to work but I haven't had a chance to investigate it more and find out was the problem fixed by the latest driver or the fact it was loaded locally on the users pc as the customer closed for a summer break. Has anybody seen this problem and found a fix for it.
Thanks.
Has anybody had an issue printing with the new TaskAlfa range in confidential print mode with Word on windows 10. I have noticed on a few occasions when the driver is set to confidential print and to prompt the user for a pin the pin does not travel to the machine. When you are at the machine and input the correct pin it gives an authentication error. What I have found is that the pin is changed from what the user inputted at the pc to 0000 at the machine. If I do a test print in confidential mode it works as it should, the pin at the pc travels to the printer and it releases the job once it is inputted.
On the occasions I have noticed this the Print drivers were loaded on the print server and pulled down to the local users. I have downloaded the latest driver and installed it locally on a user and it seemed to work but I haven't had a chance to investigate it more and find out was the problem fixed by the latest driver or the fact it was loaded locally on the users pc as the customer closed for a summer break. Has anybody seen this problem and found a fix for it.
Thanks.