• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer
ControlUp Community

ControlUp Community

Connect, Learn, and Grow

  • Blog
  • Podcast
  • Meetups
  • Archives
  • Categories
    • ControlUp One Platform
    • ControlUp for Apps
    • ControlUp for Compliance
    • ControlUp for Desktops
    • ControlUp Scripts & Triggers
    • ControlUp Synthetic Monitoring
    • ControlUp for VDI
  • Topics
  • Events
    • Logos & Wallpaper
    • ControlUp.com
  • Join

Troubleshooting Edge DX Conflicts in ControlUp

Posted on November 8, 2024

After cloning a VM but forgetting to remove Edge DX, a user faced conflicts and duplications between Edge and Secure DX. They tried clearing folders and reinstalling, but ultimately resolved the issue by uninstalling, deleting folders, and using the REGISTERWITHNAME=1 switch. The ControlUp Community offers a guide on this process for non-persistent VDI images. After multiple tries, the issue was resolved by deleting from the console, uninstalling locally, and deleting the program data folder. The user noted relief as the issue was finally resolved.


Read the entire ‘Troubleshooting Edge DX Conflicts in ControlUp’ thread below:

i cloned a VM and forgot to remove Edge DX first. I removed it and secure dx from both and reinstalled but it seems to still have a conflict. I only see one of them in the console and the stats seem to be intermingled like it thinks 2 machines are one. How can i clear that out.?


I’ve had luck resolving that by clearing this folder after uninstalling edge and the agent manager C:\ProgramData\ControlUp\EdgeDX

actually now that I’m thinking about it, might have been C:\ProgramData\Avacee


i uninstalled Edge and Secure DX and deleted the folders and they came back on reboot.

guessing i might have to uninstall from both and delete folders

the one i uninstalled shows up 2x now:


you can just uninstall from the new one remove the Avacee folder and reinstall, that should trigger it to be viewed as a fresh install

We ran into this like a year ago and it was tied to the device ID being cached in that folder. Another option is to install with the REGISTERWITHNAME=1 switch which tells edge to use the device name rather than guid as the unique identifier

This walks through gold images for non persistent VDIs but if you are confident you aren’t going to have duplicate machine names you could probably do something similar.

https://www.controlupcommunity.com/installing-controlup-edge-dx-on-nonpersistent-vdi-images/


here is what i did:

• Deleted From Edge DX console

• unintalled edge and Secure DX from programs and Features

• Deleted the C:\ProgramData\ControlUp\Edge Dx and C:\ProgramData\Avacee folders

• Rebooted

Logged in to both (did not reinstall) and all those folders were recreated and they are in the Edge DX console as expected:

these are persistent VDI desktops


did you uninstall the agent manager?


and like this in secure DX


I would assume the agent manager will reinstall controlup


ok, uninstalled Edge, Secure and agent manager and deleted those folders.

running the edge dx installer and it already has the tenant name and reg code populated. which i don’t think it did when originally installed.

Looking at DEX now

ugh:


Isn’t that what you wanted, it added the machine


not 3 times

i did the process 2 more times and so far it looks to be in a good place. is it Friday Yet? lol


uninstalling and clearing those tokens doesn’t remove the device from the backend, that would need to be done via the management consoles or API calls. Clearing that token really just gets edgedx to see the install as a new machine so a new instance will be listed in the console.


i deleted from the console as well as uninstalled locally as well as deleting program data folder. it still got he tenant and reg code from somewhere. looks to be all set now.

Continue reading and comment on the thread ‘Troubleshooting Edge DX Conflicts in ControlUp’.  Not a member? Join Here!


Categories: All Archives, ControlUp for Compliance, ControlUp for Desktops
Topics: ControlUp Agent, Physical Desktops, Scripts, Triggers, VDI

Ask Us Anything, Connect, Learn, and Grow with the ControlUp Community!

Login to the ControlUp Community to ask us anything, stay up-to-date on what’s new and coming soon and meet other like-minded techies like you.

Not already a member? Join Today!

Primary Sidebar

ControlUp Academy

Enroll in ControlUp Academy for expert-led technical training, equipping you with skills to effectively deploy, manage, and grow your ControlUp investment.

Learn here >

Rotating Images

Hidden Gem from our Community on Slack!

ControlUp Betas - What's Coming Next?
NEW ControlUp Features - Stay Up-to-Date!
ControlUp Scripts - Scripting, Zero to Hero
Latest KB Articles - Be the First to Learn
Did you Know - with Sivan Kroitoru
Practical Perspectives Technical Use Case Training

Video Tutorials Library

Visit our technical how-to videos, offering step-by-step tutorials on advanced features, troubleshooting, and best practices.

Watch here >

ControlUp Blog

Check out the ControlUp blog for expert advice and in-depth analysis.

Read here >

ControlUp Script Library

Visit the ControlUp technical script library, which offers a multitude of pre-built scripts and custom actions for your monitoring and troubleshooting requirements.

See here >

ControlUp Support

Visit the ControlUp support home and to delve deeper into ControlUp solutions.

Browse here >

Download ControlUp RealTime DX

Start with ControlUp for real-time end-user environment insights, swift troubleshooting, and unprecedented performance optimization. Download now.

Download here >

Footer

      

ControlUp Community
Of Techie, By Techie, For Techie!

Terms of Use | Privacy Policy | Security
Dive Deeper, Learn more at ControlUp.com

  • facebook
  • twitter
  • youtube
  • linkedin

© 2023–2025 ControlUp Technologies LTD, All Rights Reserved.

We use cookies to ensure that we give you the best experience on our website. by continuing to use this site you agree to our Cookie policy..