Setting up a Cameyo server within your own network or data center

Pre-requisites: up-to-date Windows Server 2016 / 2019 / 2022 (be sure to run Windows Updates).

  1. Download the installer

  2. Run the installer

    • After the initial confirmation message, click "Install":
    • Once components installation is over, use your Cameyo admin credentials to register the server:
    • Click "Activate":
    • Click "Reboot":
    • All done. Your server should be ready after rebooting.


Testing your new server

  • Expand the Action menu button on the right-hand side and select "Test Wordpad":

  • You should then be able to see your first test session:


Publishing your first app

  • Expand the Action menu button on the right-hand side and select "Connect as Admin":

  • Download your application and install it on this server. You can then publish it using the app publishing wizard:
  • The application will then be visible the Apps section on your Cameyo portal. There you can define how to share it with your users.


Session measurement (optional)

For testing and capacity planning, you can observe your server's activity in real time by connecting to it as an admin and launching the Task Manager | Users from the Windows desktop.

Advanced: for more detailed monitoring you can use the Event Viewer:

  1. On your server, open the Event Viewer (eventvwr.msc)
  2. Go to to Applications and Services Logs -> Microsoft -> Windows -> TerminalServices-LocalSessionManager
  3. Open Admin or Operational
  4. You will see the sessions list. Date/Timestamped/IP/UserName etc.
  5. Alternatively, you can also navigate to Applications and Services Logs\Microsoft\Windows\TerminalServices-RemoteConnectionManager


Hardware capacity

Hardware capacity depends on the application that needs to run on the server. It can start from 1 CPU per 12 concurrent users and 2 GB RAM per user for lightweight apps, all the way up to multiple CPUs per session. You can estimate the required capacity for your app by connecting to a server as an admin while several app sessions are being used on it, and looking at the Task Manager's "Users" tab.