Need advice on virtualizing, Windows Server 2012

[developer]

I need to redesign our company's office network. The problem - almost none server software experience. Need some advice on that.

Current situation:
there are ~10 PC's connected to network, sharing files with each other using simple Windows file sharing and some crappy NAS (does not matter at the time). All PCs are running WIndows 7 Professional x64. PC's job - mostly web surfing and website administration, Microsoft Office works (word, excel etc.). All working individually, except sharing some files with each other.

After the redesign there should be:
office worker comes to PC --> logins to some kind of virtual desktop --> works.

So we're planning to build a server with Windows Server 2012 and use all PCs as virtual workstations.

My questions, for start:
1. Should we use Windows Server Virtual machines for that? I do not have experience in that - all my experience with virtual desktops are that I've used Remote Desktop on Windows Server 2003 some time ago.
2. Could we use Windows 7 in office workers' PCs to connect to server as virtual machine, or some other OS will be needed? The idea should be that Windows would start in login virtual desktop mode.
3. If we use virtual machines, we will need lots of CPU speed and RAM on the server to make them run fast. For example, if we use 10 virtual machines with 2GB ram, we will need 20GB ram on server to make everything run fast, and 2GB ram in every PC. Is it right?

Or did I miss something and virtual machines are irrelevant in the situation?

 

[SoulWind]

you certainly can do all of that, but why would you do it? Virtual desktops would likely have very little benefit unless you are simply trying to cut device cost

 

[dbwillis]

that also ends up at twice the OS licnese cost..one for the workstation, another for the VM, doesnt make sense, esepcially for 10 users

 

[teh_chem]

If there are already physical workstations for all of the workers (already configured with everything the user needs to accomplish their work), why would you bother changing that aspect at all? Unless there is something about the data structure and access restrictions I'm missing, why not just beef up your data server? Get rid of the NAS and make an actual data server. No need to touch virtualization at all.

 

[Nexillus]

If there are already physical workstations for all of the workers (already configured with everything the user needs to accomplish their work), why would you bother changing that aspect at all? Unless there is something about the data structure and access restrictions I'm missing, why not just beef up your data server? Get rid of the NAS and make an actual data server. No need to touch virtualization at all.

Second this. +1

 

[rtangwai]

You are actually describing an Active Directory Domain and roaming profiles, not virtual machines under Hyper-V. You want any user to walk to any workstation, login in with their username/password, and see their particular desktop and files, correct? If so, you don't need Hyper-V and VMs. If you need tight control of applications due to licensing issues, security, etc. then you are really looking for a Citrix XenDesktop solution which are also VMs but do act quite a bit differently.

 

[leeleatherwood]

Based on your needs that you posted I agree with what others have said.
Sounds like you just need a simple domain with roaming profiles, and a file/print server. One machine can do that without virtualizing. You can even throw WSUS on that same machine.

Anyways, I will answer your questions if you are still dead set on Virtual Desktops:
1) Yes, use Hyper-V 2012. Each client will connect to their virtual desktop via RDP. Hyper-V server 2012 is completely free but since you should also run a domain controller as well you will need to purchase Server 2012 anyways.
2) Sure, although you may want to look at the Windows 7 Thin PC OS.
3) You will need lots of ram in the server, I suggest a minimum of 32GB because you will want to leave room for either more PC's in the future or even maybe some virtual servers. The PC's themselves will work fine with only 1GB ram, the only thing they will be doing is loading RDP. You can disable/uninstall all unneeded startup services and programs from the PC's. Windows 7 Thin PC OS already disables alot of these unneeded services as well as has additional features to run on minimal RAM. (Ive run them as low as 256mb with no issues, even though the system requirements state 1GB)

With your questions answered you should still setup a domain controller as well as a fileserver. In your scenario with so little users I would suggest running everything on one server. This brings up another issue, with all of your desktops and servers now running on 1 box, what happens when/if that box crashes? You will need at least 2 servers to provide hi-availability.

Hope this helps.