Adding Remote Desktop Services and Remote. App programs. Solutions provider takeaway: Adding Remote Desktop Services can be complex for solutions providers, but this chapter.. By submitting your personal information, you agree that Tech. Target and its partners may contact you regarding relevant content, products and special offers. Find out the steps you need to follow to properly add Remote. App programs. Adding Remote Desktop Services. You can add the Remote Desktop Services role to any Windows Server 2.

Adding Remote Desktop Services and Remote. App programs. Solutions provider takeaway: Adding Remote Desktop Services can be complex for solutions providers, but this chapter.. By submitting your personal information, you agree that Tech. Target and its partners may contact you regarding relevant content, products and special offers. Find out the steps you need to follow to properly add Remote. App programs. Adding Remote Desktop Services. You can add the Remote Desktop Services role to any Windows Server 2.

R2 server using Server Manager. Server Manager includes wizards that allow you to add many roles, and you've probably already used it by now. When adding the RDS role, you'll be prompted to answer some questions. The following sections will give you the knowledge you need to answer these questions and successfully add the role.

Edit Article wiki How to Enable Remote Desktop. Three Methods: Windows XP Windows Vista and Windows 7 Mac OS Community Q&A. Remote desktop is a feature that is. Security certificates can also cause remote desktop connectivity problems. Many VDI products use SSL encryption for users who access VDI sessions outside the network.

For here, you can close out the App Store. To access the newly downloaded app, click the the grey "Launchpad" icon in the Dock. Click the Microsoft Remote Desktop app. InformationWeek shares news, analysis and advice on operating systems, from Microsoft Windows 8 to Apple iOS 7. Windows 7 Remote Desktop Connection Problems Windows 7 Remote Desktop Connection Problems. Troubleshooting a remote desktop connection involves understanding the role.

Some of the topics related to an RD Session Host server installation include the following: Additional role services. Network Level Authentication.

Licensing mode. Local Remote Desktop Users group membership. Adding applications. After the role is installed, you'll need to take some steps to configure the server. This section will guide you through the decision- making process and the steps to add and configure the server. Remote Desktop Services Not Needed for Administrator Connections. Remote Desktop Services is not needed to connect to a server for administrator connections. Chapter 1. 4 covered remotely connecting to a server using Remote Desktop Connection (RDC) or Remote Desktops.

To use these tools, you don't need to install Remote Desktop Services. Instead, you only need to enable Remote Desktop connections on the server. A significant difference between remotely connecting for administrator purposes and using an RD Session Host server is that licenses aren't needed for administrator connections. Any server can support as many as two remote administrator connections without a license. However, licenses are required for RD Session Host server connections on one- to- one basis. In other words, you'll need a license for every connection.

Required Role Services. Remote Desktop Services is a server role and includes several role services. All of the services aren't required for every installation. You'll need to evaluate what you're trying to accomplish to determine which services to add. Remote Desktop Session Host The RD Session Host service enables the server to host Windows- based programs or a full Windows desktop. This is a required service for the role.

Remote Desktop Virtualization Host The RD Virtualization Host service is integrated with Hyper- V to allow users to connect to a virtual machine on a server hosting Hyper- V. It can be configured so that users will connect to their own unique virtual machine and allow users to run multiple operating systems simultaneously.

This service requires the Hyper- V role service and is needed if you are using the Hyper- V role service. Remote Desktop Licensing The RD Licensing service manages the client access licenses (RDS CALs) that are needed to connect to an RD Session Host server. It's possible to run Remote Desktop Services without licenses for a limited grace period of 1.

If you have never used Remote Desktop, it is a really great way to connect to another PC (office, home, etc) remotely and get work done that you otherwise could not.

If you're using multiple monitors on your system setup and you regularly connect to other systems via Remote Desktop, you know how frustrating it is to go from a.

This allows you to deploy, configure, and test the server. Remote Desktop Connection Broker The RD Connection Broker service is used for session load balancing and session reconnection in an RD Session Host server farm. It's also required to support RDS Remote.

App applications that allow users to launch applications on the RD Session Host server via Internet Explorer. If you are using multiple RD Session Host servers, the RD Connection Broker can redirect connections to the servers that are the least busy, which provides load balancing.

Additionally, if a user is disconnected, the RD Connection Broker will ensure they are reconnected to the same server where their session is active. Remote Desktop Gateway The RD Gateway service is used to allow users to connect to RD Session Host servers and remote desktops over the Internet.

This service requires additional role services including the Web Server (IIS), Network Policy and Access Services, RPC over HTTP Proxy, and the Remote Server Administration Tools. Remote Desktop Gateway was covered in much greater depth in Chapter 1. Remote Desktop Web Access The RD Web Access service allows users to access Remote. App and Remote Desktop Connection through a web browser. If the clients are running Windows 7, they can access these through the Start menu on their system. This service requires additional supporting role services including Web Server (IIS) and Remote Server Administration Tools. IIS is short for Microsoft's Internet Information Services.

