Video: Software Catalog & Policies Transcripts
Transcript
Now that we have covered deployment to a single device, let’s look into how to add additional software and configurations to Addigy with the Catalog. After that, we will dive into how to mass deploy those items using policies.
Catalog
To start, the catalog is where all software items and configurations are stored within Addigy. When an item is in the catalog, it can be accessed and used within GoLive, Self Service, or polices. Let’s dive into Software and take a look at the process of adding a new software title to the catalog.
The goal of the smart software wizard is focused on reducing several IT tasks around software deployment into a single workflow. From pre install configuration to post install conditions, removal settings, and Privacy Preferences Policy Controls- smart software has everything to make software deployment easy.
After naming our configuration and selecting a file, we can quickly add an installation script and look through the privacy preferences policy controls. For this app, we will want to allow standard users to approve screen sharing so that usability of this app is easier and does not require IT assistance. If you have other apps like Anti-virus or Screen Sharing tools, the other options within this menu will be of great help.
For Self Service deployment, description, category, and icon are strongly encouraged to maintain a great user experience for end users.
In the installation script section, we see that there is already populated text. This command will take care of any basic installations without needing to be modified. For more advanced workflows, additional commands can be added before or after to do pre-installation configuration or post installation cleanup.
Next is the very powerful condition script. Using the condition script builder, we can quickly set a few requirements for this app to install. For example, we should verify that the app is not installed OR that the version is older than the version we are building.
Now that we have created a new software title, let’s move to policies and see how to queue deployments of software and settings to groups of devices.
Policy
If the catalog is our storage locker for all of our possible software and settings, policies are then the blueprints for delivery. All software and settings can be grouped and deployed to devices that are assigned to that policy. Additionally, policies support hierarchy and will inherit software and settings from the policies above them. Let’s take a look at a typical corporate policy tree. With this configuration, there is a main company policy to streamline enrollment and baseline settings for all managed devices. From here the tree breaks down further into regions and then organizational departments.
For our software title, we have decided to roll it out to the Americas region first. If we want to push out the software silently, the add app button is what we use. However, this app we would like to have in Self Service instead. To do this, we can adjust our published version using the column on the left.One important thing to know about policy is the concept of staging an item. By clicking add to a software title or setting will not immediately send that out to devices. The change must be confirmed in order to be seen by managed devices. A list of staged changes can be found on the policy overview page.
With our smart software builder and policies, making changes quickly to a fleet of devices is simple and straightforward.