Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA Enterprise SCADA

Apply/install the package manually

  • Last UpdatedApr 24, 2025
  • 2 minute read

After the contents of the Management of Change (MoC) package have been reviewed and verified, you can apply/install the package contents offline manually.

Note: To run the dnapackage install command, you must be a member of the DNA Authority - SCADA Emergency Package Admin group.

To apply/install the package contents manually

  1. On the desktop, double-click the Windows PowerShell for DNA shortcut.

    Windows PowerShell for DNA opens.

  2. Execute the following commands:

    set-silo RealTime

    dnapackage install --package <package file path>

    Where:

    • --package <package file path> is the fully qualified path to the package file you want to apply to the system.

      For example: dnapackage install --package C:\temp\package.pkg

If the command was successful, a message similar to the following will appear:

Successfully installed changeset 2

Successfully installed changeset 3

Successfully installed package from C:\temp\package.pkg

Note: The Package Tool (dnapackage) displays a success or failure message in the console that indicates the result of attempting to install each changeset. If a changeset installation fails, dnapackage also displays information about the rollback of each changeset.

If the package was successfully rolled back, the package status will be Install Failed - Rollback Successful in the MoC zone. If the package was unable to be rolled back, the package status will be Install Failed - Rollback Failed in the MoC zone.

If the package installation takes too long to complete, the package status will be Timed Out in the MoC zone. The package status does not indicate that the installation has failed, only that manual intervention may be required to determine whether the installation is blocked. If the package store audit log is being updated with subsequent events after the time out event, then no action is required. If the package store audit log does not show progress after waiting for a reasonable period, consider contacting the AVEVA Enterprise SCADA Support Team to determine how to proceed.

If the package installation succeeds, the savedata command will be run on the RealTime computer where the changes were made, and the package status will be Installed in the MoC zone where it was installed.

For more information on package status, refer to Understanding the status of an MoC package.