I have a new client that has purchased 10 thin clients.
The thin-clients are each operating as users of a single Hyper-V virtual machine running Server2012. The VM is running on its own server, also running Server 2012.
Is this a system that has to be scrapped and started from the beginning?
EDIT: Months later, here's a clearer picture of what was wrong:
There was one server doing everything (Domain Controller, SQL Server, Web Server, Hyper-V Server, Application Server)
A problem in one part would cascade throughout the server causing untraceable errors.
We scrapped it and started from scratch.
Purchased two lightweight Dell R230s - one as primary DC and one as SQL/Web server.
We then reformatted the old server and installed only Hyper-V. We ended up with a single VM and RDS sessions from the thin-clients versus the full VDI.
We also created a VM domain controller for failover protection if the primary suddenly died (which had no backups originally).
So far, so good. Everything is running smoothly. Errors are easy to track. Performance has improved.
Take stock of the big picture before jumping into implementing Hyper-V or virtualization simply because it's cool. The benefits are ABSOLUTELY worth it, but you have to have the right infrastructure to support it. It's not something you just run for fun on an old server you have lying around or as part of a multi-role server.