A user asked how to install EdgeDX on a RDSH Farm. It was suggested to modify the command line, adding "RegisterWithDeviceName": true and "REGISTERWITHNAME=1". Additionally, there will also be a need to check if the device group/tag needs to exist, as that may be a factor in the devices not appearing in Edge DX. Resources can be found at https://support.controlup.com/docs/edge-dx-agent-distribution-and-installation-for-windows.
Read the entire ‘Installing EdgeDX on RDSH Farm: Command Line Configuration and Group/Tag Considerations’ thread below:
We would like to install EdgeDX on a RDSH Farm via the following commandline:
msiexec /i C:\install\agentmanagersetup.msi /qn DEVREGCODE=xxxx TENANT=xxxp.sip.controlup.com ALLUSERS=1 ONLYSTARTONBOOT=1 GROUP=Terminalserver
When installing it on the Image, the Master is showing up in EdgeDX and the clones (after rolling out) only when starting the service manually.
Any hints?
Does the tag for the group have to exist?
https://support.controlup.com/docs/edge-dx-agent-distribution-and-installation-for-windows
Let me look this up internally. The deployment for multi-user environment works different. I think you can’t use the devregcode
Let me see what I can find
This might be separate from the device tag/group part. I think it needs to exist, but let me check on both
Ok, so first of all, if you are building a master image, you will need to do 2 things:
• In Custom Agent Settings (in Edge DX UI -> Configuration -> Settings, towards the bottom) you will need to add "RegisterWithDeviceName": true
• Then for the MSI command line you will need to add REGISTERWITHNAME=1
So it will look something like this
msiexec /i agentmanagersetup.msi /qn DEVREGCODE=XXX TENANT=tenantname.sip.controlup.com ONLYSTARTONBOOT=1 ALLUSERS=1 REGISTERWITHNAME=1
As far as the device group/tag having to exist. Let me double check on that
@member are you saying that the devices that you see in Edge don’t show the Terminalserver device group?
@member they don’t show up at all unless you start the agent manually. For the group I’ll check again on Monday as I’m not connected anymore at the customer.
Try with the above setting for the master image install. I think that might have to do with it. Normally we read the dev reg code from a txt file, but I think it can’t find that in a multiuser env, hence the devicename method. Give it a go and see if it solves the problem
perfect, I’ll let you know!
Continue reading and comment on the thread ‘How to install ControlUp Edge DX via Command Line’. Not a member? Join Here!
Categories: All Archives, ControlUp for Desktops