Rocket ETX

While using the ETX software, I noticed that users with identical usernames can log in successfully even if their passwords, home directories and shell paths are different. Only a matching username is required for login. My test‑case details are listed below: 1. The ETX server is integrated with LDAP. The LDAP user `user` has the password `password123`, home directory `/net_home` and shell path `/bin/csh`. There is also a local user with the same username `user` on the ETX node server, whose password is `password456`, home directory `/home` and shell path `/bin/bash`. Under this scenario, the user `user` is able to launch a virtual desktop successfully on the ETX node. And it picks up the home directory and shell variables from the local `user` account on the node, instead of the values from LDAP.2. The ETX server uses Node A for account authentication, and Node B for virtual‑desktop loading. Node A and Node B both contain a user named `user`, but their passwords, home directories and

Hi,when will be the support for Vulkan in ExceedTurboX available?  best regards,Stefan

My company intends to increase the security of clients by using Microsoft App Control.This basically means that any executable not located in %programfiles...% must be digitally signed with our company key.Now signing the executables is  a bit of a hassle but generally not really a problem. But for ETX, two security mechanisms come in to conflict. The ETX launcher checks the hash value of the main (Native Client) executable but if the executable is signed by us the hash value changes. So: sign the main executable -> The ETX Launcher won't start it.Don't sign the main executable: Microsoft App Control prevent execution.Oops!Has anybody found a solution for this problem?

You can find the most recent ETX hotfix in KB Article 000088551.Please note that the download is available to active maintenance customers with Rocket Community login.

In yesterday's webinar we had questions about our planned future telemetry support.   We envision telemetry providing ETX session statistics to a standard on-premise 3rd-party aggregation system. Please reply if you would find telemetry useful. Would OpenTelemetry work with any telemetry system you already have in place?  Let us know what use cases you see, and security concerns you have.

Hello ETX friends and fans,As I mention in my last post about the 12.5.4 launch webinar we captured your questions. The attached PDF has answers I hope you will find useful as you plan for installing and start adopting the latest ETX release.Let's get the conversation started if you have additional questions.

Hello ETX Forum!Thank you to everyone who joined us for the ETX 12.5.4 Launch Webinar yesterday!If you missed it or want to revisit the discussion, you can access the webinar recording on-demand using the registration link.We’ve also compiled the resources mentioned during the event for easy access:Product documentation Release notes Product downloads (RCC) Technical support ETX LiveYour thoughtful questions during the webinar were greatly appreciated. We’re reviewing them now and will publish responses in an FAQ format after the end-of-year holidays.Wishing you a joyful holiday season and a successful start to 2026!Thank you,The Rocket ETX Team

I am pleased to announce the availability of Rocket ETX 12.5.4.Customers trust Rocket® ETX as their remote access solution for graphically intensive applications. With 12.5.4, Rocket Software product team is reinforcing its commitment to help customers keep critical IP secure and deliver high quality access to applications as the business needs grow. Improved performance and scalability. New security capabilities including native support for MFA and SSO via the new ETX authentication server.ETX 12.5.4 includes 44 bug fixes and 43 feature requests. For more details you can read the 12.5.4 release notes.Get started today - Download the latest release from the Rocket Customer Community (RCC) or talk to your Account Executive