I was wondering if anyone has ever run into an issue like this. We just finished installing Uniflow on Server 2016. All the printer we have are up to date on drivers. The secure printer is using "uniFlow Universal PxlL Driver". A couple of night ago I ran the windows update on the server to install the security patches. Everything was working fine on the server once it came up.
2 days later when users tried to print to secure printer they were getting a message "Driver need to update". Since we are using GPO to push out all printers for workstation, not users profile. when it tried to install the update it would fail every single time. Some workstation was able to still print but other users could not.
Canon Uniflow Driver Download
Download Zip š„ https://tinurll.com/2yGBeU š„
I checked everything on the server. The only way I could figure it out was to delete the printer and create it all over again. I then had to run gpupdate on the workstation to remove the printer, and then reinstall the printer again. Once that was done the printer started to work.
I see the same type of problem with Windows server 2019 and Microsoft Security patches. I loaded the Nov security patch and basiclly all my users where prompted to download updated driver. I reverted back to the snap befor the pathc and every thing is back to normal. My uniflow is setup with helper queue
Need some help with understanding how the printing works on the macos.
Previously I always have set up the printers in our jamf Pro Server and it works all fine. We need only the standard printing(keeping it simple).
Now I have to set up a new canon Uniflow printer available in every office with different models. How do I get the printer driver, which can be different for each printer?
The Printers in our company are configured on a win print server and the driver used on windows devices is: Canon Generic Plus PCL6. How do I get the driver for the printer?
I can access the smb share where the printers are.
While configuring the printer, I couldn't figure one which ppd file to choose from the list. So I chose the Generic.ppd.
Again the question, which PPD file shoud be chosen for the various printer?
I have been digging for Information on how the printing works on macos. really confusing for something very simple.
Can someone show me the right path for this?
ThanksĀ
Best regards
Mehdi
You can get in to the weeds with protocols (LPD, SMB, ext), just use whatever the vendor recommends. Odds are with it being a Windows Print Server it will be SMB. MacOS prefers LPD but that may need extra configuration on the server, and macOS will usually work with SMB.
Keep printer nightmare in the back of your mind with this. A LOT has changed in printing encryption and authentication in the past year. Depending on the configuration of your Print Server and what version of macOS you are using it may flat out just not work. I can write a book just on this and its workarounds, I'll save that for if you ask for it.
Start with the driver. Reach out to the vendor to see if they even support their printers or print servers on macOS. If they dont support macOS, you will be finished before you even start.
If you are getting the authentication pop that means the handshake with the printer (or print server) is working and its asking who you are. That is a good thing. Honestly the steps where you are at is really your print teams problem. The Job left the Macs Printer queue, its up to the printer team to figure out if the Job made it to the printer (if it left the Macs printer queue it made it to the printer). The can check the printer queue for jobs with your ID (since you authenticated) or jobs that arrived around the time you printed, I'd let them figure out how they want to find the job. I have seen jobs come through with the SVC Account that mapped printers, that is a setting wrong on the print server if they see this.
The next part is if the drivers actually worked. The printer could still not print correctly if the driver you used is not using the correct "language" as the printer. If your job printed right, I'd just leave it. If it not print correctly your printer people need to source a driver to give you. Push sourcing the driver off on the printer team. If there are no drivers for macOS it is on the printer team to say that printing is not supported on macOS and explain why to the higher ups. The Printer team should also be responsible for finding a printing solution for Macs.
Once you have logs you can move on from there. This is an example of what a successful print access_log would look like. If you get something like this, you are done. The job is leaving the Macs printer queue. What the job looks like on the other side is your Print teams problem. Focus on the Job leaving the Mac's printer queue.
A quick search on Canon's website indicates that the Uniflow printer doesn't have any macOS driver. Sometimes these drivers are provided by Apple but not always. The only way you could possibly do this is using a Generic driver, but you will get no features. Just a simple point-and-click black and white laser printer that will only really be good for printing basic documents. No duplex, choosing a tray, cover pages, security, etc.
In macOS, the main printing protocol for printing in an office environment is LPR. PPDs most of the time are installed through a manufacturer's installation package but also can be auto-detected and downloaded from Apple when creating a queue (direct-to-printer only).
In the scenario you described, you can either send LPR jobs directly to the printer, or through the print server. In order to go through a Windows Print Server, your sysadmin needs to actually make sure it's enabled/installed as it's an optional part of Windows Server.
Once Windows Server is configured for LPR, you install the print driver on the Mac. set up a queue on macOS using the DNS name of the print server as the printer name and the printer share name as the queue. Then, you will select the appropriate PPD and set up your custom settings, if applicable.
To push out in your environment, use Jamf Admin to capture the queue, and push out the manufacturer's installation package and the queue either through Jamf Remote or a policy.
Hi AJPinto
Thanks alot for the clarification.
I have added the printer on the jamf server using the smb:
Printer Setting are kept simple:
Cupsname: name of the printer Uniflow
Model: Blank (No Model for the canon Uniflow)
Device URL: SMB path
User generic PPD is checked as true.
I have contacted the printing department for the printer driver. As always, they know nothing about mac but they have contact the ventor for the driver, if the printer is supported for the macOS.
Strange enough, I had a Model Name of the old printer and installed the driver with the printer.
when I test to print something, it ask me to authenticate and the authencation is also successfull.
The Document dispears from the queue and sent to printer.Ā
Look likes it worked. I dont have any printer near me to check, if the document gets printed. That makes the troubleshooting more defficult and going to try it with user.
Hi AJPinto
Many many thanks for your help.
I did a clean reset and enrollment on a device and after that, the printer setting looks good. I will check the setting with the printing team and lets see what they have to say about this.
I am installing our old canon driver RN and I hope they can get me a new driver(supported on macOS) for the printing system. 152ee80cbc
popcorn time ios download no jailbreak
the secret life of unborn child book pdf download