12/24/2022 0 Comments Installpkg allowuntrusted![]() ![]() Hopefully you can use one of these two programs to do what you are after. 3 answers Top answer: Short Answer: yes.Long Answer: Yes, buta full answer to this question includes a technical. It is a bit more set up and work than Remote Desktop - but has a lot more options as well. pkg file that needs to be installed on multiple computers in my LAN, I highlight the computers I want it installed on, and tell Remote Desktop to install it. I have not used it myself, but have a lot of respect for the people coding it and using it in real life. To manage software installs (and in many cases removals) on OS X Of packages and package metadata, can be used by OS X administrators "a set of tools that, used together with a webserver-based repository If the $80 is a sticking point - you could look at munki, which is It is $80 for a license with unlimited clients. It does much more than this, but it WILL do these remote installs for you. pkg file that needs to be installed on multiple computers in my LAN, I highlight the computers I want it installed on, and tell Remote Desktop to install it. I use it as you are describing all of the time - I have a. I would recommend considering it for what you are trying to do. You mention that you don't have Apple's Remote Desktop. ![]() I think you might be dancing very close to your own answer. Installation instructions are included at Github, so I won't repeat them here. I have been meaning to do something like this for a long time, and so I finally put it together. mpkg files that are added to that folder, and then move it aside afterwards. You could, for example, make a folder such as ~/Action/AutoInstallPKG/ and tell launchd to install any. Last but not least: Automate "how?"Īs far as how you want to automate the installation, that depends on more specifics of what you are trying to do. I wrote pkginstall.sh to do some nice things like log the process, as well as tell you whether or not you are supposed to reboot after installing the package. Although I am at a loss to think of exactly what they would do, it's a trade-off of security versus convenience. However, if this is a shared Mac, then other people who are in the 'admin' group will be able to run /usr/sbin/installer without being prompted for their password.Īlso, obviously if someone gets into your 'admin' account, they too could, theoretically, cause mischief with /usr/sbin/installer. If you are the only person who uses your Mac, adding the above line to /etc/sudoers is not a big deal. See man visudo for instructions on editing that file. To do that, you can add this line to your /etc/sudoers file: %admin ALL=NOPASSWD: /usr/sbin/installer If you want to automate this, you need to tell your Mac not to require your sudo password when running the installer. Now, the problem is that sudo is going to ask you for your administrator password when you try to run installer. You may also need to specify where you want it installed, using -target / (I'm not 100% certain this is required, but it's a good idea): sudo installer -allowUntrusted -verboseR -pkg "/path/to/pkg/foo.mpkg" -target / If the installer isn't 'signed' properly, you'll need to add -allowUntrusted sudo installer -allowUntrusted -verboseR -pkg "/path/to/pkg/foo.mpkg" mpkg using this syntax: sudo installer -verboseR -pkg "/path/to/pkg/foo.mpkg" Long Answer: Yes, but…a full answer to this question includes a technical answer and a practical concern. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |