>extremely poor environment for the latest development tools - I would
>strongly suggest that Virtual PC (or any other virtualisation solution) will
>not meet your requirements...
>"Farouk" <(email address - cut out)> wrote in message
>news:(email address - cut out)...
>
>> I want to propose the virtualization of our developers workstations (80
>> users with Visual Studio).
>
>I'm primarily a developer, and I use Virtual PC all the time - but not to
>develop on! Virtual PC is superb at what it does well but, like all software
>virtualisation products, it has limitations. The main limitation is the set
>of emulated hardware - this cannot be changed and is, generally, very
>low-spec. E.g. the emulated graphics card in every VPC VM is a S3 Trio with
>4MB RAM, which can be increased to 16MB after installing the VM Additions
>and manually modifying the VM's vmc file. This means that technologies like
>Direct3D etc simply aren't possible in a VM, no matter what physical
>graphics card the host has...
>
>Secondly, it's important to remember that as soon as you launch a virtual
>machine you suddenly have two computers competing for the same resources -
>the physical host machine and the virtual guest machine. E.g. if the host
>machine has 2GB RAM and you create a virtual machine with software which
>itself requires 2GB RAM to run with anything like acceptable performance
>(e.g. Visual Studio.NET 2008 on Vista), then you're not going to get very
>far...
>
>Thirdly, apart from a handful of exceptions, virtual machines are considered
>the same as physical machines when it comes to licensing. E.g. if you
>currently have 80 workstations running Windows, and build 80 virtual
>machines all running Windows, that's 160 Windows licences... Same with
>Office, Visual Studio.NET, etc...
>
>Virtual PC provides a superb environment for software testing but, IMO, an
>extremely poor environment for the latest development tools - I would
>strongly suggest that Virtual PC (or any other virtualisation solution) will
>not meet your requirements...

> "Farouk" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>
>> I want to propose the virtualization of our developers workstations (80
>> users with Visual Studio).
>
> I'm primarily a developer, and I use Virtual PC all the time - but not
> to develop on! Virtual PC is superb at what it does well but, like all
> software virtualisation products, it has limitations. The main
> limitation is the set of emulated hardware - this cannot be changed and
> is, generally, very low-spec. E.g. the emulated graphics card in every
> VPC VM is a S3 Trio with 4MB RAM, which can be increased to 16MB after
> installing the VM Additions and manually modifying the VM's vmc file.
> This means that technologies like Direct3D etc simply aren't possible in
> a VM, no matter what physical graphics card the host has...
>
> Secondly, it's important to remember that as soon as you launch a
> virtual machine you suddenly have two computers competing for the same
> resources - the physical host machine and the virtual guest machine.
> E.g. if the host machine has 2GB RAM and you create a virtual machine
> with software which itself requires 2GB RAM to run with anything like
> acceptable performance (e.g. Visual Studio.NET 2008 on Vista), then
> you're not going to get very far...
>
> Thirdly, apart from a handful of exceptions, virtual machines are
> considered the same as physical machines when it comes to licensing.
> E.g. if you currently have 80 workstations running Windows, and build 80
> virtual machines all running Windows, that's 160 Windows licences...
> Same with Office, Visual Studio.NET, etc...

> I want to propose the virtualization of our developers workstations (80
> users with Visual Studio).

>> Virtual PC provides a superb environment for software testing but, IMO,
>> an
>> extremely poor environment for the latest development tools - I would
>> strongly suggest that Virtual PC (or any other virtualisation solution)
>> will
>> not meet your requirements...
>
> I do a LOT of development in VPC actually, it's great if you want
> different environments or you want to share an environment between
> more than one workstation...

> Visual Studio licenses are per developer, not per machine.

> Virtual Server is the way to go. Check FAQ at Microsoft for info.
> http://www.microsoft.com/windowsserversystem/virtualserver/evaluation/virtualizationfaq.mspx

>
> jorgensen;1009633 Wrote:
>> Virtual Server is the way to go. Check FAQ at Microsoft for info.
>> http://www.microsoft.com/windowsserversystem/virtualserver/evaluation/virtualizationfaq.mspx
> I've downloaded a copy of this MS Virtual server. I am sorry to say but
> I dont know whats next to do after installation :(
>
>
> --
> kenjiemichael
>
> '*Easy Installer*' (http://joomlatag.com/) | '*Joomla Components*'
> (http://joomlatag.com/) | '*Joomla Installer*' (http://joomlatag.com/) |
> '*Joomlatag*' (http://joomlatag.com/) | '*My first website*'
> (http://websitefirst.blogspot.com/)