Remote Desktop publishing Hyper-V remote Lab

hi,

we have offer remote access virtual lab environment running on hyper-v. each user has got own hyper-v machine hosting set of virtual machines, has access remotely. makes more difficult same lab environment running on each hyper-v host. reason virtual machines configured use internal-only hyper-v network.

somewhere have heard connecting hyper-v host machine , opening hyper-v terminals locally on machine consume huge amounts of bandwidth. true? know better way configure environment?

thank you,

dagmar

 

 

hi dagmar,

i think selected pragmatic setup. have 2 demo environments configured in same way yours: rdp hyper-v console presenter machine , start vms use internal network. make sure hyper-v host os configured have access internal network. allows copy data , from the vms easily.

btw: during intall phase give vms access physical network card of hyper-v server, called external network. allows me install necessary patches , activate vms. disable external network in each vm's hyper-v properties, isolates them internet. makes them lot less vulnerable , preserves settings. in addition, backend servers, such dc, running in such isolated mode cannot influence other pcs in lan.

the downside the performance of double-hop rdp (user client pc connected hyper-v host , hyper-v host connected each vm) not direct connection user client pc vm, in particular if windows 7 windows 7. should not problem demo lab setup.

in summary: yes, setup consumes more bandwidth direct rdp connection vms. for demo lab environment, however, your solution best practice.

benny

Windows Server  >  Remote Desktop Services (Terminal Services)