Sequencing and Publishing MProof Clientele ITSM

This is a fast recipe to sequence and publish MProof’s Clientele ITSM in conjunction with App-V. The reason to blog about it is that the application popped up at several of my projects.  At my last project the solution to get Clientele ITSM to work with App-V was unknown. So here goes.

The installation is a simple drag an drop folder action into the %ProgramFiles(x86)% folder and the creation of a shortcut that points to the main executable Clientele.Loader.exe. There is however one small thing to know about this application. Use the command line parameter -nodownload in conjunction with Microsoft App-V, otherwise you will end up with an application that will try to download the complete application from the server backend at runtime. This is because the server backend will check the last modified time stamp of the files and these time stamps will be altered when the application is published through the App-V client. The parameter -nodownload disables the timestamp check.

The initial Clientele.Loader executable points to a second executable. Either Clientele.Loaderx86.exe or Clientele.Loaderx64.exe will (depending on the bitness of the client) will be started through the initial executable. So if you are publishing the application with RES Workspace Manager it is necessary to authorize both executables (Authorized Files mechanism).

Finally, the application will save user settings in a file called user.config somewhere in the local application data portion of the user profile (AppData\Local). After sequencing save this file and distribute it through the RES Workspace Manager zero profiling mechanism.

If you are already using RES Workspace Manager  it is also possible to sequence the applictaion without adding the command line parameter, so you can add the command line parameter is RES Workspace Manager.

Leave a Reply




This site uses Akismet to reduce spam. Learn how your comment data is processed.