Jump to content

Search the Community

Showing results for tags 'remote session launcher'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Google Plus Account


Location


Interests


Biography


Location


Interests


Occupation

Found 9 results

  1. Wouldn’t it be more convenient if you could just passthrough the credentials? We now use Apache Guacamole (https://guacamole.apache.org/) as remote desktop gateway, and you can set ${GUAC_USERNAME} and ${GUAC_PASSWORD} in the RDP settings, so the account you are logged in with in the web interface is also used for RDP, without the need for retyping or store it and the risk of going out-of-sync when it’s changed in AD.
  2. Hello, Please add AnyDesk Remote Session Launcher Command Line syntax: AnyDesk Command Line Interface Or Add Custom App in Connection Type parameter, administrator will be able to add custom Launcher function in PSLauncher.ps1 Best regards, Long time user :-)
  3. **Edit 27th September 2019** We've updated this forum post with some more suggestions, including how to turn on verbose logging and a link to some known error codes. The Browser Based Remote Session Launcher that was introduced in Build 8275 requires some installation and configuration to be applied to your Passwordstate web server, but if you find you cannot launch session for any reason, please run through these troubleshooting steps below to resolve the problem: Issue 1: Do you see the Passwordstate-Gateway Service running on your web server? If not then please follow the documentation under https://www.clickstudios.com.au/downloads/version8/Passwordstate_Remote_Session_Launcher_Gateway_Install_Guide.pdf to set up this feature as a once off process Issue 2: The Passwordstate-Gateway service is running but connections won't launch, you should be presented with a page of troubleshooting steps. Try clicking the "Test SSL Certificate" link on this page and see what results that gives you. If you get results saying your certificate is not secure, take the necessary steps to ensure your browser trusts your Passwordstate certificate. This could be installing the certificate into the Trusted Certificate Authorities on your desktop though Internet Explorer, or adding an exception in Firefox as an example. Issue 3: If you receive a Web Proxy Gateway error like the screenshot above in Issue 2, this might be caused by a firewall on your web server blocking the connection. To fix this, log into your web server and run he following command in elevated Command Prompt to create a firewall rule: netsh.exe advfirewall firewall add rule name="Passwordstate-Gateway" dir=in action=allow protocol=TCP localport=7273 Issue 4: If you receive a Web Proxy error like the screenshot above in Issue #2, this may be caused by incorrect syntax in your gateway.conf file. Please ensure the syntax of this section of the gateway.conf file is in the same format as the below screenshot Issue 5: Can you successfully start the Passwordstate-Gateway service on your web server? If not, please try these suggestions: Possible Fix Suggestion 1: Check the name of the C:\inetpub\Passwordstate\hosts\gateway\Passwordstate.pfx file is correct. This file must be called 'Passwordstate.pfx' for the service to work correctly Possible Fix Suggestion 2: Did you install OpenJDK on your web server? If not please refer to section '4. Install OpenJDK 12' in the following document for thishttps://www.clickstudios.com.au/downloads/version8/Passwordstate_Remote_Session_Launcher_Gateway_Install_Guide.pdf Possible Fix Suggestion 3: Did you configure the SSL Certificate for the gateway, and put the encrypted password for this certificate in the gateway.conf file? If not please refer to https://www.clickstudios.com.au/downloads/version8/Passwordstate_Remote_Session_Launcher_Gateway_Install_Guide.pdf which describes how to export your Passwordstate certificate, and apply it to you Gateway service Possible Fix Suggestion 4: Is the default port of 7273 is in use by something else? To test this, run a command prompt on your web server, and run the following command: netstat -ano | findstr :7273 You should get a blank result back from this command if the port is free. If something else is using the port, try changing the listening port in the C:\inetpub\Passwordstate\hosts\gateway\gateway.conf file to something else under 10000, save and restart the service Possible Fix Suggestion 5: Check the password that you set when exporting the certificate is the same password that you have encrypted and applied to your C:\inetpub\Passwordstate\hosts\gateway\gateway.conf file. One way to test this is to export the certificate again from IIS, and set a new password. Update the password in the Gateway.conf file and see if the service starts then Possible Fix Suggestion 6: In the Gateway.conf file, update SSL to false, and save the file. Try restarting the service again now, and if it starts, this confirms that the certificate is the issue. And you should try running through the export process again and confirm everything is configured according to the documentation under https://www.clickstudios.com.au/downloads/version8/Passwordstate_Remote_Session_Launcher_Gateway_Install_Guide.pdf **Note** The SSL value in the gateway.conf file needs to be set to true in order to establish successful connections. This test of changing it to false is purely to establish if there is something wrong with the certificate. You should set this back to true after you have finished troubleshooting your issue. Possible Fix Suggestion 7: Possibly the recording path that is set in the Gateway.conf file does not exist or is incorrect. Try changing the recording path back to the default location which is shown in the screenshot below, and then try starting the service again" Issue 6: RDP into Server 2008 and Server 2008 R2 is not working, but Server 2012 and above is working okay. If you run into this issue, it's because your server's are not patched with the TLS1.2 and TLS1.2 updates from Microsoft. Please download and installed the appropriate patch below: Server 2008 - https://support.microsoft.com/en-us/help/4074621/add-rds-support-for-tls-1-1-and-tls-1-2-in-windows-server-2008-sp2 Server 2008 R2 - https://support.microsoft.com/en-au/help/3080079/update-to-add-rds-support-for-tls-1-1-and-tls-1-2-in-windows-7-or-wind Issue 7: You can establish some connection to some machines with the Browser Based Launcher, but others seem to hang and do not make a connection. Try one of these suggestions to help troubleshoot this kind of scenario: Possible Fix Suggestion 1: Try doing an open port test when logged in to your Passwordstate web server, to the remote host? Does this return True or False? This Powershell example would be is me connecting to my remote Windows host: Test-NetConnection devpc1 -Port 3389. If you are having issues with SSH connections, the default port you should be testing for is 22. Possible Fix Suggestion 2: Possible you will get an error code in returned to you in the Error Console which will help diagnose the issue. See this forum post for a list of Error Codes: https://www.clickstudios.com.au/community/index.php?/topic/2853-error-codes-for-the-browser-based-remote-session-launcher/ Possible Fix Suggestion 3: You could temporarily enable verbose logging for your connections, and then refer to the logs to see if this can help diagnose the issue. See this forum post on how to enable verbose logging of connections: https://www.clickstudios.com.au/community/index.php?/topic/2852-enabling-verbose-logging-for-the-browser-based-remote-session-launcher/ Installation Video of installing the Gateway can be found below, which outlines all steps to set this up on your web server: We hope this helps and please log a support call with support@clickstudios.com.au if you are still having difficulty getting the Browser Based Remote Session Launcher to work correctly. Regards, Support.
  4. 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
  5. 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:
  6. As of Passwordstate 8, it is now possible to configure the Remote Session Launcher to connect using TeamViewer, instead of using the native windows Remote Desktop Connection tool. Below are some simple instructions on how to do this, and we assume you have some experience with setting up the Remote Session Launcher utility previously. You will need to ensure that you have the Remote Session Launcher installed, your browser configured and you know how to add hosts into the system. For more information on now to do this, please see this Forum Post: https://www.clickstudios.com.au/community/index.php?/topic/2110-how-to-set-up-the-remote-session-launcher-passwordstate-8/ This also requires you to install the TeamViewer client on your machine, and set up your remote TeamViewer machine for unattended access. This means you should have a static password configured for the remote TeamViewer machine. Step 1: When adding a Host into the system, ensure you configure it to use TeamViewer Step 2: When adding in a Remote Session Credential, for TeamViewer accounts, you are not required to link it to a Password Record. instead, simply configure the Remote Session Credential for TeamViewer and click Save: Step 3: Ensure you have a Password List that is enabled for Resets: Step 4: When adding a password into your List, ensure you choose TeamViewer as the Account Type, and select the appropriate Host you configured in Step 1. The username should be the Teamviewer ID and the password is the unattended access password you have previously set on the remote machine You should now be able to click the TeamViewer Launch button and it will log you directly into your remote TeamViewer machine, without the need to enter a UserID or Password: Regards, Support Click Studios
  7. 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
  8. trexman

    Teamviewer

    Hello, I'm a new user of Passwordstate. Is there a possibility to save Teamviewer login credentials and use it with the Remote Session Launcher feature? So that nobody has to know a fix password of a Teamviewer ID and can start the Teamviewer like the RDP Remote Session Launcher. Christian
  9. Hi, We set this up and it was working fine. However we are having issues with connection to some servers. These particular machines have a setting the stops people signing in with credentials that are saved in the remote desktop client. So when first connecting to these servers the remote session launcher worked fine, but after that we now get back the "The servers's authentication policy does not allow connection requests using saved credentials. Please enter new credentials" message. This happens on both windows 7 and windows 10. Is there anything we can do to stop this happening? So passwordstate connects in the same way as the initial connection every time? Kind regards, Jamie
×