Deploy updated packages

After you update the packages, deploy them using a variation of the method that you used to initially deploy IXIA CCMS Desktop.

Note: Companies often deploy CCMS Desktop in different ways. Refer to your company's internal processes and documentation first. These steps provide only a general overview of the steps.

To deploy updated packages:

  1. To finalize the packages, take the following actions:
    Table 1. Actions to finalize packages

    Deployment method

    Action

    Network share

    Copy the packages to the network share

    Automated tools

    Add the packages to the deployment tool

    Manual

    Zip the packages and provide them to users
  2. Make sure CCMS Desktop is not running.
    Note: If your deployment uses a remote access solution (such as Citrix or a dedicated SaaS deployment), ensure that no users are logged in.
  3. If you are deploying to users' machines, take the following actions:
    Table 2. Actions to deploy local packages

    Deployment method

    Action

    Network share

    Ask users to follow the instructions in Trigger a user update

    Automated tools

    Push the package to the users' machines

    Manual

    Ask users to copy the zip file to their machines, and unzip the package
  4. If you are deploying to a remote access solution, take the following actions:
    Table 3. Actions to deploy remote access packages

    Deployment method

    Action

    Network share
    Ask the administrator of the remote servers to double-click the required batch file on the network share:
    • update-ccms-online.bat if the server has any active sessions
    • update-ccms-offline.bat if the server has no active sessions

    Automated tools

    Push the package to the servers

    Manual

    On each server, copy the zip file to the machine, and unzip the package