cterry

We recently ran into an issue where one of our developers couldn't connect to a server because the launcher icon was missing from the password hub even though they had a valid license.

Turns out that our org-wide settings were configured to use the default profile of "business user" when it should have been 'it professional'.

I think it makes more sense to assume that anyone with a launcher or RDM license is an IT professional rather than a business user or, at the very least, display the launcher or rdm icon even if under a business user profile so long as they have the appropriate license.

Another consideration is that perhaps the default org-wide profile should be IT professional rather than Business User.

I've had this same issue and so has my colleague. You have to clear your cookies for *devolutions* in your default browser then authenticate again. Not sure why a desktop application would be dependent upon cookies in the browser, but it has resolved the issue every time.

Combine this with the overly complex authentication process for devolutions password hub/devolutions portal and you've got quite a frustrating experience on your hands!