Adding a Deployment Schedule for a Group of CAL Packages

Certain nodes in the tree do not have corresponding CAL packages. You can use these nodes to group CAL packages. For example, you can configure packages that affect All Simphony or the Service Host.

1. In the CAL Packages module, expand the Simphony or Custom subgroups, and highlight a node without a corresponding CAL package.
2. Click the Deployment Schedules tab.
3. Click Add Deployment.
4. From the Choose CAL Package For Deployment drop-down list, select the package you want to deploy.

   The list of available CAL packages in the dialog changes depending on the node highlighted in the tree. For example, if you highlight the Simphony node, the list of packages contains all Simphony CAL packages. If you select the Service Host node, the list contains only the Service Host packages.

5. From the Deployment Type drop-down list, select the type of deployment:

   • 1 - Property/Enterprise

   • 2 - Specific Service Host

6. Click the ellipsis button.
7. In the Select Properties or Select Service Host dialog (depending on your selection in Step 5), select one or more properties or Service Hosts where the package will download, and click OK.

   • Filter lengthy lists by property number or name, or by workstation number or name.

   • Select the Show already configured properties option to prevent yourself from configuring duplicate deployment schedule records.

   • Press and hold the Ctrl key while performing a left mouse click to select multiple properties. You can click theSelect All or Clear All links to affect all properties in the list.

   • You can select multiple service hosts or specific workstations.

8. In the Action To Take field, select one of the following options:

   • If you want the deployment to proceed, select Install.

   • If you want to prevent a package from being downloaded select Skip.

   You can configure multiple deployment schedules for the same CAL package. Simphony uses the most granular deployment when given multiple deployment schedules. For example, if you configure a deployment schedule for a workstation and for the property, Simphony uses the workstation deployment. If you configure a CAL package deployment for a property with Install and a deployment for a workstation with Skip, the CAL package is not installed on the workstation.

9. (Optional) In the Effective From field, select the start date when the package becomes active. You can use this field to schedule Simphony upgrades.
10. (Optional) In the Effective To field, select the end date when the package becomes inactive.