Running EdgeDX in a Non-Persistent VDI/DaaS Deployment – Tips and Troubleshooting.

A user asked a detailed question about running EdgeDX within a non-persistent VDI/DaaS deployment. The discussion covers specific deployment requirements and tips from other users. Troubleshooting steps, including checking the event viewer and using the msiexec command with specific parameters, are also mentioned.

Read the entire ‘Running EdgeDX in a Non-Persistent VDI/DaaS Deployment – Tips and Troubleshooting.’ thread below:

Hi, Is anyone running EdgeDX within a non-persistent VDI/DaaS deployment? (so Edge DX agent within Guest VM) – I have a bunch of questions but before I get started just this basic question since most CU deployments in VDI/DaaS will use RealtimeDX 🙂

It’s possible, but I think there are some specifics around deploying the agent

I have a couple of customers who do it

yeah – that’s one of the questions. Right now installing and ‘activating’ the Windows Agent on the master machine and than publishing this machine to production doesn’t work. The new production machines aren’t listed in the EdgeDX console.

make sure to use the onlystartonboot option https://support.controlup.com/docs/edge-dx-agent-distribution-and-installation-for-windows#command-line-installation

I expect CU setup on the machine machine to be installed/configured differently –

I think you’d also benefit from the register with name option but I don’t see it there

let me get you some details 🙂

Btw, what’s the reason why you are doing Edge DX instead of RTDX?

Also – different question in same context of non-persistent VDI/DaaS. Is it possible to (auto) remove non-active CU machines? In Frame/DaaS context after every ‘Publish’ the production VMs are terminated and new machines will be created. I want to auto remove the Frame terminated machines from the ControlUp EdgeDX solution as well.

“Btw, what’s the reason why you are doing Edge DX instead of RTDX?” >> long story … short version the architecture of RealTimeDX..

There is a global setting for Edge re removing devices. If you want to do it differently, not sure if there’s an API for that

You might want to look at msp mode with reverse agent from v9 😉

“You might want to look at msp mode with reverse agent from v9 😉” >> already done – 😉

kk

with that if a new machine spins up with the same name it will continu to use the old record

msiexec /i agentmanagersetup.msi /qn DEVREGCODE=XXX TENANT=[tenantname.sip.controlup.com](http://tenantname.sip.controlup.com) ONLYSTARTONBOOT=1 ALLUSERS=1 REGISTERWITHNAME=1

Thanks – will give it a try

Since physical machines can have the same device name Edge uses a generated UID and its stored in C:\programdata\Avacee\sip_agent\cachefiles. This file/UID is generated on first start of the agent and if it changes you wind up with duplicate machines in the UI. Register with device name tells the agent to use the machine name in the UID file instead of a generated guid.

Quick Question – I did install EDX agent with the install parameters in the master machine, all good. Published the master machine to production and I do see EDX is installed in control panel but don’t see the machine in device EDX console. I did add a custom setting “”RegisterWithDeviceName”: “true”” and checked the JSON. all good. Q: how best to troubleshoot why EDX isn’t listed / registered correctly?

For starters, the event viewer.

If the agent fails to contact the tenant it should throw an error in the event log.

Sounds like the agent manager isn’t deploying the agent indeed. Like Landon said check the event viewer

Continue reading and comment on the thread ‘Running EdgeDX in a Non-Persistent VDI/DaaS Deployment – Tips and Troubleshooting.’.  Not a member? Join Here!