Running Splashtop on a virtual machine can be just as effective as running it on a physical computer.
If you're looking to install Splashtop Streamer on virtual environments, note these tips below.
Installing the Splashtop Streamer
When the streamer is installed on a computer, a unique identifier, or UUID, is generated for the streamer. This UUID is used by Splashtop to distinguish between computers.
When a computer is cloned or imaged with the streamer already installed (such as a virtual machine spun up from a base image), conflicts will occur and you may see strange issues such as streamers taking precedence over others or renaming.
See this article for more info: What happens when I clone computers and VMs with streamer pre-installed?
The best practices for installing Splashtop Streamer on VMs would be one of these methods below:
- Do not include the streamer on the master image. Once the computers are cloned, you can install the streamer either manually or by using a 3rd party mass deployment tool with silent install parameters.
- If you include the streamer on the master image, run or deploy the command below to generate a new unique identifier for each new computer after cloning.
- Windows: start st-streamer://com.splashtop.streamer?resetuuid=1
- Mac: open st-streamer://com.splashtop.streamer?resetuuid=1
- Linux: splashtop-streamer config -resetuuid
How do I get audio during the remote session?
Splashtop remote sessions can only redirect audio if there is an audio driver/output device on the remote computer. Typically, virtual machines do not have one by default -- so initially, you may not be able to redirect audio over your Splashtop remote session.
Other solutions like VMWare, Windows RDP, etc., install virtual audio drivers for the session to remedy this issue. To have audio during a Splashtop session, make sure to install a virtual audio driver, which you can find on the web (there are varieties from freeware, donation-ware, and more).