As of the latest 9.18.5 OpenTAP version, the PackageCache folder has been moved to the C:\Users\XXXX\AppData\OpenTAP\PackageCache as compared to the 9.10.4 where it was located under C:\Program Files (x86)\Test Automation\PackageCache. Here, XXXX is the user account that was logged in to install OpenTAP.
Is there a way to install across all the users such that it can be accessed regardless of the windows account used to log in?
Thanks for the reply. Since our application is used by different users, there is a chance whereby the windows user logged in may be different from the user that installed OpenTAP. This results into the particular user not being able to access the packages cached/installed by other users.
Hence, we wanted to check the feasibility on such use cases. Do you have alternatives in mind?
Thanks for the suggestion. However, we are already doing that for shared set of packages - and that is not the problem here. Our problem is that when OpenTAP is installed - it installs the packages and caches them in the C:\Users\XxXx folder for that specific windows user. This results into the packages that were cached to not be accessible by other windows users.
I think there there is no way to do what you ask currently, but I also still don’t understand your usecase. Why is it necessary for the other users to access the packages through the cache and not the package repositories?
For our use case, the test stations that uses OpenTAP are used by multiple windows users. All of our applications are all user-wide settings, however OpenTAP restricts us to the specific user directories. Due to this, even though the packages are present in the user directory, we would still need to install from the central repository - requiring a network call. This deviates from the previous behaviour whereby the package cache was accessible by all users from the Test Automation folder.
I think the environment variable would make more sense for us due to the following reasons -  we don’t distribute the engine settings to our test stations and  The engine settings wont be available during installation (assuming its a fresh installation), which means the default packages may still be cached in the default location. @rolf_madsen, what are your thoughts?
@brennen_direnzo Would it be possible to release this as a seed release for 9.18.5?