Application Compatibility. If you plan on using the RD Session Host server to host applications for end users, you should install it first before installing the applications. Applications that are installed before adding the RD Session Host role may not work correctly in a multiple user environment. Although some applications will work in multiuser mode even if they've already been installed, many will not. If you've already installed applications that you want to use with RD Session Host server, you should consider uninstalling the application before adding the Remote Desktop Services role. Easy Print. A neat new feature available since Windows Server 2. Easy Print. Easy Print ensures that client printers are always installed in remote sessions without requiring printer drivers to be installed on the terminal server.

This might not seem like much, but in the past, you were required to install printer drivers on the terminal server for all the printers used by clients. If you have just 5. Now you may wondering what you need to do to support Easy Print.

Almost nothing. The support is there automatically as long as Remote Desktop Services is installed on Server 2. R2 (or Terminal Services is installed on Windows Server 2. Clients need to be running RDC 6. Microsoft . NET Framework 3. SP1. RDC 6. 1 is backward compatible to XP SP3 with a download, as mentioned earlier. Microsoft . NET Framework 3.

SP1 is available for download for XP clients from Microsoft's download site: www. Search for Microsoft . NET Framework 3. 0 Service Pack 1. Single Sign- On. Single sign- on is when users are able to provide their credentials once and these credentials are used for the entire session. As long as these credentials have adequate permissions, the user isn't asked to provide their credentials again. Without single sign- on, users can be queried several times to provide the same username and password. You can implement single- sign for clients that access the RDS server using Windows XP SP3, Windows Vista, and Windows 7 clients or from Windows Server 2.

R2 servers. Two settings are required in the RDP TCP/IP Connection properties. You'll see graphics of these later, but here are the two settings: Ensure that the Security layer is set to either Negotiate or SSL (TLS 1. General tab of the RDP TCP/IP Connection properties. Ensure that . When adding the Remote Desktop Services role, you need to specify whether NLA is required. Your decision is based on the clients the RD Session Host server will support.

NLA ensures that the authentication is completed before a full Remote Desktop connection is established. Without NLA, there is a small window of opportunity for a malicious user or malicious software to attack, even if authentication is unsuccessful. NLA is available by default in Windows Vista and Windows 7. It relies on the Credential Security Service Provider (Cred. SSP). If all the clients are running Windows Vista or Windows 7, then you should require Network Level Authentication on the RD Session Host server. Windows XP doesn't natively support NLA. However, if you upgrade to SP3 and enable Cred.

SSP, you can use NLA. You need to modify the registry to use Cred.

SSP in Windows XP SP3. Check out these two Microsoft Knowledge Base articles for more information: KB article 9. Description of the Credential Security Service Provider (Cred.

SSP) in Windows XP Service Pack 3: http: //support. KB article 9. 51. Description of the Remote Desktop Connection 6. Terminal Services: http: //support. If your clients are older than Windows XP SP3, they cannot use NLA, and NLA should not be required. The older clients will not be able to connect using NLA.

Licensing Mode. You'll be prompted to select the licensing mode when you add the Remote Desktop Services role. The licensing mode specifies what type of Remote Desktop Services Client Access Licenses (RDS CALs) you'll use.

You have three choices: Configure Later You can postpone your decision and simply select Configure Later. You'll have a grace period of 1. It's common to choose this option early in the deployment cycle and then configure the RDS CALs once you've worked out the kinks in your RD environment. Per Device A per- device CAL is issued to a client computer or device. If the licensing mode is set to Per Device and a licensing server has been configured, the licensing server will issue the device a temporary license the first time the device connects.

The second time the device connects, the licensing server will attempt to issue it a permanent license. The licensing server will enforce per- device CALs. In other words, if a per- device CAL doesn't exist for the device and an RDS CAL isn't available to be issued, the connection will be blocked. You should use per- device CALs if multiple users will use the same device to connect to an RD Session Host server. Per User A per- user CAL allows a user to connect to an RD Session Host server from any number of devices.

Interestingly, the license server doesn't track the per- user CALs. This can make things both easier and more difficult.

It's easier to manage on a day- to- day basis because the RD Session host server won't stop users from connecting. However, administrators still have a responsibility to ensure that appropriate CALs have been purchased, which does take some extra administration.

Running this program with no extensions will bring up the remote desktop connection program. However, mstsc. exe has a full set of switches that can be used to accomplish things from the command prompt. For instance, mstsc. Chris's specialties include general network administration, Windows Server 2. You can view Chris' personal website at www.