Can we remove “3CXMyPhone Client Addin.log” or move location

Discussion in '3CX Phone System - General' started by JohnGrenfell, Mar 27, 2012.

Thread Status:
Not open for further replies.
  1. JohnGrenfell

    May 18, 2010
    Likes Received:

    We’re about to start running 3CX Phone as a Out-of-browser application with the “3CXMyPhoneDesktopComponents”.
    We have 3000 stations and need to ensure any roaming user can run the MyPhone app first time. We have found that if we use the shortcut installed by the manual install of MyPhone if will reference a path which is unique per user per station which just doesn’t work in our environment.

    We have a successful deployment of the Silverlight 5 client and 3CXMyPhoneDesktopComponents are successfully created a nice script which makes us of sllauncher.exe to install the xap locally and then run it.

    /emulate:"\\3cx\data\MyPhone\application.xap" /origin:"" /overwrite
    /install:"\\3cx\data\MyPhone\application.xap" /origin: /shortcut:startmenu /overwrite

    We’ve noticed that every time we run using this technique a new directory is created under the users profile “AppData\Roaming\3CXMyPhone Client Addin” (3CXMyPhone Client Addin\\3CXMyPhone Client Addin.log) which contains a file “3CXMyPhone Client Addin.log” . This location will roam with our users and create slow login times (I currently have 13 folders!). I’m surprised these logs are not created in either the TEMP folder or under AppData\Local.

    Can we safety remove these folders/files or point to a new location?



    There’s a useful read here about sllauncher if anyone’s interested -
  2. Raf Wenger

    Apr 5, 2010
    Likes Received:
    Re: Can we remove “3CXMyPhone Client Addin.log” or move loca

    Hi John

    Great post! We're trying to do the same: deploy the 3CXMyPhone via a script.
    Thanks to your post, we've got the command line part sorted.
    The odd thing, is that when we start the 3cx Myphone app installed via the command line, we're caught in a login loop.
    I enter an extension number and a PIN, click OK and the login screen appears again after a second or two.

    I've compared the metadata files in the out-of-browser for both the manually installed version and the command-line installed version. They are identical.

    It seems as if the command-line installed version isn't talking to our pbx to authenticate.
    Any clue about what I am doing wrong? Is there any log file I can look at to give me some clues?

Thread Status:
Not open for further replies.