Contents x
    How to Update SBAs and AA-VE in On-Premises Environments
      • Print
      • Dark
        Light
      • PDF
      Contents

      How to Update SBAs and AA-VE in On-Premises Environments

        • Print
        • Dark
          Light
        • PDF
        Article Summary

        We regularly publish new scripts for importing community Script-based Actions (SBAs) and Automated Actions (Virtual Expert) to your ControlUp on-premises database.

        As private (organizational) scripts are saved in a different location, the import of community scripts will not affect your private scripts.

        How to update Script-based Actions

        Note

        These steps can be performed without administrative privileges.

        To update Script-based Actions:

        1. In the Windows Control Panel and open Programs and Features.
        2. Right-click ControlUp Server and click Change. The configuration dialog of the ControlUp Server appears.
        3. Click Update SBAs.
          image.png
        4. In the file dialog, open the SBA_Package.sql file. This starts the import of community SBAs.
          image.png
        5. Upon completion of the update, the following popup appears
          image.png

        How to Update Automated Actions & Virtual Expert Rules

        To update Automated Actions:

        1. As a user with administrative privileges, open the Windows Control Panel and click Programs and Features.
        2. Right-click ControlUp Server and click Change. The configuration dialog of the ControlUp Server appears.
        3. Click Update VE & AA.
          image.png
        4. In the file dialog, open the AA_VE.ldif file. This starts the import of community Automated Actions and rules for the Virtual Expert.
          image.png
        5. Upon completion of the update, the following popup appears
          image.png

        Troubleshooting

        If the Update VE && AA button is grayed out, the user that performs the update doesn't have local administrative rights. This problem can be resolved by running the installer as an administrator.
        image.png

        Was this article helpful?
        What's Next