Table of Contents

Differences Between Portal for Desktop v2 and v3

Jason He Updated by Jason He

Portal v3 vs Portal v2

Portal v2

Pros:

  • Auto-update: Any changes to desktop specific code (screenshots, AD auth, etc) will be deployed automatically
  • Auto-update Branding: Any logo, icon, or hotkey changes will be deployed automatically

Cons:

  • Multiple portal installations appear inside installed app list
  • Multiple install locations. There is an application installed inside Program Files and and app installed under user's Local App Data folder.
  • When uninstalling, some left over data remains
  • Problem with windows permission restriction during installation or update
  • Portal for desktop is always behind web Portal's release cycle
  • Terminal Server is not supported (due to the install location being inside Local App Data)
  • Multiple installers for same portal, not easy to figure out which one for which situation
Portal v3

Pros:

  • Single install location - Program Files
  • Single app inside uninstall application list
  • Portal always up to date with web Portal. We embed the web Portal directly rather than bundle it with the installer. The web Portal is desktop aware, so everything still works as you would expect.
  • Supports terminal server
  • In application logo will always up to date (fetched at app startup), no need to wait for auto-update cycle
  • Easy to uninstall. Hit uninstall and everything related to Portal is removed. It can be easily done with RMM.
  • Installation plays well with RMM tool
  • Single installer, no brainer

Cons:

  • Desktop shortcut icon, application name, or hotkey combination won't be automatically updated. It requires re-deployment.
  • Any fixes or updates to desktop portal specific features require re-deployment. Such as
    • Active Directory login
    • ScreenConnect integration
    • Sticky notifications
    • Screenshot functionality
    • Any update to rendering engine of Portal for Desktop requires re-deployment

We expect to have less version updates for v3 in the future. Generally one or two released per year, it is also it is your choice to update when new version been released. For example, if you don't use sticky notifications and the fix is only for sticky notifications, then you don't have to upgrade. Or if the fix is only to upgrade rendering engine and you haven't notice anything broken? You don't have to re-deploy.

How did we do?

Troubleshooting your DeskDirector Portal installation

Contact