Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I mean, I understand that it's kind of a risk to directly log on.

But why should I just administrate it via Remote instead of directly manipulating it? :S

share|improve this question

closed as off-topic by HopelessN00b Mar 9 '15 at 14:10

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions on Server Fault must be about managing information technology systems in a business environment. Home and end-user computing questions may be asked on Super User, and questions about development, testing and development tools may be asked on Stack Overflow." – HopelessN00b
If this question can be reworded to fit the rules in the help center, please edit the question.

Well, unless the machine is under your desk, having to get up and walk to the server room to sit down in front of the console when you don't have to seems inefficient. I don't know if I'd go so far as to say it's stupid, at least comparatively speaking.

share|improve this answer
+1 for the early morning chuckle – Izzy Nov 3 '09 at 14:34
+1 for the laziness ! And think about when you will have 50-60 servers =) – Antoine Benkemoun Nov 4 '09 at 9:52

Some things are better to do when you're right in front of the server, some are better from a remote command line and some are better from a remote GUI - it makes sense to have all of these tools in your arsenal, so think 'better for using RDP when appropriate' rather than 'an idiot for never using it' ;)

share|improve this answer

Remote Desktop has saved me a lot of trips back to work when there were troubles. Just make sure you close down the ports you don't need. Use a strong password, don't brag about the fact that you can administer the server from home. The less people know, the better.

And also don't forget that physical access is the first line of security. Make sure nobody can access the server and if you really want to lock it down, (only possible with a static IP) add a rule in the firewall, so that only your internet connection from home is allowed to connect to the RDP port over the internet.

But don't forget: if they can access the server with their hands, feet, or anything else :p then it doesn't matter what you do for security!

share|improve this answer

I don't see any reason other than convenience for using remote desktop over the console. There may be a few security related reasons to avoid using remote desktop, however.

share|improve this answer

I disagree that there is a security risk of directly logging in, there's nothing more secure than physically logging into the server. Also there is no more implicit risk of having remote desktop enabled for your server assuming you have correct account lock out policies and proper security for an internet enabled server in general.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.