Topics tend to come into Leostream Support in waves. The latest stream of questions center around managing multiple simultaneous connections to a Linux machine running a VNC server. This allows several users to share one Linux machine while giving each user an independent session, similar to Microsoft Remote Desktop Services. In this blog post, we show you how you can configure the Linux server and Leostream to support this scenario.
By now, you’ve likely heard about the Spectre and Meltdown vulnerabilities and their potential consequences. Fortunately, there's very little chance your Connection Broker is in danger, but there are some precautions you may want to take. For more information on whether your Leostream Connection Broker is at risk from these vulnerabilities, and how to protect your environment, please refer to our Knowledge Base article here:
If you’ve read through our Teradici Cloud Access Platform quick start guide, you may have discovered that you need the PCoIP Connection Manager to get your PCoIP connections working with the Leostream Connection Broker. We’re here to highlight the steps of the Connection Manager configuration process
An essential part of the Connection Broker’s job is to smoothly allocate and assign desktops to users based on various rules. With Policy and Release Plan settings, you can optimize desktop usage, ensuring that desktops that aren’t in use become available for people to access, while desktops that need to stay assigned to their users are kept out of the available pool.
Some of the most common issues we see in the support queue have to do with center scans and refresh intervals. A center scan is when we query your center for any changes, and the refresh interval refers to the frequency of the center scans.
If it’s time to migrate to a newer version of vCenter Server, you’ll need to consider your VMware vSphere Center setup in your Connection Broker.
To prevent and troubleshoot various desktop assignment issues, it helps to understand how rogue user assignment and management works.
RemoteApp is the key to running remote applications that appear as though they are running locally on your users’ client device, which is perfect for remote access, branch offices, kiosk workstations, or deploying multiple versions of a single program.
When a user logs in to their remote desktop operating system with one username, and then uses a different username to access the Connection Broker, you may notice some unwanted snags, like desktop assignments not being released. What’s going on there – and how do we resolve it?
We are pleased to announce the latest release of the Leostream Connection Broker 8.2.33! Broker 8.2.33 is a small update from 8.2.27 but includes two new features we are excited to share with you.