Configuring Collections
A bunch of configurations is known as a Collection. Collection can be deployed in the target client workstation using Endpoint Central. The advantages of Collection are -
- The targets are defined once for multiple configurations.
- When the configuration is deployed, it saves time to apply the configuration since collection of configuration is applied in each workstation.
Define Collection
- Navigate to Collections from Configurations tab.
- Choose the collection type as User Collection or Computer Collection. This opens the Add Collection Wizard.
- Provide a name and description for the collection.
- Choose the configurations that have to added to this collection and click Next. The configurations are specific to the collection type you have selected above.
- Define the chosen configurations. Refer to User Configurations and Computer Configurations sections for details about the configurations.
Define Target
Select the targets for which the configurations have to be applied. Refer to the Defining Targets topic for more details.
Save or Deploy Collection
After defining the configurations and targets, click Finish to deploy the defined configurations to the selected targets. You also have an option to save the configurations as drafts for later modifications by clicking the Save as Draft button.
Configurations supported in a Collection
A Collection allows multiple configuration types to be grouped and deployed together using the Add Computer Collection or Add User Collection screen. Supported configuration types include Custom Script, Certificate Distribution, File and Folder Operation, Registry, Scheduler, Services, Shortcut, and User Management, depending on the collection type.
Install/Uninstall Windows Software is not available as a configuration type within a Collection.
To deploy multiple software packages in a specific order within a single software deployment configuration, use Add More Packages. To execute scripts or other supported tasks before or after software installation, use Pre-Deployment and Post-Deployment Activities. Alternatively, software deployments and configuration tasks can be deployed separately.