Adding a Deployment Schedule for One CAL Package

  1. Select the Enterprise, click Setup, and then click CAL Packages.
  2. Expand the Simphony or Custom subgroups, and then highlight the CAL package to deploy.
  3. Click the Deployment Schedules tab.
  4. Click Add Deployment to create a new row in the deployments grid.
  5. In the CAL Package field, select the version number.
  6. From the Deployment Type drop-down list, select the type of deployment:

    • 1 - Property/Enterprise: Click the ellipsis point (...) button and select one or more properties where the package downloads.

      If you select this deployment type, the CAL package deploys to all service hosts at the same time.

    • 2 - Specific Service Host: Click the ellipsis point (...) button and select one or more service hosts or workstations where the package downloads.

  7. Click OK to close the Choose CAL Package to Upload dialog.
  8. In the Action To Take field, select 0 - Install.

    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 0 - Install and a deployment for a workstation with 1 - Skip, the CAL package is not installed on the workstation.

  9. (Optional) In the Effective From field, select the start date when the CAL packages automatically stop installing, and select the stop time (in 24-hour format).

    You can use this field to schedule Simphony upgrades.

    Note:

    The date and time selected in Effective From and Effective To fields are determined by the application server’s time zone, not by the property or workstation time zone.
  10. (Optional) In the Effective To field, select the date when the CAL packages automatically stop installing, and select the stop time (in 24-hour format).

    To keep the installations perpetual, do not set an Effective To time.

  11. Click Save.

Parent topic: Simphony 18.2 and 18.2.1 Deployment