Hamachi VPN as service – why?

Ya know, I still see a lot of folks talking about Hamachi. And that’s cool — it is truly an incredible piece of software. I use it just about daily now.

Pre beta 1.0, the trick to using Windows Remote Desktop over Hamachi involved running Hamachi as a service. Well fine, but I wasn’t real gung ho about that. BUT. Beta 1.0 fixed that. Since I upgraded all my stuff to the current beta, RDC works fine and I don’t have to do the service thing. Yet now I’m reading all these posts (and Hamachi patches even!) about running the Beta as a service for RDC. Why?!? I suppose I’m being goofy here, but I just don’t see why I’d want to run this as a service if I don’t have to? How easy is it to work with when running as a service? Can I easily add other networks? Boy, it just seems like a pain.

Or is RDC still not working for some folks with the beta?

[added later]

I’m probably missing some key fact here. I suppose people just want to run it as a service… because? Because they can? I see advantages there if you expect a machine to reboot unattended I suppose. The more I think about it, I suppose that’s just about gotta be it.

[added much later]

Honest, I get it!

Possibly Related posts:

  1. Nesting Remote Desktop Connections
  2. Hamachi2 and Linux and Haguichi
  3. Broke (then fixed) VMware Player Networking
  4. Belt and Suspenders With ChrisControl

About Chris

I consider myself a jack-of-all-trades. Which means I know a little about a lot... or think I do, at any rate. Check my "About Me" page for more info.
Tagged , . Bookmark the permalink.