Think about hospitals, if a doctor works on a computer connected to a virtual machine on the RD Virtualization Host, and that computer crashes, the doctor simply moves to another physical computer and reconnects to his virtual machine; the session or data is not lost. Remote Desktop Licensing — this service is taking care of the licenses used by clients and licenses issued to them. If one of the RD Session Host fails, users are redirect to another one available without losing their work.
A small interruption of the session is possible or users have to reconnect to get their session back. Remote Desktop Gateway — is for those users that need to connect from outside of the company. This is very useful for administrators, because they only need to open port on the firewall, witch may already be opened if the company has a secure web site publish to the internet.
Remote Desktop Web Access — this service enables users to connect to remote applications and desktop from a web browser. If users are working from a Windows 7 machine they can connect to those applications from the Start Menu. Select all the role services except RD Virtualization Host and choose to add the required role services when the Add Roles Wizard window pops-up. Click Next to continue.
If you will not have more than 25 users depending on the hardware you can put them all on one machine. Technically you could install all the roles on one machine, but this would not be recommended. If you only have one RDS host you can install the licensing role onto the same machine. An important step at the planning of an RDS environment is to check if the applications are able to run on an RDS host. Which applications do you want to host and how many users are gonna use them?
I intend to install the following applications on my RDS: 1. Office 2. Enterprise Propriatary Databse Application 3. Adobe set Flash, Reader, etc. Java 5. Symantec Endpoint Protection 6. There will only be about 10 - 20 users on this server.
In this case you should be fine with a single machine on which you can install all the applications and also the licensing role.
Do you already know which licenses you want to buy? I would highly recommend a "per user" licensing mode. In this case you are more flexible than with the "per client" mode. If you only want your user to access the apps through VPN, you won't need a gateway or the web access portal. 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. If previous connections have been established the User name field will be populated with the user name used in the preceding session. If you need to log in as a different user this option will be provided on the next screen which appears after the Connect button is pressed:. In this screen enter the password for the selected user note that remote desktop access is only available for user accounts which are password protected.
If a user other than the one displayed is required, simply click on the Use another account link and enter the necessary details. Click on OK to establish the connection. After a short delay the remote desktop will appear on the local computer screen. When the Remote Desktop Client is exited by pressing the 'X' on the control panel the remote session continues to run on the server even though no client is connected.
Next time the user connects the desktop session will appear exactly as it was left before. To end the session select Start in the remote desktop session, click on the right arrow button in the bottom right hand corner of the menu and select Log Off.
This will close down the remote desktop session and close the remote desktop client. Multiple concurrent remote desktops can be run and managed within a single window using the MMC Remote Desktops snap-in. This may either be snapped into the MMC or launched from the command-line or a Run dialog by typing:. Once launched, right click on the Remote desktops item in the tree in the left hand panel and select Add a new connection from the menu.
They are not assigned to specific users permanently like Device CALs are to devices. The connection method you used during activation, is retained. I chose Enterprise Agreement. These are the steps for Enterprise Agreement 4. Then click Next to complete the license installation process. When you are done specifying license servers, click OK.
0コメント