Best Practices For Running SignalPro in Cloud VM

Prior to installing SignalPro onto a Virtual Machine, it is recommended to review the system requirements found here: https://edxwireless.atlassian.net/wiki/spaces/EWKB/pages/249528333

This will assist with determining which VM service will be needed, as many VM services will be limited terms of RAM and Storage.

The installation of SignalPro on a virtual machine is similar to other installations of SignalPro. A user can experience some trouble when trying to install the software onto a VM from a remote desktop connection. Please use this link if you need to review the installation process: https://edxwireless.atlassian.net/wiki/spaces/EWKB/pages/575799330

A user will need either Cirrus Licensing or a Network Key to use SignalPro on a Virtual Machine. Cirrus licensing is seamless and the easiest to setup and operate. With a network key there are some things you will want to be aware of. Such as avoiding connecting to the network key licensing server using a VPN. Please use this link to review all possible licensing scenarios: https://edxwireless.atlassian.net/wiki/spaces/EWKB/pages/939261957

This next link will take you to an article on EDX SignalPro Directory Structure best practices: A SignalPro user will want to avoid using a network drive to share data files. This is also important to consider when selecting a VM service to run SignalPro.

Each Licensed seat of software should sit on its own VW with one user using the VM at a time. Multiple users can share storage on a shared drive, but it is recommended to move projects and data to the local VM when working on them. And then the project should be copied back onto the shared drive for other users to access. This eliminates the possibility of someone opening up or saving over a project currently being worked on.