redundant server hardware setup

I have a customer whom has 30 workstations all win 7 pro 64 they are on a 2003 domain. I want to replace the servers. I need recommendations on a setup. I need the following dhcp, dns,  file and print roles. I don't want a San cause that would be over kill. I need all the roles to be redundant incase a server goes down. As for space they don't have a lot about 300 gb of data. The server will also house a quick books db. I would like some recommendations.

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

RantCanSr. Systems AdministratorCommented:
Two servers;
Windows server 2012 (each license of windows server 2012 standard gives you two VMs, so this will give you four VMs to run.

Set up a hyper-v failover cluster;

Create a role with two domain controllers, both dns with a split scope dhcp 60/40;

Create a file server and a print server.

Here is an article on Hyper-v and failover clustering.
Joseph OLoughlinIT Support SpecialistCommented:
I agree with RantCan
AD relies on DNS
Get DNS working on both servers first.  Test DDNS and don't be tempted to go AD integrated
Get AD working and have plans for moving FSMO roles for if and when failures happen.
The cluster nodes need external DNS to register resources, e.g. the cluster name, than can fall over from one node to the other.

Your cluster will look something like

The external shared storage needs a dedicated lun for the quorum, and separate luns for the accounts database and resources to be clustered.
> I don't want a San cause that would be over kill.

I would agree which means you can't have a Hyper-V cluster. Some people may have missed that part of your question.

All the Windows server roles you mention can be made highly available without clustering using two Windows servers except for print server and for 30 users they can work around that.

Set up one Windows server with all the FSMO roles on it, both servers can be DNS servers, both can be Global Catalog since it's a single domain, both can be DHCP servers (create two separate scopes, 50 IP addresses in each that do not overlap), both can be fileservers, you just setup DFS replication between them.

Quickbooks doesn't have a database engine, just files so that may run on DFS, however note that there were problems with it on DFS, see for example. That problem is probably solved in later versions of QB.

So that just leaves printserver, unless they have a huge pile of printers just make both servers print servers and if they can't print to server1printer1 then they can send their prints to server2printer1 instead. For only 30 users that shouldn't be too hard, they will have found both print queues anyway when they first connected their PCs.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Server Hardware

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.