Accepted Solutions
Thank you spravtek 
I guess what you are asking me is everything that I need to know,
I havent worked much with virtualization before (...and by not much i mean nothing at all...), what i really need help with is, what would be the best practices to use to setup this enviroment efficiently like i know i need one one VM for the linux server, but like how many Microsoft servers are recommended, can one VM DC be able to handle all the services needed, or should i setup more than one. and how much much memory / space should i allocate to these servers etc,
and like you said what will be the most efficient way to setup the vswitches for this type of network. This site will have at most 80 users at any time, and i will be using Windows Server 2012 as the domain controller
I know what all that Im asking is a very broad and vague question, but any advise would be really helpful right now . . .
much appreciated spravtek
In an ideal environment you would have at least 1 physical DC as a backup, especially handy when your entire virtual environment went down for some reason, as I said, that would be ideal, but not necessary.
For your environment 1 DC would be enough, you could have two of course, devide your DNS and DHCP services between the two, then when 1 of your 2 DC's would tank you have backup for it, of course, if your entire virtual environment would go down, it doesn't do much good.
Since you only have the 1 ESXi host there isn't much room for redundancy, I suggest to invest in a good backup system for your VM's.
The virtual network should be set up so that you have your management and vmotion on a separate vswitch with its own physical nics connected to it, then another vswitch for the LAN and if needed (maybe for mail) another switch, or portgroup if you use VLANs, for DMZ. (same goes if you're using VLANs on your network).
As for your VM's, always start with a low setting for CPU and memory, for example always make your VM's with 1vCPU where possible, then later check the performance and add another vCPU where needed (in modern Windows OS's this is hot plugable without any issues) ...
Same goes for memory basically, I have customers running Windows 2008R2 DC's with 2GB memory and they are running fine, if you see your DC struggling just add some more memory and or cpu.
As for disk space, that is another ballpark figure, usually, when available, people will create a template using thin provisioned disks and make full VM's from them using eager zeroed ... For Windows servers a minimum of 30GB is recommended (though with all updates lately 40 to 50Gb is sometimes used as well), disks in Windows usually can be extended quite easy, so you don't need to worry about that too much.
Mail servers are usually quite memory/cpu hungry, so try to find some information as what is the minimum requirements for your setup, most of the time if you follow the requirements the software maker gives you, you'll be ok.
I hope this helps you out a little, as you said, it's quite broad ...
If you're looking to pick up some more knowledge about ESX and/or design, check out this book: http://www.amazon.com/VMware-vSphere-Design-Forbes-Guthrie/dp/0470922028
If you have any more questions, I'll try to answer them as good as possible 
Good luck
Thanks spravtek, this is really gonna help me, i will definitely keep you informed about the progress besides im sure im gonna be asking you more questions soon!! lol
thanks once again spravtek
ok i will theck these out now
thanks once again spravtek and i will keep you informed of progress