- #Thin remote desktop client update
- #Thin remote desktop client software
- #Thin remote desktop client Pc
- #Thin remote desktop client series
Not only does the client software detect the network client, it can also detect changes in the network and adapt its own settings accordingly. In another move toward the seamless user experience, Microsoft has eliminated the need for end users to set the network in the Remote Desktop client. You can even set it up so that your users who are domain members and using managed devices to connect to their remote sessions won’t be prompted to enter credentials they’ll be signed on with the domain credentials with which they’re logged on locally. With a better and less cumbersome process for configuring single sign-on in Windows 2012, users are more likely to be able to use RemoteApp and hosted desktops without having to enter their credentials multiple times. The process of getting connected to a remote desktop session has also received a boost in the ease-of-use department.
#Thin remote desktop client update
The Remote Desktop client update for Windows 7 SP1 computers can be downloaded here. Also new is support for dynamically changing the resolution or orientation so that the applications in a remote desktop session or RemoteApp behave the same way as local applications. The new client supports transparent windows and borders on RemoteApp programs as well as the ability to move and resize RemoteApp windows. The latest version of Remote Desktop Protocol and the client software is v8.1, which can also be installed on Windows 7 computers. Of course, users who prefer to work in the traditional desktop environment can still use the “legacy” RDP client. It remembers your recent connections and makes it easy to reconnect. Microsoft has provided a Metro-style Remote Desktop app in the Windows Store (shown in Figure 1) that’s touch-friendly and simple to use. The Server 2012 RDP experience takes this into account. Many of these are touch-enabled, and users are beginning to warm up to the Windows 8/8.1 modern user interface (formerly known as Metro). Today’s users are moving away from their looming tower workstations and getting work done on smaller devices such as laptops and tablets (and laptop/tablet hybrids such as the Surface Pro). With Server 2012 RDS, Microsoft is getting closer to that goal. Remote Desktop users want their RDP connections to work seamlessly, so that there’s no difference between the performance and functionality in a remote session than when they’re working on a local machine desktop. For added security and control, you can also deploy a Remote Desktop Gateway (RDG) and RemoteFX makes for a much richer user experience than we had with the old TS.
Today’s RDS goes much further, allowing you to deploy applications (rather than the whole desktop) through the RemoteApp feature or deploy a VDI (Virtual Desktop Infrastructure) in which users connect to individual virtual machines.
#Thin remote desktop client Pc
The original TS was pretty simple users could connect to the server from a PC or thin client and work in individual desktop sessions that are sent to the client via Remote Desktop Protocol (RDP). RDS has come a long way, getting a new name and undergoing a transformation in the process. It has grown far more sophisticated over the years, and Microsoft has made a number of improvements and included new and enhanced functionality in the Windows Server 2012 iteration of RDS.
Remote Desktop Services began rather modestly back in the late 1990s, with its roots in a variation of the Windows NT operating system that was called Terminal Server Edition. Remote Desktop Services in Windows Server 2012/2012 R2 and Windows 8/8.1 (Part 3).Remote Desktop Services in Windows Server 2012/2012 R2 and Windows 8/8.1 (Part 2).
#Thin remote desktop client series
If you would like to read the other parts in this article series please go to: