What is Smart Software?
Smart Software seeks to simplify some of the nuances that come with packaging and deploying software to macOS devices. macOS devices require a multitude of end user permissions. Smart Software streamlines the process of creating the necessary permissions with just a few clicks.
How to Use Smart Software
Smart Software is most commonly used to deploy third-party applications to macOS devices via Addigy, but it can be leveraged to accomplish various tasks.
For a complete 'How To' guide on setting up a new Smart Software item and what each option is capable of, please refer to the following article: Creating Smart Software
Note: At this time, Smart Software is only compatible with macOS devices. For guidance on deploying software to iOS or iPadOS devices, see Configuring Apps & Books
Configuring Smart Software Items for Third-Party Applications
As an admin tasked with deploying a new application to your fleet of devices, your first order of business should always be to consult the software developer's documentation on deployment via a remote management solution. Many developers offer detailed, step-by-step guides on how to configure installation using any MDM solution. Instructions on deployment written for another MDM solution can typically be translated into Smart Software terms and configured via Addigy.
Adhering to developer documentation on installation via MDM will ensure the most seamless deployment process. Developer documentation should also be consulted to build corresponding MDM Profiles (Full Disk Access, System Extension, etc.) if you are hoping for a silent installation.
If documentation for remote management does not exist or is not sufficient, the following articles can be referenced for general instructions to build Smart Software items by file type:
- Creating Smart Software (for .pkg and .sh installation files)
- How-To: Create Custom/Smart Software items (.dmg files)
- How-To: Create Smart Software items (.app files)
Additionally, our knowledge base contains some Addigy-specific documentation for certain software our customers use most often:
- How To: Deploy SentinelOne via Addigy
- How to Install Sophos with Addigy
- Installing Webroot via Addigy
- Deploying Bitdefender using Addigy
- Deploying Adobe CC Applications using Addigy
- Deploying ESET with Smart Software via Addigy
- How To: Install LogMeIn via Smart Software
You can also always check out our Public Software Catalog to find prebuilt installers for popular applications: Public Software Managed by Addigy
Deploying Smart Software
Once a new Smart Software item is created, it can be deployed to devices using a few different methods:
1. GoLive
GoLive can be used if you'd like to deploy a Smart Software item as a one-off installation. This functionality is useful when testing a newly built software item before deploying it en masse.
Deploying Software to Individual Devices in GoLive
2. Policy
Deploy a Smart Software item to multiple devices by adding it to a policy (or policies). Regular policy deployments run roughly every 30 minutes.
Note: The installation of Smart Software items without a Condition for Install will only be attempted one time after being added to a policy, then will not be attempted again. The Deploy Now button in the Policy view page will force any Smart Software without a condition script to rerun its install script.
Adding a simple Condition for Install (for example, a condition to check if the application being installed already exists on the device) will allow reinstallation to be attempted when the Condition for Install is passed.
The output for a software item displayed in the Policy Deployment window will reflect the most recent attempt at installation via the policy. This output will not be updated unless the installation status of the most recent attempt changes.
In some cases, certain Smart Software items are not applicable to all devices in a policy. Some software developers provide installation files based on device architecture (most commonly, we see that separate installers must be used for Intel vs. Silicon devices). In these cases, we suggest leveraging Flex Policies to automate the process of deploying software to devices based on Device Facts: Flex Policies
Sometimes admins must restrict software installation to certain times of day to avoid disrupting end users. This can be accommodated by setting a software deployment schedule for your policy: Setting a Software Deployment Schedule
When updates are released and new versions of a Smart Software item must be created, they can easily be swapped with previous versions in policies as needed: Updating Smart Software, Public Software Library Titles, and Self Service Items in Policies
3. Self Service
Smart Software items can also be added to Self Service for end users to install on their own time.
Adding a Smart Software item to a policy's Self Service configuration does not install the application on devices, it simply makes it available to the end users so that they can install it themselves.
Note: Similarly to GoLive, Variables are not currently supported for deployment via Self Service.
Adding Software to the Self Service Catalog
Miscellaneous Use Cases for Smart Software
Although Smart Software is primarily used to remotely install applications on devices, it can be leveraged to accomplish other tasks, including but not limited to the deployment of:
- Fonts & Wallpapers: Managing Fonts and Desktop Wallpapers on macOS with Addigy
- Printers: How To: Configure and Deploy Printers via Smart Software (Supports AirPrint)
- Launch Daemons/Agents: Using Custom Software to create a LaunchDaemon or LaunchAgent