Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-57541

Companion App MSI should automatically startup on next login after install

XMLWordPrintable

    • 12
    • 9
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Problem Definition

      Currently when the Companion App MSI file is deployed by admins wishing to roll out this feature to multiple Windows machines the app still needs to be manually started before it can make the system call to add it to launch at startup. Customers have run into this issue and see that only after running the app manually the registry entry is placed here: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run

      This differs from the normal installer behaviour (.exe) which does launch the Companion App after installing. However, MSIs are usually installed via an admin account, so having the executable launch automatically after installation will not solve the problem (as this will only add the registry entry for the admin user). 

      Current scenario:

      After user runs the App for the first time, the registry key will be added in the following path

      HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run

      Workaround:

      The registry key can be added to HKCU (for all users that should have Companion running) during the deployment to ensure that the app is started automatically without having the user to start it manually.

      For 32-bit OS:

      msiexec /qn /i "Atlassian Companion.msi"
reg add "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run" /v "electron.app.Atlassian Companion" /d "C:\Program Files\Atlassian Companion\Atlassian Companion.exe --was-opened-at-login" /f

      For 64-bit OS:

      msiexec /qn /i "Atlassian Companion.msi"
reg add "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run" /v "electron.app.Atlassian Companion" /d "C:\Program Files (x86)\Atlassian Companion\Atlassian Companion.exe --was-opened-at-login" /f

       

      As of Companion 0.6.0, a registry key can alternatively be manually added to HKLM (instead of HKCU) with no side effects. This will allow Companion to automatically launch for all users on the machine. The process will be the same as above, but adding the registry key to HKLM: 

      HKEY_LOCAL_MACHINE\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Run

       

            [CONFSERVER-57541] Companion App MSI should automatically startup on next login after install

            Alex K added a comment -

            A fix for this issue is available in Companion 1.1.0. View the Release Notes to see what other issues are resolved.

            If Companion is installed via the MSI, then it will need to be manually updated to the new version.

            Alex K added a comment - A fix for this issue is available in Companion 1.1.0. View the Release Notes to see what other issues are resolved. If Companion is installed via the MSI, then it will need to be manually updated to the new version.

            Alex K added a comment -

            This issue has now been fixed in Confluence 7.3.0+ and Companion 1.1.0+. 

            Confluence will be able to launch Companion even if Companion is not already running and has not been launched before. 

            Alex K added a comment - This issue has now been fixed in Confluence 7.3.0+ and Companion 1.1.0+.  Confluence will be able to launch Companion even if Companion is not already running and has not been launched before. 

            Belnet Logistics added a comment -

            Upgrading to version 1.0 still doesn't work.

            With the following installation script, Companion gets updated but never starts, even after a reboot.

            REM Install application
msiexec /qn /i "Atlassian Companion.msi"
 
