After remotely ssh'ing to a Mac, running ardkick as sudo will restart the ARDAgent. It is a shorthand for /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart -restart -agent because who wants to keep typing that out.
Why is this a package and not just a bash/zsh alias?
This was designed for a Mac lab. I'd rather not have to hand-touch an entire lab to add and alias, and this is easily distrubuted and installed via MDM (e.g. Munki). Additionally it makes it available to all admin users, again without touching .$SHELLrc. Oh, and I just wanted to 🤷♀️
If you want to build / sign yourself as opposed to using release packages. Admittedly these are mostly because I won't remember the commands later.
| Purpose | Command | Notes |
|---|---|---|
| Build Component Package | pkgbuild --root ./root --scripts ./scripts --identifier $IDENTIFIER (e.g. wtf.ashe.ardkick) --version $VERSION ../builds/ardkick_install.pkg |
Run from inside the package directory's bundle_raw folder. --sign "$MYDEVID" can be added to sign on creation, or productsign can be used after. |
| Build Component Uninstall Package | pkgbuild --nopayload --scripts ./scripts --identifier $IDENTIFIER (e.g. wtf.ashe.ardkick) --version $VERSION ../builds/ardkick_uninstall.pkg |
Run from inside the package directory's uninstall folder. --sign "$MYDEVID" can be added to sign on creation, or productsign can be used after. |
| Sign Packages/Products (after creation) | productsign --sign "Developer ID Installer: Johnny Appleseed (01JOAP11)" $PACKAGE_IN.pkg $PACKAGE_OUT.pkg |
Run from inside the package directory's builds folder (See package trees). Signing packages is best practices, but it does require an Apple Developer account. You don't have to, but you probably should. |