Vocalpoint

I hear you loud and clear on the single point of failure. But - I didn't really do not want to have to build out another "server" either. I do have a bunch of parts laying around here but that means more rackspace, noise etc etc. But logically a working network is wayyyyy more important. Especially since I am just now dipping my toe into a domain structure. I should probably consider your layout and leave the file server standalone and place these other two elements in a separate space where I can ensure everything can be accessed if an issue arises. So - ESXI vs Hyper-V? Where should I go? Pros? Cons? VP

Thanks for the update. Your ideas are exactly where I am at. But I am confused (for the File Server portion) on whether to go hardware RAID (LSI 2308 onboard the Supermicro) - OR go with Storage Spaces (native to WS2012R2). Both have pros and cons. As far as the OS goes - that will be on a single SSD and will be imaged daily so I am not worried about running that in RAID1. And the actual file server data stash represents the "2" in our 3-2-1 backup strategy. Every file that is stored on the server - has it's origin on a workstation. Then all the data on the server is sent to Crashplan - so we have three copies of everything at all times. With respect the the VMs - that's exactly what I needed to hear. File server on the physical install of Windows Server 2012R2 - and then do I just add the Hyper-V role to the physical file server and set up the DC and WSUS servers as separate VMs? Appreciate the info! VP

We have a very small network here with just a half dozen Windows 7 workstations and I recently took delivery of the following parts to build what I planned to be an "old school" new master file server for the home network: SUPERMICRO MBD-X10SL7-F-O Micro ATX Server Motherboard LGA 1150 Intel C222 DDR3 1600 Intel Xeon E3-1220V3 Haswell 3.1GHz LGA 1150 80W Server Processor Crucial 16GB (2 x 8GB) 240-Pin DDR3 SDRAM ECC Unbuffered DDR3 1600 (PC3 12800) Server Memory 4x4TB Seagate NAS ST4000VN000 But then I started thinking about how much admin I am doing on the network so this may be the time to move away from the "WORKGROUP" hassles and finally get an Active Directory layout going. Given the physical parts above - and assuming a clean install of some form of Windows Server (Standard 2012R2, Hyper-V Server 2012R2?) - what would be the most efficient way to make the following happen: 1. New Domain Controller (with AD) 2. WSUS Services (Windows updates are getting annoying) 3. New File Server to replace old Windows 2003 box that is definitely on the way out. Ideally - "efficient" to me means using the new hardware without needing to buy more stuff right away AND hopefully making admin/maintenance fairly easy. I am guessing I could install ALL of the above using Windows Server 2012R2 right on new physical box and treat it like normal old school server but I have been reading that installing things like a DC and WSUS might work out better being on separate server instances - meaning VMs would clearly be needed so I am open to using Hyper-V. Or maybe even installing Hyper-V Server and virtualizing ALL of the above? Just trying to establish some sort of "order" or plan prior to installing anything so I do not waste a ton of time going down one track and find out I should have been doing something better. Appreciate any "intel" from the field. This is all new to me so be gentle VP