You may now press the OK button to close the dialog box.Īt this point, your server is ready for ThinManager to use it as a Remote Desktop Server (Terminal Server).RDP or Remote Desktop Protocol is a Microsoft protocol that enables remote connections to a local server (or network), to a desktop or a server over the Internet. The default settings (shown below) should work fine for you ThinManager system. Select the items you wish to change, and press Apply. Select the Client Setting item in the menu to the left. You can leave the Allow Connections Only from… item checked. Note: Network Level Authentication ( NLA) is supported in Firmware Package 7.1.3 and later. Key for ThinManager clients is that you UNCHECK the Allow Connections Only from… item.
Make sure your settings match those shown in the image below. Press the Security item in the Menu to the left. The defaults here will work fine for ThinManager. Select the Session item in the left menu, and make any adjustments you would like to use for your system. Use the Add button, and Apply once you’ve finished. Select the User Groups item in the menu on the left, and add the User Groups that you want to be able to remotely connect to your server. If you would like to change the name of the collection to something other than QuickSessionCollection you can do it here, and press the Apply button. In the Server Manager, with Remote Desktop Services > Collections > QuickSessionCollection selected, press on the Task drop down shown in the image below, and then select “Edit Properties”. At this point, we need to now look at some of the other settings. Once it completes, it will go back to the previous screen. This will allow you to specify a file, URL, *.CLI, *.SCU, or other file to run using AppLink. Select Parameters and select Add any command-line parameter. Right click on the published application and select Edit Properties. You need to allow Command Line Parameters to specify specific files or URLs. Verify that all of the applications you want to run are listed, and press Publish. Press Next once you have selected your applications. Use the scroll bar to the right to scroll down for more applications. In the example here, we have selected Calculator, Paint, and Wordpad.
If it still does not appear, make sure the application is properly installed on this server. If you don’t see your specific application, then use the Add… button to browse for it. Select the applications you want to launch from the list that appears. On the next window, select QuickSessionCollection, and then press the link for P ublish RemoteApp Programs. In the Server Manager Dashboard, press Remote Desktop Services in the link on the left side of the window. If you would like to access individual applications using AppLink, follow these steps: After each restart, it will go back into Server Manager and post the status of the deployment.Īfter the deployment completes successfully press Close.Īt this point, your Remote Desktop Server is setup and will allow you to make Remote Desktop connections to this server. It may also restart one or more times during the deployment process. The server will automatically restart if the deployment is successful. Press Next.Ĭheck the Restart the destination server… box, and press Deploy.Ī progress screen will appear and display information on the new deployment progress. It should select automatically create a server pool, and add your local server. Select Session-based Desktop deployment, and press Next. Select Remote Desktop Services installation, and then press Next. Log into the Server with a Domain Admin account. That setup is outside the scope of this document.
It is possible for you to setup Active Directory for a stand-alone server, and make that server also a Domain Controller. This document will assume that your new Remote Desktop Services Server is already part of a domain and you have credentials for a Domain Admin user account.
#Server 2012 r2 remote desktop services single server windows#
Starting with Windows Server 2012, it is highly advised that the server be part of a domain as the Remote Desktop Services graphical configuration is only available to Domain Admins. For printable instructions with pictures see Server 2012 R2 and Remote Desktop Services
0 kommentar(er)
