Table of Contents

Differences Between Desktop Portal v2 and v3/v4

Jason He Updated by Jason He

DeskDirector Portal v2 vs v3/v4

Portal v2


  • 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


  • 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 leftover 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 the same portal, not easy to figure out which one for which situation
Portal v3/v4


  • Single install location - Program Files
  • Single app inside uninstall application list
  • Portal is always up-to-date with Web Portal. The Web Portal directly is directly embedded into the desktop App rather than bundled with the installer. The web Portal is desktop-aware, so everything still works as you would expect.
  • Supports terminal server
  • The application logo will always be up-to-date (fetched at app startup), so there's 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


  • 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 releases per year, it is also your choice to update when new versions are 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 don't see anything broken from your end? You don't have to re-deploy.

How did we do?

Portal Release Notes - Windows/macOS

Portal Release Notes - Web Client