The idea is that my admins can remote desktop to their own boxes without stepping on anyone else's toes.
I caught a little snag when it comes to the new systems. Long story short is this - I bought a subnet of IPs for the virtual servers but cannot seem to get them to work correctly.
Question
Anyone here familiar with setting up virtual machines that have their own IP addresses in a 2008 R2 box? If so, would you mind helping me out?
I'm going to ask the same question on SA if I don't get a reply here then farm the help out to a contractor. Ghost of Forums Past fucked around with this message on 04-16-2012 at 07:06 AM.
I haven't touched the Microsoft VM stuff. I've dealt with VMWare GSX, ESX and ESXi products for similar tasks, but it seems like the virtualization you're doing is not "Machine" VM but "App Instancing" VM..
quote:
Random Insanity Generator had this to say about Cuba:
*points to VMWare ESXi*I haven't touched the Microsoft VM stuff. I've dealt with VMWare GSX, ESX and ESXi products for similar tasks, but it seems like the virtualization you're doing is not "Machine" VM but "App Instancing" VM..
I just want a bunch of different operating systems running independently on one box via a hypervisor. If you could help with that, that'd be amazing. I have no problem frying the whole box to linux or whatever to make that happen.
Can't say how easy or hard it is with Hyper-V, but I can't imagine it's anything other than trivial.
quote:
Drysart was naked while typing this:
It's really straightforward with the more consumer-level VMware products to do a bridged networking setup, or at least it was a few years ago when I messed with VMware last. You basically choose bridged instead of NAT when you set up the VM, and point it to which physical host adapter you want to share and it just works.Can't say how easy or hard it is with Hyper-V, but I can't imagine it's anything other than trivial.
This would be my assumption. And I know it's still that easy with VMWare as I've got an ESXi box here at home doing just that. And it wasn't just the 'consumer level', it was that simple across all their versions... Just configure the "hardware" when defining the VM as NAT (Local) or Bridged (World).
Had a friend that was in the infrastructure group where I'm working that said that Microsoft's setup was shockingly similar to VMWare's, just slightly different names and such.
