Microsoft Windows Remote Desktop Connection

01-05-2021 admin

Microsoft Remote Desktop Connection Windows Xp Download
Windows Accessories Remote Desktop Connection
Microsoft Windows Remote Desktop Connection

-->

Dec 02, 2017 You need to open up Administrative ToolsRemote Desktop ServicesRemote Desktop Session Host Configuration on the destination server and double click on the top RDP-TCP connection. This brings up the RDP-Tcp properties box. In my case with DC #3, the cert hyperlink at the bottom was not clickable like the one on DC #1 which I could RDP into.
Use the Microsoft Remote Desktop app to connect to a remote PC or virtual apps and desktops made available by your admin. The app helps you be productive no matter where you are. Getting Started Configure your PC for remote access first.

Open RemoteApp and Desktop Connections in Control Panel, either by opening Control Panel, or by using Windows Search. Click Set up a new connection with RemoteApp and Desktop Connections. This will start the new connection wizard. Enter the URL of the connection. This URL will generally be of the form. After you use the Remote Desktop Connection tool to connect to another computer, the name of the computer is added to the Remote Desktop Connection Computer box. It's easy for you to quickly select the same computer at a later time. In Remote Desktop Connection, type the name of the PC you want to connect to (from Step 1), and then select Connect. On your Windows, Android, or iOS device: Open the Remote Desktop app (available for free from Microsoft Store, Google Play, and the Mac App Store), and add the name of the PC that you want to connect to (from Step 1).

Applies To: Windows Server 2012 R2, Windows Server 2012

This topic describes the Remote Desktop Services functionality that is new or changed in Windows Server 2012 R2 and Windows Server 2012.

In this topic:

What’s new in Remote Desktop Services in Windows Server 2012 R2

In Windows Server 2012 R2, Remote Desktop Services offers enhanced support in the following areas:

Session Shadowing

In Windows Server 2012 R2, Session Shadowing enables you to remotely monitor or control an active session of another user on a Remote Desktop Session Host (RD Session Host) server. The current version includes integration with Server Manager and Remote Desktop Connection (mstsc.exe).

Online Data Deduplication

In Windows Server 2012 R2 the Data Deduplication feature, released in Windows Server 2012, can be used with actively running personal desktop collections when the desktop virtual hard disks (VHDs) are stored on a file server running Windows Server 2012 R2 and accessed by using Server Message Block (SMB). Storage capacity requirements can be dramatically reduced by using the Data Deduplication feature. Data Deduplication on the SMB server caches frequently accessed data, allowing performance improvements on many read-intensive operations, including parallel remote client boot.

Improved RemoteApp behavior

In Windows Server 2012 R2 RemoteApp programs are one step closer to the look and feel of local applications by including support for transparency, live thumbnails, and seamless application move that allows the application content to remain visible while the application is moved on screen.

Quick reconnect for remote desktop clients

In Windows Server 2012 R2 Quick Reconnect improves connection performance enabling users to reconnect to their existing virtual desktops, RemoteApp programs, and session-based desktops more quickly. The connection process for RemoteApp programs has been redesigned for Windows® 8.1 and Windows Server 2012 R2 clients, to be more informative and user friendly.

Improved compression and bandwidth usage

Windows Server 2012 R2 improves performance on the Windows Server 2012 remote experience, by using codecs that enable better compression, delivering bandwidth savings (for example video content delivery over a WAN utilizes up to 50% less bandwidth compared to Windows Server 2012).

Dynamic display handling

In Windows 8.1 and Windows Server 2012 R2 support has been added for display changes on the client to be automatically reflected on the remote client. This translates to seamless device rotation, and monitor addition and removal (for example connecting to a projector or docking a laptop) for both remote sessions and RemoteApp programs.

RemoteFX virtualized GPU supports DX11.1

The RemoteFX vGPU in Windows Server 2012 R2 includes support for DX11.1 on systems that have DX11.1 capable GPU cards. Graphics intensive applications that rely on DX11.1 features can be virtualized and run in a virtualized environment on Windows 8.1 and Windows Server 2012 R2. Windows Server 2012 R2 introduces the following functionality:

Non-Uniform Memory Access (NUMA) support: RemoteFX running on NUMA-based platforms will experience improved scaling capabilities.
Video RAM (VRAM) changes: Adding system memory, to the server running Hyper-V, will allow for a dynamic increase in virtual machine VRAM which can improve performance for applications.

