windows server 2012 remote desktop security

By default, Windows uses a self-signed certificate which does not provide any security at all.

This is configured in the RD RemoteApp Manager. Windows server can be configured to digitally sign RDP files before they are sent to the end-user device. This may allow an intruder to substitute it with a tampered RDP file to redirect the user to a server of his liking. The RDP file is transmitted through the same channel that is used for access RD Web Access. This causes a RDP to be downloaded to the client where it is used to configure the local RDP client to connect to the target system. When using RD Web Access, a user authenticates using the web browser and launches an application by clicking on the corresponding icon. This article describes three measures to increase the security of an remote desktop deployment. Although current target servers provide the client with a certificate to proove their identity, most users are a certificate warning because hardly any server is configured with a certificate that can be successfully verified by the client. Traditionally remote desktop connections to Windows servers have been secured by authentication mechanisms based on username and password. Tags #Certificate #Certificate Authority #Group Policy #RDP #RDSH #RDWA #Server Manager #SSL #TLS #Windows 2008 R2 3 Measures to Make Your Remote Desktop Deployment more Secure

Windows server 2012 remote desktop security