Atlassian Companion app does not work with session-based virtual desktops or virtual app streaming

Summary

• Edit Files using Atlassian Companion may not work on specific terminal server environments when using multiple desktops concurrently. 
• Each desktop session on the server must have a separate (virtual) network interface for the Atlassian Companion to work.  

Steps to reproduce

1. The first user tries to edit the document and receives a prompt to download and install the Atlassian Companion app which then gets installed into their user profile. And they can open the document correctly.
2. The second user logged on to the same Terminal Server tries to open a different document using Atlassian Companion (the second user will not be prompted to install the Atlassian Companion – instead the document will open on the first user’s desktop)
3. If the first user shuts down the Atlassian Companion by clicking Quit in its tray menu, the second user will now be prompted to download and install the Companion app and the second user able to open documents on their second user desktop.
4. If another user tries to edit a document using Atlassian Companion it will open on the second user’s desktop.

Environment

• Operating System: Windows Server 2012 R2.

Expected Result

• Editing a file using Atlassian Companion will show on the same desktop session.

Actual Result

• Editing a file using Atlassian Companion will show on the previous desktop session that has Atlassian Companion running.

Workaround

• If the user already done using the Atlassian Companion to close the Atlassian Companion.