RestrictedAdmin Mode Remote Desktop

Windows 8.1 and Windows Server 2012 R2 support a new remote desktop option to connect in RestrictedAdmin mode. When connecting using RestrictedAdmin mode, the user’s credentials are not sent to the host by the remote desktop client. Using this mode with administrator credentials, the remote desktop client attempts to interactively logon to a host that also supports this mode without sending credentials. When the host verifies that the user account connecting to it has administrator rights and supports Restricted Admin mode, the connection is successful. Otherwise, the connection attempt fails. Restricted Admin mode does not at any point send plain text or other re-usable forms of credentials to remote computers.

Note

Once connected to a host in RestrictedAdmin mode, the user will not be able to seamlessly access other network resources from that host using the credentials they provided to the remote desktop client.

To connect using RestrictedAdmin mode requires

Windows 8.1 or Windows Server 2012 R2 for the remote desktop host
Windows 8.1 or Windows Server 2012 R2 for the remote desktop client

Remote Desktop Services role services description

Remote Desktop Services is a server role that consists of several role services. In Windows Server 2012 R2, Remote Desktop Services consists of the following role services:

Role service name	Role service description
RD Virtualization Host	Remote Desktop Virtualization Host (RD Virtualization Host) integrates with Hyper-V to deploy pooled or personal virtual desktop collections within your organization.
RD Session Host	Remote Desktop Session Host (RD Session Host) enables a server to host RemoteApp programs or session-based desktops. Users can connect to RD Session Host servers in a session collection to run programs, save files, and use resources on those servers.
RD Connection Broker	Remote Desktop Connection Broker (RD Connection Broker): Allows users to reconnect to their existing virtual desktops, RemoteApp programs, and session-based desktops. Enables you to evenly distribute the load among RD Session Host servers in a session collection or pooled virtual desktops in a pooled virtual desktop collection. Provides access to virtual desktops in a virtual desktop collection.
RD Web Access	Remote Desktop Web Access (RD Web Access) enables users to access RemoteApp and Desktop Connection through the Start menu on a computer that is running Windows 8, Windows 7, or through a web browser. RemoteApp and Desktop Connection provides a customized view of RemoteApp programs and session-based desktops in a session collection, and RemoteApp programs and virtual desktops in a virtual desktop collection.
RD Licensing	Remote Desktop Licensing (RD Licensing) manages the licenses required to connect to a Remote Desktop Session Host server or a virtual desktop. You can use RD Licensing to install, issue, and track the availability of licenses.
RD Gateway	Remote Desktop Gateway (RD Gateway) enables authorized users to connect to virtual desktops, RemoteApp programs, and session-based desktops on an internal corporate network from any Internet-connected device.

Removed or deprecated functionality

For a list of deprecated features, see Features Removed or Deprecated in Windows Server 2012 R2.

What’s new in Remote Desktop Services in Windows Server 2012

The Remote Desktop Services server role in Windows Server 2012 provides technologies that enable users to connect to virtual desktops, RemoteApp programs, and session-based desktops. With Remote Desktop Services, users can access remote connections from within a corporate network or from the Internet.

In Windows Server 2012, Remote Desktop Services offers enhanced support for the following scenarios:

Virtual Desktop Infrastructure (VDI) deployment

Remote Desktop Services introduced a VDI deployment in Windows Server 2008 R2. In Windows Server 2012, Remote Desktop Services includes new ways to efficiently configure and manage your virtual desktops. Some of the enhancements include:

Unified central experience – Deploy VDI quickly, and then manage your pooled and personal virtual desktop deployments through a new unified central experience.
Automated and simple single-image management – Take advantage of automated ways to deploy and manage pooled virtual desktops with a virtual desktop template.
User personalization – Preserve user personalization settings for pooled virtual desktop deployments by using user profile disks.
Less expensive storage – Use inexpensive local storage with live migration functionality between host computers for pooled virtual desktops. Personal virtual desktops can use the less expensive SMB central storage.

Session Virtualization deployment

In Windows Server 2012, Session Virtualization deployment in Remote Desktop Services includes new ways to efficiently configure and manage your session-based desktops. In earlier versions of Remote Desktop Services, ongoing management of the RD Session Host servers is performed at a per server level. By using a Session Virtualization deployment scenario, centralized management and installation is enabled. Session Virtualization in Windows Server 2012 offers the following benefits:

