The installation of the same package is different for workstations reporting to two distinct scalability servers.
In the first case the activate directory is created locally as "C:\Program Files\CA\....", in the other case the directory is "Z:\activate\ ...."
What explanation is there for the activate path being local when installing a package via one scalability server while it is a mapped network drive when installing via another scalability server?
<Please see attached file for image>
<Please see attached file for image>