I'm setting up a Remote Desktop Services (RDS) environment and would love some feedback on my configuration. Here's the breakdown:
I've got two Hyper-V servers linked with a 10G connection. On HV1, I have the Domain Controller, Connection Broker, File Server, and a Database Server that unfortunately doesn't support high availability. HV2 has a Backup Domain Controller, Backup Connection Broker, File Server, and a second terminal server.
The replication is as follows: the database on HV1 replicates to HV2, and TS1 on HV1 replicates to HV2, while TS2 on HV2 replicates back to HV1. Users will connect through the Connection Broker, which will redirect them to one of the terminal servers. I've implemented folder redirection on both servers to a DFSN+DFSR-based share, ensuring data is replicated and always accessible.
I wanted to confirm that this setup will maintain minimal downtime and that not replicating the domain controllers is okay since they'll share the same data through DFSR.
Also, I have a question about Outlook configuration. Right now, users will need to set up their Outlook profiles from scratch on both servers, which is a hassle. I considered using FSLogix, but it doesn't seem ideal due to the lack of redundancy in a local setup. I've heard about creating OST files on the DFS share with roaming profiles, but I've never attempted that before. Could anyone suggest a better approach? Thanks for any insights!
3 Answers
You might want to think about a failover cluster with shared disks through a hyperconverged SAN. That would protect your OS and hardware—so if one host fails, your VMs would stay up on the other. Plus, with FSLogix stored on a network drive, your profiles could sync across both RDS servers.
I’m not sure why you'd replicate the terminal servers considering they should be identical. A single farm setup might simplify things. Have you thought about implementing FSLogix? It’s great for profile management, and it’d streamline your users' experiences. Plus, I just want to clarify, but you can't have OST files on a network share, so that's something to reconsider in your design.
Ditching FSLogix would be a huge mistake. I've been in RDS since Server 2003, and FSLogix is a game changer for profile management. It’s significantly more efficient than traditional methods, so definitely look into it.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures