A user asked about installing ControlUp for VDI in a non-persistent image. Another user suggested using a built-in synchronization feature and confirmed that the agent will not register in golden image mode as long as the machine name matches the image. The sync with Citrix will also prevent stale machines from cluttering up the interface.
Read the entire ‘How to Install ControlUp for VDI in a Non-Persistent Image’ thread below:
Hi, I am trying to install the ControlUp for VDI in a non-persistent image. I saw this article "https://support.controlup.com/v1/docs/agent-outbound-communication#configure-agent-for-master-images". If I install it in the master image, what will happen when a non-persistent VDI gets created from that master image? Will the agent self-register or is there something else needed to be done when a new VDI gets created from the master image?
with the reg key it will register with the monitors for outbound if the machine is already added to the console. To do that I suggest to use the built-in sync withe your euc connectoons https://support.controlup.com/docs/built-in-folder-synchronization
I do have the folder sync enabled with Citrix integrated.
yes so in that case it will see the machine is deployed from the golden image (because the name changed and I believe something else) , registers itself with the monitor for outbound communications and starts sending data. No need for you to do anything else
Thanks, will there be any duplicates when the VDI resets?
No. In golden image mode the agent won’t register as long as the machine name matches the image. It’ll only try to register when its name is different
And the sync with Citrix will prevent stale machines from cluttering up the interface
Continue reading and comment on the thread ‘How to Install ControlUp for VDI in a Non-Persistent Image’. Not a member? Join Here!
Categories: All Archives, ControlUp for VDI