x
Reset Search
 
 

 

Troubleshooting Article

Desktop app doesn’t auto-start when settings rolled out by Active Directory

Explains what to do if the Workshare desktop app doesn't auto-start after install after settings have been rolled out using Active Directory


Scenario

By default, the Workshare desktop app launches after install and starts up each time the user logs in to their Windows machine.

If the auto-start option is turned off, the desktop app will no longer start when the user logs in. Auto-start can be switched off in the desktop UI or in the Registry:

  • UI: Deselecting the Launch Workshare when I login option in the Preferences dialog (General tab).
  • Registry: Setting the Registry option StartOnLogin to False (HKEY_CURRENT_USER > Software > Workshare > Workshare Desktop > General)

If an admin then turns auto-start back on again (StartOnLogin to True) and rolls out this setting using Active Directory group policy, the desktop app will still not start when the user logs in. This is because the desktop app is not running and therefore does not check the settings.

Workaround

Either of the following actions will correct this issue:
  • The user can launch the desktop app manually. The desktop app will check the settings and will auto-start appropriately in the future.
  • The admin can remove the HKCU Active Setup key from the Registry. This is the key that triggers the desktop app to launch for each user after install. At the next logon for each user, the desktop app will run, check the settings and will auto-start appropriately in the future. The HKCU Registry key can be found at:
    • 64-bit OS: HKEY_CURRENT_USER > Software > WOW6432Node > Microsoft > Active Setup > Installed Components > WorkshareDesktop
    • 32-bit OS: HKEY_CURRENT_USER > Software > Microsoft > Active Setup > Installed Components > WorkshareDesktop
Environments

Helpful?      

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255