Splashtop Connector FAQ

A: If you run into error when connecting to remote computer like the following, please look into this page to find out the meaning of the error code: 

RDP error details

A: If you are connecting to Windows Server 2012, and get a black screen, it's very possible that Windows Server Essential Experience has not been enabled on the server. Please refer to the following steps to enable it. 

1. Log on to your server as a local administrator.

2. Open Server Manager, and then click Add Roles and Features.

3. In Select server roles, select the Windows Server Essentials Experience role. In the dialog box, click Add Features, and then click Next.

4. In Features, click Next.

5. Review the Windows Server Essentials Experience role description, and then click Next.

6. In the pages that follow, click Next, and then on the confirmation page, click Install.

7. After the installation is complete, Windows Server Essentials Experience should be listed as a server role in Server Manager.

8. In the flag notification area in Server Manager, click the flag, and then click Configure Windows Server Essentials.

9. (Optional) Change the server name if needed.

    Important

   You cannot change the server name after you have configured Windows Server Essentials.

10. Follow the wizard to configure Windows Server Essentials as described in the Deploying Windows Server Essentials section.

11. Follow the wizard to configure Windows Server Essentials as described in the Deploying Windows Server Essentials section.

A: No, it is not required to install the Splashtop Streamer on any machines.

A: Yes.

A: Like standard RDP limitations, two users cannot simultaneously access the same OS user profile via RDP.

A: This is possible, but it may depend on your use case. By default, Splashtop Streamer connections connect to the machine’s console session. If a user logs into the console session, RDP connections are disconnected, and vice versa – this is an RDP limitation. However, you may connect to the Splashtop Streamer and use the Terminal Session icon to view active RDP sessions. This does not give the ability to have a separate desktop session.

A: Text and File copy-and-paste are both supported during these RDP sessions. File copy-and-paste is only support from the Windows Business App client. Features such as remote command, and others from standard Splashtop Streamer connections are not supported at this time.

A:Many times users connect to remote Windows systems, do work, and close the remote session without properly log off the account. In that case, multiple applications, which are still running with that login session uses system resources. Sometimes it causes a slow response of our servers and creates pain for us. So this will be good to auto log off disconnected sessions from the Windows system.

This tutorial will help you to log all the disconnected remote sessions on the Windows system. This tutorial has been tested with Windows Server 2019.

1. Open the ‘Group Policy Editor‘ on your server. Start run window by pressing “Win + R” and type gpedit.msc on run window.

2. Navigate to the following location as the below given location

  Local Computer Policy 
   =>  Computer Configuration 
     =>  Administrative Templates 
	=>  Windows Components 
          =>  Remote Desktop Services 
            =>  Remote Desktop Session Host 
              =>  Session Time Limits

3.Double click on “Set time limit for disconnected sessions” to open it. By default, it is configured a ‘Not configured. Change this to ‘Enabled. Now you will see an option “End a disconnected session” in the lower-left side. Set this value to the desired time.