Contents tagged with SID
-
Hyper-v DOs and DON'Ts - Item 1 - Re-Sid your machine.
We've started utilizing hyper-v for our product system testing. Beforehand the system test environment was composed mostly of around 16 physical machines playing different roles in different topologies. The machines applicative layer was mostly managed by loading up pre built specific role images. Things like different operating systems, different applicative clients (IE6/7/8 Office/2k3/2k7, etc) . Moreover, the network topology was mostly managed by a VLan switch which was good in the flexibility point of view of moving machines between different networks without plugging out and plugging in different network cables. But once more complicated scenarios were introduced and more people got involved in the system testing effort , it was pretty obvious that the current test lab wouldn’t be able to scale up to the system testing requirements. So after a basic pros and cons analysis and discussion we have decided that we are going to introduce and rely on hyper-v as our virtualization engine but keep the old physical lab as a Plan-B if we would have to prove issues or sightings on a physical environment as well. Around one month down the road, we're very satisfied by the agility the virtual environments is providing us, changing network topologies on the fly , having a library of role specific images and a lot of other time saving advantages that I'll probably share in the future. Having said that , we've collected several good to know DOs and DON'Ts for working with a virtual environment in general and Hyper-V specific.