managing server remotely


Recommended Posts

Other than that use either shell or rdp. I am not going to argue here, anyone dealing with servers from day to day will tell you TW is not the right thing to go with. Period.

Let's get rid of the "period" part, because I'm genuinely intrigued. Why is Teamviewer not a recommended suggestion?
Link to comment
Share on other sites

Yeah - would love to hear your well thought out reasoning here..

Sorry but this is not a valid answer.

"use teamviewer (which is meant for client-to-client) then go ahead."

What do you think RDP can be used for.. Your clearly not understanding the concept of client-server relationships and think that because its a "Server" it shouldn't be used because TV is touted as going from my client machine to another "client" machine to support it.. That is just aspect of what it can do.

It is Remote software that provides the ability to access the console/gui interface of another device that not your local machine. Be it a server OS or not.. It also can give you vpn access into this remote network. It can allow you to present your screen as show to multiple users all at once.

The ability for it to be used in unattended mode and service reboot, and even before login to the console makes it a GREAT tool for supporting not only desktop OSes with users on it, but also for support servers remotely.. For example when the server admin has a question on how to do something.

While your RDP -- blanks out the console when accessed, and make it not as easy to use when trying to show a remote admin how to do something, or to have him show you something on the "server" that he has questions on or the server is doing, etc.

But come on we are waiting for why it does not a good "server" administration/support tool.. Love to hear this logic!

Edit: Maybe you should inform teamviewer how their product is not appropriate for "server" support.. Because they seem to be touting all over their website -- stupid teamviewer coders, don't even understand the proper way to use their product ;)

post-14624-0-12322900-1387135896.png

post-14624-0-76626200-1387135966.png

Link to comment
Share on other sites

Yeah - would love to hear your well thought out reasoning here..

Sorry but this is not a valid answer.

"use teamviewer (which is meant for client-to-client) then go ahead."

What do you think RDP can be used for.. Your clearly not understanding the concept of client-server relationships and think that because its a "Server" it shouldn't be used because TV is touted as going from my client machine to another "client" machine to support it.. That is just aspect of what it can do.

It is Remote software that provides the ability to access the console/gui interface of another device that not your local machine. Be it a server OS or not.. It also can give you vpn access into this remote network. It can allow you to present your screen as show to multiple users all at once.

The ability for it to be used in unattended mode and service reboot, and even before login to the console makes it a GREAT tool for supporting not only desktop OSes with users on it, but also for support servers remotely.. For example when the server admin has a question on how to do something.

While your RDP -- blanks out the console when accessed, and make it not as easy to use when trying to show a remote admin how to do something, or to have him show you something on the "server" that he has questions on or the server is doing, etc.

But come on we are waiting for why it does not a good "server" administration/support tool.. Love to hear this logic!

 

You can log into an account with TeamViewer, even if the desktop/server is in the login window.

Link to comment
Share on other sites

^

----

http://www.teamviewer.com/en/help/330-How-does-the-terminal-server-support-work.aspx

How does the terminal server support work?

On server operating systems, TeamViewer operates without any special adaptation. Only if several users should connect simultaneously to the server operating system using Remote Desktop (RDP) from Microsoft, you should activate Enhanced multi-user support in the Options under Advanced. This generates an individual TeamViewer ID for every user who connects to the server using RDP as well as for the physical console. Therefore, parallel and individual work of each session is possible.

The Info Dialog now displays two different IDs:

Server ID:

TeamViewer ID of the console of the server operating system (as if one were physically sitting in front of the server)

User ID:

TeamViewer ID of the user logged into this server using RDP.

---

But clearly its not meant for "server" support ;)

Link to comment
Share on other sites

Let's get rid of the "period" part, because I'm genuinely intrigued. Why is Teamviewer not a recommended suggestion?

 

Seconded. I can't really see why teamviewer is much different than straight up RDP here. At it's base it is just a modified version of either VNC or RDP (older versions were definitely VNC based). The only effective difference I can see is that it requires 3rd party authentication so perhaps that can be seen as an additional attack vector.

Link to comment
Share on other sites

Oh god. If people don't know any better than suggesting you to use teamviewer (which is meant for client-to-client) then go ahead.

