Skip to main content
6月 1, 2017 1:49 下午 UTC
New Idea

Solve client installation problems

Please solve the existing problems with client installations and keep scripting functionality

Some cases have been already created to try to find solutions with the support.

https://support.ptc.com/apps/case_logger_viewer/auth/ssl/case=12979482

https://support.ptc.com/apps/case_logger_viewer/auth/ssl/case=13475340

https://support.ptc.com/apps/case_logger_viewer/auth/ssl/case=13376940

PTC ILM client installation has some general problems, that must be solved:

- support of several parallel installations of integrity clients from different releases and/or same release but different hotfixes on the same client computer

- avoid the usage of PATH variable for searching for client executables (e.g. Excel-AddOn or IRC 3.2) and make every ILM part configurable regarding the executables to be used (see C12979482)

- avoid in the client installation process the setting of the PATH variable, because only the last installation "wins" (see C12979482)

- avoid write access to client installation directory (see C13376940) after the installation is finished

- implement a client update process, that allows hotfixes to be used/installed without write access to install directory or usage of admin rights (see C13475340)

it is very important to

- keep the scripting functionality by commands (CLI) and Java-API on client side, we depend on the scripting for several processes

- keep the possibility, that client hotfixes can be installed on the client before the server has to be updated with the hotfix

    3回复

    6月 2, 2017 8:57 上午 UTC

    Can you please clarify that where you are expecting support of several parallel installations of integrity clients from different releases and/or same release but different hotfixes on the same client computer, in these cases the Clients are communicating with different servers or the same server?

    kkasper作者
    6月 2, 2017 10:54 上午 UTC

    I meant each client installation is only communicating with its specific server.The number of parallel releases/projects shall not be limited.

    Example with different releases

    client installation project A-VW -> server installaion project A-VW (everything release 10.9, with several hotfixes)

    and parallel on the same client computer

    client installation project SWE -> server installaion project SWE (everything release 10.8, with several hotfixes)

    or

    example with same release, but potentially different hotfixes

    client installation project A-VW -> server installaion project A-VW (everything release 11.1, with several hotfixes)

    and parallel on the same client computer

    client installation project SWE -> server installaion project SWE (everything release 11.1, with several hotfixes)

    6月 6, 2017 5:11 上午 UTC

    Hello Kay,

                     I think the general direction of this is similar in nature to the Idea. Let us use that for tracking the multi-client behavior.

    About the change in Client behavior & better hotfixing ability, I believe you are aware that PTC is working on a UI replacement project & these issues are expected to get handled there.

    Thanks

    Kartik