I'm working on a plan for a refresh of our environment at work. Unfortunately, as with many small businesses, our budget is 'as little as possible'.
I'm thinking of moving our PC's over to a Remote Desktop Services environment. Mainly to reduce costs of refreshing PC's but also to reduce IT staff workload - hopefully less time spent fixing and supporting the PCs. We'd also like to use RD gateway and web access for remote access - currently staff have to use a VPN client which they find a bit clunky.
I'm also looking at Hyper-V for our server environment. We've got 6 aging Windows 2003R2 servers doing various things from file, print, mail, SQL and IIS. They aren't really working very hard, most are running at less than 10% CPU and have 1-2GB RAM free (out of 4GB). When the backups aren't running we are looking at a peak total of 40-50MB/s of disk usage, and about 1500 IOPS (60-70% write).
However the main impetus for Hyper-V is to take advantage of Hyper-V Replica for disaster recovery purposes. Currently our DR is pretty lacking, there's only 2 servers there and there's no replication set up and I'm hoping with HyperV Replica we can basically mirror our entire environment.
. A NAS or SAN is out of the budget , So what I was thinking was getting a few grunty servers and loading them up with a dozen or so SAS drives in RAID10, and running HyperV off the local disks. 2 at head office and one at the DR site, and use HyperV replica to mirror to the DR server.
So what I'm thinking at the moment is:
-Anyone done a migration from desktop PC's to RDS? Any pitfalls or heartaches?
-Do you virtualize your RDS session hosts or keep them bare metal?
-What sort of specs would you expect for RDS session hosts running ~85 users? usage is mainly web applications and office.
-Would you run HyperV with local disk storage?
-Any pitfalls with HyperV replica?
I know I could call a system integrator like DiData or something for this but I hate dealing with sales people
