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.
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.
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?
Today, we’re pleased to announce the launch of the Leostream Knowledgebase, a support information hub for Leostream users that covers everything from Broker configuration basics to frequently asked questions about our unique features.