One of the reasons is obvious, your organizations user base has grown to an amount that simply does not “fit” (in terms of technical resources) on one RD Session Host server. There are several reasons for needing an RDS farm. So why do we need a RDS farm? I highly doubt this but in case you are not convinced, read this paragraph: In this article we use the term farm when we describe multiple servers running the RD Session Host role that serve the same purpose, so either publish the same desktop or publish the same applications and share the same initial connection (later on in this article we’ll see exactly what this means). There are of course also 3rd party tools available that work on top of and extend RDS farms, but in this article our main focus will be out-of-the-box Microsoft solutions. Why would you need a RDS Farm? What are the options? What are the scenarios? These are some of the questions we will answer in this article. A Remote Desktop Server farm consists of multiple Remote Desktop Session Host Servers. In this article, we will be taking a closer look at Remote Desktop Farms in Windows Server 2008 R2. If you would like to read the next part in this article series please to to Remote Desktop Server farms explained (Part 2).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |