windows server 2012 remote desktop administrator access

Perhaps it would be better to see if PowerShell could make the configuration change you need. I don't normally think much about security, but I must point out that changing the configuration so that a server can receive remote connections is asking for trouble from hackers. Therefore, you either need to make that long walk to the server room, or else stay where you are and connect via RDC. Configure the Windows Server 2012 for Remote Desktop ConnectionĪ classic scenario for setting up RDC is that none of Microsoft's remote tools will allow you to view a particular GUI on the Windows 2012 Server. Terminal services is designed for thin clients to get the full Windows 8 experience for this they utilize the server's memory, CPU and if necessary, disk storage. The two systems have different purposes a remote desktop connection is for having a quick peek at a remote machine. Terminal Services on the other hand, is available only on a Windows Server, and needs to be added as a role before any clients can connect. While RDC is disabled by default for security reasons, you can enable it easily in the Control Panel.

Secondly there is Terminal services installing this role allows many Windows 8 clients to connect to one Server 2012.Ī Remote Desktop Connection (RDC) is available on all Windows clients and servers. There are two distinct systems, firstly, the one-to-one Remote Desktop Connection as discussed on this page. However, it's also possible to create a remote desktop connection between two Windows Server 2012 computers. Normally the local machine, where you launch the RDC, would be a client such as Windows 7. In order to make this connection work, one computer is the local machine, while the other is a distant server. Configure the Windows Server 2012 for Remote Desktop Connection.Logon to that distant machine without leaving your desk. Remote Desktop Connection (RDC) in Server 2012

Windows server 2012 remote desktop administrator access