DeskDirector / UserVoice

Feature request tracker
14 stars 2 forks source link

[46732] DD Portal Removal Tool support for V5.x #681

Closed Aycorn closed 1 year ago

Aycorn commented 1 year ago

The current DD Portal Removal tool supports versions 2.x/3.x/4.x

https://help.deskdirector.com/article/huqqqba1r0-ddportal-removal-tool-uninstalling-windows-portals

Feature request to include version 5.x as part of this tool.

Nness commented 1 year ago

We implement uninstall tool mainly due to the chaos of version 2.x. The version 2.x's installation location is branded, which cause uninstall to not working at all. So the logic was to go through all registry and install folder to remove possible version 2.

Since we are out of v2 chaos, there is no intention or reason for us to support latest v5. Maybe in the future, there are registry or file that didn't clean up by MSI, we might implement different script to clean up.

All in all, we are less likely to involve on existing removal tool. The intention was only cover desktop portal Electron version's leftover junks. And it has achieved it needs.

Version 5 is native .net based, registry also handled by MSI. The only possible junk was setting and logo file. So far they have been cleaned up by MSI.

I will close this until we have solid reason. Such as what is missing, what kind junk was left behind that we need such removal tool.

RyanScottT commented 1 year ago

The reason for this request is the possiblity of our clients requesting the latest v5.0*** being removed from all devices. The current uninstaller provided does not work with v5 as confirmed with the DD support team

If a new version is being released then surely an uninstaller should be released also to ensure for any reason, the application being installed can be uninstalled cleanly without per device, manual intervention. Why would you not support a new version you are releasing?

Nness commented 1 year ago

@RyanScottT You can use MSI to uninstall the application. Or you can use RMM to uninstall, labtech can do that as well, I believe.

We never need to release uninstaller, only due to v2 we had folder branding, and plus v2 and v3 both have left over during uninstallation. So we have to create uninstaller to resolve issue. This shouldn't be the case for new installer. There were a lot of mistake we have made on v2 and v3, the script is only there to fix issue not for ordinary uninstall and we have no intention to maintain such project as we moving forward.

The script was only created for the mess we have caused in v2 and v3. I was not expect v4 to be added to script.