Jump to content

Search the Community

Showing results for tags 'rdp'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Essentials
    • Announcements
  • Passwordstate 8.x
    • General Support
    • Feature Requests
    • Feature Requests - Completed
    • Known Issues
    • Installing Passwordstate
  • Knowledge Base
    • General FAQs
    • Password Resets
    • Remote Session Launcher
    • Mobile Client
    • Passwordstate API
    • Browser Extensions
    • Password Reset Portal
  • Passwordstate 7.x
    • General Support
    • Known Issues

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL





Google Plus Account







Found 4 results

  1. We use RDP to connect to a selection of our servers via Passwordstate. Unfortunately, we have applications running on the server desktops, so all have to connect as the same domain user account per server. For example, to connect to mydomain\server1.com server we use the mydomain\server1.user account to RDP onto this server. This works fine. We can RDP, and we all see the same desktop, with the apps running onscreen. The issue is that this latest connection bombs the last one out (without warning for that existing user). So, if someone was doing something on there, they are disconnected. This is just the way RDP works when you connect as the same user. This request is to ask if you could add an option to run a quick script displaying the last known RDP logon to that server (and date/time) with a continue yes/no button. This information could be pulled from the passwordstate audit log. For example, the following is recorded in the audit logs, so could be used for the prompt: Fred Smith (mydomain\fsmith) initiated a Remote Session connection to Host 'server1.mydomain.com' (server1 (mydomain server1.user)) using credential '\mydomain\Server Logon Users -> server1.user'. at 21/10/2019 15:05:15 Whoever is connecting can then message the listed user separately, to make sure they've finished what they were doing. If Passwordstate tracks when an RDP session is disconnected, then that info would be useful too, but I don't believe that is tracked. This feature would be of massive benefit to us, rather than looking at 3rd parties to get around the issue. Thanks
  2. Purpose: This post outlines the process you need to follow, to grant someone access to the Remote Session Launcher, without them having the need to know the password. An example could be you have a contractor coming on site, and you want them to connect to machines and perform work,but you do knot want them knowing the password they are using to connect. If you are not familiar with how to set up the Remote Session Launcher, please see this in depth Forum Post - https://www.clickstudios.com.au/community/index.php?/topic/2110-how-to-set-up-the-remote-session-launcher-passwordstate-8/ There are three areas you'll need to attend to, to grant someone this type of access: 1. Under Hosts tab -> Hosts Home, grant your user access to the remote session Credential of your choice **Note this Credential will be linked to a password record, you should NOT grant them access to that record** 2. Grant the user access to the Folder of your choice, which has the machines added into it. This will make the Folder and the machines visible in the Host tab for them, when they log into the system. They should now be able to choose a host and click Launch, and they will gain access to the system without know thing password. Regards Support Click Studios
  3. In the first quarter of 2018 a new Browser Based remote session launcher was introduced into Passwordstate. This video will show you how to use this new launcher:
  4. With the release of Passwordstate 8 is a new, easier to use Remote Session Launcher utility. This forum Post advises how to set this up from scratch, assuming you have never used our remote session launcher before, and will be connecting into a Windows 10 machine. Related Links: How to configure the Remote Session Launcher for use with TeamViewer - https://www.clickstudios.com.au/community/index.php?/topic/2111-using-the-remote-session-launcher-to-use-teamviewer-to-connect/ How to allow other users access to log into machines without knowing the password - https://www.clickstudios.com.au/community/index.php?/topic/2112-remote-sessions-without-access-to-password-credentials/ How to set up a Host Discovery job to import Windows or Linux machines in from Active Directory on a schedule - https://www.youtube.com/watch?v=UifVi2rH8x0 Setting up the remote session launcher can now be configured by following these steps. Step 1: Add an account into a password list that has permissions to connect to your machines. Ensure you prefix the username with the domain, if you are using an Active Directory account. Step 2: Under Hosts tab -> Hosts Home, Add a new Remote Session Credential When adding the credential, ensure you select Windows as the operating system, RDP and link it to the account we created in step 1 simply by searching for it. Other options on this page help filter on what machines this Remote Session Credential will connect to, if you choose. Step 3: As a once off process, you will need to install the Remote Session Launcher. Go to Hosts tab -> Hosts Home and click Install and Configure Remote Session Launcher Now click Install Remote Session Launcher and it will download the install files through your browser. Run this as an administrator on your machine The installation is simple, as you can see in the below screenshots: Step 4: You will need to configure your browser to use a custom protocol, so the Remote Session Launcher can launch directly from your browser. This needs to be completed once per user, per machine. Below are the options you should choose depending on what browser you are using. Once you have set this, please close down the blank window that is on your screen Step 5: Add a Host into your System that you wish to connect to. The instructions below are how to add a single host in manually, but it is possible to use other methods to add multiple hosts into Passwordstate quickly. Under Hosts Home, click View All Host Records Click Add Host Configure the host using the screen below as a guide Step 6: begin adding Hosts into your Host Navigation Tree. This is where you'll be launching your sessions from All Hosts must reside inside a Folder. Right Click Passwords Home and select Add Folder Next give the folder a name and click Save Right click the new folder, and select Add Hosts to Folder Search for your Host, select it and click Add Selected Hosts Now you should be able to select the host and click Launch, and it will log you directly into the machine **UPDATE MAY 2018** A recent build has provided an option for Security Administrators to grant access to the Client Based Remote Session Launcher. These permissions can be set under Administration -> Feature Access -> Remote Sessions: **Update 2** In a recent build you can now launch Remote Session directly from a Password Record, which will then use those credentials in the record to connect to the Host. You must be given access tot his feature under Administration -> Feature Access -> Remote Sessions: Your Password Record must be a local account for the host you are connecting into, and it must also be linked to the Host. You can then launch session using this icon: Or directly from the Actions Menu of the Password Record: Training Video: For a video of this set up process, please watch the following: Regards, Support Click Studios
  • Create New...