Hi Asgeir,
Not sure about best practice but will go with a proven practice in our environment.
We download the version we would like users to use e.g. IBM_PAfE_x64_2.0.83.3.xll and then rename it to remove the version number.
IBM_PAfE_x64_2.0.83.3.xll becomes IBM_PAfE_x64.xll
We then share it to a location accessible to users. Users are notified of the new version and can pick it up from there and save locally, overwriting the previous version which would have the same name.
From there, some users already have the file linked as an add-in, others who do not launch it from their saved location (typically the desktop).
Many users do not keep the add-in automatically added as they run other add-ins for ERPs etc. and like to reduce any possible contention between the add-ins.
This is still largely a manual process and requires discipline from the user but does not require administrator rights to install or update.
There may be better ways to deploy the updates with domain logon scripts, software center etc. etc. but would depend on the environment. The one thing that will no doubt keep the process simple is keeping the filename consistent so that updates overwrite rather than having to remove, add, change registry settings etc. etc.
Let's see what others in the community have to offer on this topic.
------------------------------
George Tonkin
Business Partner
MCI Consultants
Johannesburg
------------------------------
Original Message:
Sent: Fri March 03, 2023 06:01 AM
From: Asgeir Thorgeirsson
Subject: PAX setup, sysadmins
Hi all
What is the best practice for sysadmins to distribute and install PAX?
Prior to version 2.0.65, we distributed a PAX package through our "SoftwareCenter"
The guidelines in the following link only describe a method for manual installation on the users machine.
Installing the Planning Analytics for Microsoft Excel .xll file as an add-in to Microsoft Excel - IBM Documentation
------------------------------
Asgeir Thorgeirsson
------------------------------