A customer had an issue with configuring ControlUp for Linux instant clones. It was determined that Linux support for VDI is not currently available. The agent can be installed directly from the command line, but currently there is no option to register by device name. ControlUp for Desktops (CU4D) is used for monitoring Linux devices, but not for master image or instant clones scenarios. The customer was informed that this is a feature question on the roadmap, but no timeline is available yet.
Read the entire ‘Can you Monitor Linux for Instant Clones with ControlUp?’ thread below:
Hi Team, One of our customer is trying to configure ControlUp for Linux for instant clones. We installed the agent on Master image and it’s reporting in the console, but when we push the snapshot on the pool, the other machines are not registering. and on the VDI machines I can see the agent is present
@member I’ll need to look into this, on windows device we have a specific install for master image i’ll need to check if same is support for Linux. Can you raise a support ticket and DM the number and i will pick it up
@member Sure I’ll raise it. So far I know Linux for VDI is not supported but support suggested me to go for ControlUP for Desktops. Not sure if it’s only for dedicated desktops or it should work for stateless desktops as well.
Yes CU4D is the product for linux but need to check on the master image install
Thanks Luke, raising ticket now
mention you talking with me already
don’t think there’s a master image option for the linux installer as of now
@member How do we enable ControlUp agent on Linux VDI instant clone machines? is there any alternate way?
its not the issue of the Linux machines its the using of the master image. and that install been used for multiple devices.
these are the installation steps what you could do is run the installer in a post-installation script (installer docs) @member do you now if there’s an option to register with device name for Linux? I have no idea if this would cause tons of duplicates
followed this step : Alternative installation method
You can also install the Agent directly from the command line.
On the Downloads page, click Download to download the latest GA Agent for your Linux architecture.
- After the Agent is downloaded, expand the section for your Linux architecture and scroll down to the section Direct install from the command line.
- The commands are ready for you to copy and already include your unique tenant URL and device registration code.
But i only see master image on console where these commands were executed, not other machines
Divya lets take this into support ticket and I can engage with the development team to be sure if this can and can’t be done. Once we get confirmation can come back here and share the results with the community.
Divya, replied back in ticket, CU4D is used to monitor Linux devices but not if the are built from a master image or used in an Instant Clones scenario
One of the key technical considerations with CU4D is that each device must register as a unique entity in our backend. This is done using a Device Identifier that’s generated during agent installation and registration. If two devices share the same identifier (for example, when cloned), they will overwrite each other’s data, leading to inaccurate information in the DEX Portal.
For Windows deployments, there is an option called “Register with Device Name”, which uses the computer name as the unique identifier. This works well in environments where each device has a unique hostname:
🔗 Edge DX Agent Distribution and Installation for Windows
However, for Linux devices, this option is not currently documented or officially supported:
🔗 Edge DX Agent Distribution and Installation for Linux
So, to answer your question directly — Horizon Instant Clones with Linux OS are not currently supported for monitoring in CU4D. But the is a feature question open for this on the roadmap that i can see internally but no time line
Oh ok. Thanks
no problem
workaround would be to deploy the agent post-cloning but you would end up with lots of duplicates until the maintenance setting kicks in and removes them
but not supported
Continue reading and comment on the thread ‘Can you Monitor Linux for Instant Clones with ControlUp?’. Not a member? Join Here!
Categories: All Archives, ControlUp for Desktops, ControlUp One Platform, ControlUp Scripts & Triggers