Other than that use either shell or rdp. I am not going to argue here, anyone dealing with servers from day to day will tell you TW is not the right thing to go with. Period.

Just as an fyi, quite a few of us deal with multi client support and are not tied to any single site or single domain. Rdp, remote services and vpns to each site either can not be done or are counter productive. The companies that I used to work for needed the techs to work on multiple sites/clients at a time, the tools you mention would be extremely cumbersome to use effectively and securely.

Link to comment
Share on other sites

I don't use RDP for one simple reason: You have to open ports to the outside world if you're off site & there isn't a VPN in place. TeamViewer and LogMeIn you don't. If someone hacks my LMI or TV account, then yes, they get access to my client list, but that only gets them access to the computer list - they would also need passwords for the computers.

 

With RDP, you just need time and the port (which get scanned for constantly - if you have any type of security appliance in place, you'd see this) and you'd get in, eventually. There is of course going to be an 'Administrator' account in nearly every case, so you just need to brute force the password.

Link to comment
Share on other sites

So..my answer with TeamViewer still doesn't work after 3 pages?

Teamviewer is fine as a solution. So far we haven't heard back on why some people think otherwise.
Link to comment
Share on other sites

Teamviewer is fine as a solution. So far we haven't heard back on why some people think otherwise.

 

Food for thought guys. You can listen to your remote PC with TeamViewer like external speakers. You can also present to multiple people at once. You can connect the same desktop remotely 10 times in a row if you wanted to. Better yet, you can disable the screen on that remote PC so that only you can see the desktop/laptop/server on TeamViewer.

 

If you care about keeping TeamViewer, just use it as personal, not commercial. Since this is only about one desktop/server, obviously.

Link to comment
Share on other sites

I am enjoying this thread.  I listed TV in the beginning because it makes things so easy, but thought I would get the "thats great for desktop support but not business blah blah blah - you peon noob.."

 

I have used some desktop/end user software in corporate enviro because it makes things easier for me, but I realize its not the ideal situation -  

 

(Like using Acronis True Image to back up a server before I do something to it) - when I know using the Symantec BackupExec or Veeam would be more appropriate - its just so much easier with the other stuff.

I usually think its because I dont know enough about the enterprise level stuff and Im just being an inexperienced noob - but it hasnt caused an issue thus far...

 

FWIW - I use RDP when connecting to servers in the domain, when Im @ my desk.  Anytime I need to access another machine, or am on my laptop or not @ my desk - teamviewer gets used.  I was the person to convince the IT Mgr to pay the $1500 commercial license.

Link to comment
Share on other sites

I am enjoying this thread.  I listed TV in the beginning because it makes things so easy, but thought I would get the "thats great for desktop support but not business blah blah blah - you peon noob.."

 

I have used some desktop/end user software in corporate enviro because it makes things easier for me, but I realize its not the ideal situation -  

 

(Like using Acronis True Image to back up a server before I do something to it) - when I know using the Symantec BackupExec or Veeam would be more appropriate - its just so much easier with the other stuff.

I usually think its because I dont know enough about the enterprise level stuff and Im just being an inexperienced noob - but it hasnt caused an issue thus far...

 

I agree. To me, just because a software is labled "enterprise" or for "business", doesn't make it great, when the simplest themes can do better large scale.

Link to comment
Share on other sites

  • 2 weeks later...

Hello,

While Teamviewer on desktop is a handy choice it's not for servers. The best way for a windows server is still RDP or try some shell access.

Why is it not for servers?

 

 

TeamViewer is not free for commercial usage.

Well, the OP never states its for commerical or noncommercial usage.

Talking about that, some time ago I installed Teamviewer on my laptop (Windows 8.1). Suddenly for some odd reason it changed to commercial mode. It gaves me a few days to try it and later it stopped working (incomming and outcomming connections). I called up Teamviewer, they asked me a couple of questions (and a couple of IDs a recently connect to) and they changed the license to free in 10 minutes or less. Great support for a company giving out a free software solution.

Link to comment
Share on other sites

For RDP you would also have to setup a VPN to get through the firewall. Because you wouldn't want to open a port. So the good thing about teamviewer is that it handles all of that for you.

 

Although you could do a combination of a paid hamachi account and RDP.

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.