Unified central experience – In Windows Server 2012, you can deploy Session Virtualization quickly and manage your deployments through a new unified central experience.
Simplified and centralized deployment – Simple scenario-based installations allow you to create an entire session collection at one time.
User personalization – User profile disks allow you to preserve user personalization settings for your session collections.
Centralized and unified management – Manage all of the RD Session Host servers in your session collection from a single location.
Fairshare experience – For a predictable user experience in Windows Server 2012 and to ensure that one user does not negatively impact the performance of another user’s session, the following features are enabled by default on RD Session Host servers:
- Network Fairshare – Dynamically distributes available bandwidth across sessions based on the number of active sessions to enable equal bandwidth utilization.
- Disk Fairshare – Prevents sessions from over utilizing disk usage by equal distribution of disk I/O among sessions.
- CPU Fairshare – Dynamically distributes processor time across sessions based on the number of active sessions and load on these sessions. This was introduced in Windows Server 2008 R2 and has been improved for heavier loads in Windows Server 2012.

A Session Virtualization deployment consists of RD Session Host servers along with infrastructure servers, such as RD Licensing, RD Connection Broker, RD Gateway, and RD Web Access servers.

A session collection (referred to as a farm in earlier versions of Windows Server) is a grouping of RD Session Host servers for a given session. A session collection is used to publish one of the following resources:

Session-based desktops
RemoteApp programs

Session Virtualization is a scenario-based installation within Server Manager that allows you to install, configure, and manage RD Session Host servers from a central location. With the Session Virtualization deployment scenario, you’re presented with two deployment types:

Quick Start: Installs all the necessary Remote Desktop Services role services on one computer to enable you to install and configure Remote Desktop Services role services in a test environment.
Standard deployment: Allows you to flexibly deploy the various Remote Desktop Services role services on different servers.

Centralized resource publishing

In Windows Server 2008 R2, publishing and managing applications on both pooled and personal virtual desktops is a very time-consuming and costly process. Because RemoteApp programs only partially integrate with the native Windows® experience, they add to the management cost since there is no way to organize published RemoteApp programs to users.

Remote Desktop Services in Windows Server 2012 enables you to publish and manage resources, such as RemoteApp programs, session-based desktops, and virtual desktops, from a centralized console. Using this new publishing feature, you can get an historic view of resources assigned to end users, change published resources for any given collection, and edit properties of published resources.

In addition to the centralized console, you can now configure a RemoteApp and Desktop Connection URL by using Group Policy, and then give users access to the URL automatically through an email address.

Centralized resource publishing provides end users with an experience that can replace locally installed applications.

Rich user experience with Remote Desktop Protocol (RDP)

Windows Server 2008 R2 with Service Pack 1 and Windows 7 with Service Pack 1 introduced Microsoft RemoteFX, which enables the delivery of a full Windows user experience to a range of client devices, including rich clients, thin clients, and ultrathin clients. Windows Server 2012 builds on this platform to enable a richer and more seamless experience on all types of networks and devices. Specifically, Remote Desktop Protocol (RDP) enables a consistent user experience when connecting to centralized workspaces even on networks where bandwidth is limited and latency is high.

Following are the key benefits for end users and IT professionals in using RDP in Windows 8 for their centralized workspace deployments.

RDP key benefits to end users	RDP key benefits to IT professionals
Rich end user experience Access to corporate desktop and applications from anywhere by using any device Secure, managed, and fully supported desktops and applications	Flexible deployment options Virtual desktops Session-based desktops RemoteApp programs Full desktop clients Thin clients Corporate networks Branch offices Diverse workforce support Roaming users Telecommuters Bring your own computer Keep costs down

Rich graphics experience with RemoteFX vGPU

Windows Server 2008 R2 with Service Pack 1 and Windows 7 with Service Pack 1 introduced Microsoft RemoteFX vGPU support, a set of technologies for a rich PC-like experience for virtual desktops. Windows Server 2008 R2 with Service Pack 1 introduced the following functionality:

Host-side remoting
Render-capture-encode pipeline
Highly efficient GPU-based encode
Throttling based on client activity
DirectX-enabled virtual graphics processing unit (vGPU)

