The final configuration screen allows the user experience to be configured. The reason that these features are not enabled by default is that they consume considerable amounts of bandwidth and place an extra load on the RD Session Hosts. Unless you specifically need users to be able to stream audio both to and from the session host and video to the remote desktops and use the latest graphics intensive desktop effects it is recommended that these features remain disabled:.
Clicking Next proceeds to the Confirmation screen. Read carefully any warnings that are displayed. Typically the wizard will recommend any currently installed applications should be re-installed before remote access is provided to users steps to achieve this are outlined in the next chapter. Click Install to begin the installation process. Partway through the installation it will be necessary to restart the Windows Server R2 system. Once rebooted, be sure to log in as the same administrative user to complete the Remote Desktop Services configuration process.
Once the process is complete, a screen similar to the following will appear:. The default configuration for Remote Desktop Users Group is to allow all members of the Administration group to connect remotely. Active Directory also contains a Remote Desktop Users group to which users may be added to provide Remote Desktop access privileges. Note that users with administrative privileges do not need to be added to this list, by default they already have Remote Desktop access.
To add additional users click on the Add Enter the name of the user in the text box entitled Enter object names to select and click on Check names to list names that match the name entered. Select the appropriate name from the list. The following example shows user Bill on server winserver Click on OK to apply the change.
The new user will now appear in the list of users with Remote Desktop access on the Remote Users screen. The specified user will now have Remote Desktop Services access to the system.
With Remote Desktop Services installed and configured on the server, the next step is to ensure the services can be accessed from a remote client. Remote Desktop Services provides both remote desktop and remote application access.
Under remote desktop access an entire desktop session running on the server is displayed on the client. The user then interacts with the desktop to launch and interact with applications details on installing applications for use with Remote Desktop Services is covered in Installing Applications for Windows Server R2 Remote Desktop Services. In the case of remote applications, the remote application running on the server appears in its own window on the client desktop, to all intents and purposes looking like a local application to the user.
With the appropriate configuration tasks completed on the remote system the next step is to launch the Remote Desktop Client on the local system. This can either be an IP address or a computer name. Since operating systems are divided into two categories, namely Client Operating Systems and Network Operating Systems, nature of Remote Desktop feature also varies according to the operating system on which it has been integrated.
In client operating systems as soon as administrators initiate Remote Desktop connection to the remote computers, locally logged on users on those computers automatically get logged off and the consoles of the remote computers are then displayed on the computers from where the Remote Desktop connection has been initiated. On the other hand, in network operating systems two concurrent remote desktop sessions can be established by the administrators without logging off the locally logged on users from remote computers.
Before administrators can establish a Remote Desktop sessions on remote computers, Remote Desktop feature must be enabled on them.
Administrators must follow the steps given below in order to enable Remote Desktop feature on Windows Server R2 :. Now that you've gotten free know-how on this topic, try to grow your skills even faster with online video training.
Once the RD License Server has been installed the next task is to activate it. Once started, the Remote Desktop Licensing Manager dialog will appear containing a list of detected license servers on the network. The only license server listed in the following figure is the one on the local server.
Because this has yet to be activated it is listed with a red circle containing an X mark next to it:. To activate a license server, right click on the server in the list and select Activate Server. After reading the welcome screen click Next to proceed to the Connection Method screen. The activation process requires communication with Microsoft in one form or another. If the server has an internet connection then the activation can be performed over this connection.
The default, recommended method, is to have the RD Licensing Manager automatically connect to gather the information. Alternatively, if an internet connection is not available or a firewall prevents such access the activation may be performed over the telephone.
If Automatic connection is selected, the following dialog will appear as the wizard attempts to contact Microsoft:. Once the Microsoft activation server has been located a new dialog will appear prompting for user, company and geographic location information.
Complete these details and click Next to proceed. The second screen requests more detailed, but optional information. Either complete this information or click Next to skip to the activation process. Once again the wizard will contact Microsoft and complete the activation.
Once completed, the following completion screen will appear:. Note that the Start Install Licenses Wizard now check box is selected by default.
0コメント