The install error is not wrong, you need to be speaking with Epson. What you are needing is a deployable or manageable installer, and if you did not get an enterprise focused printer they may not offer a manageable installer. Depending on if their dmg based installer has CLI options, you could deploy the DMG, mount it, and run through the install with CLI but again they have to provide binaries for this to be possible.
The other options is to just grab the drivers from /Library/Printers/ and try to package and deploy them. You can also use composer to take a snapshot of the disk and run the Epson installer to see what files it drops and try to package all of those. Using Snapshots is not common anymore, but we used to lean on it pretty hard back in the day.
I looked at this for a good while last night and tend to agree with AJ; I came up with a few things, but nothing that I quite think would work, That said I'll be watching this thread with interest.
It extracts all the .pkg in a folder in /tmp named sc-p900 when you run the "Epson Installer.app". Upload those pkg to Jamf.
It extracts all the .pkg in a folder in /tmp named sc-p900 when you run the "Epson Installer.app". Upload those pkg to Jamf.
Thanks @YanW !!! Not sure how that got missed when I was snapshotting from Composer. Perhaps I didn't dig deep enough into the directory tree, or the files were deleted by the time I completed the snapshot. Will monitor that folder on a re-install.
Jamf Nation comes through again!!! Will mark as a solution after testing.
The install error is not wrong, you need to be speaking with Epson. What you are needing is a deployable or manageable installer, and if you did not get an enterprise focused printer they may not offer a manageable installer. Depending on if their dmg based installer has CLI options, you could deploy the DMG, mount it, and run through the install with CLI but again they have to provide binaries for this to be possible.
The other options is to just grab the drivers from /Library/Printers/ and try to package and deploy them. You can also use composer to take a snapshot of the disk and run the Epson installer to see what files it drops and try to package all of those. Using Snapshots is not common anymore, but we used to lean on it pretty hard back in the day.
Appreciate the reply @AJPinto !
I did do a full snapshot, as well as the fsevents based snapshot in Composer to build my package that failed to grab everything at deployment. I remember the days where this was common to do as well (been using Jamf since version 6 (2005) ) and preferred not to do it back then thanks to vendors non-compliant installers. It had a lot of components from /Library/Printers in there, so I was hoping it would work. Hope we are not going back in that direction...
My educated guess, without spending hours of wasted time troubleshooting, is that because I'm installing multiple Epson printer driver packages onto the same computer, something may be overwriting or breaking when different versions of the driver are installed using my snapshot package along with Epson's packages for the other models at the same time. I'm sure I could debug it, or capture all the printer drivers (3800, 3880, P800, P900) into one snapshot package that probably compensates for that variable, but would prefer not to do that. It looks like @YanW was able to provide me the guidance below that Epson support could not.
Thanks @YanW !!! Not sure how that got missed when I was snapshotting from Composer. Perhaps I didn't dig deep enough into the directory tree, or the files were deleted by the time I completed the snapshot. Will monitor that folder on a re-install.
Jamf Nation comes through again!!! Will mark as a solution after testing.
Worked perfectly. Thanks @YanW!