Windows Server 2012 builds upon this platform and implements support for the vGPU from DX9 to DX11. The user experience is also improved including support for additional monitors at higher resolutions. As hardware acceleration proliferates to more applications like the web browser, the vGPU enables applications to run higher levels of DirectX within Remote Desktop Virtualization Host (RD Virtualization Host).

Maximum monitor resolution for virtual machines per Windows Version:

Maximum resolution	Monitors per virtual machine for Windows 7 with SP 1	Monitors per virtual machine for Windows 8
1024 x 768	4	8
1280 x 1024	4	8
1600 x 1200	3	4
1920 x 1200	2	4
2560 x 1600	-	2

Remote Desktop Services role services description

Remote Desktop Services is a server role that consists of several role services. In Windows Server 2012, Remote Desktop Services consists of the following role services:

Role service name	Role service description
RD Virtualization Host	Remote Desktop Virtualization Host (RD Virtualization Host) integrates with Hyper-V to deploy pooled or personal virtual desktop collections within your organization by using RemoteApp and Desktop Connection.
RD Session Host	Remote Desktop Session Host (RD Session Host) enables a server to host RemoteApp programs or session-based desktops. Users can connect to RD Session Host servers in a session collection to run programs, save files, and use resources on those servers.
RD Connection Broker	Remote Desktop Connection Broker (RD Connection Broker): Allows users to reconnect to their existing virtual desktops, RemoteApp programs, and session-based desktops. Enables you to evenly distribute the load among RD Session Host servers in a session collection or pooled virtual desktops in a pooled virtual desktop collection. Provides access to virtual desktops in a virtual desktop collection.
RD Web Access	Remote Desktop Web Access (RD Web Access) enables users to access RemoteApp and Desktop Connection through the Start menu on a computer that is running Windows 8, Windows 7, or through a web browser. RemoteApp and Desktop Connection provides a customized view of RemoteApp programs and session-based desktops in a session collection, and RemoteApp programs and virtual desktops in a virtual desktop collection.
RD Licensing	Remote Desktop Licensing (RD Licensing) manages the licenses required to connect to a Remote Desktop Session Host server or a virtual desktop. You can use RD Licensing to install, issue, and track the availability of licenses.
RD Gateway	Remote Desktop Gateway (RD Gateway) enables authorized users to connect to virtual desktops, RemoteApp programs, and session-based desktops on an internal corporate network from any Internet-connected device.

Removed or deprecated functionality

For a list of deprecated features, see Features Removed or Deprecated in Windows Server 2012.

Install the client

Choose the client that matches the version of Windows. The new Remote Desktop client (MSRDC) supports Windows 10, Windows 10 IoT Enterprise, and Windows 7 client devices.

You can install the client for the current user, which doesn't require admin rights, or your admin can install and configure the client so that all users on the device can access it.

Once you've installed the client, you can launch it from the Start menu by searching for Remote Desktop.

Update the client

You'll be notified whenever a new version of the client is available as long as your admin hasn't disabled notifications. The notification will appear in either the Connection Center or the Windows Action Center. To update your client, just select the notification.

You can also manually search for new updates for the client:

From the Connection Center, tap the overflow menu (...) on the command bar at the top of the client.
Select About from the drop-down menu.
The client automatically searches for updates.
If there's an update available, tap Install update to update the client.

Workspaces

Get the list of managed resources you can access, such as apps and desktops, by subscribing to the Workspace your admin provided you. When you subscribe, the resources become available on your local PC. The Windows Desktop client currently supports resources published from Windows Virtual Desktop.

Subscribe to a Workspace

There are two ways you can subscribe to a Workspace. The client can try to discover the resources available to you from your work or school account or you can directly specify the URL where your resources are for cases where the client is unable to find them. Once you've subscribed to a Workspace, you can launch resources with one of the following methods:

Go to the Connection Center and double-click a resource to launch it.
You can also go to the Start menu and look for a folder with the Workspace name or enter the resource name in the search bar.

Subscribe with a user account

From the main page of the client, tap Subscribe.
Sign in with your user account when prompted.
The resources will appear in the Connection Center grouped by Workspace.

Subscribe with URL

From the main page of the client, tap Subscribe with URL.
Enter the Workspace URL or your email address:
- If you use the Workspace URL, use the one your admin gave you. If accessing resources from Windows Virtual Desktop, you can use one of the following URLs:
  - Windows Virtual Desktop (classic): https://rdweb.wvd.microsoft.com/api/feeddiscovery/webfeeddiscovery.aspx
  - Windows Virtual Desktop: https://rdweb.wvd.microsoft.com/api/arm/feeddiscovery
