Hi everyone, I. HATE. PRINTERS. That being said, we have to work with them.
and... Canon does not make it easy.
Here is what I was able to find out from several places online, in order to get this "installer" to actually work. So let's jump on to our Macs and get this over with.
Downloading the "Installer"
1. Log into your Uniflow Online (web)
2. Start Printing (Side Bar)
3. Install Printer Driver > Click [Download macOS printer driver]
Getting Files in the Right Location
Using Composer to Create the PKG
Next click the :down_arrow: next to Sources
Right click on Scripts > Select [Add Shell Script] > Select [postinstall]
Next replace all text with the following:
sudo installer -pkg /tmp/uniflowclient/SmartClientforMac.pkg -target /
exit 0 ## Success
exit 1 ## Failure
Now click [Build as PKG] in the composer toolbar. Save it to your Mac.
Boom. Chef's Kiss, You're PKG is ready to take out of the oven.
Now you can upload it to Jamf Pro, then put into a Policy to push out to your Macs.
Hope this helps you out!
You might want to add the Uniflow Client to the employee's startup items via a Config Profile.
1. Click on Computers
2. Click on Configuration Profiles > New > Create a Name for it, and Scope.
3. Click Login Items
4. Click [+ Add ] Items, then add the path to the App. Make sure to put the "/" at the end other wise it will not work.
5. Click Save.
@andymason great guide, just tried it out, works like a charm 😀.
I got an issue that appears randomly from time to time with the uniFLOW Smart Client not starting at our Macs, it happens as I said, randomly among our 60 Macs here at work.
It does not help adding it to Login Items, have you or anyone else reading this seen it before?
Mostly it just works after starting the app manually, but sometimes I have to run the uninstall script and reinstall it afterwards.
I have spoken to NT-Ware that says it is a developer issue and no solution yet, I have to wait for the developers to get this issue corrected.
Have not had any issues with uninstall script and the installation after.
I have a policy published in Self Service for running the uninstall script, then, since I have not had this solution in place, I manually logged into my uniFLOW tenant, downloaded the iso and manually installed it once again, always working for me.
I previously done it the same way as above (policy to install) and i found it sometimes opened the app and somtimes didnt. The results were inconsistant on our machines. All the files installed correctly it just looks like the install scripts randomly didnt work correctly, you could uninstall and reinstall the ap pwithout sucess, however after a OS upgrade the software would reinstall / work on some devices
Well, my biggest issue is with the app not starting randomly, making the user frustrated when the arrive at the printer just to find the Secure Print queue empty, making them walk back to the computer, start uniFLOW Smart Client manually and then heading back to the printer. 9 out of 10 times the app starts as expected after manually starting it from Finder.
We have also have this issue randomly at certain location. I believe this is related to another issue we have where the uniFLOW Smartclient, does not get connected to the cloud tenant randomly. According to NT-ware this has something to do with the below setting in the configuration of the uniFLOW Smartclient. Unchecking this option should 'fix' the issue. Only... the option in not available for Smartclient on macOS. NT-ware says they will pick this up with the highest priority...
@jorrig Did you find the solution to the issue? I currently going thru the same issue that you were going thru with the install. But one differences is that when I go to the pkg after the installed "completed" to rerun the client, it would take multiple times. The only real solution I found that worked was doing the uninstall and reinstall but there be a host of different problem along the way. Like having to reset the printing setting to get the printer to map right on a machine or two.
Any thoughts would be appreciated.
Hi @jorrig, following NT-WARE this should be fixed in a new version of the Smartclient. So the steps would be:
Have not elaborated this out myself yet. Is something for next week. Just back from JNUC :-)
Wondering about syncing the account name with uniflow on the computer to our azure logins, since it isnt matching.
IE the mac installer looks at the account name (johnsmith) where as the provisioning in uniflow only looks at the login name (email@example.com). Not finding a way to link the two without having the end user sign into uniflow separately. I was really hoping to save that extra login.
If the names match then any new print jobs get set right up in their queue