REM Register the application for automatic startup
reg add "HKEY_LOCAL_MACHINE\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Run" /v "electron.app.Atlassian Companion" /d "\"C:\Program Files (x86)\Atlassian Companion\Atlassian Companion.exe\"" /f

            (With Confluence server 6.13)

            Belnet Logistics added a comment - Upgrading to version 1.0 still doesn't work. With the following installation script, Companion gets updated but never starts, even after a reboot. REM Install application msiexec /qn /i "Atlassian Companion.msi" REM Register the application for automatic startup reg add "HKEY_LOCAL_MACHINE\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Run" /v "electron.app.Atlassian Companion" /d "\" C:\Program Files (x86)\Atlassian Companion\Atlassian Companion.exe\"" /f (With Confluence server 6.13)

            Makisa Appleton added a comment - - edited
            Atlassian Update - September 2019

            Hi all

            Thank you for your votes and comments on your experience with the Companion App and Confluence.

            The Confluence Server team is exploring technical and user experience improvements to the Atlassian Companion App. We've received feedback on various aspects of using Companion and would like to speak with Confluence Server/Data Center customers to better understand the concerns and problems.

            What's involved?

            • Sessions will be 45 minutes in length and conducted over video conference, with our team in Sydney. 

            How do I participate?

            • If you're interested in speaking to us, please send me an email at mappleton@atlassian.com 
            • We will confirm a few details before sending through a calendar invitation with video conference details
            • During the session, we'll start with a general chat to understand more about your role and your company, then dive deeper into your experience with the Companion App - what's working well, what isn't working well and suggestions for improvement.
            • As a token of our appreciation, you'll receive a thank you gift following the completion of your session.

            We can't guarantee that we will be able to speak with all interested parties but we definitely appreciate your interest and enthusiasm to help us make Confluence easier and more enjoyable to use.

            Thanks

            Makisa | Senior Product Manager, Confluence Server and Data Center

            Makisa Appleton added a comment - - edited Atlassian Update - September 2019 Hi all Thank you for your votes and comments on your experience with the Companion App and Confluence. The Confluence Server team is exploring technical and user experience improvements to the Atlassian Companion App. We've received feedback on various aspects of using Companion and would like to speak with Confluence Server/Data Center customers to better understand the concerns and problems. What's involved? Sessions will be 45 minutes in length and conducted over video conference, with our team in Sydney.  How do I participate? If you're interested in speaking to us, please send me an email at mappleton@atlassian.com   We will confirm a few details before sending through a calendar invitation with video conference details During the session, we'll start with a general chat to understand more about your role and your company, then dive deeper into your experience with the Companion App - what's working well, what isn't working well and suggestions for improvement. As a token of our appreciation, you'll receive a thank you gift following the completion of your session. We can't guarantee that we will be able to speak with all interested parties but we definitely appreciate your interest and enthusiasm to help us make Confluence easier and more enjoyable to use. Thanks Makisa | Senior Product Manager, Confluence Server and Data Center

            Klaus Wagner added a comment -

            We are currently setting the run registry entry in HKLM on deployment. However on login the app still stets the current user run registry entry.

            This is to be expected since the app doesn't know anything about HKLM and this is currently only a workaround so users don't have to start the app manually once.

            However sometimes the icon doesn't appear in the task bar and no further UI is shown (trust the server, ...). I think this happens when the current user run and HKLM run is executed simultaneously. The processes are shown as running in taskmanager. It doesn't happen always, so I think its a timing issue.

            Klaus Wagner added a comment - We are currently setting the run registry entry in HKLM on deployment. However on login the app still stets the current user run registry entry. This is to be expected since the app doesn't know anything about HKLM and this is currently only a workaround so users don't have to start the app manually once. However sometimes the icon doesn't appear in the task bar and no further UI is shown (trust the server, ...). I think this happens when the current user run and HKLM run is executed simultaneously. The processes are shown as running in taskmanager. It doesn't happen always, so I think its a timing issue.

            Belnet Logistics added a comment -

            Hi Alexander,

            I don't know elsewhere, but here at least it's the sole way we have to do it.

            Here, when a user is not logged in her machine is most probably switched off (and disconnected from the network).

            Best regards,

            Cyrille

             

            Belnet Logistics added a comment - Hi Alexander, I don't know elsewhere, but here at least it's the sole way we have to do it. Here, when a user is not logged in her machine is most probably switched off (and disconnected from the network). Best regards, Cyrille  

            Alex K added a comment -

            logistics

            Is it common to deploy updates to users while they are logged on? 

            Other customers are requesting different behaviour which is why this ticket is focused on launching at next login (i.e. adding that HKLM registry key during the install process). 

            Alex K added a comment - logistics Is it common to deploy updates to users while they are logged on?  Other customers are requesting different behaviour which is why this ticket is focused on launching at next login (i.e. adding that HKLM registry key during the install process). 

            Belnet Logistics added a comment -

            Note that there's also an issue when you want to update Atlassian Companion via SCCM.

            Scenario:

            1. Atlassian Companion 0.5.3 is running
            2. Admin pushes Atlassian Companion 0.6.0
              => Atlassian Companion 0.5.3 must be stopped before the update can take place
            3. Atlassian Companion is updated but stopped
              => User cannot edit attachments until next login. And, worse, user might install the per-user version of tlassian Companion

             

             

            Belnet Logistics added a comment - Note that there's also an issue when you want to update Atlassian Companion via SCCM. Scenario: Atlassian Companion 0.5.3 is running Admin pushes Atlassian Companion 0.6.0 => Atlassian Companion 0.5.3 must be stopped before the update can take place Atlassian Companion is updated but stopped => User cannot edit attachments until next login. And, worse, user might install the per-user version of tlassian Companion    

            linuxsc added a comment -

            In LexisNexis we have a similar issue: 

            When pushed from Microsoft Configuration Manager (SCCM), Companion App does the install under the SYSTEM account, not the logged in user's account. Because of this, the install has no idea of what profile to install under.

            These are our requirements to have the Companion app start automatically:

            1. Install the companion application under all the C:\Users\Public profile so all users have the installation.
            2. As part of the install, have it place the shortcut in the HKLM\Software\Microsoft\CurrentVersion\Run key so that the app will start automatically for all logged in users.
            This would solve the problems.

             

            linuxsc added a comment - In LexisNexis we have a similar issue:  When pushed from Microsoft Configuration Manager (SCCM), Companion App does the install under the SYSTEM account, not the logged in user's account. Because of this, the install has no idea of what profile to install under. These are our requirements to have the Companion app start automatically: 1. Install the companion application under all the C:\Users\Public profile so all users have the installation. 2. As part of the install, have it place the shortcut in the HKLM\Software\Microsoft\CurrentVersion\Run key so that the app will start automatically for all logged in users. This would solve the problems.  

              aknight@atlassian.com Alex K
              wmasters Will Masters
              Votes:
              33 Vote for this issue
              Watchers:
              27 Start watching this issue

                Created:
                Updated:
                Resolved: