Troubleshooting Edge DX Agent Installation and Upgrades for Non-Persistent Virtual Desktops in Citrix

A user inquired about installing the sipagent2.17.0.6185.msi on a Master Image for MCS without the Agent Control Manager, and if there was a way to suppress automatic upgrades of Edge DX agent using the agentmanger MSI. It was recommended to tag machines with a specific tag and make a rule for that tag to align with a specific agent version. Another user commented that EdgeDX could be used for non-persistent virtual desktops in Citrix, and requested assistance from other customers who have done so. There is currently no way to suppress the automatic upgrade of Edge DX agent using the agentmanager MSI.

Read the entire ‘Troubleshooting Edge DX Agent Installation and Upgrades for Non-Persistent Virtual Desktops in Citrix’ thread below:

Hello Team,

I am looking to install sipagent2.17.0.6185 on a Master Image for MCS. My intention is to avoid installing the Agent Control Manager and to install solely the EdgeDX / SIP Agent. I have obtained only the SIP Agent from the DEX portal.

I attempted to install it using the following command line:

msiexec.exe /i sipagent2.17.0.6185.msi /qn DEVREGCODE= TENANT=sip.controlup.com ALLUSERS=1 ONLYSTARTONBOOT=1 REGISTERWITHNAME=1 GROUP=Test

Nevertheless, I am not observing the ONLYSTARTONBOOT parameter functioning as anticipated. The SIP Agent is being installed, and the service is starting automatically. I found that the only_start_on_boot key is not present in the registry after executing the command line. Am I executing the command line correctly, or is there an alternative method to achieve this?

those options are in the agent manager only and prevent the agent from starting because the moment the agent starts it will try to register which is what happens for you. Only workaround would be te remove the registration file at start but that might cause challenges by itself

Is there a way to suppress the automatic upgrade of Edge DX agent using the agentmanager MSI

yes tag the machines with a specific tag and make a rule for that tag to align with a specific agent version

@member, we plan to use EdgeDX for non-persistent virtual desktops managed by MCS, and the Agent Manager will not affect version control since it will be managed by MCS. Are there any customers currently using EdgeDX for non-persistent virtual desktops in Citrix? We could use some assistance.

Continue reading and comment on the thread ‘Troubleshooting Edge DX Agent Installation and Upgrades for Non-Persistent Virtual Desktops in Citrix’.  Not a member? Join Here!