Setup of the Installation Package and Rollout Strategies

Required Permissions: IT Admin

For empower®, there are different setup types and different rollout strategies that you can use to distribute the software in your company.

Setup of the Installation Package

A distinction is made between per Machine and per User Installations.

The per User installation is recommended for environments in which the users install empower® themselves on their device.

The per Machine installation is recommended for software management in the case of distribution by IT. In this case, empower® is installed for the respective device.

The only difference between the installation packages is the different .msi file that is executed.

Furthermore, the installation package contains a payload folder in both variants. This contains important files for the complete installation of the software.

Auto Updater

To ensure that the client version of empower® is continuously updated, the Auto Updater can be installed during the initial installation of empower®.

However, this option is only available for the per User variant.

If the client is configured for auto updates, the Auto Updater is started each time the system is restarted and regularly checks whether new updates are available.

If this there is an update, the client is updated automatically.

Note

For further information regarding the Auto Updater, see Overview about the empower® Auto Updater.

Load Balancing

To avoid overloading the backend, it is important that not all clients try to synchronize with the backend at the same time. This is what load balancing is for.

Load balancing can be used from empower® Version >= 9.3. It prevents the backend from being overloaded by too many clients synchronizing at the same time.

The settings for load balancing are made during the backend installations.

If you host in the empower® Cloud, empower® Support automatically adopt the appropriate setting.

Note

Despite the load balancing, it is recommended to roll out in waves to avoid longer waiting times for the clients.

Note

For further information regarding the load balancing, see Load Balancing for Desktop Synchronization.

Possible Rollout Strategies for empower®

empower® can be rolled out using different strategies.

In the following, three rollout strategies are summarized:

  • Wave Rollout

  • Pilot Rollout

  • Big Bang Rollout

Wave Rollout

If you roll out empower® in waves, the following process should be followed:

  1. The group of people (wave) that is to receive the software first is defined.

  2. Possible problems are identified and rectified.

  3. The next group of people (wave) receives the software. This step is repeated until everyone has received the software.

The rollout in waves is recommended for a number of users of 1,000 and higher.

Pilot Rollout

If you roll out empower® with a pilot group, the following process should be followed:

  1. The pilot group that is to test the software intensively is defined.

  2. Possible problems are identified and rectified.

  3. The software is then gradually rolled out to other groups and/or departments.

The rollout with a pilot group is recommended for a number of users of 1,000 and higher.

Big Bang Rollout

With a big bang rollout, the software is distributed directly to all users.

As all users are directly affected by the change, intensive preparation and extensive testing are necessary to ensure that the software works smoothly and that potential problems can be resolved in advance.

The rollout with a big bang is recommended for a number of users of max. 1,000.

Was this article helpful?

/

Comments

0 comments

Article is closed for comments.