POWER STUDIO

Updating Power Studio

Keep all Power Studio computers in one station on the same version.

Normal Update

  1. Schedule a maintenance window.
  2. Make a database backup.
  3. Stop Power Studio on all computers that use the shared database.
  4. Install the new Power Studio version.
  5. Run the Configuration Tool on the first updated computer.
  6. Click Update to update the database.
  7. Update the remaining Power Studio computers.
  8. Start Power Studio and test playout, audio routing, playlists and plugins.

The database update is shared. After it has been applied, older Power Studio clients may no longer be compatible.

Do not update one workstation and leave other shared-database clients on an older version for normal operation. Plan the update so all production clients can be brought to the same version in the same maintenance window.

Updating Multiple Instances On One Computer

For multiple Power Studio instances on one computer, every instance must have its own configPostFix. Check this before updating, because the postfix is what keeps instance-specific settings, cache folders, license file selection and Multi studio identity apart. See Multiple Instances On One Computer for the full setup workflow.

The installer updates the main installation folder only. If the computer runs multiple Power Studio instances from separate folders, update those folders manually:

  1. Close all Power Studio instances on the computer.
  2. Install the update normally.
  3. Confirm that every additional instance has a Configuration Tool transform profile for its instance-specific settings, such as its own configPostFix.
  4. Copy the updated files from the main installation folder.
  5. Paste the updated files into the other instance folders and overwrite the old application files, including PowerStudio.exe.config.
  6. Do not overwrite the instance-specific Logs folder.
  7. Do not overwrite the instance-specific license file.
  8. Before starting the copied instance, apply the correct Configuration Tool transform profile so the instance-specific settings are written into the updated config file again.
  9. Check PowerStudio.exe.config, especially the configured configPostFix.
  10. Start the instance that acts as multi-studio server first, if applicable.

The config file should be updated with the new version, because new Power Studio releases may add or change configuration entries. Do not keep an older instance-specific config file just to preserve the postfix. Instead, keep the instance-specific changes in a transform profile and apply that transform after copying the updated files.

The instance-specific files and settings are what keep each instance connected to the right database, logs and license. Check them again after copying files and applying the transform, especially PowerStudio.exe.config and the configured configPostFix.