Remote Desktop Windows Server 2012
Logon to that distant machine without leaving your desk.
In order to make this connection work, one computer is the local machine, while the other is a distant server. Normally the local machine, where you launch the RDC, would be a client such as Windows 7. However, it's also possible to create a remote desktop connection between two Windows Server 2012 computers.
There are two distinct systems, firstly, the one-to-one Remote Desktop Connection as discussed on this page. Secondly there is Terminal services; installing this role allows many Windows 8 clients to connect to one Server 2012.
A Remote Desktop Connection (RDC) is available on all Windows clients and servers. While RDC is disabled by default for security reasons, you can enable it easily in the Control Panel.
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.
The two systems have different purposes; a remote desktop connection is for having a quick peek at a remote machine. 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.
A 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. Therefore, you either need to make that long walk to the server room, or else stay where you are and connect via RDC.
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. Perhaps it would be better to see if PowerShell could make the configuration change you need.
Ok, you clearly want to get the remote connection working, so this is how to prepare the Windows Server 2012.
SolarWinds' Network Performance Monitor will help you discover what's happening on your network. This utility will also guide you through troubleshooting; the dashboard will indicate whether the root cause is a broken link, faulty equipment or resource overload.
Perhaps the NPM's best feature is the way it suggests solutions to network problems. Its second best feature is the ability to monitor the health of individual VMware virtual machines. If you are interested in troubleshooting, and creating network maps, then I recommend that you give this Network Performance Monitor a try.
Troubleshooting Techniques for Remote Desktop Connection
Hostname Problems - Remote Desktop cannot find computer...
If you have selected Network Level Authentication then you must type the full computer name at the client. For example, myserver.local and not plain myserver. If in doubt try: ping myserver. You can see the full computer name in the Control Panel, System and Security, System.
Once you get the connection working turn the firewalls back on and just make an exception for the Remote Desktop Connection.
Entering Your Credentials
Remote Server Administration Tools (RSAT)
A quick word about the Remote Assistance option you see just above the Remote Desktop settings; this allows a techie to access your computer so that they can troubleshoot the server's problem. Unlike Remote Desktop, Remote Assistance allows both of you can see the same computer screen; there is even an option for sharing the mouse pointer.
RDC Registry Setting - fDenyTSConnections
Providing you can get the remote registry service started on the target computer, you can edit fDenyTSConnections with Regedit and turn on 'Allow remote connections to this computer' without using the Control Panel.
The scenario is you plain forgot to enable the distant server to accept a Remote Desktop Connection. My method requires you edit the registry setting fDenyTSConnections from 1 to zero; what this achieves is to reverse 'Don't allow connections to this computer' on the target machine.
Step 1 Start the RemoteRegistry Service
Use PowerShell to start the registry service on the remote machine.
# PowerShell cmdlet to start the Remote Registry Service
Step 2: Remote Registry Edit
Our mission is to change the value of fDenyTSConnections from 1 to 0. Launch Regedit and navigate along this path: File Menu, Connect Network Registry.
Naturally, you need the hostname of the computer. Next, let us connect to the correct registry hive on the target machine (see screenshot):
Now find the Reg_DWord called fDenyTSConnections and set the value = 0 (zero)
Step 3: Restart the Server with PowerShell
Unfortunately, you have to reboot the target machine before the change from 1 to 0 takes effect. To achieve this I use the following PowerShell command:
Restart-Computer -computer DistantServer-force
Encouraging computers to sleep when they're not in use is a great idea - until you are away from your desk and need a file on that remote sleeping machine!
WOL also has business uses for example, rousing machines so that they can have update patches applied. My real reason for recommending you download this free tool is because it's so much fun sending those 'Magic Packets'. Give WOL a try - it's free.
Highlights of Windows 2012 Remote Desktop
RDC focuses on the RemoteFX technology. This is what it delivers:
Problems Once You Make a Remote Desktop Connection
Full Screen Mode
Summary of Remote Desktop Connection for Windows Server 2012
Remote Desktop Connection (RDC) is available on Windows Server 2012, you just need to enable the setting in the Control Panel. Be aware that remote desktop connection is attractive to hackers, thus this only really suitable for a test network, or a private network not connected to the internet.
If you like this page then please share it with your friends
Microsoft Windows Server 2012 Topics