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 kDownload macOS printer driver]
- Navigate to Download Folder
- Open SmartClientMac.iso > Open SmartClientMac Volume >
- Notice here you only have 1 file. But actually there are 4. 3 are hidden.
- On your Keyboard us the show hidden files shortcut: Command+Shift+.(Period)
Getting Files in the Right Location
- You will now see 3 other files. We only need the SmartClientForMac.pkg and tenantcfg.plist files.
- Next, Go to Finder > Go > Go to Folder (Shift+Command+G)
- Enter 'private/tmp'
- Next create a new folder called 'uniflowclient'
- Which is now located in private/tmp/uniflowclient
- Drag the two files (SmartClientForMac.pkg and tenantcfg.plist) from the mounted SmartClientMac to the private/tmp/uniflowclient folder
- Close the SmartClientMac window.
Using Composer to Create the PKG
- Next Open Composer
- Drag the uniflowclient folder from finder into composer
- Click on uniflowclient under Sources, navigate private > temp > uniflowclient to confirm files are there
Next click the ⬇️ next to Sources
Right click on Scripts > Select Add Shell Script] > Select postinstall]
Next replace all text with the following:
#!/bin/sh
## postinstall
sudo installer -pkg /tmp/uniflowclient/SmartClientforMac.pkg -target /
exit 0 ## Success
exit 1 ## Failure
Now click wBuild 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!
This presentation is beautiful.
One more thing...
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.
/Applications/uniFLOW SmartClient.app/
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.
Did you actually get get the uninstall and reinstall working? I found that after it uninstalled for a upgrade the login window wouldnt come back up for users
Did you actually get get the uninstall and reinstall working? I found that after it uninstalled for a upgrade the login window wouldnt come back up for users
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
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.
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...
Incredible work. You saved me a TON of discovery on my own.
@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.
@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.
Have not heard anything about my issue with the smartclient not starting randomly.
I have not had that many new macs installed after I published this pkg into Jamf.
What exactly are you having trouble with now @Jorelwilkins12
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 (johnsmith@yourdomain.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
Have not heard anything about my issue with the smartclient not starting randomly.
I have not had that many new macs installed after I published this pkg into Jamf.
What exactly are you having trouble with now @Jorelwilkins12
Issue with it installing properly. It take multiple installs for it to run successfully.
Issue with it installing properly. It take multiple installs for it to run successfully.
Sorry, but that issue have I never had, always installing properly.
Have not heard anything about my issue with the smartclient not starting randomly.
I have not had that many new macs installed after I published this pkg into Jamf.
What exactly are you having trouble with now @Jorelwilkins12
Hi @jorrig, following NT-WARE this should be fixed in a new version of the Smartclient. So the steps would be:
- Generate a new macOS Smartclient from the uniFLOW console and download the PKG. This should be version 2023.3.
- Package the PKG again like described above.
- Upload the PKG to Jamf Pro.
- Uninstall the Smartclient like described in here.
- Create a new policy to install the new custom PKG.
You can also include an uninstall script in the policy for your new Smartclient. This prior to the install step. You can find the inspiration in /etc/smartclient/uninstall-smartclient.bash. You would have to check if the 'SmartClient' process is still running and if it is kill it with the 'killall SmartClient' command.
Have not elaborated this out myself yet. Is something for next week. Just back from JNUC :-)
Hi @jorrig, following NT-WARE this should be fixed in a new version of the Smartclient. So the steps would be:
- Generate a new macOS Smartclient from the uniFLOW console and download the PKG. This should be version 2023.3.
- Package the PKG again like described above.
- Upload the PKG to Jamf Pro.
- Uninstall the Smartclient like described in here.
- Create a new policy to install the new custom PKG.
You can also include an uninstall script in the policy for your new Smartclient. This prior to the install step. You can find the inspiration in /etc/smartclient/uninstall-smartclient.bash. You would have to check if the 'SmartClient' process is still running and if it is kill it with the 'killall SmartClient' command.
Have not elaborated this out myself yet. Is something for next week. Just back from JNUC :-)
Thanks for the info!
Leaving for some vacation, playing some golf in Spain, so I will try to do this in 2 weeks ;-)
If you get around to try this out, please keep me informed of the results.
Hi @jorrig, following NT-WARE this should be fixed in a new version of the Smartclient. So the steps would be:
- Generate a new macOS Smartclient from the uniFLOW console and download the PKG. This should be version 2023.3.
- Package the PKG again like described above.
- Upload the PKG to Jamf Pro.
- Uninstall the Smartclient like described in here.
- Create a new policy to install the new custom PKG.
You can also include an uninstall script in the policy for your new Smartclient. This prior to the install step. You can find the inspiration in /etc/smartclient/uninstall-smartclient.bash. You would have to check if the 'SmartClient' process is still running and if it is kill it with the 'killall SmartClient' command.
Have not elaborated this out myself yet. Is something for next week. Just back from JNUC :-)
For the uninstall part I just set the files & processes section to this and it worked.
You do not need to package the files from the .iso that you download from Uniflow (tested with Uniflow Online SmartClient; macOS 14.1.1; Jamf Pro 11.1. YMMV with on-prem Uniflow, but it should work the same way).
- Read the help article regarding the options for creating the installer. Pay close attention to "Login name substitution" and "Silent user registration".
- Download the iso and zip all of the files and place the .zip file on your distribution point.
- Create a policy and use the .zip file instead of a .pkg. Jamf Pro sees the package inside the .zip and installs it while respecting the .plist and other files in the .zip.
Seems no matter what method I try, works locally, but it fails to install via Jamf. Getting "Installation failed. The package could not be verified." The custom PKG was signed and when I tried it just as a zip files it also can't be verified. Which makes me think the issues is the PKG in the ISO from the uniflow server. Anyone run into this issue, have a fix for it?
Did you make changes to SmartClientForMac.pkg?
You may be able to override that error with the following script set to AFTER in the policy that you're pushing the .zip with:
#!/bin/bash
xattr -d com.apple.quarantine /Applications/uniFLOW\\ SmartClient.app
exit 0
Did you make changes to SmartClientForMac.pkg?
You may be able to override that error with the following script set to AFTER in the policy that you're pushing the .zip with:
#!/bin/bash
xattr -d com.apple.quarantine /Applications/uniFLOW\\ SmartClient.app
exit 0
Turn out to be a really dumb issue. The new upload had a space in the name and that was causing the issue. After I removed the space from the name, it worked. I have had spaces in names in the past, and they worked fine, but maybe something on the newer version of Jamf changed.
Turn out to be a really dumb issue. The new upload had a space in the name and that was causing the issue. After I removed the space from the name, it worked. I have had spaces in names in the past, and they worked fine, but maybe something on the newer version of Jamf changed.
Ok good. After I posted that, I realized that wouldn't help if the package won't install. Too bad you can't edit these responses.
Once the client software is installed, my client is reporting that they are getting errors related to the size of the print jobs. The biggest job was only ~100 pages.
"The print job exceeds the maximum allowed file size. Try reducing the print job size, e.g., by printing fewer pages, and then try again".
They had to print it in ten jobs, which is insane. I'm wondering if anyone else has ran into this? The only thing related to file size that I can find, is the hard 100 MB limit on emailed jobs. These jobs are initiated from the Mac SecurePrint queue that the macOS uniFLOW Client installs. One of the rejected jobs was 298 MB.
I migrated from uniFLOW on-prem. They only started seeing these errors in uniFLOW Online.
Hi! As I'm fairly new to packaging apps for MacOS, I'm struggling to accomplish repackaging the uniFLOW installer with the free tool "Packages" (lacking a license for Jamf Composer). I'd be very grateful if somebody could maybe give me some guidance on that!
