Im after some advice on art-of-the-possibles with Hyper-V / RDS / VDI on an upcoming scenario we have. Im a solution architect but by no means a Windows guy so looking for some advice and best practice
We have a requirement where 300 staff will be moving to a new organisation and be on new desktop kit on a new LAN. However those staff still require access to their apps/desktops on their previous LAN for a transition period. The site they are in will have access to both networks
Im therefore thinking the simplest way to do this would be to use RDS sessions on a Hyper-V host. I thought about Remote App but am thinking as the existing apps are many and diverse this would be complex and isnt a realistic option and what may be best is to P2V a few of their existing desktops, create a VM template and use Hyper-V / RDS to broker connections and either go a VDI approach (pools of desktop VM's etc) or use shared desktops (old style terminal services). So i have a few questions
- Can you use P2V to create a VM template or would be better to start with a clean image and reinstall all the apps we need. What do we need to do this?
- Is there any issue in us having multiple NICs on the host (connected to the old and new LANS) and configuring Hyper-V networking to use these in desktop VM's so as to allow Remote Desktop Clients to access the vm's from the new physical desktops on the new kit?
- Roughly, how many concurrent desktops could we expect to support on a mid level physical host and do we have large storage requirements for the VDI approach?
- As opposed to VDI and pooled desktops are shared desktops better (the old style terminal server) and whats the way to do this in Hyper-V / RDS? Is it an option when you create the role?
Many thanks for the advice