it is PKG on MacOS, different binaries are generated by this InstallBuilder installer.
2 Likes
Iām not sure I follow that logicā¦Theyāre already two different installers (EXE & DMG currently), might as well use the MSI installer on the Windows side as that offers the most flexibility in terms of deployment options and potentially consolidate to a single installer for all the modes Edge Agent offers.
1 Like
it is one installer product that is building installer for different OS.
Problem with single installer is that for services we specify the necessity to run in admin mode from the beginning. It is done in the manifest and is not conditional. For the local edge agent I need to run it in non-elevated mode too.
But I am still curios what is so flexible in MSI that you donāt see here.
1 Like
Ah, ok. Youāre referring to InstallBuilder being used to create both the Mac and Windows install packages for each OS. Thatās a very common approach. Unfortunately InstallBuilder doesnāt support MSI output 
I just found that in recent years a well packaged MSI file tends to be easier to work with when it comes to deploying and maintaining apps on Windows 10/11. Thereās of course a place for each type of install package type but, generally speaking, an MSI offers more flexible deployment options and has broad support across vendors that offer application deployment tools, like Intune, SCCM, PDQ and others. Iād bet if we took a survey today, most Epicor customers (at least their IT) would say they would prefer an MSI over an EXE.
2 Likes
well, you can create an idea and find out 
MSI is always easier.
1 Like
It was #6. A reboot and waiting ten minutes pulled all printers and it worked fine. Clarifying notes: we are kinetic browser only, I used LOCAL INSTALLATION, and our printers are managed on Print Servers and permissioned via GPO.
I will have to revisit a lot of this threadās comments later when I try to do a deployment to all machineās via our RMM. Right now, I just need to get it to work for one small department.
1 Like
If you are already using print servers we setup our Network EA which are now becoming more reliableā¦ some hilarious issue such as when it boots if there is a network issue it will not wait and attempt to re-connect later 
(1.2.644)
limitations to this are you miss a lot of printer specific functionality, say each user wants to output to their own output tray.
Beats issues where sysmon crashās and staff stop printing without noticing.
Iām using Atera as my RMM. It has the ability to run almost any kind of script remotely and when it does, it automatically runs elevated so no need to worry about Run As Admin issues. I ended up having two scripts. The first installs & configures the EA in Local Mode. The second script runs just the first time to start the EA. Thatās pretty much it. Weāre also just browser only so thankfully no need to worry about maintaining legacy Kinetic clients.