Remote control devices using P9 Connect

Table of contents

With P9 Connect, you no longer need tools like Teamviewer, LogMeIn or VNC for remote control access to your machines. P9 Connect is built-in to the already installed Panorama9 agent and delivers a full-featured remote control solution. If you already have a favourite remote control tool, then Panorama9 will, of course, continue to play nicely with it.

Connect to any device in seconds

Use the built-in P9 Connect from any location to quickly access computers or servers regardless of where they are. Provide remote support or administration as if directly in front of the machine - whether you're in the same building or across the world.


Gone are the days of requesting users' IP addresses and other ID information. With P9 Connect, simply search for the computer or user name and connect with the click of a button.


  • No client install required (It's included with your Panorama9 agent)
  • Log in and connect directly to client machines through the Panorama9 dashboard
  • Traverse network and connect to machines behind firewalls
  • Chat with the user of the machine
  • Transfer files and folders
  • Open multiple sessions to allow more than one technician to connect to the same machine
  • Supports mixed-OS environments (Microsoft Windows and Apple OS X. P9 Connect is confirmed to work with Java SDK 8u40 Build b05 and newer)
  • Allow multiple monitor support
  • Use the Toolbox included with the P9 Connect client to quickly run debugging tools
  • Record remote control session for later review
  • Connect securely with 256-bit AES session encryption
  • Enable temporary or permanently remote control access
  • Require user consent before remote session can be established

How to start/stop P9 Connect

The P9 Connect client can be started by the desktop user, remotely through the Panorama9 Dashboard or command line script (see below).

Desktop user

You control the Connect client through the Panorama9 status bar. Just choose the number of minutes or hours the remote control client should run or set it to operate indefinitely. To begin a remote control session, simply click the "Connect to" link on the Panorama9 dashboard.


Panorama9 Dashboard

Navigate to a device and click on the "Start P9 Connect" link. Wait for the Panorama9 Agent on the device to notice your request (typically takes less than 1 minute). Once the P9 Connect client is started the "Remote tools" widget will update and include a link to start the remote control session.


How to gain remote access to a device using P9 Connect

Once you click on the “Connect to” link, a P9 Connect token is issued and remains valid for the next 24 hours. To begin the remote control session, simply run the downloaded binary. There’s no need to pre-install a viewer - everything you need is in the downloaded file.


You can send the downloaded file to others to give them access to the device. After 24 hours (or sooner if P9 Connect is stopped) you're no longer able to use the downloaded file. A new one then needs to be generated through the Panorama9 dashboard.

Allow access permanently on remote machines

You may enable P9 Connect through the command-line interface. Use this with e.g. a logon script if you wish to bulk enable P9 Connect.

Enable P9 Connect (allow permanent access):

For 32bit systems

C:\Program Files\Panorama9>p9-connect.exe --start 

For 64bit systems

C:\Program Files (x86)\Panorama9>p9-connect.exe --start 

(Note: The "-h" argument lists required and available command line arguments)


Another option is to  use "PsExec" to start a remote process and run the P9 Connect client command line utility through that. Running a remote process requires that both the local and remote computer have file and print sharing (the Workstation and Server services) enabled and that the default Admin$ share (a hidden share that maps to the \windows directory) is defined on the remote system. You can read more about PsTools and download the PsExec utility here:

To start P9 Connect (allow permanent access) using PsExec:

psexec \\computername -s "%ProgramFiles%\Panorama9\p9-connect.exe" --start


Last updated:


  • Avatar
    Shawn Ross

    How do I take my currently deployed systems and set them all to "allow indefinitely"? Can I 'default' the client to an indefinite allow if I choose? That would give me the same functionality as something like LogMeIn Free.

  • Avatar
    Mark Kennedy

    Yes please enable a setting to allow us to set the clients to "allow Indefinitely" from the dashboard.  I like the idea of the user granting access, but most of my clients prefer I aways have access.  


    Keep up the great work, you guys are on to something here.  I'm so happy to have you at the core of my new MSP.

  • Avatar
    Henrik Andersen

    Hi Guys,

    Thanks for the feedback -- we're already building a command-line tool which can be used to tweak access permissions.

    Furthermore, we're investigating other options as well.

  • Avatar

    We've added a command-line tool that can be used to enable the Panorama9 Connect client (allow permanent access). The article above has been updated with instructions.

  • Avatar
    It Director

    The Remote Assistance menu item is grayed out / inaccessible on our clients.  What are we missing?  

  • Avatar
    Mark Kennedy

    IT Director, you have to contact support and have them enable it for your network.  Not sure why this isn't in the documentation.

  • Avatar
    Henrik Andersen

    Hi All,

    Just wanted to let you know that this feature is now (and has been for a while) enabled per default so you don't have to contact support :-)

  • Avatar
    Shawn Ross

    FYI, I recently setup a Server 2012 Core instance, and to get P9 Remote Connect working on the Server Core instance I needed to do the following (in powershell):

    • Install-WindowsFeature -Name NET-Framework-45-core
    • Install-WindowsFeature -Name NET-Framework-45-Features

    Just keep in mind you're adding .NET Framework 4.5 to your Server Core instance (some may not like this)

    After installing these and restarting the host I am able to connect to the server core instance using P9 connect.

    Thanks to Claus (Support) who helped me figure this out and answered some questions.

    I believe this will also work with Server 2012 R2, but I have not tested it.

  • Avatar
    Philippe Ségard


    When I try "remote connect", the eapp wants to connect to the LAN IP (192.168.x.x). This means I cannot use P9 remote connect to connect from outside the LAN.

    What am I doing wrong? How can I connect from internet (WAN)?

  • Avatar


    When you click the "remote connect" link your browser should download a .exe (Windows) or .jnlp (OSX/Linux). Is that happening?

    If not, have you configured your browser to use a proxy?

    Still an issue then please send a support ticket to

  • Avatar
    Steve Laurel

    I seem to be having problems with the script above. Does it work on Win10 Pro systems?

  • Avatar
    Steve Kanter

    Is there a way to make a token permanent? I have a VM for an outside accountant's use. I don't want to have to renew/resend him a token every time he wants to access. Need something always available like logmein/teamviewer. Is this possible with P9 Connect?