- To use email, enter your email address. This tells the client to search for a URL associated with your email address if your admin has setup email discovery.
Tap Next.
Sign in with your user account when prompted.
The resources will appear in the Connection Center grouped by Workspace.

Workspace details

After subscribing, you can view additional information about a Workspace on the Details panel:

The name of the Workspace
The URL and username used to subscribe
The number of apps and desktops
The date/time of the last refresh
The status of the last refresh

Accessing the Details panel:

From the Connection Center, tap the overflow menu (...) next to the Workspace.
Select Details from the drop-down menu.
The Details panel appears on the right side of the client.

After you've subscribed, the Workspace will refresh automatically on a regular basis. Resources may be added, changed, or removed based on changes made by your admin.

You can also manually look for updates to the resources when needed by selecting Refresh from the Details panel.

Refreshing a Workspace

You can manually refresh a Workspace by selecting Refresh from the overflow menu (...) next to the Workspace.

Unsubscribe from a Workspace

This section will teach you how to unsubscribe from a Workspace. You can unsubscribe to either subscribe again with a different account or remove your resources from the system.

Microsoft Remote Desktop Connection Windows Xp Download

From the Connection Center, tap the overflow menu (...) next to the Workspace.
Select Unsubscribe from the drop-down menu.
Review the dialog box and select Continue.

Managed desktops

Workspaces can contain multiple managed resources, including desktops. When accessing a managed desktop, you have access to all the apps installed by your admin.

Desktop settings

You can configure some of the settings for desktop resources to ensure the experience meets your needs. To access the list of available settings right-click on the desktop resource and select Settings.

The client will use the settings configured by your admin unless you turn off the Use default settings option. Doing so allows you to configure the following options:

Display configuration selects which displays to use for the desktop session and impacts which additional settings are available.
- All displays ensures the session always uses all your local displays even when some of them are added or removed later.
- Single display ensures the session always uses a single display and allows you to configure its properties.
- Select displays allows you to choose which displays to use for the session and provides an option to dynamically change the list of displays during the session.
Select the displays to use for the session specifies which local displays to use for the session. All selected displays must be adjacent to each other. This setting is only available in Select display mode.
Maximize to current displays determines which displays the sessions will use when going full screen. When enabled, the session goes full screen on the displays touched by the session window. This allows you to change displays during the session. When disabled, the session goes full screen on the same displays it was on the last time it was full screen. This setting is only available in Select display mode and is disabled otherwise.
Single display when windowed determines which displays are available in the session when exiting full screen. When enabled, the session switches to a single display in windowed mode. When disabled, the session retains the same displays in windowed mode as in full screen. This setting is only available in All displays and Select display modes and is disabled otherwise.
Start in full screen determines whether the session will launch in full-screen or windowed mode. This setting is only available in Single display mode and is enabled otherwise.
Fit session to window determines how the session is displayed when the resolution of the remote desktop differs from the size of the local window. When enabled, the session content will be resized to fit inside the window while preserving the aspect ratio of the session. When disabled, scrollbars or black areas will be shown when the resolution and window size don't match. This setting is available in all modes.
Update the resolution on resize makes the remote desktop resolution automatically update when you resize the session in windowed mode. When disabled, the session always remains at whichever resolution you specify in Resolution. This setting is only available in Single display mode and is enabled otherwise.
Resolution lets you specify the resolution of the remote desktop. The session will retain this resolution for its entire duration. This setting is only available in Single display mode and when Update the resolution on resize is disabled.
Change the size of the text and apps specifies the size of the content of the session. This setting only applies when connecting to Windows 8.1 and later or Windows Server 2012 R2 and later. This setting is only available in Single display mode and when Update the resolution on resize is disabled.

Give us feedback

Have a feature suggestion or want to report a problem? Tell us with the Feedback Hub.

You can also give us feedback by selecting the button that looks like a smiley face emoticon in the client app, as shown in the following image:

Note

To best help you, we need you to give us as detailed information about the issue as possible. For example, you can include screenshots or a recording of the actions you took leading up to the issue. For more tips about how to provide helpful feedback, see Feedback.

Access client logs

You might need the client logs when investigating a problem.

Windows Accessories Remote Desktop Connection

To retrieve the client logs: