The problem:
Recently Atea was approached by an investment company having issues with application distribution through a mass deployment tool – due to vendor designed logic, the application did not work as expected when distributed per-machine using a standard approach.
IT’S A GOOD THING THAT OUR TEAM ARE EXPERTS WHEN IT COMES TO THINKING OUT OF THE BOX.
The Atea solution:
As soon as our team looked into the issue the customer was having they realized that a repackaging process was required as the application was setup installer that did not contain the vendor MSI.
During the repackaging, our Application Packaging team found out that the application was writing per-machine registry values that contained references to currently logged on user profile directories. This means that the vendor did not support installations for multiple users on a single machine.
At this point, we needed to get creative to be able to successfully launch the application for each logged-on user on a single machine. It’s a good thing that our team are, experts, when it comes to thinking out of the box.
We created a separate feature in our MSI package that triggered a quick repair on an application launch event when a new user launches the application. With this, we were able to fill the per-machine registry values with currently logged on user values in the per-machine registry part. That resulted in a successful application launch and full functionality for the customer when distributing the application using any mass deployment tool in a corporate environment.
The customer was so impressed and happy with the provided solution that they continued to use our application packaging services.
The problem:
Recently Atea was approached by an investment company having issues with application distribution through a mass deployment tool – due to vendor designed logic, the application did not work as expected when distributed per-machine using a standard approach.
IT’S A GOOD THING THAT OUR TEAM ARE EXPERTS WHEN IT COMES TO THINKING OUT OF THE BOX.
The Atea solution:
As soon as our team looked into the issue the customer was having they realized that a repackaging process was required as the application was setup installer that did not contain the vendor MSI.
During the repackaging, our Application Packaging team found out that the application was writing per-machine registry values that contained references to currently logged on user profile directories.
At this point, we needed an out of the box solution for us to be able to successfully launch the application for each logged-on user on a single machine. It’s a good thing that our team are, experts, when it comes to thinking out of the box.
We created a separate feature in our MSI package that triggered a quick repair on an application launch event when a new user launches the application. With this, we were able to fill the per-machine registry values with currently logged on user values in the per-machine registry part. That resulted in a successful application launch and full functionality for the customer when distributing the application using any mass deployment tool in a corporate environment.
The customer was so impressed and happy with the provided solution that they continued to use our application packaging services.